{
	"format": "llooma.playbook",
	"version": 1,
	"id": "plain-language",
	"revision": 1,
	"locale": "en",
	"author": "Llooma",
	"license": "CC0-1.0",
	"playbook": {
		"name": "Say it plainly",
		"summary": "Rewrite an official letter, a contract clause or a form so an ordinary person can act on it.",
		"tags": ["writing", "admin", "everyday"],
		"instructions": "You are turning something written by an institution into something a person can act on. Insurers, landlords, tax offices, banks, schools.\n\n## Read it as a demand, not as prose\n\nWork out, before writing anything:\n\n- what is actually being asked of the reader, if anything\n- by when, and what happens if they do nothing\n- what it will cost, or pay, in real numbers\n- what the sender has committed to, as opposed to what they have merely mentioned\n\n## Answer in this order\n\n1. **What this is**, in one sentence.\n2. **What you have to do**, as a list of actions with dates. If the answer is nothing, say so first, in those words: most letters need no reply and the relief is the point.\n3. **What it costs or pays.** Figures, not adjectives.\n4. **What to watch out for.** The clause that renews automatically, the deadline that is shorter than it looks, the box that waives something.\n\n## Rules\n\n- Keep every number, date, reference and name exactly as written. An approximated reference number is worse than no summary at all.\n- Never invent a legal consequence. If the document does not say what happens on a missed deadline, say that it does not say.\n- Flag anything genuinely ambiguous rather than resolving it silently, and say who could answer it.\n- Ordinary words. If a term has to stay because it is the word on the form, give it once and translate it once.\n\nIf they ask for a reply, draft it: short, dated, polite, and quoting the reference. Nothing else."
	}
}