T The Useful Margin
Weekly Review

File Naming Conventions for Notes: A Practical Guide

A The Useful Margin guide · Updated 2026-09-09 · 7 min read
File Naming Conventions for Notes: A Practical Guide
Quick answerA useful naming convention for notes puts a meaningful subject, a clearly defined date and any necessary version in a consistent order. Choose the first field according to how you expect to find the note: by time or by topic. Keep file extensions intact and document your abbreviations. For shared or protected records, follow the responsible owner's rules; do not bulk-rename files or assume existing links will survive.
Contents

What makes a useful file-naming convention for notes?

A useful naming convention for notes puts a meaningful subject, a clearly defined date and any necessary version in a consistent order. Choose the first field according to how you expect to find the note: by time or by topic. Keep file extensions intact and document your abbreviations. For shared or protected records, follow the responsible owner's rules; do not bulk-rename files or assume existing links will survive.

The purpose is recognition, not a perfectly uniform archive. A filename should help you distinguish the note you need from a nearby note that sounds almost the same. It does not have to summarise the document.

The method below is an original, tool-neutral planning exercise for ordinary notes. It draws on institutional file-organisation guidance without turning those institutions' local rules into universal requirements. No reader files were renamed, and no notes app was tested.

Should the subject or the date come first?

Begin with a retrieval question, not a punctuation rule. Will you remember the week when you wrote something, the project it concerned, or the type of record?

MIT Libraries' research-data guidance recommends planning names and folders around later retrieval and considering sorting when choosing the first filename element. That is research-data guidance; our examples adapt the principle to personal notes.

What you expect to ask later Possible naming order Main limitation
What did I record that day? Date, subject, note type Notes on the same subject can be separated by other subjects.
What have I recorded about this project? Subject, date, note type A whole-week view may require a separate search or index.
Which record did the other note reference? Stable identifier, short subject The identifier needs an index or enough accompanying context to be understandable.

Choose one principal route for a small collection. A meeting notebook and a research archive need not use identical names if they answer different questions. Write down the distinction rather than letting each new note establish its own rule.

What does the order change in a concrete example?

Here are six fictional filenames, shown in ascending lexical order. Cedar and Orbit are invented project labels, not actual organisations. The suffix v01 is simply the initial revision label in this example.

A date-first collection looks like this:

2026-09-08-orbit-meeting-v01.txt
2026-09-08-orbit-research-v01.txt
2026-09-09-cedar-meeting-v01.txt
2026-09-10-orbit-meeting-v01.txt
2026-09-11-cedar-research-v01.txt
2026-09-12-orbit-research-v01.txt

Put the subject first and the same six records sort this way:

cedar-2026-09-09-meeting-v01.txt
cedar-2026-09-11-research-v01.txt
orbit-2026-09-08-meeting-v01.txt
orbit-2026-09-08-research-v01.txt
orbit-2026-09-10-meeting-v01.txt
orbit-2026-09-12-research-v01.txt

The first arrangement groups the two September 8 notes together. The second groups the two Cedar notes together and the four Orbit notes together. Neither creates more information: both contain six records, with the same subjects, dates and types.

We checked this ordering by sorting the illustrative strings in memory. That verifies this lexical example, not how a particular app displays notes. A program may instead be showing modified dates, pinned items or another selected order. Inspect its actual view before expecting the filename's first field to control it.

Which date belongs in the name?

Define the date before choosing its format. A meeting date, writing date and period covered can all be useful, but they answer different questions.

For example, a note written on September 10 about a September 8 meeting could use September 8 if the convention means “event date.” Record the writing date inside the note when it matters. Do not switch to September 10 merely because the note was typed later.

MIT Records Management recommends year-month-day dates and numbered draft versions in its file-naming guidance. A consistent date representation is useful here, but it cannot resolve an unknown date. Do not invent a day to make a filename fit the pattern.

For a weekly summary, define whether the date means the week's starting date or the review date. Put the covered interval inside the note. If you routinely need both, use an index with separate fields instead of forcing every date into the filename.

A date in a name is a label chosen under your convention. It is not independent evidence that an event happened, an approval was given or a record became effective then.

How much context belongs in a filename?

The Smithsonian Institution Archives' electronic-file guidance explains how meaningful folder names can supply context while individual names identify particular files. It also discusses consistent vocabulary and abbreviations. These are organisational principles, not a requirement to copy Smithsonian storage arrangements.

Ask what context would disappear if someone encountered the note outside its usual folder. A filename such as meeting-v01.txt may be clear in one location and ambiguous in a mixed search result. A short subject label can preserve the missing distinction.

