Document Naming Standards for Better Governance

The way an organisation names its files and folders reveals almost everything about its information governance maturity. Inconsistent file names create findability problems, version control failures, data loss risks, and compliance gaps. A well-designed naming standard, on the other hand, is one of the highest-return governance investments any organisation can make.

Why File Naming Is a Governance Issue

File naming is not just an administrative preference. It directly affects:

• Findability: If staff cannot find the document they need, they create a duplicate or make a decision with incomplete information.
• Classification: A file name that describes its content enables automated classification and sensitivity labelling.
• Retention: Without knowing when a document was created or what it relates to, applying retention schedules is nearly impossible.
• POPIA compliance: Knowing what personal information you hold, and where, requires documents to be identifiable without opening them.
• Audit readiness: Regulators expect organisations to locate specific records on demand. A chaotic file system makes this extremely difficult.

The Problem With Most File Naming Systems

In practice, most organisations have no naming system at all. Employees develop their own conventions, leading to folder structures containing files like:

• Final report v3 ACTUAL FINAL.docx
• Copy of Copy of Invoice.xlsx
• JohannesCV (2).pdf
• URGENT - please review.msg
• Untitled document (4).docx

These names tell you almost nothing about the document’s content, date, author, or status. Multiply this across thousands of files and a shared drive becomes ungovernable.

Elements of a Good File Name

A well-designed file name answers these questions at a glance:

1. What is it? (Document type — Invoice, Contract, Report, Policy)
2. Who is it about? (Client name or reference, project code, department)
3. When was it created or applies to? (Date in YYYY-MM-DD or YYYYMM format)
4. What version or status? (Draft, Final, Signed, Archived)

A naming convention that incorporates all four elements might look like:

[DocumentType]_[ClientRef]_[YYYY-MM-DD]_[Status].ext

For example:

• Contract_SMITHCO_2025-04-01_Signed.pdf
• Invoice_SMITHCO_2025-05-31_Final.xlsx
• PolicyReview_Internal_2025-06-01_Draft.docx

Choosing a Date Format

Always use ISO 8601 format (YYYY-MM-DD). Never use DD/MM/YYYY in file names. The reasons:

• Files sort chronologically when the year comes first.
• Slashes are not allowed in file names on most operating systems.
• DD/MM/YYYY causes ambiguity when sharing across different regional settings.

Choosing a Delimiter

The most universally compatible delimiter choices are:

• Underscore (_): Safe on all operating systems, visible in most fonts, widely used in technical contexts.
• Hyphen (-): Preferred by some web standards (Google recommends hyphens in URLs).

Avoid spaces in file names. Many systems still handle spaces poorly, particularly on network drives and when sharing across platforms. Use underscore or hyphen instead.

Version Control

Poor version control is one of the most common causes of costly mistakes. A clear versioning convention prevents working from an outdated document:

• Use _v01, _v02, etc. for draft versions
• Use _FINAL for the approved final version
• Use _SIGNED for executed/signed documents
• Use _ARCHIVED for superseded documents moved out of active storage

Building a Naming Standard for Your Organisation

A practical implementation process:

1. Agree on the standard — Get input from the departments that will use it. A standard no one follows is worthless.
2. Document it — Write it down in a one-page reference guide. Post it where staff will see it.
3. Train all staff — Cover the standard in onboarding and annual refreshers.
4. Automate where possible — Templates with pre-populated naming, document management systems with naming enforcement, or browser extensions that flag non-compliant names.
5. Audit periodically — Run a quarterly check on new files to measure compliance rates and identify problem areas.

Folder Structure Matters Too

Even perfect file names become useless in a disorganised folder structure. A tiered approach works best:

• Level 1: Department or function (Finance / Legal / HR / Operations)
• Level 2: Client, project or year
• Level 3: Document type (Contracts / Reports / Correspondence)

Limit folder nesting to 4–5 levels maximum. Deeper structures become navigation nightmares.

The Governance Dividend

Organisations that implement and maintain good naming standards consistently report:

• Significantly reduced time spent searching for documents
• Fewer “lost” files and version conflicts
• Easier compliance with POPIA subject access requests
• Better audit readiness
• Lower storage costs as outdated documents are more easily identified and deleted