Fact-check content when a claim could be wrong in a way a reader could catch and you could not defend: numbers, prices, dates, quotes, named products, and anything a draft states as settled that nobody on your team actually confirmed. When to fact check content is really a triage question, not a stage you run on every sentence. Most of a typical piece is opinion, style, or something a writer already knows first-hand, and none of that needs a source hunt. The sentences that do need one share a pattern. Once your team can spot the pattern, the fact-check stage takes minutes, not an extra day.
Editing and Fact-Checking Are Not the Same Job
Editing improves how a piece reads: flow, structure, voice, whether the second paragraph earns the first. Fact-checking confirms it is true: the claims, the citations, the attributions, whether something is still current. A draft can be beautifully edited and completely wrong, and a clean copy pass on a wrong number makes the number read more confidently, not less.
Treating the two as one stage is the most common way a workflow loses its fact-check entirely. An editor smooths a sentence, feels like they “went through it,” and the number inside the sentence was never actually checked, just made to read better. The Knight Science Journalism fact-checking guide (read 2026-09-18) recommends a specific sequence for exactly this reason: fact-checking works best as its own stage, done after the top edit has settled the piece’s substance and before proofreading polishes its surface. Doing it earlier means checking a version that is about to change. Doing it later means a typo pass gets blamed for catching what fact-checking should have caught.
On a small team you will merge stages. That is fine. What cannot merge is the fact-check into a general “look it over” pass, because a general pass has no list of what to look for and defaults to checking nothing in particular.
A Short Test: Which Sentences Actually Need a Source
Run every draft against this list. Anything on it gets a source before it ships.
- Any number. A statistic, a percentage, a count, a date, a duration. Numbers are the single most common thing readers can quietly disprove.
- Any price or cost figure. Prices move, and a wrong one costs the click and the trust the moment the reader follows it.
- Any specific claim about a named product, tool, or company. “Supports unlimited users,” “starts at $X a month,” and “used by Y companies” each need a current source, not last quarter’s memory of the vendor’s page.
- Any quote or paraphrase attributed to a person. If you cannot point to where they said it, it does not go in as a quote.
- Any legal, medical, or financial specific. These carry the highest cost when wrong and the lowest tolerance from readers and platforms alike.
- Anything an AI-assisted drafting pass produced that nobody on the team personally verified before it landed in the file. The risk here is not that a tool was used; it is that a sentence read as though someone checked it when no one did.
- Anything time-sensitive. A true statement in March can be false by September without a single word changing.
What Does Not Need the Same Scrutiny
Not everything in a draft belongs in the queue above, and treating it as if it does is how a fact-check stage turns into a bottleneck nobody respects.
- Opinion and framing. “The better way to think about this is…” is a position, not a claim of fact.
- Style and structural choices. How a piece is organized is an editing question.
- A process claim the writer can vouch for from their own work. If the site’s own voice already establishes that the writer runs this workflow, describing how they run it is not a claim that needs an outside source, it is a report of their own practice.
- Evergreen definitions that do not hinge on a number, a name, or a date. Explaining what a stage in a process is for does not usually need a citation.
Running the trigger list against everything, including these, is what makes a fact-check stage feel like busywork and get skipped under deadline. Scope it to what can actually be wrong.
When to Fact Check Content: Where the Stage Sits in the Process
Sequence matters more than most teams assume. The stage belongs after the piece has been drafted and substantively edited, and before it goes out or gets a final polish pass. Checking earlier means checking a version that will not survive to publication. Checking after publication is a correction, not a fact-check.
On a two-or-three-person team, the stage still needs an owner, even if that owner also wrote or edited the piece. What breaks the process is not merging roles, it is having no defined moment where someone runs the trigger list on purpose, out loud, against a specific draft. Without that moment, “somebody probably checked it” quietly becomes the actual policy.
If a freelancer wrote the draft, tell them up front what will be checked and what you expect delivered alongside the file: a link or a note for every number, price, and quote, not a bare claim you have to chase down after the deadline. Rushed turnaround costs more than planned turnaround, and the Editorial Freelancers Association’s own rate guidance (read 2026-09-18) names turnaround time as one of the factors that moves a freelance job’s price. Building one day for a fact-check pass into the original brief is cheaper than asking for a same-day fix after a late file lands, and far cheaper than a correction after publication.
The cleanest way to make the trigger list consistent across a team of staff and freelancers is to put it where your other standards already live, not in a separate document nobody opens. A one-page editorial style guide that already states your voice and formatting rules is also the right place to state which sentences get checked and by whom.
Two Ordinary Examples From a Content Operation
A pricing claim. If a draft states what a platform costs, that price is exactly the kind of claim the trigger list flags. Verify it against the vendor’s current page or label it clearly as an estimate with a date, the way reading a CMS pricing page without being misled walks through for that specific, common case.
A “free” claim. A vendor’s own description of a tool as free, or free forever, deserves the same scrutiny rather than a repeat. What “free” actually means in a given product is easy to misstate without checking, which is exactly the distinction open source is not the same as free, and not the same as safe covers.
Neither example needs a dedicated fact-checker. Both need someone to stop for thirty seconds before publishing and confirm the specific number or claim against its source, rather than trusting that it was probably right when it was written.
Building the Habit, Not Just the List
A trigger list on a page nobody consults does nothing. The habit that matters is smaller: whoever approves a piece for publishing is accountable for whether the list was actually run against it, not just for whether the piece reads well. That single accountability line, stated plainly rather than assumed, is what turns “we should probably fact-check this stuff” into a stage that happens every time.
The Short Version
- Fact-check anything a reader could catch and you could not defend: numbers, prices, dates, quotes, product claims, and anything unverified from an AI-assisted pass.
- Skip the same scrutiny for opinion, style, and process claims a writer can vouch for from their own practice.
- Fact-checking is a separate stage from editing, and it belongs after substantive edits settle and before final polish, not folded into either.
- Tell freelancers up front what will be checked and ask for sources delivered with the draft, not chased down afterward.
- Put the trigger list in your one-page style guide so it is consistent across everyone who writes for you.
- Assign the check to whoever approves the piece, so it is a named accountability rather than an assumption.
FAQ
What is the difference between editing and fact-checking?
Editing improves how a piece reads: flow, structure, and voice. Fact-checking confirms it is true: the claims, the citations, and whether something is still current. A draft can be well-edited and still wrong, which is why the two need to be separate stages rather than one general pass.
When in the process should fact-checking happen?
After the piece has been substantively edited and before it gets a final polish or goes out. Checking earlier means checking a version that will change; checking after publication is a correction rather than a fact-check.
Do freelancers need to be told in advance what will be fact-checked?
Yes. Naming the trigger list in the brief and asking for sources delivered with the draft avoids a scramble at deadline and avoids a rushed same-day fix, which typically costs more than planning the check in from the start.
Does every number in an article need to be fact-checked?
Every number that could be wrong and that a reader could catch, yes: statistics, prices, dates, counts, and specific product or company claims. General framing or a writer’s own process description does not carry the same risk and does not need the same scrutiny.
What if a solo writer has no separate fact-checker?
The check still has to happen, just self-directed. Running the trigger list against your own draft before it goes out, on purpose and by name, is what keeps a one-person operation from quietly skipping the stage altogether.
