Guides

Part of Developing news stories: a guide to facts, context, and updates

How to build and maintain a news timeline

News timeline method for recording event times, source times, publication changes, uncertainty, corrections, dependencies, and the next expected action.

What to take away

  • Record when an event occurred, when it was reported, and when it was verified.
  • Give every timeline entry a source and confidence state.
  • Use exact dates and time zones instead of relative phrases.
  • Keep reporting notes more detailed than the public timeline.
  • Revise an entry openly when later evidence changes it.

A news timeline is not a stack of headlines. It is a controlled record of events in sequence. Done well, it exposes gaps, prevents time errors, and lets a reader enter a complicated story without reading every earlier article.

The public version should be concise. The reporting version should retain source details, conflicts, and revision history.

A timeline usually serves a larger live file. The guide to covering developing news stories shows where the chronology sits among the other components.

Photo and credit

A journalist interviewing wildlife-service staff in the field
The Wikimedia Commons page for the field interview credits Ashley Spratt and the Pacific Southwest Region of the U.S. Fish and Wildlife Service, dates the photograph to December 12, 2014, and lists a CC BY 2.0 license. The downloaded file is a Commons-generated 1,200-pixel copy. Remove the image if the author requests it.

The photograph documents an interview setting. It does not verify what any participant said.

Step 1: define the timeline's question

Write one sentence stating what the chronology must explain. Examples include "How did the evacuation order expand?" and "Which decisions led to the court hearing?" A broad subject produces a crowded list. A question gives editors a reason to include or exclude each event. A chronology built around litigation should follow the stages in the court reporting guide, because filings, hearings, and rulings carry different statuses.

Also set boundaries:

  • start date or triggering event;
  • geographic area;
  • institutions and people in scope;
  • planned end point;
  • minimum evidence required for inclusion.

Step 2: create a private event ledger

Use one row per event. Do not draft elegant prose yet.

Field What to record
Event time Best-supported time the event occurred
Time zone Named zone and daylight-saving status if relevant
Description Neutral statement of what happened
Source Exact document, observation, recording, or interview
Source time When the source published or supplied the information
Status Confirmed, reported, disputed, or unknown
Revision note What changed and why

If the event time is a range, store the range. If only a date is known, do not invent a clock time to make the table sort neatly.

Step 3: normalize time without hiding local meaning

Keep the original time from the source and add a normalized time for sorting. For a local public-safety story, show local time to readers. For an international sequence, a consistent reference zone may help, but the displayed entry should still name the zone.

Daylight saving status belongs in the record too. NIST's page on United States daylight saving time rules says the Department of Transportation, not NIST, regulates time zones and daylight time, which runs from the second Sunday of March to the first Sunday of November and is not observed in places such as most of Arizona, Hawaii, and Puerto Rico. A bare clock time near a boundary can be an hour off.

Avoid "today," "last night," and "hours earlier" in durable timeline entries. Those phrases become unclear when an article is read later or republished elsewhere.

Step 4: separate event order from publication order

An agency may disclose a morning decision late in the afternoon. Put the decision at its event time, then note when it became public if that delay matters. A document uploaded Tuesday can describe a meeting held Monday. Those are two times, not one. The method for reading an official document makes the same separation a habit, recording the document date, version, and access date as separate fields.

This distinction can change interpretation. It may show what decision-makers knew at a given point or why an earlier report lacked a later fact.

Step 5: test dependencies

For every claimed cause or consequence, ask whether the chronology alone proves the connection. Sequence is necessary for causation, but it is not sufficient. Event B occurring after Event A does not establish that A caused B.

Use restrained wording:

  • "followed" for sequence;
  • "the order required" for a documented rule;
  • "the agency attributed" for a sourced explanation;
  • "coincided with" when timing is the only established relation.

The same restraint governs numbers. The guide to reporting statistics and polls keeps association and causation apart when two measures move together.

Step 6: edit for the public version

Choose entries that change the reader's understanding. Merge repetitive procedural notices only when no meaning is lost. Give each entry a date, a compact statement, and attribution where the fact is contested or not independently established.

Poynter's review of interactive chronologies says they can add historical context, organize ongoing reporting, and help journalists working on different parts of a story get up to speed. The timeline reporting examples also describe the labor involved in collecting dates, descriptions, locations, and related material. The older product examples on that page are not current software recommendations.

Step 7: maintain a change log

When evidence changes an entry, keep three things:

  1. the previous wording;
  2. the new wording;
  3. the reason and source for the change.

The public correction should identify the affected fact. "This timeline was updated" is not enough if the earlier version gave the wrong date or sequence. The context checklist for developing stories makes this update-and-correction pass a standing step.

Quality checks

  • Sort by event time and scan for impossible overlaps.
  • Compare every name and number with the cited record.
  • Confirm that time zones are consistent.
  • Mark estimates and preliminary figures.
  • Remove claims that rely only on publication order.
  • Check that the latest entry does not assume an unresolved outcome.
  • Read the timeline from the perspective of a first-time visitor.

Common questions

Should the newest event appear first?

A reverse-chronological feed helps repeat visitors find updates. A background timeline is usually easier to understand from earliest to latest. Label the order.

What if two sources give different times?

Record both in the private ledger, seek the underlying record, and explain the conflict if it affects the public account.

Can a quotation be a timeline entry?

Only when the statement itself is an event that matters. Otherwise, summarize the event and use the quotation as support.

How long should each entry be?

Use enough words to identify the action, actor, and significance. Move extended explanation into a background note rather than packing it into every row.

More in Guides

Guides

Developing news stories: a guide to facts, context, and updates

Developing news story guide covering confirmed facts, open questions, timelines, background, attribution, update notes, corrections, and reader needs.

Rules

Seven developing news briefing problems and how to fix them

Developing news briefing problems explained with fixes for stale leads, false certainty, weak attribution, time confusion, clutter, and hidden corrections.

Maintenance

Developing story context checklist for editors

Developing story context checklist for facts, attribution, chronology, definitions, affected people, uncertainty, fairness, corrections, and updates.

Reviews

News briefing formats compared: event, issue, and accountability

News briefing formats compared by reader question, evidence, time frame, structure, update pattern, limits, and best use for developing coverage.