Pillar 03 — Real Project WorkflowGraduate Architects · Project Architects · Design Managers · Arkitask Staff ⓘEducational content only
CoreSkills+ shares practical knowledge based on real project experience. This is not professional advice. Always verify against your office's project management procedures and any applicable contractual requirements.
Project File Management
Every project generates hundreds of documents. Without structure, things get lost, and in the built environment, a lost document is never just an inconvenience.
Most graduates walk into their first project role without ever being taught how documents are managed. Nobody covers it at university. You learn it on the job, usually by making a mistake on a live project. This topic explains how a project filing system is structured, who manages what, and what goes wrong when there is no structure in place from day one.
Document management looks like admin. It is not.
It is one of the most consequential parts of project delivery. Here are three things that actually happen on real projects when there is no document structure in place.
01
A builder receives a drawing directly from a consultant via email, bypassing the architect entirely. The drawing is three revisions old. The builder builds from it. The error is not discovered until the slab is poured.
02
A graduate saves a revised specification to their desktop and emails it to the hydraulic engineer. Three weeks later the specification is updated again, but the engineer never receives the new version. The hydraulic design goes to tender based on a superseded document.
03
A council submission is prepared using drawings pulled from a shared drive folder that has not been maintained. Two of the drawings are from the wrong issue. The application is rejected.
None of these are dramatic failures. They are ordinary, preventable, and expensive.
A standard project filing system uses the following top-level folders. Each exists for a specific reason. Click each folder to understand what it contains, why it exists, and what happens in practice.
Who manages whatDocument management on a project is not a team activity where everyone has equal access. There is a clear hierarchy, and understanding it early is one of the most useful things a graduate can do.
Design Manager
Owns the filing system. Controls what gets published to the formal register, who can issue documents externally, and how the folder structure is maintained.
On a well-run project, nothing leaves the office without the Design Manager knowing about it.
Project Architect
Contributes documents and works within the structure. Uploads drawings, adds received documents to the correct folder, and maintains their own discipline's records.
Does not issue documents externally without going through the Design Manager.
Consultants and Collaborators
Receive documents. Do not contribute to the project's internal filing system. Given access to what they need, when they need it, through formal issue, not open folder access.
The moment a consultant starts sending drawings directly to a builder, bypassing the architect, is the moment document control transfers away from the architect.
These are the filing failures that appear on almost every project where document management has not been established from day one.
—No structure at all
Everything lives in a single shared drive folder or on someone's local desktop. Documents are found by searching, not by knowing where to look. This is the starting point for every project that ends in a dispute.
—Inconsistent file naming
Files saved as "Drawing Rev 3 FINAL FINAL USE THIS ONE.pdf" are not an exaggeration. When there is no naming convention, the file name carries no information and finding the right version becomes a guessing game under pressure.
—Consultants issuing directly to the builder
Common. Dangerous. A consultant who emails drawings to the builder without going through the project architect has removed the architect from the coordination chain. The architect no longer knows what the builder has received, or what revision they are building from.
—Multiple copies of the same document in different locations
When a document exists in three places with three different modification dates, there is no single source of truth. Someone is always working from the wrong version. In our experience this is how construction errors begin, not with deliberate decisions, but with honest confusion about which document is current.
—No record of what was issued and when
Without a transmittal register, the project has no formal record of what left the office, at what revision, and who received it. This becomes critical the moment a dispute arises about what the builder was given and when.
Coming Soon — Nimbus+The tool that puts this structure into practice from day one
Nimbus+ includes a built-in project filing system pre-loaded with the standard folder hierarchy. A transmittal issued through the Drawing Management tool is automatically available in the Issued Documents folder. The Design Manager controls the system. Team members contribute. Collaborators receive.
Join the waitlist →Pre-loaded standard folder hierarchy Consultant sub-folders by discipline Transmittals linked to Issued Documents RFI responses in filing system Design Manager access controls Free ChecklistProject Filing Setup Checklist
12 items to set up a project filing system before the first document is generated.
Download Checklist+
Something to add?
A filing structure your office uses differently? A real project mistake we have missed? Help us build guidelines that reflect practice.
🤝
Collaborators
Practitioners who shaped this topic with real-world input
No collaborators yet, be the first to contribute above.
Contributions are reviewed by the CoreSkills+ team. Want to contribute? Use the form above.
