Each technique serves one of the four principles in ISO 24495.
Numeric targets are working proxies, not clauses of the standard:
treat them as tripwires for a second look, not as hard caps.
Relevant — content selection
Name the reader before editing. One line, e.g. "customers waiting for
a refund" or "engineers on call". Every cut and keep decision follows it.
Cut throat-clearing. Openers like "It is important to note that",
"In today's fast-paced world", "As previously mentioned" carry no reader
value. Delete them; keep the clause they were delaying.
Cut what this reader will not use. Background the reader already has,
internal process detail, defensive caveats aimed at the author's boss.
When unsure, move it to the end rather than deleting.
Findable — structure
Front-load the point. Conclusion, decision, or required action in the
first sentence or a bolded first line. Reasons after.
Informative headings. A heading states the content's message ("Refunds
take 5–7 days"), not its category ("Refund information") when the message
fits.
One topic per paragraph; ~5 sentences as a tripwire.
Lists for 3+ parallel items — steps, options, conditions. Keep list
items grammatically parallel.
Tables for lookups, prose for reasoning. If the reader will compare
values, it is a table.
Understandable — wording
Sentence length ~20 words as a tripwire. Longer is allowed when the
sentence carries one idea cleanly; two ideas in one sentence is the real
violation.
Active constructions with explicit actors. "We will refund you" not
"A refund will be issued". Passive is fine when the actor is genuinely
unknown or irrelevant.
Verbs over nominalizations. "decide" not "make a determination";
"apply" not "submit an application" (unless the noun is the term of art).
Common words. "use" not "utilize", "help" not "facilitate", "about"
not "approximately" — unless the rarer word is a defined term.
Define terms at first use, then never rotate. One name per concept
for the whole document. Synonym variety is a literary virtue and a plain
language defect.
Kill hedge stacks. "may potentially, in some cases" → "may". Keep one
honest hedge; delete the decorative ones. Never delete a hedge that
carries real uncertainty.
Expand or gloss abbreviations at first use unless the audience
definition makes them safe.
Usable — actionability
Instructions as imperatives with explicit objects and deadlines.
"Submit the form by March 31" not "the form should be submitted in a
timely manner".
State who does what. Every obligation names its actor.
Put conditions before the instruction ("If X, do Y"), so readers can
bail out early.
End reader-facing messages with the next step, if one exists.
Self-Check (run before returning)
Can the named reader say, after one reading, what this text wants them
to know or do?
Is the main point in the first two lines?
Any sentence carrying two ideas? Any paragraph carrying two topics?
Any term used under two names, or any jargon left undefined?
Did every fact, number, condition, and honest hedge survive the rewrite?