Log inFree trial
Top view of a marble table with a printed floor plan and hands typing on a laptop

How to organize your architecture studio’s project files

Arcture team4 min read

“Where is the latest version?” may be the most expensive question in an architecture studio. Every time someone looks for a file, the project stops. And when the wrong version reaches the site or the supplier, the cost shows up as rework, wasted material and a difficult conversation with the client.

The good news is that organizing files does not take heroic discipline. It takes a few simple agreements that anyone on the team can follow: a single place, the same folder structure in every project, a naming convention and a rule for versions.

Why organization disappears

No studio decides to be disorganized. The mess arrives little by little:

  • everyone saves things their own way, on their own computer;
  • email and WhatsApp attachments become the only copy of an important file;
  • “final”, “final2” and “final_this_time” appear, and nobody knows which one was sent;
  • whoever left the studio took the logic of the folders with them.

The problem is almost never a lack of care. It is the lack of a simple rule and of a single place where it applies.

1. A single place for the project's files

Everything that belongs to a project should live in the same place: drawings, PDFs sent, site photos, supplier quotes, the contract. Personal computers, USB drives and WhatsApp chats are for working, not for keeping.

Build a habit: whatever arrives by email or message is saved in the project's folder the same day. A site photo that stayed only on someone's phone is information the studio does not have.

2. The same folder structure in every project

When every project has the same folders, in the same order, anyone finds any file without asking. A structure that works for most studios:

  • 00 Admin: proposal, contract, invoices and receipts
  • 01 Briefing and survey: the client's answers, measurements, photos of the current state
  • 02 References: inspiration images and materials
  • 03 Preliminary study
  • 04 Design development
  • 05 Construction drawings
  • 06 Consultants: structure, electrical, plumbing and HVAC
  • 07 Specifications and purchasing
  • 08 Construction site: photos, visit reports, measurements
  • 09 Client deliveries

The numbers at the start keep the order of the stages instead of the alphabetical order. Keep this structure as a template and copy it into each new project. And avoid going deeper than three levels of folders: whatever is buried too deep stops being found.

3. A naming convention anyone understands

A file's name should say what it is without anyone having to open it. A simple formula: project, discipline, sheet number, content and revision. For example:

  • CJE_ARC_08_Elevations_R02.pdf
  • CJE_ELE_03_Outlets_R00.pdf
  • CJE_Site_2026-09-30_Visit.jpg

A few rules make the convention error-proof:

  • No accents, spaces or symbols. Some software and systems get confused by them.
  • Dates as year-month-day (2026-09-30), so the alphabetical order is also the order in time.
  • Revisions with two digits, from R00 on, so R10 comes after R09.
  • Never “final” in the name. The final version is the latest approved revision, and it can change.

4. Versions: keep the history, show only the current one

The project's folder should show the revision in force for each sheet. The earlier ones do not disappear, but they are not mixed with the current one either: they go into the history, where they can be looked up when someone asks what changed.

Also keep the revision table in each sheet's title block, with the number, the date and a short description of the change. And record what was sent, to whom and when: when the site calls with a question, you will know exactly which version they have in hand. There is more on this in the guide on revision control.

5. Everyone sees what they need to see

Not everyone needs access to everything. A project's contract and finances do not concern whoever is detailing the joinery, and the client should see what was delivered to them, not the internal studies. Set the access when someone joins the studio and review it when someone leaves.

6. A finished project is not a forgotten project

When construction ends, set aside the final PDFs, the photos of the finished project and the suppliers' contacts. Two years later, the client will call asking for the electrical plan to install an air conditioner, and it needs to be a minute away.

How to do it in Arcture

Arcture has a studio Drive, with each project's folders and file previews right in the browser. When you upload a file with the same name, or use the “Upload new version” button, it keeps a new version: the earlier ones stay under “Versions” and can come back with “Restore”. On a PDF, “Compare versions” shows the two side by side, overlaid or with a swipe, and points out the areas that changed.

Deleted items go to the Trash, and in the portal the client sees only what you deliver or share with them. See Arcture's plans.