A File Naming Convention for Construction Documents (With a Template)

Ask ten people on a project to name the same drawing and you'll get ten filenames. Multiply that by thousands of files and a few years, and search becomes impossible. A shared naming convention is the cheapest, highest-impact document habit a construction or facilities team can adopt.

What a good convention does

A filename should answer three questions at a glance: what sheet is this, which version, and when. It should also sort correctly on its own, so a folder of files falls into drawing order without anyone lifting a finger.

The components that matter

Include these, in this order:

• Sheet number — first, so files sort in drawing order (not alphabetically by title)
• Sheet title — human-readable description
• Revision — so the current version is never in doubt
• Date — in ISO format (YYYY-MM-DD) so it sorts chronologically

A template you can copy

[SheetNumber] - [Sheet Title] - [Revision] - [YYYY-MM-DD].pdf

Examples:
A-101 - First Floor Plan - Rev 2 - 2026-05-14.pdf
E-201 - Second Floor Power Plan - Rev 3 - 2026-06-02.pdf
M-301 - Rooftop Mechanical Plan - Rev 0 - 2026-04-28.pdf

The rules that keep it clean

• Zero-pad numbers where it helps sorting (A-005, not A-5).
• Use ISO dates only. 2026-06-02 sorts correctly; 6/2/26 never will.
• Pick one delimiter (a hyphen with spaces reads well) and stick to it.
• Never bury the version in words like final, final2, or USE-THIS. Use an explicit Rev N.
• Avoid special characters (# % & { }) that break links and some systems.

If two careful people would still name the same file differently, your convention isn't specific enough yet. Write it down and give real examples.

Naming is only half the job

A perfect filename still can't tell you "show me every Level 2 electrical sheet across all buildings." That's what metadata is for. The best setup pairs a naming convention with tags — entity, site, building, floor, trade — so files are both self-describing and filterable. The name handles browsing; the metadata handles searching.

Enforcing it without nagging

Conventions decay the moment enforcement depends on willpower. Two ways to make it stick:

1. Templates and examples posted where people upload — not a buried wiki page.
2. A system that captures metadata at upload and can auto-file documents based on it, so the structure is applied automatically instead of hoped for.

ArchiveView captures metadata as documents come in, auto-creates the right folders, and keeps every revision in one place — so your naming convention is enforced by the workflow, not by reminders. Start a free trial or see it in action.