Back to Blog Home

File naming convention for a small team: a standard you can copy, and a weekly check in Slack that keeps it

A team workspace with folders such as General, Company, Design and Product, and a style guide page open

A file naming convention survives only if one person gets a weekly list of the files that break it. Write the pattern on one page, put the field you browse by first, and decide who may move files before anyone renames anything, because in a Google shared drive every new member can move or delete any file by default. Put a version number in a name only for files that leave Drive, because Drive's own version history covers native Google files, and a v03 copy of a Google Doc gives you two live documents. Then hand the list to one named person.

Most small teams have agreed a file naming convention at least once. Someone wrote it in a doc, everyone nodded, and six weeks later the shared Drive holds Contract FINAL v2 (1).pdf, three undated invoices called invoice.pdf, and a client folder nobody can find. Then the questions start in Slack: which proposal is the one we sent, where is the signed copy, is this the latest price list. Each one costs a few minutes of someone else's attention, and the wrong version sometimes reaches a client.

The convention below is for a team of 5 to 100 people and fits on one page. It covers the three file types that cause the most trouble, client files, contracts and invoices, and it names who checks the names every week without a document management system or a hire to tidy folders.

A file naming convention you can copy

Here is a convention sized for a small services firm, agency or consultancy. Change the examples to your own clients and keep the shape.

File typePatternExample
Client working filesclient_project_description_vNNacme_website-refresh_sitemap_v03.docx
Proposals and quotesclient_proposal_YYYY-MM-DD_vNNacme_proposal_2026-10-14_v02.pdf
Signed contractsclient_contract-type_YYYY-MM-DD_signedacme_msa_2026-10-20_signed.pdf
Invoices you sendYYYY-MM-DD_invoice_NNNN_client2026-10-31_invoice_0142_acme.pdf
Bills you receiveYYYY-MM-DD_bill_vendor_description2026-10-05_bill_hostco_october-hosting.pdf
Meeting notesYYYY-MM-DD_meeting_topic2026-10-27_meeting_q4-planning.docx

The rules underneath the table:

  • Lowercase, with underscores between fields and hyphens inside a field. website-refresh is one field; the underscore tells you where the next one starts.
  • Dates as YYYY-MM-DD. ResourceSpace recommends a consistent date format so files sort by date. The hyphens make it readable; the order is what matters.
  • Version numbers with two digits, on files that leave Drive. v01 to v09 sort correctly before v10; this is Virtual Cabinet's leading zeros rule applied to versions. The word final is banned, because there is always another final.
  • signed only on the countersigned copy. Drafts of a contract stay in the working pattern with a version number.
  • No spaces and none of the special characters ResourceSpace lists. They cause trouble when files move between systems, which is why both vendor guides rule them out.
  • Client names come from one list. Write the short name of each client once, at the top of the convention page, so acme, acme-corp and acmeinc do not all appear.

Put a version number in the name only for files that leave Drive. A native Google Doc, Sheet or Slide keeps its earlier versions in Drive's version history, where you can also name the version you sent, while a file called v03 invites people to make a copy and edit two live documents. An uploaded file such as a Word document or a PDF is different: Drive may permanently delete its older versions after 30 days or once 100 newer versions exist, unless someone pins one with Keep forever. So the proposal you sent a client carries its version in the name, and the Google Doc you drafted it in does not.

That is the whole convention. Virtual Cabinet warns that employees are less likely to follow a structure that takes too much effort or time, and a pattern with seven fields, a project code lookup and a department abbreviation table will be ignored by the third busy week. If your version runs past one page, cut it until it fits.

What goes first in a file name

The first field decides how a folder sorts. Put the field you browse by first: the date for records you keep in time order, such as invoices and meeting notes, and the client name for files you open by account. In the table above, invoices and bills start with the date because you look for them by period: everything from October, the bill from the fifth. Client working files, proposals and contracts start with the client because you open them by account: everything for Acme. This is a recommendation built from how sorting works. A folder lists names alphabetically, so the first field becomes the grouping you see.

The rule also tells you what to do with a file that does not fit. Ask how the next person will look for it. If the answer is "by when", the date goes first. If it is "by who", the client or vendor goes first.

Before you rename anything, decide who may move files

A shared drive in Google Workspace has a default that matters here. The Google Workspace Learning Center page on shared drives says new members are Content managers by default, and that role can upload, edit, move, or delete all files. So in a shared drive where everyone was added with the default role, anyone can drag a client folder into the wrong place. Decide who may move files before you decide how to name them.

Files get moved as well as misnamed, and a weekly check will keep flagging files that someone merely dropped in the wrong folder. In an Ask HN thread about managing files, the author said the problem gets harder when folders are shared between employees and actively used, and that they had yet to see a team whose OneDrive or Google Drive was organised well enough for people to find things easily (the Ask HN thread). One reply called it a social problem: push tagging rules hard enough and people start a new dumping folder instead. These are one author's and commenters' reports, not a survey, but they match what most owners see.

The same Google page offers two tools. If someone needs one file, you can share only that item rather than making them a member, and folders inside a shared drive can be given limited access so only the drive's managers and the people you add can open them. Moving folders between shared drives needs your administrator, so plan the top level of folders before people start filing into it.

For a small firm a workable setup is:

  • one shared drive per area that has different readers, for example Clients, Finance and Company;
  • inside Clients, one folder per client using the same short name as the convention page;
  • one or two people as Managers of each drive, and everyone else added with a role that matches what they need to do, checked rather than left at the default.

