Architecture firm file management means keeping drawings, calculation reports, specifications and project correspondence in project-based folders, with a consistent naming and revision scheme and permissions by person and discipline. The aim is that everyone in the office, and every stakeholder, always works from the current revision, while earlier revisions stay recoverable rather than deleted.
How files flow through a design office today
In an architecture or engineering practice a single project produces hundreds of files. Architectural, structural, mechanical and electrical sheets, calculation reports, quantity take-offs, specifications, correspondence with the municipality or client body, client approvals and site photos all belong to the same job. They usually live in three places at once: the shared drive, staff laptops and email attachments.
The trouble usually starts with a file name: "Floor_Plan_FINAL.dwg", "Floor_Plan_FINAL_rev.dwg", "Floor_Plan_FINAL_rev_Ahmet.dwg". The project manager tries to remember which one went to the client, which one the structural engineers calculated from, and which one the site team is holding. We cover the general principles in document version control; in design offices the number of disciplines and stakeholders makes it harder still.
External parties complicate things further. Clients, contracting authorities, contractors, consultants and other design offices send and receive files as email attachments or through share links that never expire. Every attachment is a separate copy living outside the office, and tracking who still holds which revision from those copies is close to impossible. When the project ends, the correspondence stays in personal mailboxes, the drawings on the shared drive and the approvals in a drawer.
What wrong revisions and lost files cost
Searching is a cost in itself. Atlassian's State of Teams 2025 survey of 12,000 knowledge workers found that teams waste 25% of their time just searching for answers. According to Microsoft's Work Trend Index 2023, 62% of survey respondents struggle with too much time spent searching for information in their working day.
In a design office, though, the expensive mistake is the wrong revision. A site team building from an old sheet may have to break out the work and rebuild it, and a take-off, quotation or interim valuation prepared from a superseded revision is wrong too. We look at the payment side of that chain in construction interim payment tracking.
Security vendor Sophos' analysis of its State of Ransomware 2024 survey data found median overall recovery costs eight times higher for organisations whose backups were compromised.
That matters to any practice with years of project archive. Drawings and correspondence from completed jobs are needed again years later for alterations, extensions or disputes. An archive sitting on a single disk on the same network puts both current work and history at risk in a single ransomware incident, which is why the 3-2-1 backup rule applies to design offices as much as anyone.
A seven-step framework for architecture firm file management
- Set a project code and folder template. Every project opens with the same skeleton: correspondence, discipline drawings, reports, client approvals, site photos, issues.
- Write a file naming convention. For example "ProjectCode-Discipline-SheetNo-Description"; international information management standards such as the ISO 19650 series encourage the same discipline. Keep words like "final", "new" or "rev" out of the name.
- Track revisions in the system, not in the file name. A new state of the same file is saved as a new version, and earlier versions remain recoverable.
- Separate work-in-progress, checking and issued areas. A drawing lives in one area while being worked on, another while being checked and a third once issued to the client or site.
- Grant permissions by discipline and person. The structural team can read the architectural sheets but not change them; only the project lead can delete. How to build the matrix is covered in file sharing permissions.
- Log every issue. Keep a list of which version of which sheet went to the client, authority or contractor, when and with whose approval.
- Archive the project after handover. A completed project moves to a read-only archive with a defined retention period and owner.
Step six is usually left to email, and that is where the weakest link forms. Having the project lead approve a transmittal or revision notice before it leaves the office stops the wrong attachment or the wrong recipient at source; the flow is described in email approval workflow. For practices that bid for work, sending tender documents securely is a separate topic covered in tender email security.
| Area | Who can write? | Who can read? | When does it move? |
|---|---|---|---|
| Work in progress | Discipline team | Project team | When ready for checking |
| Checking | Checking engineer | Project team | Once approved |
| Issued | Project lead | Project team, stakeholders where needed | Superseded revision goes to archive |
| Archive | Nobody (read-only) | Authorised people | At project close |
These four areas work even in a small office. The real benefit is that "which file did we send the client?" can be answered by looking in one place, because the issued area holds only sent and approved versions.
On the contracting side, drawing and revision control should connect to daily site reports and materials tracking; we describe how in construction project management software.
How Digital Bridge helps design offices
With design offices we talk about how the practice actually works before we talk about tools:
- Discovery and file inventory. We map project folders on your shared drive, naming habits, discipline teams and how files are exchanged with outside parties. If the practice also takes on contracting work, we treat the file structure together with the quantity, interim valuation and site tracking solutions we build for the construction and contracting sector.
- Template and standard. We write the project folder template, naming rule and permission matrix with you and turn them into a one-page office standard.
- Pilot project. We open a new project in the new structure from day one, and move or archive older projects in a planned order under our cloud migration and infrastructure consultancy. The migration steps are set out in replacing an on-premise file server.
- Documents that need routing. Where correspondence with authorities, signed minutes and formal records need more than folders, we build a separate flow on the document management system side.
The link between office and site is part of the job too. It matters that the sheet going to site is the right version, and just as much that who enters the site is recorded, which we cover in construction site access and attendance. For the content of technical documents submitted to clients and authorities, see writing technical specifications.
A day in a design office with Smart360
In our own Smart360 family, SmartFiles file management gathers files into project-based storage areas. Each project gets its own area, and unlimited folder depth means the template above can be set up exactly as designed. Eight independent permissions (read, write, edit, delete, create folder, AI, history, notes) are granted to people or departments through a single matrix.
In the morning the architectural team uploads a new floor plan under the same name. Nothing is overwritten: it becomes a new version, and the previous one can be downloaded or restored if needed, with the office deciding how many versions to keep. The project engineer adds a note ("column grid updated per client approval"), assigns a checking task to someone in the structural team and links the document to the relevant client approval.
In the afternoon a revision request from the client arrives in SmartMail, and the attached PDF is saved to the project's SmartFiles area in one click. When the transmittal is ready it goes to the project lead for approval before sending; approval, revision with reasons or rejection is recorded with date and time. AI analysis works on PDF, Word, Excel, text and image files, so it is most useful on specifications, reports and correspondence: the team can ask the project folder "when did the client approve the façade material?". We go into this in AI document analysis.
When someone leaves the project or the practice, their access closes in one step through a single identity (SmartID). Download and preview links expire within minutes, so a link shared with a stakeholder does not stay open for months. A project folder deleted by mistake comes back from the recycle bin with its subfolders, and an upload that would exceed the storage cap is refused before it starts, so the team is never left with a half-finished upload or an incomplete issue set.
A file structure works best when it moves with the delivery schedule. SmartPM project management, from the same family, plans revision and issue tasks on a Gantt chart with dependencies: when one task slips, the tasks that depend on it shift too, and the critical path stays visible. A person added with the client role sees only the tasks opened to them and can approve or request changes.
Next step
This week, open the folders of your last three projects and count the files with "final", "rev" or a person's name in them; the number tells you how urgent a standard is. Then contact us and we will draft your project folder template together and show SmartFiles on a pilot project. For email selection criteria see how to choose business email, and for all our document guides visit the Business Email & Documents page.