What Is A Fact Pack? How Journalists Build One

A fact pack is a structured evidence file that a journalist or editor builds before drafting a story. It lists the core event, the original source, what is confirmed, what is not, where reports conflict, and what still needs checking. The idea matters most in breaking news, where information changes by the hour and a draft written from half-checked claims can go wrong fast. This guide explains what a fact pack is, what goes in one, how to build it step by step, and includes a template you can copy.

What is a fact pack?

A fact pack is the newsroom's working evidence file for one story. It sits between research and writing: everything the writer needs to know is in one place, and everything the writer must not state as fact is clearly marked.

One note on terms. "Fact pack" is not a standardized industry term, and different newsrooms use different names for the same practice, such as a research file, story file or verification log. We use "fact pack" here as a plain label for that practice.

It is also not a PR fact sheet. In public relations, a fact sheet is usually a one-to-two page background document that an organization sends to journalists, often alongside a press release, to give an overview of the company and its leaders. A fact pack goes the other way: the newsroom builds it from its own checking, and it records what the newsroom has and has not confirmed.

What goes in a fact pack

Element	What it contains	Why it matters
Core event	One sentence on what happened	Keeps the story focused
First known source	Original statement, document or post, with link and time	Shows where the information started
Confirmed facts	Claims with the evidence that supports each one	Tells the writer what can be stated plainly
Unconfirmed claims	Claims still being checked, and who made them	Prevents rumors from becoming copy
Conflicting reports	Where sources disagree on numbers, times or names	Flags what needs careful wording
Timeline	Events in order, each with a source	Makes updates easier
Documents and media	Filings, photos, video, audio, with origin notes	Keeps primary material in one place
Open questions	What is unknown and who could answer it	Drives the next round of reporting
Last verified update	Time of the most recent check	Shows how fresh the file is

How to build a fact pack, step by step

1. State the story question. Write one sentence on what you are trying to establish. A clear question stops the file from turning into a dump of links.

2. Find the original. First Draft's verification guide lists five pillars: provenance, source, date, location and motivation. It says provenance comes first, meaning you must check whether you are looking at the original account, article or piece of content. If you are not, you can miss that the same material appeared years earlier in a different form. Apply that to every item you add.

3. Log every source as you go. For each item, record the name, link, time published and time you found it. Do it while researching, not afterward, because reconstructing this later is slow and unreliable.

4. Sort every claim into a bucket. Use three: confirmed, unconfirmed and conflicting. A claim moves between buckets as evidence arrives, and the pack should show when it moved.

5. Check independence. Five websites repeating one press release are one source and four copies. The Verification Handbook, a resource developed by the European Journalism Centre, advises never to simply parrot or trust sources, whether witnesses, victims or authorities, since firsthand accounts can be inaccurate or manipulative. This step also guards against pack journalism, which Merriam-Webster describes as group reporting marked by uniform coverage and a lack of original initiative. One glossary on the topic points to deadline pressure as a cause, with reporters checking against competitors instead of verifying independently. A fact pack makes you list your own evidence rather than what rivals published.

6. Build the timeline. Put events in order, each with a source. Check dates and times carefully, including time zones.

7. List open questions. Write what you still do not know and who could answer it. This becomes the reporting to-do list.

8. Hand it to the writer and keep it live. Writing from the pack means the draft only states what is in the confirmed bucket. After publication, keep updating the pack so corrections and updates have a clear evidence trail.

A fact pack template you can copy

FACT PACK
Story:
Prepared by:
Created (date, time, time zone):
Last verified update:

1. CORE EVENT (one sentence)

2. FIRST KNOWN SOURCE
   Name / link / time published / time detected

3. CONFIRMED FACTS
   Fact | Evidence or source | How confirmed | Time checked

4. UNCONFIRMED CLAIMS
   Claim | Who said it | What would confirm it

5. CONFLICTING REPORTS
   Claim A vs Claim B | Sources for each

6. TIMELINE
   Time | Event | Source

7. PEOPLE AND ORGANIZATIONS
   Name | Role | Contacted? (yes / no / pending)

8. DOCUMENTS AND MEDIA
   Link | Original checked? | Date | Location

9. OPEN QUESTIONS AND WHO TO ASK

10. EDITOR DECISION
    Publish / Hold / Update (with note)

A tiny made-up example of two entries, for illustration only:

• Confirmed fact: "The road is closed between Exit 4 and Exit 6." | City transport notice, link | Notice opened and read | 10:20

• Unconfirmed claim: "The road will reopen tonight." | One social post | Waiting for the agency's confirmation

Mistakes to avoid

• Pasting a summary as a fact. A summary, whether written by a person or generated by AI, is not evidence. Link to the original.

• No timestamps. Without times, you cannot tell which version of a claim is current.

• Mixing confirmed and unconfirmed claims. Keep them in separate sections, always.

• Counting copies as confirmation. Trace each claim back to its first source.

• Building the pack once and abandoning it. Update it after publication.

Where AI helps, and where it does not

AI can speed up the busywork: pulling out names, numbers and dates, grouping duplicate reports, and comparing a new update with an earlier one. It should not decide what goes into the confirmed bucket. That decision needs an editor who has seen the evidence. For more on how monitoring feeds this process, read our guide to AI source monitoring for newsrooms, and for tools that help with checking, see AI fact-checking tools for newsrooms.

Where NewsBolts fits

At NewsBolts, we treat the fact pack as the step between evidence collection and drafting, so a writer works from checked material instead of raw alerts. It is one stage in the human-governed workflow described in our AI newsroom operating system guide, where editors review the evidence and decide what gets published.

FAQ

What is a fact pack in journalism? A fact pack is a structured evidence file for one story. It records the original source, confirmed facts, unconfirmed claims, conflicting reports, a timeline and open questions before the story is drafted.

Is "fact pack" an official journalism term? No. It is a plain label for a practice many newsrooms use under other names, such as a research file or verification log. What matters is the habit of separating confirmed from unconfirmed information.

How is a fact pack different from a fact sheet? A PR fact sheet is a short background document an organization gives to journalists. A fact pack is built by the newsroom itself and records what has and has not been verified.

Do small newsrooms need a fact pack? Yes, and a simple version works. A shared document with the template above is enough for a solo publisher or a small team.

Can AI build a fact pack? AI can help organize sources, extract claims and compare updates, but a journalist must decide what counts as confirmed. Treat AI output as a lead, not as evidence.

Conclusion

A fact pack keeps a story honest by separating what you know from what you have only heard. Start with one question, find the original, log your sources, sort every claim and check independence before you write. Even a simple shared document is enough. The goal is a draft that states only what the evidence supports, and a file that shows why.