Most business owners have three places where “I might need this later” material ends up: an overloaded email folder, a drawer they open twice a year, and a Slack channel they’ll never search systematically. None of these is a reference system. All three are places where useful information goes to become unfindable.

The GTD reference filing system is a single, searchable archive for material that has no immediate action but belongs in your workflow. David Allen built it into Getting Things Done because he observed that knowledge workers were using their inboxes as filing cabinets and their brains as search engines, and both were failing at the job.

Setting it up takes less than an hour. Using it well is mostly a habit. The habit is simpler than it sounds.

What counts as reference material in GTD

GTD divides everything you capture into two categories: actionable and non-actionable. Actionable material becomes a next action, a project entry, or a Waiting For item. Non-actionable material is either worth deleting, worth keeping as a future possibility, or worth keeping as reference.

Reference material is information you might want to retrieve but don’t need to act on right now. A vendor contract. A product specification sheet. Background research on a market you’re entering. A client brief you’ll need when the project restarts. Your company’s insurance policy. These items have no next action and no pending decision — they just need to be findable when the moment comes.

The distinction from someday/maybe is worth making precisely. Someday/maybe holds ideas and projects you might pursue one day but haven’t committed to. Reference holds information you might retrieve to use. If you’d look it up to act on something, it’s reference. If you’d revisit it to decide whether to act at all, it’s someday/maybe.

How the GTD reference system works

The system has one organising rule: one-touch filing. When you decide something is reference, you file it immediately rather than putting it in a “to file” pile. The pile is where most reference systems collapse. Items accumulate, the pile grows, and filing it starts to feel like a task in itself rather than a two-second decision.

David Allen’s original design uses alphabetical filing — physical manila folders, A through Z. You file each item under the word you’d use to look it up. A document about your accountant goes under A. A product warranty goes under the product name. A client brief goes under the client’s name.

The alphabetical approach has one advantage over category-based filing: there’s no ambiguity about where something belongs. A contract isn’t filed under Legal, or Clients, or Finance — it’s filed under the name on the contract. You retrieve by searching for what you already know, not by reconstructing the taxonomy you used when you filed it.

What belongs in reference — and what doesn’t

The reference system works best when it holds a specific category of material. These items belong in it:

• Legal and financial documents: contracts, invoices, company registration, insurance policies
• Client and project background: briefs, brand guidelines, context documents
• Research and reference reading: market reports, competitor data, saved articles you’ll use again
• Standard operating procedures, templates, and checklists
• Meeting notes from which all actions have already been extracted

Three categories that don’t belong in reference:

• Anything with a next action — those go on your next actions list or into a project
• Anything with a specific future date — those belong in the tickler file
• Anything with no clear retrieval value — those get deleted

The processing decision when you encounter new material is: does this require action? If yes, it goes into the action system. If no, the next question is: would this be useful to retrieve? If yes, it goes into reference. If no, delete it. That three-step triage is the GTD processing workflow applied to non-actionable material.

Building a digital reference system

Most knowledge workers operate in a mostly digital environment, which means the reference system needs a digital form. The challenge is that most people already have material spread across five or six tools with no deliberate structure, and calling that a reference system would be generous.

The simplest workable structure uses three systems, each with a defined scope:

• Documents: one cloud storage folder (Google Drive, Dropbox, or equivalent), organised alphabetically by project or client
• Emails: your email client’s archive, with a search-first approach rather than folder hierarchies
• Notes and everything else: one notes application with a flat, tag-based or alphabetical structure

The test for whether your digital reference system is working: can you name the system first, then navigate to it, without hesitating? If you have to guess which of three apps might contain a given document, the system is fragmented. The retrieval should be predictable, not exploratory.

Avoid creating a separate folder in every tool you own. A reference item that might be in Google Drive, Notion, Evernote, or your desktop folder isn’t searchable — it’s just spread across more locations.

The annual purge

Reference systems degrade over time. A contract for a project that ended eighteen months ago, a competitor analysis for a market you’ve since exited, a product spec for something you stopped selling — these items are not useful reference material. They’re clutter that erodes confidence in the system.

The NP System‘s annual review includes a reference purge: one pass through the system to delete anything that would no longer be useful to retrieve. The goal is a reference system you trust, not a comprehensive archive of everything you’ve ever saved. Trust is what makes you search it first rather than starting from scratch.

The purge doesn’t need to be thorough. Anything that takes more than a glance to evaluate is probably worth keeping. The items that go are the obvious ones — expired contracts, superseded documents, research that has definitively passed its use-by date.

How the reference system fits the wider GTD structure

The reference system closes a specific gap in the GTD processing workflow. When you empty your inbox and encounter something with no next action, it either gets deleted, added to someday/maybe, or added to reference. Without reference as an option, useful material stays in the inbox — which is why most people’s inboxes carry months of material with no pending action.

The tickler file handles one specific type of non-actionable material: things you’ll need on a specific future date. Everything else with retrieval value goes to reference. The two systems are complementary, not overlapping.

During the weekly review, it’s worth glancing at whether anything in your reference system is close to becoming active — a project restart, an upcoming renewal, a contract that’s about to expire. These items might need to move into an active project or onto a next actions list, or they might deserve a note in the tickler to surface at the right moment.

The bottom line

The GTD reference filing system solves one problem cleanly: material that has no next action but is worth keeping needs a home that isn’t your inbox. The system is as simple as it sounds — one touch, alphabetical filing, one annual purge. The sophistication is in the processing habit that feeds it.

If you want to understand how the reference system fits into the full Capture, Process, Plan, and Do structure, the free NP System course walks through each phase for business owners running multiple projects. Or take the productivity quiz to find out which part of your current system is creating the most friction.