Background Briefing Guide for Newsrooms

What to take away

A background briefing guide helps a reader understand why a current event matters and how its parts fit together. It is not a storage room for everything the newsroom has learned. Each section should answer a likely reader question, establish a needed fact, or explain a relationship that changes the meaning of the news.

Begin with a one-sentence scope statement. Name the subject, place, period, and decision or event the briefing explains. Then list what the piece will not cover. Those boundaries prevent a municipal budget explainer from drifting into a general history of taxation or an election briefing from becoming a biography of every participant.

Photo and credit

The photograph illustrates a reporting workspace. It does not depict a person, place, institution, or event discussed in this guide.

Start from reader questions

Write five to eight questions before outlining. A useful set often includes:

Put the shortest direct answer near the start. Follow it with the evidence and qualifications needed to make that answer accurate. If the answer depends on a definition, give the definition before presenting a number that uses it. The layered structure matches the guide to developing news stories, with background pulled forward.

Build a context inventory

Background earns its place by working: a date shows a warning preceded a decision.

A jurisdiction note explains why an agency can investigate but cannot prosecute, and a denominator turns a large count into a small rate. State each element's function in draft notes; the missing-denominator entry opening statistics reporting problems shows what a skipped denominator note costs.

Order the briefing for use

The Federal Plain Language Guidelines, available through Digital.gov, explain how to organize information for readers. The Plain Writing Act of 2010 requires federal agencies to use plain writing in documents for the public. The guidelines recommend putting the purpose and bottom line first, organizing around audience questions, and presenting processes in their natural order. That guidance supports a question-led briefing, but the newsroom still has to decide which questions the verified record can answer.

A reliable sequence is:

Do not force this order when another structure fits better. A geographic emergency may need a location section before institutional history. A court ruling may require the holding before the procedural timeline. For rulings, the Court Reporting Guide explains which parts carry the decision.

Mark evidence status

Use notes that distinguish a published record from a claim about that record. Label material as confirmed, attributed, disputed, estimated, preliminary, superseded, or unknown. These are reporting states, not decorative caveats. For record-side status checks, use a structured official-document review: identify the issuing body, document type, date or version, scope, operative language, and any later document that changes or supersedes it.

For every section, retain the source title, publishing body, date, version, page or table, and the sentence it supports. When two sources disagree, describe the disagreement and check whether they measure different things, cover different periods, or apply different definitions. The Source Material Types Compared table explains what each source class can establish.

Write for later updates

Use precise dates instead of relative phrases such as "last week." Name the edition of a rule, report, or dataset. Avoid language that will silently become false when a hearing ends or a preliminary total changes.

Maintain a short update ledger with the check date, result, affected section, and editor. A new fact may require more than adding a paragraph. It may change the headline, opening answer, comparison, or conclusion.

Editorial review

Before publication, ask an editor unfamiliar with the reporting to state the current situation, responsible institutions, central evidence, main uncertainty, and next step. A wrong answer points to an ordering or definition problem. A missing answer may reveal an unsupported gap.

Plain-language testers formalize this check as paraphrase testing. Digital.gov's plain-language guidance on paraphrase testing has a reader explain each section in their own words and treats every misunderstood passage as a content problem to fix, not a reader failure. It calls for only six to nine participants, a scale a desk can approximate with two or three colleagues.

Read the briefing once only for attribution. Read it again only for time and status. Those passes catch claims that became newsroom voice and old facts written as current conditions.

Common questions

How long should a background briefing be?

Long enough to answer its defined questions with evidence. Scope and reader need matter more than a fixed word count.

Is a timeline always necessary?

No. Use one when sequence explains causation, authority, delay, or change. Otherwise, a process table or short summary may work better.

Can a briefing use older sources?

Yes, for historical facts or stable definitions. Check whether a newer edition, correction, or official record has replaced them.

When should a briefing be rewritten?

Rewrite its framing when new evidence changes the main answer, not only when details need an update.