newspapers, weekly, reading, information, paper, article, politics, text, news, article, politics, politics, news, news, news, news, news. Context elements compared, from timelines to maps to glossaries
Photo by sweetlouise on Pixabay

Reviews

Part of Background Briefing Guide for Newsrooms

Context elements compared, from timelines to maps to glossaries

Context elements compared by reader need, evidence demands, strengths, and risks, including timelines, process guides, maps, data, glossaries, and profiles.

Stories that stay in the news get their context rebuilt week after week: a map of a hurricane's likely path from the National Hurricane Center, a timeline of a federal rulemaking record, a data section on the monthly jobs report, a glossary of the terms in dispute. Readers meet the same few forms again and again. This is context elements compared: what each form must prove, where each one misleads, and which parts of a running story stay genuinely uncertain.

What to take away

  • Pick the form by the reader's questionorder, rule, place, measurement, meaning, or people.
  • Timelines risk implying cause; process guides risk stating a draft rule as settled law.
  • Maps and data sections carry the heaviest evidence billdates, boundaries, scales, denominators, definitions, and revision state.
  • When two forms fit, give sequence to the timeline and formal steps to the process guide.

Each form answers a different question and carries a different evidence bill: a storm's track map and a storm's damage tally are not the same artifact, and the records behind them differ. Related reading on ranking the underlying records: source materials ranked.

Comparison table: reader need, evidence demands, strengths, risks

Comparison table

Reader need

Timeline
What happened first
Process guide
Who decides and by when
Map
Where a boundary sits
Data section
How large, compared with what
Glossary
What a term means here
Profile set
Who holds power and interest

Evidence demands

Timeline
Dates, source status, revisions
Process guide
Controlling text, effective date, branches
Map
Date, unit, layer, scale, key
Data section
Unit, population, period, denominator, source
Glossary
Authority, alternatives, exclusions
Profile set
Role entry, decisions, limits, record

Strength

Timeline
Sequence in one pass
Process guide
Route and dead ends
Map
Spatial pattern
Data section
Exact comparison
Glossary
Stops term drift
Profile set
Authority beside story

Main risk

Timeline
Proximity read as cause
Process guide
Draft rule stated as law
Map
Area size as population
Data section
Denominator mismatch
Glossary
Circular definition
Profile set
Uneven detail

The table sets out the comparison.

Context forms compared

Chronology

Best question
Consequential order?
Evidence needed
Dated records, status
Main risk
Sequence as cause

Process guide

Best question
What happens next?
Evidence needed
Current rule or procedure
Main risk
Practice as binding rule

Map

Best question
Where are boundaries?
Evidence needed
Geographic data, legend
Main risk
Hiding uncertainty

Data section

Best question
How large or changed?
Evidence needed
Dataset, units, denominator
Main risk
False precision

Timelines: sequence without implied cause

A timeline explains what happened first. Each entry needs a date, event, source status, and one line on why order changes the story. Include the start of a legal duty and any revision point.

The risk is causation by proximity. "The price rose after the vote" reports sequence, not cause. Causal claims need evidence beyond the calendar; a dated record such as the Federal Register's daily list of rules and notices lets a reader check what actually came first. Related reading on entry rules: news timeline method.

Process guides: rules, branches, deadlines

A process guide follows formal steps, decision points, responsible bodies, deadlines, and outcomes. It separates what a rule requires from what agencies often do. Show branches for appeals, waivers, and missed deadlines.

Evidence demands are steep. Check the edition and effective date of the controlling text. A proposed rule, staff manual, and enacted requirement can describe different states of one process. The Government-wide FOIA FAQ lists appeal rights, deadlines, and the nine exemptions.

The main risk is stating a proposed rule as current law. A headline can collapse a draft, a comment period, and a final rule into one verb.

A guide should name the agency that controls each step and the record that proves the step occurred. Without that, readers cannot tell a real deadline from a stated goal. A guide that skips the record is a summary, not a map of the process.

For public programs, the stages are usually set by law: the Administrative Procedure Act requires a proposed rule, a comment period, and a final rule, and each step leaves a dated document a guide must cite. Related reading on stages and records: tracing policy implementation.

Maps: place, scale, boundary and source

A map locates a boundary, route, hazard, or service area. It can also show a vote or a pattern. Every map reflects choices about inclusion, labels, symbols, and scale.

For any published map, state the date represented, the geographic unit, the source layer, the scale, and the meaning of colors or symbols. Do not use area size to imply population size. Mark estimates and disputed boundaries.

The Library of Congress worksheet analyzing maps as primary sources asks who made the map, for whom, and why. Those questions apply to a supplied map.

The main risk is reading area as population. A large rural district can hold fewer people than a small urban one. Two maps readers see often — FEMA's flood insurance rate maps and the National Hurricane Center's forecast cone — carry dates, boundaries, and caveats that a story has to repeat rather than drop. A map without a date or boundary source cannot support a claim about who is inside the zone.

Data sections: denominators, definitions, revision state

A data section answers a measurement question. Start with the unit of analysis and the defined population. Then give the period, numerator, denominator, adjustment status, source, and revision state.

Compare like with like. A monthly count beside an annual rate needs the conversion explained. A national average may not describe a small local group. If the source changed its definition, mark the break.

The Census Bureau paper on communicating with Census data through visualization advises context in every visual, descriptive titles, and the data source cited inside the visual. Census releases also arrive in stages — apportionment counts, then redistricting data, then detailed tables — so a data section should name the release it is using.

The main risk is a denominator mismatch or a moving definition. A rate that changes because the base changed is not a trend.

A glossary earns space when a term recurs, has a technical meaning, or differs across institutions. Define the term as used in the package, name the authority behind a formal definition, and note alternatives. When a story says poverty, name the publisher: the Census Bureau publishes the official poverty thresholds, and the Department of Health and Human Services publishes the poverty guidelines used for program eligibility. Unemployment has its own authority; the Bureau of Labor Statistics defines who counts as unemployed and who is out of the labor force.

Profiles explain roles, powers, relevant actions, and interests. Use the same fields for every person so the set does not favor one side. For federal officials, the U.S. Office of Government Ethics is the authority for public financial disclosure reports. Related reading: checking an expert's credentials.

The main risk for profiles is uneven detail. A long profile of one side and a one-line label for the other reads as editorial judgment.

Example: choosing between a map and a data table

Suppose a story covers a county evacuation zone. Two forms could fit.

Choosing between a map and a data table

  1. Write the reader's question in one sentence. "Where does the zone edge fall?" or "How many people live inside it?"
  2. If the answer is spatial, use a map with date, boundary source, and scale.
  3. If the answer is numeric, use a data table with the zone definition, population count, and source.
  4. If both, use the map for the boundary and the table for counts. State the same date and unit in both.

Decision rule: when two forms fit, give sequence to the timeline and numbers to the data section. Cut the overlap.

Common questions

What is the difference between a timeline and a process guide?
A timeline puts events in order. A process guide organizes formal steps, decision points, and deadlines, which may not be chronological.
When should I use a map instead of a table?
Use a map when location or a boundary carries meaning. Use a table when exact comparison of numbers matters more than geography.
What must a data section include to be trustworthy?
It needs the unit of analysis, defined population, period, numerator, denominator, source, revision state, and known uncertainty. Definitions and breaks belong in the section, not in a footnote.
How do I decide which context form fits my story?
Write the reader's question first. Match the question to one form, then check that form's evidence demands. If two forms fit, split the jobs and cut repeated prose.

More in Reviews

Latest from Costs Desk