The Checklist Nobody Writes Down Until It Fails Them

Most reporters we talk to already have a process. Ask them how a piece moves from a finished draft to something live on their site, and they can describe it — usually in a single confident sentence. The trouble tends to show up the first time that process is interrupted: a source calls back with a correction two hours before a piece is due, or a co-writer is traveling and can't do the usual second read. It's in that gap, not in the ordinary flow of work, that a shaky process gets exposed.

What we notice, sitting with people over their actual workflow, is that the steps themselves are rarely the problem. Reporters know they need to fact-check, format images, and schedule a publish time. What's missing is the boundary between one step and the next — the clear signal that a stage is genuinely finished and it's safe to move on. Without that boundary, steps get skipped under pressure, not through carelessness but because nothing marked where they began and ended.

Why a written checklist changes the outcome

A checklist does something a mental routine can't: it removes the question of whether you remembered everything. Under deadline pressure, memory is the first thing that degrades, and it degrades quietly — you don't notice a missed step until someone points it out, often a reader. A checklist that sits outside your head keeps working even when your attention is somewhere else.

The checklists that hold up in practice share a few traits. They are short enough to actually use — five to eight items, not twenty. They are specific to your own setup rather than generic advice, which means they mention your actual publishing platform, your actual image sizes, your actual byline format. And they include the boring administrative step most people skip: recording what was published, when, and where, so that corrections later have something to reference.

"The most reliable reporters we've worked with are not the fastest. They are the ones who never skip the same step twice."

Building one that survives contact with a real deadline

The temptation is to build a checklist for the calm version of your week — the one where nothing goes wrong and every source answers on the first call. Build it instead for the version where something does go wrong, because that's the week the checklist actually needs to hold. Ask what you'd want to have already confirmed if a correction request landed an hour before you meant to publish. That question, more than any general template, tends to produce a checklist worth keeping.

None of this requires new software or a formal editorial team. It requires writing the thing down once, in your own words, and testing it against a week that didn't go to plan. Most of the workflow sessions we run end with exactly that: a document short enough to glance at before hitting publish, built from a reporter's own process rather than handed down as a template.