Running a Multi-Week Investigative Project Without Losing the Thread
Why a Single-Day Story Workflow Breaks Down Over Six Weeks
Most student newsroom habits are built around a daily or weekly deadline: report it, write it, file it, move on. An investigative project blows that up, because you’re holding partial information from a source you talked to three weeks ago while waiting on a records request that might not return anything usable, and the story you thought you were writing in week one is often not the story you end up with in week six. The single biggest failure mode isn’t bad reporting — it’s losing track of what you already know, who told you what, and which threads you dropped because you got busy with something with a nearer deadline.
Set Up a Running Document Before You Make the First Call
Before any interviews happen, build one shared document with three sections: a timeline of events as best you understand them so far, a source list with contact info and what each person can speak to, and an open-questions section that you update after every single interview or document review. This sounds like overhead for a small staff, but it’s the difference between a reporter picking the project back up after finals week and actually remembering where things stood, versus starting over from half-memory. Update the timeline in real time, not at the end — details fade fast, and you will misremember exact dates and phrasing within a couple of weeks if you rely on memory alone.
Filing Records Requests Early, Because They’re the Slowest Part
If your project depends on public records — incident reports, budget documents, meeting minutes — file the request in the first week even if you’re not sure yet exactly what story you’re building. Agencies are allowed statutory response windows that run into weeks, and a request filed in week four of a six-week project usually means the records arrive after publication. Pair this early filing habit with what you already know about public records and FOIA requests — investigative work is just that same process run in parallel across multiple requests instead of one.
Talking to Sources Before You Know the Full Shape of the Story
Early interviews in an investigative project are exploratory, and it’s fair to tell a source that directly: you’re trying to understand how something works before you know what, if anything, went wrong. Being honest about that stage protects you from a source later feeling ambushed by a direction the story took after they’d already talked. Keep a habit of going back to early sources once the shape of the story sharpens, both to fact-check what they told you against new information and to give them a fair chance to respond to anything that’s turned adversarial to their interest.
Deciding When You Actually Have a Story
Investigative projects can drift indefinitely if nobody sets a checkpoint. Build in a hard decision point roughly two-thirds of the way through your reporting window where the editor and lead reporter sit down and ask plainly: what do we know for certain, what’s still unconfirmed, and is the confirmed part enough to publish on its own with the rest as a follow-up. Plenty of solid investigative work ships as two or three shorter stories over a month instead of one giant piece that keeps slipping because you’re chasing one more unreachable source.
Protecting the Project From a Single Point of Failure
Assign at least one other staffer, even a junior reporter, to know the broad shape of the project and where the files live, so a sick week or a family emergency for the lead reporter doesn’t stall six weeks of work. The nonprofit training organization Investigative Reporters and Editors publishes tip sheets and project checklists built from decades of newsroom experience at every level, and its resource library is worth a look before your first long project rather than after it goes sideways.
Getting Legal Review Before the Night Before Publication
A project that took six weeks to report shouldn’t get its first legal read the evening before it’s scheduled to run. If your school has access to a media law attorney through a state scholastic press association or a journalism program’s legal hotline, loop them in once the story’s shape is reasonably clear, even in a rough draft, rather than once the final version is locked. Waiting until publication eve to ask whether a passage is defensible tends to produce one of two bad outcomes: a rushed, fear-driven edit that softens accurate reporting, or a decision to publish anyway without anyone actually understanding the exposure. Neither is necessary if the legal conversation starts weeks earlier, while there’s still time to shore up a weak passage with another source or document instead of just cutting it.
Archiving the Reporting, Not Just the Published Story
Once a long project publishes, keep the underlying documents, interview notes, and the running timeline document somewhere the newsroom can find them later, not only on the reporter’s personal laptop. A follow-up story, a correction request, or a legal inquiry six months later goes much faster if someone can pull the original records instead of trying to reconstruct a six-week reporting process from memory after the team that did the work has already graduated and moved on.