Pacing a Story That Refuses to End on Schedule

Long investigations rarely finish when you expect them to. A source goes quiet for six weeks. A document request stalls in an office that doesn't answer emails. The scope, which looked manageable in month one, has doubled by month four and shows no sign of stopping. If you've carried a project like this alongside your regular work, you already know the particular exhaustion it produces — not the exhaustion of a hard week, but the slower kind that comes from a deadline that keeps moving.

Most advice about long projects focuses on discipline: work harder, stay organised, push through. Less is said about pacing — the decision, made deliberately rather than by accident, about how much of yourself a story is allowed to take before you check in with it again.

Scope creeps quietly, so check it on purpose

A project's scope rarely expands in one dramatic leap. It grows a source at a time, a new thread at a time, each addition reasonable on its own. The only way to notice the cumulative effect is to stop and compare the current shape of the story against what you set out to do. A short, regular check-in — even fifteen minutes with someone outside the work — does more to catch scope creep than any amount of self-discipline in the moment.

Momentum needs rest built into it, not around it

There's a temptation to treat rest as something you earn once the story is filed, which means a six-month project comes with six months of postponed recovery. Reporters who sustain long work tend to build small breaks into the schedule itself, rather than promising themselves a rest that keeps getting pushed back as the timeline slips.

A project that costs you your health to finish isn't a success story — it's a warning for the next one.

None of this shortens the timeline. What it does is make the timeline survivable, which, for a story that was never going to move quickly, matters more.