Onboarding

Set a shared drive naming convention for a virtual assistant

A naming convention that puts the client, the document type, and the date in a fixed order so a virtual assistant can file and retrieve a file without opening it.

By OnboardingEmployees editorial team | | 6 min read

Set a shared drive naming convention for a virtual assistant
On this page
  1. Decide what the name must reveal
  2. Put the date in one fixed position
  3. Separate working files from client deliverables
  4. Handle versions without the word final
  5. Publish the convention where files are created
  6. Audit names at the end of the first month
  7. Key takeaways
  8. Related reading

A shared drive naming convention is a small rule that saves a large amount of search time. When every file follows the same order, a virtual assistant can find a document by reading the folder list instead of opening files one by one. The rule also makes handovers easier because a colleague can predict where a file should sit. A convention that is too elaborate will be abandoned, so the first version should stay short.

Decide what the name must reveal

Choose the three or four facts a reader needs before opening a file. Most teams need the client or project, the document type, and the date. Some teams also need the status, such as draft or approved, but that can create stale labels. Start with the smallest set that still lets someone tell two files apart.

Write the order as a fixed pattern and give one real example beside it. A pattern such as client-document-date is easier to remember than a paragraph of rules. The example should use a current client name and a document the team recognises. A rule with no example is open to interpretation on the first busy day.

Decide how to write names that contain spaces, ampersands, or accented letters. A consistent separator prevents two files from looking identical on a system that treats those characters differently. The convention should say whether to use hyphens, underscores, or no separator at all. Pick one and use it in every example.

Put the date in one fixed position

Choose one date format and place it at the end of the name so files sort predictably. A format such as year-month-day avoids the confusion between day-first and month-first teams. The date should be the document date, not the date the assistant uploaded it. Upload dates change when a file is copied and rarely describe the content.

Explain how to date a document that covers a period rather than a single day. A monthly report might use the last day of the month, while a contract might use the signature date. The convention should name the rule for each common document type. A file dated by guesswork will sit in the wrong place in the list.

Record what to do when a document has no date, such as an undated policy or a template. Use a fixed word such as undated in the date position rather than leaving the space empty. An empty position breaks the order and makes the file hard to sort. The convention should include this case in the example list.

Separate working files from client deliverables

Give working files a clear marker so they cannot be mistaken for the version a client should receive. A marker such as working or internal at the end of the name is enough when everyone follows it. The marker should never appear on a file that has been approved for sharing. A client who receives a file labelled internal will question the process.

Keep the approved deliverable in a separate folder that matches the client-facing structure. The assistant should not have to decide at upload time whether a file is ready. A clear folder boundary makes the naming rule easier to apply. It also reduces the chance that a draft is sent by mistake.

Decide who may rename a file after it has been shared with a client. Renaming a shared file can break a link the client already has, so the rule should require a check before any change. The convention should name the person who approves a rename. A simple approval step protects both the client and the assistant.

Handle versions without the word final

Replace the word final with a version number or an approval date. A folder with three files called final is a folder where nobody knows which one is current. A number such as v02 or a date makes the order visible at a glance. The convention should say whether the number belongs before or after the document type.

Explain how a new version is created so the old one is not silently overwritten. The assistant should either copy the previous file or rely on the system's version history, depending on what the team has agreed. The convention should name the method in one sentence. A recovered old version is only useful if the team can find it.

Retire old versions to an archive folder on a stated schedule. Keeping every version in the working folder makes the current file harder to see. The convention should say when the archive happens and who checks it. A short archive rule keeps the naming convention usable over time.

Publish the convention where files are created

Put the convention in the same place as the folder structure, not in a separate policy library. A one-page guide pinned to the drive is more likely to be read than a document three levels away. The guide should show the pattern, three examples, and the archive rule. It should also name the person to ask when a case is unclear.

Include the convention in the assistant's first-week walkthrough and ask them to file one real document while the manager watches. A practical test shows whether the rule is clear enough to use. Correct the first file before the assistant files twenty more. The walkthrough should take minutes, not a training session.

Add a short note to the team about any change to the convention and the date it starts. A silent change produces two naming styles in the same folder. The note should say whether old files will be renamed or left as they are. A clear transition prevents a cleanup project later.

Audit names at the end of the first month

Sample twenty files from across the drive and check each one against the pattern. Record the number that match and the most common mistake. A single repeated mistake usually means the rule needs one clearer example. A wide spread of mistakes may mean the convention is too complex.

Ask the assistant which part of the convention was hardest to apply. The answer may point to a document type that has no clear name or a client whose files arrive with inconsistent dates. Adjust the rule for that case rather than adding a general exception. A specific fix is easier to teach than a longer policy.

Set the next audit date and name the owner before closing the review. Drives drift when a new client arrives or a team changes tools. A quarterly check keeps the convention close to real use. The owner should be the person who can approve a rename across the shared drive.

Key takeaways

Choose the few facts a reader needs before opening a file and put them in a fixed order. Use one date format and place it where it sorts predictably. Show the pattern with three real examples. A short convention is more likely to survive a busy week.

Mark working files so they cannot be confused with client deliverables. Replace the word final with a version number or approval date. Move old versions to an archive on a stated schedule. A clear boundary between draft and deliverable protects the client relationship.

Publish the convention next to the folder structure and test it during the first week. Sample twenty files at the end of the month and fix the most common mistake. Set the next audit date and name the owner. A convention that is never checked becomes a suggestion.

Continue building the workflow

Related support: onboarding operations support, contact us. The U.S. National Archives - Records management provides guidance on managing and organizing government records.