Construction engineering creates a document management problem that product engineering doesn’t have. In a manufacturing shop, a single team owns the CAD model from concept to production, revisions are controlled through PDM, and the end artifact is a set of drawings for a factory with controlled access to your files.
In construction, the same drawing passes through a structural engineer, MEP consultants, a general contractor, multiple subcontractors, a building inspector, and eventually the owner — each with different tools, different naming conventions, and different ideas about what “current” means. The DWG file from the structural engineer needs to align with the Revit model from the architect and the IFC export from the MEP team. File management failure in this environment means someone builds from a superseded drawing.
This post covers what actually works for construction-focused engineering teams: naming standards, revision workflows, submittal coordination, and as-built handoff.
How Construction Differs from Product Engineering
In product engineering CAD management, the core problems are:
- Preventing two engineers from editing the same file simultaneously
- Tracking which version of a part is in production
- Matching drawing revision to the physical part on the shop floor
In construction, those problems still exist, but the dominant challenges are different:
Multi-discipline coordination. Structural DWGs, mechanical DWGs, plumbing DWGs, and electrical DWGs all live in separate files, owned by separate firms, but must coordinate spatially. A structural beam at elevation 3600 that collides with a mechanical duct is a field problem that costs orders of magnitude more than fixing it in CAD.
Sequential phase control. Construction documents move through formal phases: Schematic Design → Design Development → Construction Documents → Issued for Construction (IFC). Each phase has different suitability — sharing a Design Development drawing with a subcontractor who quotes from it as if it were IFC creates liability and rework.
Downstream fabrication. The IFC drawing is not the last step. Subcontractors produce shop drawings (submittals) that show how they will actually fabricate and install. Those shop drawings go back through an approval loop before fabrication starts. The CAD file management system must track submittals separately from contract documents.
Closeout. When construction ends, the owner receives as-built drawings that reflect what was actually built, not what was designed. Capturing field changes back into the CAD model is a discipline most construction teams handle poorly.
Understanding these differences shapes every decision about naming, folder structure, and tooling.
Naming Conventions: ISO 19650 vs AIA vs Project-Specific
No single standard dominates globally, but two are widely adopted:
ISO 19650 (International)
ISO 19650 defines a 10-field file naming code, mandatory on UK public projects and increasingly adopted internationally:
[Project]-[Originator]-[Volume]-[Level]-[Type]-[Role]-[Classification]-[Number]-[Suitability]-[Revision]
A concrete example:
PROJ1-STRENG-ZZ-01-DR-S-30-0001-S3-P01.dwg
Breaking this down:
PROJ1— project code (agreed in the BIM Execution Plan)STRENG— originator code (the structural engineering firm)ZZ— volume/system (ZZ = applies to all)01— level (ground floor)DR— type code (DR = Drawing)S— role code (S = Structural)30— classification (30 = Structural systems, Uniclass 2015)0001— sequential numberS3— suitability code (S3 = Suitable for construction)P01— revision (P = preliminary, C = construction, P01 through P99 then C01 through C99)
Suitability codes are the piece most teams ignore but most need:
| Code | Meaning |
|---|---|
| S0 | Work in progress — do not distribute |
| S1 | Suitable for coordination |
| S2 | Suitable for information only |
| S3 | Suitable for construction |
| S4 | Suitable for post-construction record |
| D1 | Preliminary design (AEC-specific) |
A drawing that moves from S1 to S3 has passed through review and approval. This is the digital equivalent of the “Approved for Construction” stamp on a paper drawing — except it’s in the filename, making it machine-readable and audit-friendly.
AIA (United States)
The American Institute of Architects system is older and simpler. For drawings:
[Discipline][Sheet-Type][Sequential-Number].dwg
A-101.dwg (Architecture, sheet 1)
S-301.dwg (Structural, sheet 1 of section type 3xx)
M-201.dwg (Mechanical, sheet 1 of floor plans type 2xx)
Revisions use revision clouds on the drawing with a revision triangle and letter (Rev A, Rev B). For file names, a common convention appends the revision:
S-301_RevC.dwg
AIA doesn’t formally specify suitability codes, which is the main practical gap compared to ISO 19650. Teams using the AIA system typically handle suitability through folder structure (a “For Construction” folder separate from “In Progress”) rather than encoding it in the filename.
When to Use Which
- ISO 19650: international projects, UK public sector, any project where multiple firms from different countries collaborate, BIM-coordinated projects
- AIA: US domestic projects, especially building/architecture-led projects
- Project-specific: sole-source engineering (only your firm on the project) where you control the full document set — don’t add complexity you won’t benefit from
Whatever standard you choose, document it in a CAD Standards or BIM Execution Plan (BEP) document before issuing the first drawing. Changing naming conventions mid-project breaks hyperlinks, sheet references, and any automated workflows.
Revision Control: Beyond File Renaming
In product engineering, version control means PDM or Git. In construction, revision control means something more specific: tracking which revision of a drawing is the current contract document, who approved it, and when.
The minimal effective system:
Document Register. A spreadsheet or database listing every document in the project, its current revision, suitability status, issue date, and who holds an approved copy. Updated every time a revision is issued. This is the source of truth for “what is current.”
Transmittal records. Every time you send a drawing to another party, generate a transmittal — a numbered record of what was sent, to whom, on what date, and at what revision. When a dispute arises about whether someone had the correct drawing, the transmittal answers it. Most construction management platforms (Procore, Autodesk Construction Cloud) generate these automatically.
Cloud Common Data Environment (CDE). ISO 19650 formalizes this as a CDE — a single system where all project information lives and through which all exchanges occur. In practice, this is usually a platform like Autodesk Docs, BIM 360, or SharePoint with a structured folder convention. The key property: when a drawing is superseded, the old version remains visible but is clearly marked as such. Deletion is not acceptable.
Folder-based suitability (for teams not using ISO 19650 codes):
/Project-001/
/In-Progress/ (S0 — internal only)
/Issued-for-Coordination/ (S1)
/Issued-for-Construction/ (S3)
/Submittals/
/Submitted/
/Under-Review/
/Approved/
/Rejected/
/As-Built/
Moving a file from In-Progress to Issued-for-Construction is a deliberate action that requires sign-off. No one should be pulling from In-Progress for fabrication.
Submittal Packages: Shop Drawings and the Approval Loop
Submittals are fabricator-produced documents showing how a subcontractor will build something. A structural steel fabricator submits shop drawings of every beam, column, and connection with actual dimensions, material specs, and weld details. A mechanical contractor submits duct fabrication drawings. A glazing contractor submits facade panel shop drawings.
The submittal workflow:
- Subcontractor produces shop drawings (often in their own DWG or PDF format)
- Shop drawings submitted to the General Contractor
- GC reviews and forwards to the design engineer of record for that discipline
- Engineer reviews for conformance with IFC drawings — not for contractor means and methods
- Engineer stamps: Approved / Approved as Noted / Revise and Resubmit / Rejected
- Approved submittal returned to GC, then to fabricator
- Fabricator proceeds
The file management challenge: shop drawings reference IFC drawings by revision. If the IFC drawing changes after shop drawings are submitted but before they’re approved, the shop drawings may be based on superseded geometry. Your document register must track the IFC revision that each submittal was designed against.
For engineering firms on the design side, the most common failure is losing track of which submittal version was approved. Stamp the approval on the PDF, but also record it in the document register: submittal number, revision, date received, date reviewed, outcome, reviewer.
CAD files in submittals are typically DWG or DXF — the fabricator’s format. If you’re a structural engineer reviewing fabrication shop drawings, you’re reviewing DWG files from the steel shop, not SolidWorks parts. The file management system needs to accept DWG and PDF, not just the formats your design tools produce.
Coordinating DWG, IFC, and RVT Across Disciplines
Multi-discipline coordination is where construction CAD management gets genuinely hard. Three common interchange patterns:
DWG X-refs. Each discipline maintains their drawings as DWG files. The structural engineer x-references the architectural floor plan into the structural drawing. Changes to the architectural plan propagate to structural when the x-ref is reloaded. This works well if everyone uses the same coordinate system and units; it fails silently when they don’t.
IFC model exchange. In BIM-coordinated projects, each discipline exports an IFC model (structural model, MEP model, architectural model). These are federated in a coordination tool (Navisworks, Solibri, Trimble Connect) for clash detection. IFC exchange preserves geometry and some attributes but loses parametric relationships. A coordinate reference point (Survey Point and Project Base Point in Revit) must be agreed in the BEP before any model exchange.
DWG from Revit. Many projects mix Revit-based BIM with traditional 2D DWG deliverables. The standard workflow is: model in Revit → export DWG sheets for contract document delivery → retain Revit model for coordination. The DWG is the legal contract document; the Revit model is the coordination tool. These are not interchangeable. The DWG naming and revision systems apply to the DWG deliverables regardless of what generated them.
For structural and MEP engineering teams using AutoCAD or AutoCAD MEP rather than Revit, the CAD file version control guide covers how to apply Git-adjacent practices to DWG files — including handling x-refs, which are the DWG equivalent of file references in an assembly.
Folder Structure That Scales
A structure that works for construction projects up to ~50 active stakeholders:
/[ProjectNumber]-[ProjectName]/
/00-Admin/
/BIM-Execution-Plan/
/CAD-Standards/
/Transmittals/
/01-Architecture/
/01a-Models/ (RVT, IFC)
/01b-Drawings/ (DWG, PDF)
/01c-Specifications/
/02-Structural/
/02a-Models/
/02b-Drawings/
/02c-Calculations/
/03-MEP/
/03a-Mechanical/
/03b-Electrical/
/03c-Plumbing/
/04-Civil/
/05-Submittals/
/[SubmiittalNumber]-[SubcontractorCode]-[Description]/
/01-Submitted/
/02-Under-Review/
/03-Returned/
/06-RFIs/
/[RFI-Number]-[Description]/
/07-As-Built/
/[Same-discipline-structure]
The discipline numbering should match the discipline codes in your document naming convention. ISO 19650 role codes (S = Structural, M = Mechanical, E = Electrical, A = Architectural) work as prefixes.
Avoid deep nesting. More than 4 levels creates path-length problems in Windows (260-character limit on older systems) and makes folder navigation slow for field personnel on tablets.
As-Built Documentation
As-built drawings reflect the as-constructed state — what was actually built, including field changes, added elements, and deviations from the IFC drawings.
As-built capture is typically the weakest link in construction document management. The practical reality: field changes are marked up on paper prints by the superintendent or foreman, and those paper markups sit in a binder until the project ends. Converting them back to DWG at closeout is a low-priority task that gets done hastily or not at all.
What actually works:
Markup in the CDE. Use a cloud document platform (Procore, Autodesk Docs, Bluebeam Studio) that allows field personnel to mark up PDFs on tablets. Changes are timestamped, attributed, and linked to the drawing. At closeout, the CAD drafter incorporates the markups into the DWG model.
RFI tracking linked to drawings. Each RFI that results in a design change should be tagged with the affected drawing number and revision. Your document register should track which RFIs drove changes to each drawing. At closeout, every approved RFI with a design impact should appear in the as-built model.
Issue-for-Record (S4). Under ISO 19650, as-built drawings carry the S4 suitability code — Suitable for Post-Construction Record. This distinguishes them from S3 (construction) drawings and prevents confusion in future renovation projects.
File naming for as-built: append _AsBuilt to the document number and set revision to the final construction revision, not a new sequence. The as-built of S-301-RevC is S-301-RevC_AsBuilt, not S-301-RevD.
Automating File Naming Across a Team
Construction document management fails when each discipline uses a different convention, or when individuals use informal abbreviations (“My copy”, “FINAL_v2_FINAL_revised”). The CAD file naming automation guide covers rename scripts and naming template tools that enforce conventions across a team.
For DWG files specifically: AutoCAD’s Sheet Set Manager can enforce naming conventions through sheet set templates. Files created from a sheet set inherit the naming pattern defined in the template. This doesn’t require any scripting — it’s a configuration choice in the sheet set setup.
For mixed-format projects (DWG + PDF + IFC + RVT), naming automation at the file system level is more reliable than tool-level enforcement. A simple PowerShell script that validates filenames against your convention on each save catches format violations before they reach the shared CDE.
The CAD file management best practices guide covers the general principles behind these decisions — folder structure, access control, and backup policy — which apply equally to construction and product engineering contexts.
What to Implement First
If your team is starting from an informal state, the order of implementation matters:
- Agree on a naming convention and document it. Nothing else works without consistent names.
- Set up a document register. Even a shared spreadsheet is better than none.
- Establish a CDE. A shared cloud folder with write access control is the minimum. A platform with revision tracking and transmittal generation is better.
- Define suitability workflow. Document what “Issued for Construction” means procedurally — who signs off, how files move from In-Progress to IFC folder.
- Create a submittal log. Track every submittal, its revision, status, and approval date.
- Plan for as-built from day one. Decide how field changes will be captured before the project starts, not at closeout.
Construction project document management is not a technical problem — the tools exist. It’s a process and discipline problem. The teams that do it well establish the conventions before the first drawing is issued and enforce them consistently. The teams that struggle let each party manage their own files independently until coordination meetings reveal the chaos.