File naming conventions and version control for office documents

A simple suggested file naming pattern

Try Reference_Subject_YYYY-MM-DD_vNumber_Status.extension. For this suggested office convention, underscores separate the fields and hyphens separate words within a field. This is a starting point, not a universal rule: follow any existing organisational or project convention first, and test a sample name in the systems where it will be stored and shared.

Use only the fields your team needs. Where your approved document system already manages version history and review status, follow that process rather than saving a new standalone copy after every edit. Agree which identifiers belong in the filename when a document is exported or issued outside that system.

The reference identifies the document throughout its life. For example, OFF-CHK-001 could mean office, checklist, sequence 001. Keep that reference when the wording or approval status changes. Use a short subject that a colleague can recognise without opening the file; avoid personal details or confidential information in the name.

Decide what the date means before using it. In these examples it is the date that this version was prepared, written as year-month-day. It is not automatically the approval date, meeting date or reporting period. Record those separately where needed, and use a subject such as October-report when the period matters. Do not change the date merely because somebody downloads or copies the file.

The version distinguishes edits; the status explains whether the file is Draft, For-review, Approved or Superseded under your agreed rules. Agree who can change each status and what Approved permits. A filename records a decision; it does not confer approval authority or replace the review evidence in your register.

Three fictional office examples

OFF-CHK-001_Supplier-onboarding_2026-10-08_v0.2_For-review.docx is a fictional checklist awaiting its operations review. OFF-CHK-001 remains its identity; v0.2 identifies the working edit, and For-review tells colleagues that approval is still outstanding.

OFF-RPT-002_October-report_2026-10-08_v0.1_Draft.xlsx is a fictional monthly office report. October-report describes the reporting period, while 2026-10-08 records when this draft was prepared.

OFF-PLN-003_Workshop-plan_2026-10-07_v1.0_Approved.pdf is a fictional workshop plan whose appointed reviewer has approved that revision for the agreed use. The register records the decision and points to this file. All three examples are invented, not client evidence.

Latest edit is not the same as approved revision

For a small office folder, you might use v0.1 and v0.2 for drafts, v1.0 for the first approved revision, v1.1 for a proposed edit and v2.0 for the next approved revision. Write down that local rule before using it; other teams may use different numbering. In this scheme, v1.1 can be the latest edit while v1.0 remains the approved revision for use.

Record both positions clearly: the register identifies the approved revision, its location and review evidence, alongside any working revision awaiting a decision. When the reviewer approves the replacement, update the register and identify the earlier revision as superseded under the existing filing rules. Do not silently overwrite the approved copy. A recent modified timestamp or a higher version number alone is not evidence of approval.

Recover from final-final filenames

If a folder contains final, final-final and final-final-revised files, pause further issue of the affected document and ask its owner to reconcile them. Compare the contents, references and recorded review decisions. Confirm with the appointed reviewer which revision is approved and which contains unapproved changes; do not simply choose the most recently modified file.

Record the outcome in the register, including any unresolved approval gap. Once confirmed, give the controlled copy an agreed name and location, preserving the originals and their history under the organisation's existing rules. Check who uses the old links before moving or renaming anything, update affected references and test access. A tidier name should not leave a colleague following a broken link.

Roll out in one small folder

Choose one active folder and a named owner. Write a short convention covering reference meanings, date meaning, versions, statuses and reviewers. Try it on the next few new documents, check that colleagues can find the approved copy and review any confusing names together.

Leave older files and established links in place unless there is an agreed reason to migrate them. If selected files need renaming, coordinate the change with their owners, update register locations and affected links, then test them using authorised access. Keep history under the existing rules rather than mass renaming or deleting it. Extend the convention only once the small-folder routine is workable.

Keeping files and registers current

If keeping files and registers current needs regular support, Attenta Partners can provide managed file and register upkeep within agreed systems and scope. Agree the documents covered, update triggers, checks and handover outputs; your appointed reviewers retain approval authority. The related document-control service page explains what that support includes.

Sources and scope

The University of Edinburgh's naming-conventions and version-number guidance and the US National Archives Bulletin 2015-01 Appendix B were checked on 8 October 2026. They are institutional examples, not universal office rules. They illustrate consistent naming and version identification, but their separator conventions differ. The pattern and fictional examples here are our own suggestions, not quotations or prescribed templates. Your organisation's systems, project requirements and approval rules determine what is suitable.