File Naming That Survives Board Turnover

Every club has files named like this: Minutes.docx, Budget 2024.xlsx, Event Notes April 9 2024.docx. And then the folder with a dozen more versions of the minutes: Minutes (2).docx, 04-09-24_minutes.docx, Minutes 4-9-2024.pdf, Minutes_final.docx, April Minutes FINAL.docx, Minutes FINAL-final v2.docx. Nobody remembers which one is current. Nobody's sure which one was shared with the membership. Half of them are drafts. One of them is the one that should actually be in the archive, and nobody can tell which.

This is the kind of mess that board members silently put up with until they hand off the files to the next board member, at which point it becomes the next person's problem. A few small habits around file naming make the whole thing dramatically better, not just for the current board, but for every board that comes after.

Why this matters more than it seems

File naming is one of those topics that sounds too small to be worth thinking about. It isn't. There are a few reasons.

New board members can't find things. When the treasurer hands off and the new treasurer opens the shared drive, the first thing they do is try to find the current version of key documents. If everything is named inconsistently, they either give up or spend hours hunting.

Everyone makes copies. When files are hard to identify, people download their own copies, edit them, and send them around. The "canonical" version loses meaning. A year later, there are six slightly different versions floating around and nobody is sure which is the real one.

Historical research becomes impossible. "What did we decide at the September 2023 board meeting?" is a question that should take 30 seconds to answer. With bad file naming, it takes an hour.

Search doesn't save you. People sometimes assume that search makes file names irrelevant. It doesn't. Search surfaces everything matching, including old drafts and duplicates, and you still need to know which one to trust.

A few simple rules

You don't need a complicated naming scheme. You need four or five simple habits, applied consistently.

Start with the date, in ISO format

The single most valuable habit is to start file names with the date in the format YYYY-MM-DD, with year first, then month, then day, in order of specificity. This is called "ISO format," the international date standard. Example: 2026-04-09-board-minutes.pdf (April 9, 2026).

Why this specific format?

• It sorts chronologically. Files with ISO dates sort in the correct order automatically when you look at them in a folder. 2026-04-09 comes before 2026-04-15 comes before 2026-05-01. No other format does this.
• It's unambiguous. 04/09/26 could be April 9 or September 4 depending on who's reading it. 2026-04-09 has exactly one interpretation.
• It's short. Ten characters. Works everywhere.

Anything dated, like meeting minutes, financial reports, newsletters, event pages, or contracts, should lead with the ISO date.

Use descriptive, consistent names

After the date, use a short descriptive name. Here are some examples.

• 2026-04-09-board-minutes.pdf
• 2026-04-09-treasurer-report.pdf
• 2026-04-09-agenda.pdf
• 2026-04-14-membership-renewals.xlsx
• 2026-04-15-annual-event-flyer-v1.pdf

There are a few rules for the descriptive part.

• Lowercase. Easier to type, consistent, and avoids case-sensitivity issues on some systems.
• Hyphens instead of spaces. Some systems handle spaces badly. Hyphens are safer and more readable than underscores or run-together words.
• Include the type of document. "Minutes," "agenda," "report," "flyer." This helps when searching.
• Be specific enough to be unique. 2026-04-09-minutes.pdf is fine if the context is clear. 2026-04-09-board-minutes.pdf is better if there might also be committee minutes.

Pick words that age well

A few common words become traps over time. Better alternatives are usually easy.

• Use version numbers instead of "final." As soon as "final" is in the name, someone will edit it and save a newer version. Then you have final, final v2, truly final, and nothing is actually final.
• Use dates instead of "new," "current," or "latest." "New membership form" is useful for about a week. Then it's the old one. Dates stay accurate.
• Rename anything that starts with "Copy of" as soon as you save it. Otherwise you end up with Copy of Copy of Budget 2024 copy.xlsx which means nothing to anyone.

Use version numbers when it matters

For documents that go through drafts before being finalized, use simple version numbers: v1, v2, v3. Or dates for each version. Or both.

Example: 2026-04-09-event-flyer-v3.pdf.

Once a document is final and approved, remove the version number and replace it with the approval date if that's meaningful. Or just leave the version number on and don't worry about it. That's clearer than "final."

Use ALL-CAPS tags for special status

When a document's status matters, place an ALL-CAPS tag right after the date in the filename. Two common cases come up.

