Create a Document Naming Standard for the Executive Office

Search fails before the document is lost

An executive assistant rarely loses a file outright. The more common failure is finding five versions of it, none of which says which one the executive signed. Another assistant opens the shared drive, sees "Board deck final final v3" and "Board deck final reviewed" side by side, and has to interrupt someone to learn which file is current. The cost is not just a few wasted minutes. It is the risk of sending the wrong version to a director or attaching an old schedule to a client email.

A naming standard fixes that problem before it starts. It gives every document a predictable identity: what it is, who it belongs to, when it was created, and where it sits in the approval sequence. The standard does not need to cover every file on the drive. It needs to cover the documents that people search for under pressure, which usually means board materials, contracts, travel records, briefings, and anything with a version history.

Build the name from stable fields in a fixed order

Start with a short project or subject label that a person would actually type into search. Follow it with the document type, the owner or audience, and a date in an unambiguous format. End with a version marker that reflects the approval state, not a personal habit. A workable pattern is subject, document type, audience, date, and status, separated by hyphens so the name remains readable in a list view.

For example, a board finance review for a March meeting might read "fy26-budget-board-review-cfo-march-approved." The exact words matter less than the order. Subject first, because that is what people remember. Type second, because it distinguishes a memo from a deck from a signed agreement. Date third, so files sort chronologically within a subject. Status last, because it is the field most likely to change and the one people most often forget to update. Avoid spaces, ampersands, and punctuation that behaves differently across systems, and never rely on a folder name to carry the meaning.

Make version status visible at a glance

Version numbers are useful only when everyone agrees what they mean. Define a small set of states: draft, review, approved, signed, superseded. A file in review is not the same as a file approved for distribution, and a signed contract should never share a name with the draft that preceded it. Put the state in the filename and, where the tool allows it, in a status column that can be filtered.

Do not use "final" as a status. It invites "final v2" and "final actual" within a week. If the document is approved, say approved. If it has been replaced, say superseded and move it to an archive folder rather than leaving it beside the current file. The document expiry review routine should catch files that have passed their useful date, but a clear status field makes that review much faster. When a document is signed, record the signature date and keep the executed copy separate from the working draft.

Tag sensitive files without exposing the content

Some executive documents should not be discoverable by title alone. A file named for a pending acquisition, a personnel matter, or a legal dispute can leak sensitive information to anyone who can browse the folder. Use a neutral project code for those files and keep the key to the code in a restricted location. The code should be meaningful to the people who need it and opaque to everyone else.

That approach only works if access control is real. A naming convention cannot protect a file that sits in a folder the whole company can open. Pair the convention with the access boundary rules for the executive office, and review who can see sensitive folders when someone changes roles. The National Archives' records management guidance is a useful reference for thinking about records by function rather than by folder whim, even though a private company is not bound by the same schedule.

Clean up the existing drive before enforcing the rule

A new standard announced on Monday will collide with years of inconsistent names on Tuesday. Start with a bounded cleanup. Pick the folders the team uses most often, list the files that are clearly current, and rename those first. Move duplicates and superseded versions into an archive folder with a note explaining the change. Do not attempt to rename the entire drive in one pass, because the team will abandon the effort halfway through.

Set a cut-off date after which every new file must follow the standard. For older files, add a short index that maps the old name to the new one where the document still matters. Keep the index in the same folder as the current files so it is found naturally. If a document is referenced in a contract, a board minute, or a regulatory filing, preserve the original name in the record and add the new name as a cross-reference rather than rewriting history.

Check the standard with a search test

The test of a naming standard is whether a colleague can find the right file without asking. Once a month, pick three documents at random and ask someone outside the immediate team to locate the current version using only the shared drive search. Time the search and note what went wrong. If the person finds a draft first, the status field is failing. If they cannot tell which client the file belongs to, the subject field is too vague.

Use those results to simplify the standard rather than add more rules. A convention with six fields that people actually use beats a perfect taxonomy that they ignore. Write the rule in one page, put it beside the folder structure, and include it in onboarding. The handover record should point to the naming rule so a temporary assistant does not create a parallel system. For help setting up a document practice that survives staff changes, talk to our team.