How to Write a Law in Plain English: 9 Practical Steps
A practical nine-step method for drafting clear laws with observable triggers, exact duties, fair review, abuse testing and honest explanations.
Plain-English law is not law with the difficult parts removed. A clear law still needs to identify who is covered, what event triggers the rule, what must happen, when it must happen, what record proves it, what follows from failure and who can correct a wrong decision. The challenge is to make those parts exact without forcing an ordinary reader through needless legal costume.
Perfect Laws uses a nine-step drafting method built around one main problem per law and a short operative packet. It is a project method, not a universal professional drafting standard. Its strongest ideas also match public drafting guidance that puts accuracy, ordinary language, logical order and the reader’s needs first.
1. Define the failure before writing the rule
Start with an observable problem, not a preferred solution. State who is harmed, what happens in the real world, how often or at what scale it matters, and which incentive or system weakness keeps producing it. “Government should be better” is not a defined failure. “An applicant receives no decision or reason within a fixed period” is closer to something a law can solve.
This step prevents a familiar drafting mistake: building an elaborate institution before proving what it needs to change. It also gives later reviewers a standard for success. If the proposed mechanism does not directly alter the stated failure, the draft has drifted.
2. Research working mechanisms, including hidden support
Look at how capable jurisdictions handle the problem, but do not copy a sentence merely because it comes from a respected country. Ask what institutions, records, courts, staff, technology and social conditions make the rule work. A short visible rule may rely on a large invisible system.
Record outcomes and failure modes as carefully as the text. The aim is to extract the smallest useful mechanism that could work in the intended setting. For an India-scale federation, capacity, language, rural access, state variation and large numbers are not edge cases; they are part of the design.
3. Compare alternatives and choose the smallest effective mechanism
A proposal should survive comparison with at least one serious alternative. One method may remove discretion but create high cost. Another may be easy to administer but miss the people causing the problem. State the trade-off directly and choose the option that changes the harmful incentive with the least unnecessary burden.
“Smallest” does not mean shortest wording. It means the smallest complete rule. A missing appeal, transition or access route may save space while making the system unfair or unusable. Brevity is useful only after the essential mechanism is intact.
4. Put each rule in the right legal place
Enduring rights, public powers and institutional boundaries normally belong in a constitution. Adjustable rates, amounts, forms, technology and routine procedure usually belong in ordinary law. Mixing them makes future correction either too easy for fundamental protections or too difficult for practical details.
Also identify every existing law the draft relies on or changes. One binding rule should not be copied into several places. A short cross-reference is safer than two almost-identical duties that can later diverge.
5. Attack the design before an opponent does
Test honest use, mistakes, corruption, false accusations, official pressure, organised gaming, outages, rural access, disability, small firms, large firms and behaviour after people adapt. Ask how a person benefits from lying, delaying, splitting a transaction, changing ownership on paper or controlling the reviewer.
The point is not to write a clause for every imaginable story. It is to find material loopholes and concentrated power. A law that works only when everyone behaves well is not a serious system design.
6. Classify flaws instead of treating every concern equally
A fatal flaw defeats the central mechanism or violates a foundational right. A simple repair may need one definition or deadline. An implementation issue may need staff, training or a system that the law already authorises. A transition issue concerns movement from today’s position to the new rule. A minor concern may be real but too rare or small to justify extra legal burden.
Classification keeps review disciplined. Without it, a draft either ignores serious problems or grows endlessly in response to every hypothetical. Repair material flaws and record the rest honestly.
7. Design operation, evidence and correction
Name the trigger, actor, required result, deadline, record, automatic consequence, enforcement route, remedy, reviewer, cost, capacity need and transition date. Replace vague promises such as “promptly,” “adequately” or “as appropriate” with observable tests wherever possible.
A reader should be able to answer seven questions: Who? When? What? By when? What record? What if it fails? Who reviews it? If the text cannot answer them, the law may still depend on unpublished discretion.
8. Draft the law and its explanation as different documents
The operative page contains the binding rule: purpose, core rule, operative duties and essential definitions. The companion page explains the problem, mechanism, expected effect, implementation, examples, objective checks and important limit. The explanation helps readers but has no legal force.
This separation makes both pages better. The law does not become a persuasive essay, and the explanation does not pretend to create duties. Concrete examples can expose ambiguity before publication, while a clearly labelled limit discourages exaggerated claims.
9. Record status and test the rendered result
Use honest status labels such as idea, under research, proposed draft, current agreed draft or replaced. A planned subject is not a law. Then render the complete packet at normal reading size. Check margins, type, page count, scanning and whether the operative rule still makes sense outside the drafting file.
The final test is not a word count. It is whether a Class 10 reader can find the duty, whether two informed readers get the same result in ordinary examples, whether powerful people face the same rule, and whether a wrong decision has a quick and affordable correction route.
Common questions
- Does plain English reduce legal precision?
- It should not. Plain drafting removes needless difficulty while keeping every essential condition, duty, definition, consequence and review route exact.
- Should every law be one page?
- No. Perfect Laws prefers one operative A4 page and allows two when clarity or completeness genuinely requires it. The explanation remains one separate page.
- Are readability scores enough?
- No. Short words and sentences do not prove that triggers, duties, evidence or appeals are complete. Concrete examples and adversarial testing matter more.
- Why separate the explanation from the law?
- The separation keeps binding duties exact while giving readers examples, implementation detail and honest limits without accidentally giving explanatory copy legal force.
Read the sources
Go from the guide to the complete project record.
See the complete Perfect Laws method