Why Your Archive Falls Apart After Month Three

Every reporter starts a new subject with good intentions. A fresh folder, a clean naming scheme, maybe even a spreadsheet. And for the first few weeks, it holds. Then the story grows teeth — more sources, more documents, a screenshot saved in a hurry between calls — and the system that felt sturdy at the start quietly stops working.

The failure point is rarely dramatic. Nobody loses a hard drive. What happens instead is smaller and more insidious: a file gets saved with a vague name because there wasn't time to think of a better one, and three weeks later nobody, including the person who saved it, can find it again. Multiply that by forty files and the archive becomes something you avoid opening rather than something you rely on.

The naming problem is really a decision problem

Most naming conventions fail not because they're badly designed but because they ask you to make a decision under pressure. If a filename requires you to categorise, date, and summarise a document at the exact moment you're trying to finish an interview, you'll skip it — every time. The fix isn't a stricter rule. It's a shorter one: a convention simple enough to apply without thinking, even at 11pm.

"The best filing system is the one you'll actually use when you're tired." — a rule worth writing on a sticky note above your desk.

Build for the version of you that comes back later

The real test of an archive isn't whether it makes sense today. It's whether it makes sense in four months, to a version of you who has forgotten most of the context, or to a colleague picking up the story after you've moved on. That means writing filenames and folder structures for a stranger, even when the stranger is future-you.

A short index file — one page, plain text, updated as you go — does more for long-term usability than any elaborate folder tree. It doesn't need to be clever. It needs to answer one question fast: where did I put the thing I'm looking for.

None of this requires new software or a steep learning curve. It requires deciding, once, on a system small enough to survive contact with a deadline — and then sticking to it before the pile grows past the point where sorting it feels worth the effort.