Building a Spending Story Over Months, Not a Deadline

Most spending stories don't fail because a reporter lacked documents. They fail because the reporter tried to write the story before the documents were ready, forcing conclusions the paper trail didn't yet support. The accountability programme we run is built around the opposite instinct: let the documentation set the pace, and write only once it does.

That means treating a spending story less like a single assignment and more like a slow-growing file. Each session we run adds a layer — first the published budget line, then the procurement record, then site verification, then the official response — and only after all four are in place does a draft take shape.

Resisting the pull of a premature deadline

Editors, understandably, want a publish date. The discipline here is agreeing on a realistic one from the start — typically eight weeks for a programme like ours — rather than compressing the documentation phase to meet a date set before anyone had seen the records. A story published two weeks late with the response letter in hand beats one published on time without it.

Keeping residents as people, not evidence

It's tempting, once you have strong documentation, to let residents' quotes serve mainly as colour for a case you've already built. We push trainees to interview residents early and let their account shape which documents matter, rather than treating people as confirmation for a conclusion reached in a filing cabinet.

By the final session, a finished story should be legible to the community it's about — not just to an editor or a records clerk. That's often the harder rewrite, but it's the one that makes the reporting worth the months it took.