Name Files by Project, Purpose, and Version

“Final notes revised” makes sense while a document is open. Later, it leaves three questions unanswered: Notes for which project? Useful for what? Revised compared with which copy? A filename can carry those answers without becoming a summary of the whole document.

Filename planning card

Project: [Short, memorable project name; include an occasion or year if needed]
Purpose: [The specific job this document performs]
Version: [v01, or the next number for a distinct revision of this document]

Filename: [Project] — [Purpose] — [Version]

Future request: I need the [Purpose] for [Project], revision [number].

Naming rule: Keep the project and purpose wording steady for revisions of the same document. Give a different document purpose its own name and version sequence.

Hypothetical example: Maple Fair — Volunteer Brief — v02

Give each part one job

Think of the name as three answers in a fixed order: What is this part of? What will I use it for? Which revision is it? Write those answers as Project — Purpose — Version. The separators simply make the three parts easy to distinguish.

For the project, choose a short name you expect to remember. For the purpose, name the job the document performs, such as Volunteer Brief or Room Layout. For the version, use a sequence such as v01, v02, and v03. These are planning choices for readable names, not technical requirements.

Hypothetical worked example: the Maple Fair

Suppose Elena is planning a fictional neighborhood event called Maple Fair. She has three documents with working names: Notes, Schedule new, and Final revised. She expects to return to them when briefing volunteers, checking setup timing, and arranging tables.

She gives each document the project label Maple Fair, then replaces its vague description with its purpose. Notes becomes Maple Fair — Volunteer Brief — v01. Schedule new becomes Maple Fair — Setup Schedule — v01. Final revised becomes Maple Fair — Table Layout — v01. For this example, each is the first revision Elena identifies under the convention.

The names now answer different future requests. “What do volunteers need to know?” points to Volunteer Brief. “When does setup happen?” points to Setup Schedule. “Where do the tables go?” points to Table Layout. The useful distinction comes from the document’s job.

Let versions change without changing the identity

Elena later revises the volunteer assignments. The next distinct revision is Maple Fair — Volunteer Brief — v02. Its project and purpose stay the same because it is still the same kind of document for the same event.

In this method, advance the number when you need to distinguish a revision you might refer to separately; you do not need a new number for every small edit. Each purpose has its own sequence, so Volunteer Brief can reach v03 while Table Layout remains at v01.

The number tells you sequence, not approval. Avoid asking words such as Final or Latest to do that job: they stop distinguishing copies as soon as another revision appears.

Add a distinction where the ambiguity lives

If Maple Fair becomes a recurring project, the project label needs more detail: Maple Fair 2027. If Elena needs separate volunteer briefs for setup and cleanup, the purpose needs more detail: Setup Volunteer Brief and Cleanup Volunteer Brief. Those are different document jobs, rather than two versions of one brief.

Keep extra words tied to a real distinction. Maple Fair 2027 — Cleanup Volunteer Brief — v01 answers a specific future need. Adding a long description of everything inside would make that answer harder to spot.

Try the name against a future request

Before settling on a name, finish this sentence: “I need the [purpose] for [project], revision [version].” Then check whether the filename supplies those exact answers. If you would naturally ask for a setup schedule, use Setup Schedule consistently instead of alternating among Timeline, Plan, and Schedule.

For Elena, “I need the volunteer brief for Maple Fair, revision two” maps directly to Maple Fair — Volunteer Brief — v02. Use the template below to make the same decision for one of your own documents.

Choose words your future request is likely to contain. Keep those words stable, and let the version number carry the revision history.