Construction Industry Guide
Construction document naming standards
ISO 19650, CSI MasterFormat, and BIM-compliant naming conventions for every document type — from RFIs and submittals to closeout packages. With verified industry data, real naming templates, and honest tool comparisons.
Construction · Document Naming
A construction document naming convention encodes project code, discipline, document type, revision, and status into every filename — enabling instant search, preventing wrong-revision errors, and satisfying BIM and ISO 19650 compliance.
- ISO 19650 defines a 10-field naming code (Project–Originator–Phase–Level–Form–Discipline–Classification–Number–Suitability–Revision) mandatory on UK public projects and widely adopted internationally.
- CSI MasterFormat provides a 50-division, 6-digit classification system (e.g., 26 05 19 = Low-Voltage Electrical Conductors) used to organize documents by trade.
- Poor document naming contributes to $31.3 billion in annual U.S. construction rework — most of it preventable with consistent conventions enforced at the point of file creation.
Based on ISO 19650:2018, CSI MasterFormat 2020, and the 2018 PlanGrid/FMI rework study of 599 construction leaders.
Industry data
The cost of inconsistent document naming
Document naming failures don't just create filing headaches — they directly cause rework, scheduling delays, and financial losses.
$31.3B
Annual U.S. rework from poor data and miscommunication
Source: PlanGrid/FMI, 2018
5.5 hrs/wk
Time construction pros spend searching for project data
Source: PlanGrid/FMI, 2018
12%
Average percentage of project costs consumed by rework
Source: Construction Industry Institute
$88.69B
Global rework costs from bad data in 2020
Source: Autodesk/FMI, 2020
Real-world consequence
Real examples
Before and after: construction document filenames
AI reads each document — title blocks, project stamps, revision letters — and generates compliant filenames automatically.
scan_001.pdfPRJ-2401_RFI-0047_Column-Grid-Revision_Open.pdfDocument (3).pdfPRJ-2401_SUB-0112_Div-09_Flooring-Spec_Rev-B.pdfIMG_20260318.pdfPRJ-2401_DR_2026-03-18_GC-Turner_Weather-Clear.pdfchange order final FINAL.pdfPRJ-2401_CO-008_HVAC-Reroute_$42,500_Executed.pdfphoto_inspection.jpgPRJ-2401_PL_2026-03-15_Unit-4B_Finishes_Open-12.pdfasbuilt rev3.pdfPRJ-2401_AB_Div-22_Plumbing-Riser_Floor-03_C01.pdfInternational standard
ISO 19650 naming convention — the 10-field code
ISO 19650 (published 2018, superseding BS 1192:2007) defines the international standard for naming information containers (files) in construction projects. Mandatory on UK government-funded projects and widely adopted across Europe, Singapore, and the Middle East.
{Project}-{Originator}-{Phase}-{Level}-{Form}-{Discipline}-{Classification}-{Number}-{Suitability}-{Revision}101-WSP-CD-L2-DR-A-A40-010-S2-P01.pdf| # | Field | Length | Description | Example |
|---|---|---|---|---|
| 1 | Project | 2–6 | Project code assigned by the appointing party. Used consistently by all parties. | 101 |
| 2 | Originator | 2–6 | Organization that created the file. | WSP |
| 3 | Phase | 2 | Project stage at time of issue. SD = Schematic Design, DD = Design Development, CD = Construction Documentation. | CD |
| 4 | Level / Spatial | 2 | Spatial location. GF = Ground Floor, 01/02 = upper floors, B1 = basement, ZZ = multiple levels, XX = N/A. | L2 |
| 5 | Form | 2 | Presentation type. DR = 2D Drawing, M3 = 3D Model, SP = Specification, RI = RFI, SH = Schedule. | DR |
| 6 | Discipline | 1–2 | Technical discipline. A = Architecture, S = Structural, M = Mechanical, E = Electrical, C = Civil. | A |
| 7 | Classification | 2–4 | Uniclass 2015 or project-specific classification code. Groups documents by element or system. | A40 |
| 8 | Number | 3+ | Sequential number to ensure uniqueness within the other fields. | 010 |
| 9 | Suitability | 2–3 | Document status. S0 = WIP, S2 = Shared for coordination, S4 = Stage approval, A1 = Approved. | S2 |
| 10 | Revision | 3 | Version identifier. P01, P02 = preliminary drafts. C01, C02 = contractual/formal issues. | P01 |
2021 UK National Annex update
Suitability (status) codes
The suitability field controls document workflow through the Common Data Environment (CDE).
| Code | Category | Meaning |
|---|---|---|
| S0 | Work in Progress | Initial — should not leave authoring environment |
| S1 | Shared | Suitable for coordination between design teams |
| S2 | Shared | Suitable for information and development |
| S3 | Shared | Suitable for review and comment |
| S4 | Shared | Suitable for stage approval |
| S6 | Shared | Suitable for PIM authorization |
| S7 | Shared | Suitable for AIM authorization |
| A1–A3 | Published | Fully approved and accepted |
| B1–B3 | Published | Partial sign-off |
Discipline codes
Based on BS 1192 and Uniclass 2015. Used in field 6 of the ISO 19650 naming convention.
U.S. standard
CSI MasterFormat — all 50 divisions
MasterFormat, maintained by the Construction Specifications Institute (CSI) and Construction Specifications Canada (CSC), organizes construction work into 50 divisions using a 6-digit numbering system. Current edition: MasterFormat 2020.
{Division} {Section} {Sub-section}26 05 19 → Electrical > Common Work Results > Low-Voltage ConductorsProcurement
General
Facility Construction
Facility Services
Site and Infrastructure
Process Equipment
34 active divisions
Compliance
BIM Level 2 and ISO 19650 document requirements
The UK mandated BIM Level 2 for all centrally procured public projects in April 2016 — the world's first national BIM mandate. Now superseded by ISO 19650.
What ISO 19650 requires for naming
- All files must follow the standardized 10-field naming convention
- Naming must be agreed in the BIM Execution Plan (BEP) before project start
- All parties (architects, engineers, contractors) must use the same convention
- The appointing party assigns the project code used by everyone
- Each field must use codes from agreed code lists (Uniclass 2015 for UK)
- Suitability codes control workflow through the CDE
- Revision codes must distinguish preliminary (P-series) from contractual (C-series)
Countries with BIM mandates
- United Kingdom— Mandatory since April 2016, extended through 2030
- Germany— Federal mandate for infrastructure projects
- France— Growing adoption via Plan BIM 2022+
- Netherlands— Required for Rijksvastgoedbedrijf projects
- Nordic countries— Finland, Norway, Denmark public sector mandates
- Singapore— CORENET X initiative requires BIM for building applications
- Middle East— UAE and Saudi Arabia require BIM for major projects
Common Data Environment (CDE) states
Suitability codes in the filename map directly to CDE states:
Work in Progress
S0
Not shared — authoring only
Shared
S1–S4
Visible for coordination and review
Published
A1–A3
Formally approved for use
Archive
—
Superseded, retained for record
The process
How to implement a naming convention on your project
Five steps from kickoff to automated enforcement. Start at the BEP — don't wait until closeout to fix naming problems.
Define your naming convention at project kickoff
Document the convention in the BIM Execution Plan (BEP) before any files are created. Specify field order, separator characters, allowed codes, and revision format. Distribute to all parties — GC, subs, architects, engineers.
{Project}-{Originator}-{Phase}-{Level}-{Form}-{Discipline}-{Classification}-{Number}-{Suitability}-{Revision}101-WSP-CD-L2-DR-A-A40-010-S2-P01.pdfChoose your classification system
For international projects, use ISO 19650 with Uniclass 2015 codes. For U.S. domestic projects, CSI MasterFormat division numbers are the industry standard. Many firms use a hybrid — CSI divisions in the filename with ISO 19650 structure.
Hybrid approach works
Set up folder structure to match
Mirror your naming convention in the folder hierarchy. Top level: project code. Second level: discipline or CSI division. Third level: document type (drawings, specifications, submittals, RFIs). This redundancy ensures files are findable even if misnamed.
Enforce with automation
Connect your cloud storage (Google Drive, Dropbox) to Renamed.to. As documents arrive from subs and inspectors, AI reads each file, extracts project codes and revision letters from title blocks, and applies your naming convention automatically.
Procore and Autodesk Build workflow
Audit and maintain throughout the project
Run weekly naming audits. Flag files that don't match the convention. During closeout, a well-named document set saves days of sorting — O&M manuals, as-builts, and warranties are already organized by trade and division.
Copy-ready templates
Naming templates for every construction document type
Each pattern encodes the information needed for instant search and correct-version identification. Variables in green are extracted automatically by AI.
RFI (Request for Information)
Project code, sequential RFI number, subject description, and current status.
{ProjectCode}_RFI-{Number}_{Subject}_{Status}.pdfPRJ-2401_RFI-0047_Structural-Column-Grid-Revision_Open.pdfSubmittal
CSI division encoded, material specification, revision letter, and approval status.
{ProjectCode}_SUB-{Number}_Div-{CSI}_{Spec}_{Rev}_{Status}.pdfPRJ-2401_SUB-0112_Div-09_Flooring-Spec_Rev-B_Approved.pdfChange Order
Sequential number, scope description, dollar amount, and execution status.
{ProjectCode}_CO-{Number}_{Scope}_{Amount}_{Status}.pdfPRJ-2401_CO-008_HVAC-Ductwork-Reroute_$42,500_Executed.pdfDaily Report
ISO date for chronological sorting, contractor name, weather conditions.
{ProjectCode}_DR_{Date}_{Contractor}_{Weather}.pdfPRJ-2401_DR_2026-03-18_GC-Turner_Weather-Clear.pdfShop Drawing
Division code, detail description, revision, and ISO 19650 suitability code.
{ProjectCode}_SD-{Number}_Div-{CSI}_{Detail}_{Rev}_{Suitability}.pdfPRJ-2401_SD-0034_Div-05_Steel-Connection-Detail_Rev-C_S3.pdfPunch List
Date, location, trade category, and open item count for quick triage.
{ProjectCode}_PL_{Date}_{Location}_{Trade}_{OpenItems}.pdfPRJ-2401_PL_2026-03-15_Unit-4B_Finishes_Open-Items-12.pdfAs-Built Drawing
Trade division, drawing description, location, and contractual revision.
{ProjectCode}_AB_Div-{CSI}_{Description}_{Floor}_{Rev}.pdfPRJ-2401_AB_Div-22_Plumbing-Riser-Diagram_Floor-03_C01.pdfLien Waiver
Conditional vs unconditional, subcontractor name, pay period, and amount.
{ProjectCode}_LW_{Type}_{Subcontractor}_{Period}_{Amount}.pdfPRJ-2401_LW_Conditional_ABC-Plumbing_2026-03_$85,000.pdfCloseout Package
Division, trade, document type within the package, and warranty expiration.
{ProjectCode}_CLO_Div-{CSI}_{Trade}_{DocType}_{Warranty}.pdfPRJ-2401_CLO_Div-26_Electrical_OM-Manual_Warranty-Exp-2028.pdfPitfalls to avoid
7 common construction document naming mistakes
These patterns cause the most damage on real projects. Each one is preventable.
No version control in filenames
Consequence: Crews build from outdated drawings. A 2018 PlanGrid/FMI study found that poor project data and miscommunication cost U.S. construction $31.3 billion per year in rework.
Fix: Always include a revision field (Rev-A, Rev-B, or ISO 19650 P01/C01 format).
Using spaces and special characters
Consequence: Files fail to sync across cloud storage platforms. SharePoint truncates paths over 400 characters. Spaces break command-line tools and scripts.
Fix: Use hyphens to separate fields, underscores within fields. No spaces, no special characters (/ < > : * ? " |).
No project code prefix
Consequence: Documents from multiple projects mix in shared drives. Searching for "floor plan" returns hundreds of unrelated results.
Fix: Every filename starts with the project code. Assign codes at project kickoff and include in the BIM Execution Plan.
Inconsistent date formats
Consequence: Is "03-04-2026" March 4th or April 3rd? Ambiguous dates cause scheduling errors and version confusion across international teams.
Fix: Always use ISO 8601 dates (YYYY-MM-DD). This also ensures chronological sorting in file explorers.
"Final" / "Final_v2" / "FINAL_FINAL" versioning
Consequence: Nobody knows which "final" is actually final. The GC sends the wrong version to the owner, who approves a superseded design.
Fix: Use sequential revision codes (Rev-A through Rev-Z, then AA, AB). Or follow ISO 19650 P01/P02 → C01/C02 progression.
No discipline or trade identifier
Consequence: During closeout, the team cannot quickly separate architectural from structural, mechanical, or electrical documents. Sorting takes days instead of hours.
Fix: Include a discipline code (A, S, M, E, C) or CSI division number in every filename.
No suitability/status indicator
Consequence: Draft documents are treated as approved. A subcontractor fabricates steel connections from a "for review" drawing that was never signed off.
Fix: Include a status field: Draft, ForReview, Approved, Superseded. Or use ISO 19650 suitability codes (S0–S4, A1–A3).
Tool comparison
Manual naming vs template tools vs AI-based renaming
The right choice depends on your document volume, team size, and how varied your incoming filenames are.
| Feature | Manual | Template Tools | Renamed.to (AI) |
|---|---|---|---|
| Reads document content (OCR) | |||
| Extracts project codes from title blocks | |||
| Works with any input filename | |||
| Batch processing (500+ files) | |||
| Cloud storage integration | |||
| Detects revision letters (A/B/C) | |||
| CSI division encoding | |||
| No software cost | |||
| Works offline | |||
| Scales past 50 docs/day without errors |
Manual naming
PMs and admins rename each file by hand following a written convention.
Pros
- No software cost
- Full control over every filename
Cons
- Human error rate of 10–25% on large batches
- Does not scale past ~50 documents/day
- No enforcement — convention drifts over time
- New hires need extensive training
Best for: Small firms (<10 employees) with low document volume.
Template tools (Advanced Renamer, Bulk Rename Utility)
Desktop utilities that apply pattern-based renaming rules using regex, counters, and metadata fields.
Pros
- Free or low-cost
- Fast batch processing
- Good for repetitive, predictable patterns
Cons
- Cannot read document content — relies on existing filenames or metadata
- No OCR — cannot extract project codes from title blocks
- Rules break when input filenames vary
- No cloud storage integration
Best for: Teams with consistent incoming filename patterns and no need for content extraction.
AI-based (Renamed.to)
OCR + AI reads each document, extracts project codes, revision letters, CSI divisions, dates, and amounts, then generates compliant filenames.
Pros
- Reads title blocks, stamps, and handwritten annotations
- Works with any input filename — even "scan_001.pdf"
- Cloud integration (Google Drive, Dropbox) for automated workflows
- Confidence preview before applying changes
- One-click undo — originals are never overwritten
Cons
- Subscription cost ($15–49/month)
- Requires internet connection
- AI accuracy depends on document quality (damaged scans may need review)
Best for: Mid-size to large firms processing 100+ documents/week, especially when documents arrive from multiple subcontractors with inconsistent naming.
Integration
Works alongside your existing tools
Renamed.to handles the naming layer — the step between "documents arrive" and "documents are filed in your project management platform."
Not a replacement for Procore or Autodesk Build
Procore
Project management, document distribution
Import correctly named files. Search by project code, division, or revision.
Autodesk Build
BIM coordination, clash detection
ISO 19650 filenames feed directly into ACC document management.
Bluebeam Revu
PDF markup, takeoff, punch lists
Pre-named files arrive organized. Markup exports carry naming forward.
PlanGrid
Field collaboration, drawing management
Upload pre-named drawings. Revision detection ensures latest versions.
Typical workflow
Subs send files
Email, Drive, Dropbox
Renamed.to processes
OCR + AI naming
Files imported
Procore, ACC, PlanGrid
Team collaborates
Markup, review, approve
FAQ
Frequently asked questions
What is the ISO 19650 file naming convention?
ISO 19650 defines a 10-field naming convention for construction documents: Project–Originator–Phase–Level–Form–Discipline–Classification–Number–Suitability–Revision. Each field is separated by a hyphen. For example, "101-WSP-CD-L2-DR-A-A40-010-S2-P01.pdf" identifies project 101, created by WSP, during Construction Documentation phase, for Level 2, as a 2D Drawing, in the Architecture discipline, with classification A40, document number 010, shared for coordination (S2), at preliminary revision 01. The standard is mandatory on UK government-funded projects and widely adopted internationally under BIM frameworks.
How does CSI MasterFormat apply to document naming?
CSI MasterFormat organizes construction information into 50 divisions (Div 00 through Div 49) using a 6-digit numbering system. For example, 26 05 19 means Division 26 (Electrical), Section 05 (Common Work Results), Sub-section 19 (Low-Voltage Electrical Power Conductors). In document naming, include the division number as a prefix or field — e.g., "PRJ-2401_SUB-0112_Div-09_Flooring-Spec.pdf" — so documents can be filtered and grouped by trade during submittals, closeout, and archival.
What naming convention should I use for RFIs?
A proven RFI naming format is: ProjectCode_RFI-SequentialNumber_Subject_Status.pdf. For example: "PRJ-2401_RFI-0047_Column-Grid-Revision_Open.pdf". Always use zero-padded sequential numbers (0047, not 47) so files sort correctly. Include the status (Open, Responded, Closed) to avoid opening stale RFIs. Pair the RFI with its response using the same number: "PRJ-2401_RFI-0047-Response_Column-Grid-Revision_Closed.pdf".
How much does poor document naming cost construction projects?
A 2018 study by PlanGrid (now Autodesk) and FMI Corporation surveyed 599 construction leaders and found that poor project data and miscommunication cause $31.3 billion in rework annually in U.S. construction alone. A follow-up 2020 Autodesk/FMI study of 3,900+ professionals found $88.69 billion in global rework costs from bad data. Construction professionals spend an average of 5.5 hours per week just searching for project information. Consistent document naming directly reduces search time and prevents wrong-revision errors that lead to rework.
Is ISO 19650 naming required for BIM projects?
In the UK, ISO 19650-compliant naming has been mandatory for all centrally procured public projects since April 2016 (originally as BIM Level 2, now under the UK BIM Framework). Germany, France, the Netherlands, Singapore, and parts of the Middle East have adopted similar mandates. Even where not legally required, most BIM Execution Plans (BEPs) specify ISO 19650 naming because BIM workflows depend on consistent, machine-readable filenames for clash detection, model federation, and Common Data Environment (CDE) management.
How do I name closeout and turnover documents?
Closeout packages should be organized by trade/CSI division and document type. A recommended format is: ProjectCode_CLO_Division_Trade_DocumentType_Details.pdf. For example: "PRJ-2401_CLO_Div-23_HVAC_OM-Manual_AHU-01.pdf" for an O&M manual, or "PRJ-2401_CLO_Div-26_Electrical_Warranty_Exp-2028-06.pdf" for a warranty document. Include warranty expiration dates in the filename so facility managers can filter for upcoming expirations without opening each file.
Can AI tools like Renamed.to work alongside Procore and Autodesk Build?
Yes. The typical workflow is: documents arrive from subcontractors via email, Google Drive, or Dropbox with inconsistent names. Renamed.to processes these files — reading title blocks, extracting project codes, revision letters, and CSI divisions via OCR and AI — then renames them according to your project convention. The correctly named files are then imported into Procore, Autodesk Build, or PlanGrid, where they integrate with existing document control workflows. Renamed.to handles the naming layer; your project management platform handles distribution, markup, and approval.
Stop renaming construction documents by hand
Renamed.to reads title blocks, extracts project codes and revision letters, and encodes CSI divisions into every filename — automatically.
50 free file credits · No credit card · $0.009/file after
Continue exploring
Related guides, solutions, and resources for construction teams