Skip to content

Plain-Language Transparency Report

A public-facing summary artifact — instantiates Transparency for Accountability

Rewrites already-disclosed records into a short, plain-language account a non-expert can actually read, so the disclosure reaches the people it is meant to make power answerable to.

A Plain-Language Transparency Report publishes no new facts. It takes disclosures that already exist — a ruling, a policy, a dataset, a set of decisions — and renders them into a short, jargon-free account that a non-specialist can read and act on. Its whole reason to exist is that disclosure only produces accountability when the intended audience can actually understand it; a technically complete record written in code, statute citations, and acronyms is disclosed and yet effectively hidden. What makes it this mechanism and not its siblings is that it operates one layer above the record: it is a comprehensibility and framing layer over material other mechanisms produce, and it always points back to the authoritative source rather than replacing it.

Example

A member's insurance claim for a costly procedure is denied. The insurer already issues the legally required determination — several pages of policy citations, procedure codes, and "medical necessity" language almost no member can parse. The plain-language report sits alongside it: one page, roughly an 8th-grade reading level, saying what was decided (the procedure won't be covered), why (it was judged not medically necessary under the plan's stated criteria), what evidence was weighed, and — the part that makes it accountable — exactly what the member can do next and by when (request the full file, submit new evidence, escalate to external review within ≈60 days). It does not soften the denial; it makes the denial and its challenge path legible.

How it works

The distinguishing move is audience-first rewriting, not summarizing-for-brevity. Fix a specific reader and a target reading level, then rebuild the record around the questions that reader actually has — what happened, why, what it means for me, what I can do — in that order. Layer it: a plain top summary with links down into the full technical record, so simplification never severs the reader from the authoritative source. Nothing is added or decided here; fidelity to the underlying record is the binding constraint.

Tuning parameters

  • Reading-level target — the reading grade you write to. Lower is more inclusive but forces harder editorial choices about what to drop.
  • Layering depth — how many tiers from headline summary to full record. More tiers serve mixed audiences but cost effort and can bury the detail.
  • Audience specificity — written for one named group vs. a general public. Sharper targeting reads better but needs a separate pass per audience.
  • Simplification vs. fidelity — how much nuance to compress. Over-simplifying is where a summary quietly stops being true; this is the dial to watch.
  • Localization — languages and accessible formats (translation, screen-reader, easy-read). Widens reach at production and maintenance cost.

When it helps, and when it misleads

Its strength is converting formally-complete-but-unreadable disclosure into the only kind that actually holds anyone to account — the kind the affected audience can read and act on. It is cheap leverage, too: the records already exist, and a good summary multiplies who can use them.

Its failure mode is that simplification is editorial power, and editorial power can spin. A "plain-language" summary can lead with the favorable line and bury the adverse finding, or flatten a contested judgment into settled fact — becoming public relations wearing the costume of openness. The classic misuse is running it as gloss: a reassuring readable summary issued precisely to keep readers from opening the real record. The discipline that guards against this is a fidelity check against the source and the rule that the summary is published with the full record and links to it, never instead of it — the plainness is a door to the record, not a substitute for it.[1]

How it implements the components

  • comprehensibility_and_format_layer — its entire substance: it reformats and rewrites the disclosure for a defined non-expert reader.
  • transparency_purpose — it states, in the reader's own terms and up front, what the disclosure is for and whom it is meant to serve.

It does not produce the records it renders — the decisions come from the Public Decision Log, the reasons from the Reason-Giving Template, and the criteria from the Rule & Criteria Register; this artifact only makes them legible.

Notes

Comprehensibility is necessary but not sufficient: a perfectly readable summary with no way to ask a question or contest the decision still leaves power unchallenged. The report earns its accountability value only when it links to a live challenge path — see Public Comment & Question Channel.

References

[1] The U.S. Plain Writing Act of 2010 requires federal agencies to write public-facing material in clear, well-organized language — a real duty to be understood, distinct from the duty to disclose. It is the legitimate practice this mechanism generalizes; the abuse it must avoid is using plainness to editorialize. ↩