Every architecture project runs on two streams of communication: the drawings you send out, and the words you wrap around them. When both of those live in email, the project slowly turns into a scavenger hunt. You keep clients updated and share drawings through a growing pile of threads, and within a few weeks nobody can find the version that was actually approved.
The problem is not that email is bad at messages. It is that email is terrible at keeping the message, the file, and the decision together in one findable place. Fixing that is one of the highest-leverage things a studio can do.
Why email breaks down for drawing sharing
A single set of plans goes out, the client replies with a question, someone forwards it to a consultant, a revised sheet comes back with a different filename, and now there are four copies of the same drawing in four inboxes. Nobody is sure which is current. The classic email failures show up every single project.
- Attachments get stripped, bounced, or silently truncated by size limits
- Version numbers live in filenames that everyone renames differently
- The approval is buried three replies deep in a thread nobody kept
- New team members have zero access to the history that came before them
- The client updates you on a phone reply that never reaches the project
Separate the update from the file, then reunite them
A good client update is short and specific: here is where we are, here is what we need from you, here is the drawing to look at. The mistake is treating the drawing as an attachment to that message. Instead, the drawing should have a home, and the update should point to it. When the plan lives in the project and the message references it, there is only ever one current version, and the conversation stays attached to it.
The version that was approved should never be a question you have to answer from memory.
Make approvals a status, not a sentence
The single most expensive thing to lose is an approval. When a client signs off on a material or a plan set inside a paragraph of email, that decision is only as findable as the thread it lived in. Turn approvals into something the whole team can see at a glance: a status on the project, a clear marker that this phase or this drawing was signed off, and when. That way, the answer to did the client approve this is a thing you can look at, not a thing you have to dig for.
Give the client one place to look
Clients are not trying to make your life hard. They lose track because you have given them ten different threads and no single view of the project. When there is one place where the latest drawings, the current status, and the outstanding questions all live, the client stops emailing you to ask what the latest is, because they can see it. Fewer where are we emails is one of the quietest but most real time savings a studio can win.
Keep the trail for the people who come later
Projects outlast the people who start them. A project architect leaves, a new one joins, and the entire history of decisions is locked inside someone else's sent folder. Keeping the drawings, the updates, and the approvals attached to the project instead of to individuals means the record survives staff changes. The next person can catch up by reading the project, not by begging for forwarded emails.
A cleaner way to run client comms
The fix is to give drawings a home, turn updates into short pointers to that home, and make approvals visible. Spreadbox is built for this: file and PDF sharing keeps your drawing sets and plans attached to the project instead of scattered across inboxes, project status tracking makes phase approvals something the whole team can see, and team chat channels keep the conversation next to the work rather than in a private thread. Spreadie, the built-in AI assistant, can draft the client-facing update so you send a crisp summary in seconds, and two-way Google Calendar sync with Meet keeps review meetings on everyone's calendar. The result is fewer lost files, faster sign-offs, and an inbox that stops running your projects.