Keep the convention alive with a weekly list

Nobody owns the check. Virtual Cabinet's guide to file naming conventions for businesses advises regular checks that employees stick to the convention, especially in the first phase, and the ResourceSpace guide to file naming conventions advises reviewing the convention as teams grow. Neither says who does that work. In a 15 person company there is no records manager. The founder means to look, gets busy, and the folder drifts.

A naming convention fails in a small team because nobody is assigned to check it, so the check should be a scheduled weekly list that a person acts on, not a rule that lives in a document. The rule tells people what to do. The list tells one person, every Monday, exactly which files to fix. That is a recommendation, but it follows directly from what both vendors say: the check is the part that keeps the rule alive, and it is the part with no owner.

Someone has to look at the folders every week, list what breaks the pattern and fix it. In many small firms that is the job they plan to hire a virtual assistant for. If your team works in Slack, the Kipwise agent can do the listing part.

Here is what the Kipwise agent's Google Drive connection does today. It searches Google Drive, lists a folder and reads Docs, Sheets, Slides and text files with the asking person's own Drive access, so it only sees files that person can open. When asked, it can create a folder, rename or replace a text file, move a file, or move a file to the Trash, and each of those changes waits for an Approve card first. Editing is a separate connection from reading, so a teammate who only searches never has to grant it. Scheduled tasks are created in plain language, need approval once, and post their results in the channel with the same permissions as the person who set them up.

An illustrative thread (made up, to show the shape):

Owner: @Kipwise here is our naming convention [link to the one-page doc]. List the files in Clients/Acme whose names do not match it, and suggest a correct name for each.

Agent: 6 of 41 files do not match. Acme proposal final.pdf has no date or version; suggested acme_proposal_2026-10-14_v02.pdf based on the date in the document. invoice.pdf is an invoice and belongs in Finance; suggested 2026-10-31_invoice_0142_acme.pdf ...

Owner: Good. Run this check every Monday at 9:00 for every client folder and post the list here.

Agent: [Approve card for the scheduled task]

From then on, the list arrives each Monday in the channel. The weekly run only reads and lists, so it changes nothing on its own. A person then fixes what is on the list. For a text file or a misfiled document, the person can reply in the thread, "rename the first two and move the invoice to Finance", and approve each change on its card. For files the agent cannot rename, such as a PDF, the person renames them in Drive. Either way, a person decides every change.

Keep three things with a person. Choosing and changing the convention is a team decision. Deleting files is risky, and the agent only moves files to the Trash when asked, where they can be restored. Who can see a folder is a permission choice for the drive's managers.

Pricing, for reference: the Kipwise agent is $10 per user per month or $108 a year, with a minimum of 3 users, and a trial costs $2 for 7 days or $10 for 14 days.

When the list misbehaves

The list is too long to act on. The first run on an old folder may flag hundreds of files. Do not fix history. Apply the convention to files created from today, point the weekly check at those, and rename old files only when someone opens them.

Two names for one client. If the check keeps flagging acme-corp against acme, the client list on the convention page is incomplete. Fix the page, not the files one by one.

People rename to pass the check. A file called acme_misc_2026-10-01_v01 matches the pattern and tells you nothing. Look at the description field in the weekly list now and then, and ask for a real description.

The check runs but nobody reads it. A list posted to a busy channel scrolls away. Post it to a small channel with the one person who owns fixing it, and ask them to reply in the thread when it is done.

Files outside Drive. If part of the team keeps files in OneDrive, the agent can also search OneDrive, list a folder and rename any file there when you explicitly ask. Files on personal laptops are out of reach of any shared check, which is a good reason to make the shared drive the only home for client work.

Give it four weeks. The weekly list should get shorter instead of staying the same length, "where is the latest version" questions in your client channels should fall (count them by searching Slack for "latest version" or "which file"), and new team members should file correctly in their first week using the one-page convention and nothing else. If the list stays long after a month, the convention is too complicated or the person fixing it does not have time. Cut fields first.

Other options, and when they make sense

A document management system with metadata, fixed fields and tagging, which ResourceSpace argues reduces reliance on file names, is worth it when you manage thousands of assets or have compliance retention rules. For a small team with a few hundred active files a month, a convention plus a weekly check costs less and needs no migration.

Hiring a virtual assistant to tidy folders works, and a person can also rename any file type and chase people who keep breaking the rule. Our guide to what a virtual assistant costs covers that trade-off. You can also do both: the weekly list comes from Slack, and the assistant works through it.

If you also want the convention written as a process a new hire can follow, see how to write an SOP a new hire, virtual assistant or Slack agent can follow. For naming Slack channels rather than files, the same thinking applies in our tips on organizing Slack channels. And if you want other weekly checks run the same way, Slack reminders for teams explains what /remind cannot do and what a scheduled check can.

Open the folder for your busiest client today. Write the six patterns from the table above into a one-page doc with your own client short names, and set the file naming convention for files created from tomorrow. Then set up one weekly check on that folder, give the list to one named person, and look at its length again in four weeks.

Topics

Related posts

Put an AI teammate in your Slack

Free trial on install: $2 of AI credit for 7 days on the fast model, or $10 for 14 days with all models on a paid Slack plan or for existing Kipwise customers.