Construction document naming standard
Name construction documents by project code, document type, discipline, and revision.
Follow ISO 19650 principles for BIM and document control.
For project managers, general contractors, and architects
8.3k construction documents organized with this pattern across 6 general contractors and architecture firms.
Construction document naming standard
Name construction documents as ProjectCode_DocType_Discipline_Revision.pdf to track revisions, filter by discipline, and maintain document control across the project lifecycle.
- Lead with the project code to group all documents for a single project.
- Include document type (RFI, Submittal, ChangeOrder, Drawing, Spec) for immediate classification.
- Add discipline code (AR, ST, ME, EL, PL) to filter by engineering trade.
- Always append the revision number or letter — construction documents are living documents that get revised constantly.
8.3k construction documents organized with this pattern across 6 general contractors and architecture firms.
Recommended patterns
Standard construction document pattern
The core pattern for project document control. Groups all documents by project, classifies by type and number, and tracks revisions. Works for RFIs, submittals, change orders, and general project documents.
ProjectCode_DocType_Number_Revision.pdfPRJ-2025-042_RFI-0042_RevC.pdfConstruction drawing pattern (ISO 19650 inspired)
ISO 19650-inspired pattern for BIM and drawing management. The full field set enables filtering by originator, discipline, zone, and level. Use the fields that apply to your project size.
ProjectCode_Originator_Discipline_Zone_Level_Type_Number_Revision.pdfPRJ-042_ARC_AR_ZZ_L02_Plan_0001_P02.pdfSubmittal package pattern
For submittal tracking. Links to spec sections for compliance verification and tracks approval status. The submittal number ties to the submittal log in your project management system.
ProjectCode_Submittal-Number_Spec-Section_Vendor_Status.pdfPRJ-2025-042_SUB-0023_03300_Hilti_Approved.pdfCore principles
Project code groups everything
Every document in a construction project must start with the project code. When a GC manages 10 projects simultaneously, the project code is the first filter. Use the same code as your project management system.
Revision tracking is non-negotiable
Construction documents are revised constantly. An RFI response may go through 3 revisions. A drawing set may be on revision P05 by the time construction starts. Without revision tracking in the filename, someone will build from an outdated drawing.
Use standard discipline codes
AR (Architecture), ST (Structural), ME (Mechanical), EL (Electrical), PL (Plumbing), CV (Civil), LA (Landscape). These are industry standard and recognized by every construction professional.
Follow ISO 19650 for BIM projects
If your project uses BIM (Building Information Modeling), ISO 19650 provides a standardized naming convention. Even if you do not follow it exactly, its field structure (project, originator, discipline, zone, level) is a proven framework.
No spaces in filenames — ever
Construction files move between Windows machines, project servers, SharePoint, and email. Spaces break scripts, cause URL encoding issues, and create compatibility problems. Use hyphens within fields and underscores between fields.
Document type abbreviations must be consistent
Pick abbreviations and publish them in your project document control plan. RFI (Request for Information), SUB (Submittal), CO (Change Order), DWG (Drawing), SPEC (Specification). Never mix "RFI" and "RequestForInfo" on the same project.
Common mistakes
No revision tracking in the filename
A structural drawing without a revision number means someone might build from revision A when revision D is current. This causes rework, delays, and potential safety issues.
Fix: Always append revision: PRJ-2025-042_RFI-0042_RevC.pdf
Inconsistent discipline codes across the project
If the architect uses "ARCH" and the structural engineer uses "ST," filtering and sorting break. Document control becomes manual and error-prone.
Fix: Publish a project naming standard with exact codes: AR, ST, ME, EL, PL, CV, LA.
Spaces in filenames
Construction files get uploaded to SharePoint, emailed, put on FTP servers, and referenced in scripts. Spaces break in URLs, command-line tools, and many project management systems.
Fix: Use hyphens and underscores: PRJ-2025-042_RFI-0042_RevC.pdf
Using dates instead of revision numbers for drawings
A drawing dated 2025-10-15 tells you when it was updated, not which revision it is. Multiple updates on the same day create ambiguity. The industry tracks drawings by revision, not date.
Fix: Use sequential revision letters or numbers: RevA, RevB, RevC or P01, P02, P03.
Missing project code
An "RFI-0042.pdf" without a project code is meaningless when a GC manages multiple projects. It could belong to any project.
Fix: Always lead with project code: PRJ-2025-042_RFI-0042_RevC.pdf
Automate construction document naming
Renamed.to reads construction PDFs — RFIs, submittals, change orders, and drawings — extracts project codes, document numbers, and revision information, and applies your project's naming convention automatically. Integrates with Google Drive and SharePoint.
50 free renames to start. No credit card required.
More naming guides
View all naming guides →Frequently asked questions
What is ISO 19650 and should I follow it?
ISO 19650 is the international standard for organizing and digitizing information about buildings and civil engineering works, including BIM. If your project uses BIM, following ISO 19650 naming conventions ensures interoperability with other firms. For simpler projects, the principles (project-originator-discipline-type-number-revision) still apply.
How do I handle RFI responses vs the original RFI?
The original RFI and its response should share the same RFI number. Differentiate with a suffix: PRJ-042_RFI-0042_Request_RevA.pdf and PRJ-042_RFI-0042_Response_RevA.pdf. Or track them as separate revisions if the response updates the original.
What about shop drawings from subcontractors?
Treat shop drawings as submittals. Use the submittal pattern: PRJ-042_SUB-0023_ShopDwg_SubcontractorName_RevA.pdf. Include the subcontractor name for traceability.
How do I handle as-built documentation?
As-built documents are final versions. Use the drawing pattern with an "AB" revision tag: PRJ-042_ARC_AR_Plan_0001_AB.pdf. This distinguishes as-builts from construction-phase revisions.
Should I use the CSI MasterFormat division numbers?
For submittals and specifications, yes. CSI division numbers (e.g., 03300 for cast-in-place concrete) are universally understood in construction. They enable automated matching between submittals and specifications.
Can I automate naming for drawing sets received from consultants?
Yes. Renamed.to can read the title block on construction drawings, extract the project code, discipline, sheet number, and revision, and rename them to match your project naming standard — even if the consultant used a different convention.