Make a community briefing.
Help people understand one issue: what is happening, what remains unclear, who can decide, and what comes next.
A briefing gives an issue room to make sense. Start with a short explanation, then let readers choose the detail they need.
Editable text template (Markdown): a briefing outline, question script, and source-check notes. Open it in any text editor; no account needed.
Start with the question. Follow the evidence.
Choose one public question.
Write the question your readers need answered and why it matters now. Name the intended audience, publisher, and correction contact. Decide what this briefing can explain and what it cannot settle. A general public explanation should not become a place to collect people’s private cases.
Separate facts, interpretation, and gaps.
List the claims the explanation depends on, including the headline and proposed next step. Give each a source, check date, and limit. Keep an interpretation or suggested option visibly distinct from a supported fact. Use “Known,” “Developing,” and “Unresolved” only as the evidence warrants.
Show who can answer or decide.
Name the actors involved and distinguish their roles: who has information, who makes the decision, who carries it out, and who can correct a mistake. An office title, nearby location, or public statement does not establish authority over everyone concerned.
Write a short entrance and useful detail.
Begin with one sentence saying what this is, followed by a short explanation of what happened, why it matters, who is affected, and what a reader can do. Add a timeline, comparison, or status display only when it helps. Put supporting sources and fuller reasoning within reach.
Give the next step a practical tool.
If you promise an action, supply something usable: a question to ask, a call script, a date to check, or a short decision guide. Connect it to someone able to respond. When a decisive fact is unknown, the next step may be to ask or verify; do not make the reader act as if it were settled.
Test the explanation and plan its upkeep.
Ask another reader to explain the issue, uncertainty, decision-maker, and next step in their own words. Record any repairs. Name the person who approves the exact version, the correction route, and the next review date or event. Preserve earlier versions when you update it.
When children or families are readers
Make a separate explanation around people, choices, care, and what happens next. Keep the same facts and uncertainty. Do not simply shorten adult prose or give children responsibility for resolving an adult problem. Use appropriate human review for child, safety, legal, health, or other consequential claims.
Include a tool someone can actually use.
Question script · template only
“I’m trying to understand [specific issue]. The public notice says [supported statement], but I could not confirm [missing detail]. Does your office decide this, or can you identify who does? Where can I find the current written information?”
Beside the script, add the checked contact route, what that person or office can answer, and what the reader should do if the route does not work.
The starter includes a short public explanation, status summary, authority table, optional timeline, next-step tool, source record, and private production notes. Use the parts your issue needs without hiding a material uncertainty.