Skip to content

Plain-Language Disclosure

A disclosure document — instantiates Premise–Action Decoupling

A layered, plainly-worded statement that puts the scope, limits, and boundary of what agreeing commits you to in a first-time reader's line of sight — so assent is informed rather than inferred from not-having-noticed.

Plain-Language Disclosure is the document that says out loud what a bundled communication would otherwise leave implied — and says it so a first-time reader actually grasps it. In accessible, layered language it states the scope of what agreeing commits you to, the limits on that commitment, and the boundary where the action stops, putting the decision-relevant terms where a hurried reader will meet them instead of on page 40. Its defining move is legibility before assent: it neither detects a smuggled premise nor confirms your answer — it makes the terms and their edges readable in advance, so that whatever assent follows is informed rather than manufactured by not-having-noticed. Its whole value is measured by reader uptake, not by completeness: an exhaustive disclosure no one can parse discloses nothing.

Example

A "0% introductory APR" credit-card offer. The headline invites you to apply and start spending; what it leaves implied is where that 0% stops. A Plain-Language Disclosure re-expresses the commitment's scope and edges in layered plain English: a short top layer states what you are actually signing up for — the intro rate lasts ≈15 months — the boundary where it ends — after that, the rate resets to roughly 24% — and the limit that quietly voids it — a single missed payment can end the promo early — with the full agreement underneath for anyone who wants it. A standardized summary box makes the go-to rate as visible as the "0%." You can still apply; the surface action is untouched. But applying no longer doubles as "I didn't realize the rate would reset," because the scope, the limit, and the action-boundary of the commitment now sit in the reader's line of sight.

How it works

  • Rank by materiality. Identify the few terms that actually change the decision and lead with them; everything else is a lower layer.
  • Translate. Re-express each term in plain, concrete language a non-specialist reads correctly on the first pass — numbers, consequences, and limits, not defined-term cross-references.
  • Draw the scope and its edges. Say what the commitment covers and, just as explicitly, where it stops and what voids it; the limit and boundary are part of the disclosure, not omissions.
  • Layer. A salient summary on top, the full text beneath, so depth is available without burying the decision-relevant bit.

The distinguishing point is that it is judged by uptake, not completeness — a disclosure that is exhaustive but unread has failed at the one thing it is for.

Tuning parameters

  • Layering depth — how many tiers from headline to fine print. More tiers serve both skimmers and diggers but risk hiding the material term one layer too deep.
  • Reading-level target — the audience the plain language is pitched to. Too high and it excludes; too low and it can shade into omitting real complexity.
  • Salience budget — how much prominence the single most decision-relevant term gets. Everything can't be bold; deciding what is, is the core editorial act.
  • Scope precision — how sharply the limits are drawn. Vague scope invites later over-reading; over-precise scope becomes unreadable itself.

When it helps, and when it misleads

Its strength is that it converts "we told them" into "they could actually tell," and puts the material term where a real, hurried reader will meet it. Done well it is the difference between consent and consent-shaped paperwork.

Its failure mode is disclosure theater — piling on so much accurate detail that nothing is salient, then treating "it was disclosed" as a liability shield while the term that matters sits on page 40.[1] Run backwards, a disclosure is drafted to be technically complete and practically unread. It also cannot force attention: legibility is necessary, not sufficient, and a reader determined to skip will skip. The discipline is to measure uptake — can a sample of real readers state the material term back? — rather than page count, and to treat salience, not volume, as the deliverable.

How it implements the components

Plain-Language Disclosure realizes the legibility components — the ones a document fills by making terms readable before a decision:

  • consent_scope — it states, in plain language, exactly what agreeing does and does not commit the reader to.
  • scope_or_limit — it spells out the limits and the conditions that cap or void the commitment, so they are disclosed rather than discovered.
  • action_boundary — it marks where the action's commitment stops: what applying or signing does not reach.

It makes terms legible but does not verify that the reader actually understood and assented to that scope (that's Assent-Scope Confirmation), test whether the underlying premise is warranted (that's Assumption Audit), or split a compound clause into separately-acceptable pieces (that's Bundled Clause or Motion Split).

References

[1] The U.S. SEC's Plain English rule (adopted 1998) requires the key sections of a prospectus to use short sentences, everyday words, and the active voice; consumer-finance regimes such as the Truth in Lending Act add standardized summary formats (the credit-card "Schumer box") so the decision-relevant term is legible at a glance. All rest on one premise: a disclosure no one can parse discloses nothing. ↩