Why Every Law Needs a Plain-Language Explanation Page
Learn why Perfect Laws separates the binding rule from a one-page explanation with mechanisms, examples, objective checks and an honest limit.
A law and an explanation do different jobs. The law creates duties, powers, records, consequences and review rights. The explanation helps a reader understand why the mechanism exists, how it is expected to operate, what ordinary examples produce and where the proposal stops. Mixing those jobs can make the binding text vague and the explanation misleadingly authoritative.
Perfect Laws therefore gives every published packet two distinct parts. Page A is the operative law and may use one or, when necessary, two A4 pages. Page B is exactly one A4 page called “What It Solves and How It Works.” Page B follows the law immediately but has no legal force.
The operative page must stand on its own
A person should not lose a right or face a consequence because of a persuasive sentence in a brochure. The binding page must itself state who is covered, the observable trigger, the required action, the deadline, the record, the consequence and the review route. Essential definitions belong there too.
This discipline prevents the explanation from quietly repairing an incomplete law. If an example produces the intended result only because the reader imports words from Page B, Page A needs revision. The explanation can clarify the design, but it cannot supply a missing legal duty.
The explanation begins with the real problem
Page B starts by stating the pain the proposal is meant to address. It then shows a problem → mechanism → expected effect chain. That sequence lets a reader challenge the causal reasoning instead of accepting a label such as “reform,” “modernisation” or “accountability.”
Expected effect is deliberately not written as guaranteed effect. A legal mechanism changes incentives and procedures, but people adapt and institutions fail. The explanation should show what the rule is trying to change without inventing evidence that the result has already occurred.
Implementation steps expose hidden machinery
A one-sentence law may rely on identity records, software, auditors, trained staff, courts, notices, budgets and correction processes. Page B lists the practical sequence so readers can see whether the short rule depends on an unrealistic invisible system.
This does not turn the companion into a technical manual. It identifies the essential actors and order of work. Longer research, financial models and operating instructions can remain separate, but the public should not have to guess how the central mechanism reaches the promised result.
Examples test the words before real people must obey them
Concrete examples reveal whether two informed readers obtain the same answer. A transfer-tax example can show who pays, what the receiver gets and when the tax is excluded. A school-placement example can show the difference between a young child near home and an older child assigned elsewhere in the state.
Examples also reveal missing boundaries. If the draft cannot answer a same-owner transfer, an unsafe school, a genuine old banknote or a mistaken identity record, the uncertainty should be repaired before publication rather than left to discretionary interpretation later.
Objective checks turn a general idea into an auditable one
Page B lists questions that can be answered with evidence: did final settlement occur, did ownership change, was the notice period met, can an auditor repeat the draw, was free hostel support provided, or did a written court order authorise the exception? These checks help readers, implementers and reviewers focus on the same facts.
An objective check is not a substitute for a remedy. Page A still needs the consequence and review route. The checklist simply makes the mechanism easier to inspect and reduces the room for a public body to declare success without showing the required record.
The important limit is a trust requirement
Every proposal has a boundary. A transfer tax cannot solve every form of corruption. A low-denomination note cannot create perfect traceability. Shared dependence on public schools cannot guarantee excellent teaching. Page B must name the most important limitation directly.
This is not an apology placed at the end of the page. It tells readers what other laws, institutions or evidence would still be needed and prevents the proposal from being marketed as a cure-all. Honest limits make comparison and later review more useful.
One page forces priority without forcing tiny text
The explanation page is limited to one A4 page, but body text must remain readable, normally 10–11 points and never below 9.5 points, with at least 14 mm margins. If everything does not fit, the answer is to remove repetition and choose the most useful examples, not compress the page until it becomes tiring.
That constraint keeps the companion focused on public understanding. It should answer what the law solves, how it works, how to check it and where it stops. Research papers can be long. The page beside the law should remain something an ordinary reader can finish and hold in mind.
Common questions
- Does the explanation page have legal force?
- No. It is clearly labelled as explanation. Every binding duty, power, consequence and remedy must appear in the operative law or a named supporting law.
- Why not put examples inside the law?
- Some examples may be legally necessary, but ordinary explanatory examples can make the binding page longer or accidentally narrow the rule. Keeping them on Page B preserves the distinction.
- Can Page A use two pages?
- Yes, when clarity or completeness genuinely requires it. Page B remains exactly one page and follows the operative pages immediately.
- What belongs on Page B?
- The problem, mechanism, expected effect, practical implementation, useful examples, objective checks and the most important limit.
Read the sources
Go from the guide to the complete project record.
See the law and explanation together