VASCOM TECHNOLOGY AUTOMATION CO., LTD
Home › News › Name Files and Folders So You Can Find…

Name Files and Folders So You Can Find Them Six Months Later

Learn to name files with consistent dates, document types, subjects, and versions, organize folders around how colleagues search, and avoid ambiguous labels so your team can retrieve the right documents months later.

In many businesses, files are not lost; they are buried in folders that only one person knows how to navigate. When the team needs to retrieve a signed contract or an acceptance record, everyone has to open file after file to guess which version is correct. Names such as “official-version”, “new-final”, or “last-edit” only make sense when the file is created. A short convention, applied consistently, is often more useful than buying another tool while still letting each person use a different naming style.

Use one shared convention: date, document type, subject, version

A filename should answer four questions: what date the document relates to, what type of document it is, what subject it concerns, and which version it is. Businesses can use the structure date_document-type_subject_version, with underscores separating the components and hyphens used within each component.

  • Date: use the yyyy-mm-dd format so that the filename order also matches the chronological order. Agree on whether this is the issue date, signing date, or creation date; do not let each person interpret it differently.
  • Document type: use a short list such as contract, record, report, and proposal. Avoid writing “rpt” sometimes and “report” at other times.
  • Subject: enter the project, department, or partner code according to the agreed list. Do not use nicknames or abbreviations that only a small group understands.
  • Version: use v01, v02, and v03. Once a document is approved, use the status issued instead of continuing to create “final” versions.

For example: 2026-04-18_contract_supplier-a_v03.docx. From this name, the person who later takes over the work can identify the document before opening it. More importantly, the date and version must be updated in the same way; if only the end of the filename follows the convention, searching will still be difficult.

What not to include in filenames

A filename is an identifier, not a place to record the entire work history. The more information it contains, the harder it is to read and the more likely users are to create new variations. Content that requires a lengthy explanation should be placed in the document, the system’s notes field, or a separate tracking table.

  • Do not use vague statuses such as latest, standard, ok, final-2, or urgent-edit.
  • Do not include long sentences, messages to colleagues, editor names, or temporary processing milestones.
  • Do not put personal identification numbers, account information, payroll data, or other sensitive content in filenames.
  • Limit spaces and special characters that may cause errors when uploading, syncing, or creating links.
  • Do not repeat information already included in the path, such as adding the project name to a file when the parent folder already identifies it clearly.

If teams need to distinguish drafts being edited from released versions, they should use a consistent status or separate folders. Do not turn a filename into a string of notes such as “revised-based-on-this-mornings-feedback”.

Arrange folders the way other people will search

A filename convention cannot fix an overly deep folder tree. Project records can be organized by project → record type → year, while internal documents can be organized by department → area of work → year. Each area should use only one primary axis. Avoid dividing some folders by month, others by the person in charge, and still others by customer.

  • Make the root folder’s scope clear, for example project-a or accounting-department.
  • Use stable groups at the next level, such as contract, acceptance, and report.
  • Only create an “archive” folder for rarely used records; do not use it to hold every file whose proper location is unclear.
  • Place a short guide in the root folder covering the convention, the list of abbreviations, and the person responsible for maintaining them.

Before creating a new branch, consider the perspective of the person taking over: will they search by project, document type, or date? That answer is more reliable than the folder creator’s personal habits.

Move old folders to the new convention without disruption

Do not start with bulk renaming. This can break links, affect synced copies, and cause people who are actively working to open the wrong documents. Work through small scopes, with checks before and after each change.

  1. Choose an active project to pilot the convention. Confirm the person in charge, the file scope, and the implementation date; pause individual renaming efforts within that scope.
  2. List the current paths, create a backup, and check access permissions. Add a mapping table with the old name, new name, basis for the selected date, version, and processing status.
  3. Check for duplicate files before renaming. Compare their content and edit history, not just their names or sizes; retain the necessary versions and clearly mark the version that will remain in use.
  4. Prioritize documents in use and the latest version of each record. For locked records or records needed for audits, retain the originals and use the mapping table if renaming carries risks.
  5. After the migration, test opening files from familiar links, shortcuts, and synced devices. Update the affected paths before applying the convention to the next scope.

Old, rarely used folders do not all need to be cleaned up in one pass. They can be moved to an archive area, with the mapping table retained, and standardized only when they are needed again.

Actions to take now

  1. Choose a small project and rename the active files using the four agreed components.
  2. Write the convention on one page, with correct examples, incorrect examples, and a list of permitted codes.
  3. Assign one person to perform periodic checks and address filenames that deviate from the convention before the new approach spreads.

A good convention helps a new team member find the right document without having to ask their predecessor. When moving documents into management software, VASCOM can work with the business to review this foundation first, so the data remains clear and easy to hand over later.

Tips and how-to Talk to VASCOM
More news

Keep reading

Zalo ☎
VASCOM
Call 0822.577.579 Get a consultation