How to organize CAD files in an architecture firm

Every firm knows the file plan_final_v3_DEFINITIVE_for_real.dwg. It's not a joke — it's the symptom of a system that was never designed, only accumulated. Organizing CAD files doesn't require sophisticated software or military discipline: it requires three decisions made once, and kept always. This guide shows which ones.

The typical chaos (and why it happens)

File disorder in a firm almost always follows the same pattern:

• Folders by person, not by project. Each employee has "their" version locally, and the truth is spread across three machines and an external drive.
• Email as the archive. The version sent to the municipality is in a March attachment. The client's is in another. Which is current? Depends on who you ask.
• Names without a convention. final, final2, really_final, NEW_final. Each of those names is a future decision postponed to the worst possible moment.
• No notion of phase. The same file serves preliminary design and permitting — with unrecorded changes in between.

The cost isn't aesthetic. It's billable time lost searching, the risk of submitting the wrong version to the authorities, and the inability to answer "what was delivered and when?" with confidence.

A phase-based folder structure that works

The most important structural decision: organize by project → phase → content type, never by person or by year. A concrete, copyable model:

2026-034-cascais-house/
  01-concept/
    drawings/
    references/
    client-presentations/
  02-preliminary/
    drawings/
    engineering/
    estimates/
  03-permitting/
    submitted/          ← what went to the authority, untouchable
    in-progress/
    official-responses/
  04-construction-docs/
    drawings/
    engineering/
    quantity-schedules/
  05-site-assistance/
    clarifications/
    changes/
    as-built/

Two rules make this tree robust:

• The submitted/ folder is immutable: what goes in is never edited again. Correcting means creating a new version in in-progress/ and resubmitting.
• Nothing lives outside the tree. If a file "doesn't have a place yet", its place is the current phase — never someone's desktop.

Naming and version conventions

A convention only works if it fits on a post-it. A field-tested suggestion:

[project]-[phase]-[content]-v[NN].ext
2026-034-PER-site-plan-v03.dwg

• Project number first — groups everything in the file explorer, even outside the tree.
• Abbreviated phase (CON, PRE, PER, CD, SA) — identifies context without opening the file.
• Two-digit versions — v03, never final. The word "final" is banned by convention: it's always a lie within a week.

Layers and external references (Xrefs)

External references only work if they live inside the project tree and are linked with relative paths. An Xref pointing at C:\Users\ana\Desktop\survey.dwg breaks the day someone else opens the drawing — or the project folder moves.

Rules that prevent most of the trouble:

• References stay in the phase they belong to. The topographic survey, the architectural base and the consultants' drawings live in a subfolder of the phase (for example, 02-preliminary-design/references/), never in a personal folder.
• Relative paths, always. In AutoCAD, choose the relative path when you attach an Xref; in Revit, linked models can use relative paths too. That way the whole tree can be copied or archived without breaking links.
• One layer standard, for every project. Layer names with the discipline prefix and the element type, the same across all of the firm's projects. ISO 13567 is a good reference if you want to start from an existing standard.
• Package before you send. A DWG sent on its own arrives without its references. Before handing a drawing to a consultant or uploading it to a platform, bundle it with its Xrefs — AutoCAD's eTransmit does this — or into a ZIP.

Review and approval before anything leaves the building

The most dangerous moment in a file's life is when it leaves the firm — to the client or to the authorities. It pays to formalise a review step: whoever drew it isn't whoever approves it, and the approval is recorded with a date and an author. In a dedicated system this flow is part of the tool: deliverables are uploaded to a stage's folder and go through review and approval file by file — by the team and, in client-review stages, by the client too — with every decision on record.

Automating: when folders stop being enough

The structure above works on any file system. Its limit is that people have to keep it — and by the third tight deadline, someone won't. A project management platform takes the same model and makes it structural: files belong to project stages by construction, each new version comes in as a new submission (Submission #2, Submission #3…) without deleting the earlier ones, and the history of who reviewed and approved what is recorded effortlessly. CAD and BIM files — DWG, DXF, RVT, IFC and others — are stored up to 500 MB each, and open in each person's own software. If you're evaluating that step, our guide to choosing software for architects helps separate the essential from the accessory — and full project management is the context files fit into.