Use terms you would actually search. If your notes alternate between “launch,” “release” and “go-live” for the same project, decide whether those mean the same thing. Document the chosen term or record the alternatives in an index. Do not quietly combine terms that represent different events.

Keep confidential information out of filenames and broad indexes. A descriptive title does not need a diagnosis, private account number or another person's sensitive details. Use approved systems and access arrangements for protected material; naming consistency is not a privacy control.

How do versions differ from stable identifiers?

A version label distinguishes revisions within a chosen scheme. A stable identifier points to a particular record. Decide which job you need.

In our example, v01 does not mean approved, implemented or legally authoritative. Adding v02 would not establish any of those facts either. Record status and approval in the appropriate place rather than trying to make a higher number do that work.

A stable identifier such as N014 can remain attached to a note even if its short descriptive title changes. Write that convention down, and do not reuse the identifier for an unrelated note. It is a local reference label, not evidence of a universal numbering system.

For the reasoning behind a choice, keep the actual explanation in a decision log. The filename can identify that record; it cannot replace its assumptions, evidence or authorised status.

What should a one-page naming rule contain?

Use this original convention card before applying a scheme:

Collection: ordinary project notes
Primary retrieval question: what happened on this date?
Order: event-date, project-label, note-type, revision
Date meaning: event date; unknown dates stay unresolved
Project vocabulary: cedar; orbit
Note types: meeting; research
Revision meaning: numbered draft revision, not approval
Extension: retain the file's actual extension
Exceptions: record why an item does not fit
Owner: person authorised to maintain this collection

This is a fictional example card, not a prescription for every collection. Replace the fields with your actual needs in an appropriate private record. Keep the explanation short enough to consult when creating the next note.

A useful exception explains why a file differs. It does not require immediate renaming. A received attachment, externally supplied record or document managed by another system may have naming requirements you do not control.

How can you adopt a convention without reorganising everything?

Start with new notes you are authorised to create. Sketch a few candidate names before touching existing records. Ask whether they distinguish the event, subject and record type without needing private context.

For existing material, avoid bulk renaming as a first step. Check the application's documented rename behaviour and the consequences for links, references and collaborators. If a small manual change is appropriate, verify the affected references afterwards. Do not assume an old path or link continues to work.

Leave extensions alone during a naming cleanup. Microsoft's Windows guidance states that changing an extension does not convert the underlying file format. The fictional names represent text files; they are not instructions to turn other documents into text by renaming them.

A naming review is not authority to delete originals, move shared records or override retention obligations. Ask the responsible owner when an item is governed by organisational, legal or other formal requirements.

How do you know whether the convention is useful?

During your next weekly notes review, try three ordinary retrieval questions: find a note from a known date, find two notes on the same subject, and identify which record a reference points to. Use non-sensitive material and your actual tool.

Record any ambiguity rather than inventing a performance score. Perhaps “research” is too broad, or the chosen date means different things in different files. Change the rule only where that observation justifies it.

Keep this bounded within your weekly-review routine. The goal is a name you can understand when memory is unavailable, not an archive whose consistency becomes another unfinished project.

Sources

FAQ

Should a note filename start with the date or the subject?

Choose according to the question you expect to ask later. Date-first names support a date-oriented lexical listing, while subject-first names group matching subject labels in that listing. Your app may display another sort order, so check its actual view. Neither convention is universally better or a substitute for a useful title.

Which date should I use when I write notes after a meeting?

Define what the filename date means. If your collection uses event dates, a note written later can retain the meeting date, with the writing date recorded inside when relevant. Do not invent an unknown date or switch meanings silently. A filename date is not proof of approval, implementation or legal effect.

Does a higher version number mean the note is approved?

No. In the proposed scheme, a version number identifies a revision; it does not establish approval, authority or implementation. Record those facts through the appropriate process. A stable record identifier has a different job: it points to the same record even when its descriptive title changes under an authorised convention.

Should I rename all my old notes to match?

Not as a starting point. Apply the convention to new notes you are authorised to create, then consider existing material separately. Check the app's documented rename behaviour, shared ownership and reference implications before any small manual change. Do not bulk-rename, delete or move protected records under the guise of tidying filenames.

Can I change the extension to make all my notes the same format?

No. Renaming an extension is not format conversion, and a naming convention should retain the file's actual extension. Use the appropriate application and authorised process if a format change is genuinely needed. This guide supplies neither conversion instructions nor permission to alter shared records, originals or files subject to retention requirements.