• DRAFT. Not yet approved. Example: 2026-04-09-DRAFT-board-minutes.pdf. Delete the DRAFT file once the final is approved, so there's only one authoritative version.
• EXECUTIVE. From or for executive session, and not for public viewing. Example: 2026-04-09-EXECUTIVE-session-notes.pdf. Unlike DRAFT, this tag stays on the file permanently. It's a signal to every current and future board member that the document isn't meant to be shared outside the board.

Putting the tag right after the date keeps it visible at a glance and groups same-status files for the same meeting together when the folder sorts alphabetically. All the EXECUTIVE files from one meeting end up next to each other, separate from the regular ones.

The ALL-CAPS styling is the point. Anyone glancing at the folder sees the status immediately. It's also another reason to keep the rest of the filename lowercase. The tag only stands out if nothing else around it is capitalized.

Organizing folders

File naming only goes so far. A good folder structure is the other half.

For most clubs, a structure organized by year and type works well.

``` Club Documents/ Meeting Minutes/ 2026/ 2026-01-15-board-minutes.pdf 2026-02-19-board-minutes.pdf ... 2025/ ... Financial Records/ 2026/ 2026-Q1-financial-report.pdf 2026-04-bank-statement.pdf ... Membership/ 2026/ ... Events/ 2026/ 2026-annual-gala/ ... Governance/ bylaws-2024.pdf privacy-policy-2025.pdf ... ```

This structure follows a few principles.

• Top-level folders for categories, not years. Years go inside categories, not the other way around. This way, related things stay together.
• One category per folder. Don't create a folder called "Miscellaneous" or "Other." It becomes a dumping ground that nobody ever cleans out.
• Archive old years. After a year or two, move completed year folders into an Archive subfolder. This keeps the active folders uncluttered.
• Keep evergreen documents at the category root. Bylaws, privacy policies, long-term contracts go in Governance/ directly, not in a year folder.

A one-page cheat sheet

If you want to make this stick, write a short cheat sheet, literally one page, that describes your club's naming and folder conventions. Keep it in the top of the shared drive, where every board member can see it. New board members read it when they start. Existing board members can refer to it when they're not sure.

Here's what to put on the cheat sheet.

• The date format (ISO)
• The naming pattern for files (lowercase, hyphens, descriptive)
• The folder structure
• A few examples
• Where to put things that don't fit

This is a 20-minute project that saves many hours over time.

Retroactive cleanup

If your club's current files are a mess, don't panic. You don't need to rename everything at once.

Here's a reasonable approach.

1. Set up the new naming and folder conventions going forward. New files follow the new rules from day one.
2. Clean up the current year as you go. When you touch an old file for any reason, rename it to the new convention.
3. Do a one-time cleanup of the most important files. Meeting minutes, bylaws, policies. An hour or two of focused effort can get these into shape.
4. Leave the rest. Old drafts, obsolete documents, and things nobody looks at anyway aren't worth renaming. If they're not worth keeping under the new rules, they probably weren't worth keeping at all.

Where Clubistry fits in

Clubistry's Document Library is where final, public and members-only documents live, in their finished versions. Works-in-progress and internal administrative documents stay on the club's shared drive. That division reflects the draft-then-publish flow: drafting happens on the shared drive, and once a document is final, it gets uploaded to the Document Library.

Every file uploaded to the Document Library gets two names: the filename you upload (following the conventions in this article) and a display name that members see when they find the document. The display name follows similar logic but allows caps and spaces, since it's meant to be read by people, not parsed by file systems.

Dates still lead in the display name, in the same ISO format, when the document is tied to a specific moment.

• 2026-11-04 - Board Meeting Minutes
• 2026-03-25 - Specialty Meal Order Form

But evergreen documents that get updated over time should not be dated in the display name.

• Club Bylaws
• Privacy Policy

The distinction matters because each Document Library entry has a stable URL slug. Replace the attached file on an existing entry, and the slug stays the same, so any link to that entry keeps working. Evergreen documents benefit from that. A link to Club Bylaws on a page elsewhere on the site, in a welcome email, or on another website continues resolving to whatever the current version is. Dated entries don't need this protection. Each meeting gets its own entry, and nobody's linking generically to "the minutes."

Good file naming isn't glamorous. But it's one of those quietly important things that makes every other piece of club administration easier. A little discipline now saves future board members from inheriting a mystery.