A studio loses a team member. Nothing dramatic. They have been there for a while, leave on good terms, do what would normally be called a proper handover. The week after they're gone, the principal goes to make a payment to a contractor and realises they have no idea what was actually agreed. The number was in the team member's head, and the team member is no longer at the studio.
This is the small operational version of the story. When the admin or operations person leaves, the studio finds out, sometimes within a week, sometimes within a month, how much of the day-to-day was running through one person. Contractor payments. Staff salaries. Attendance corrections. Invoice schedules. None of it was being hidden. It just lived in the team member's working memory because the studio had been running smoothly that way for years.
The harder version surfaces when an architect leaves. Two years later, a client on a long-running project asks about a decision made early on, something that affects what's about to happen next. The principal goes to look it up and finds that the person who handled it left the studio two years ago. The drawings might be in the studio folder. They might be in that person's personal Google Drive. They might be in an email thread nobody has searched in two years. The project is still active. The context isn't.
Both versions are common. They show up in different forms, but the underlying problem is the same. A practice that depends on individual people holding context will lose context whenever those people leave, and the loss only becomes visible when the studio needs something specific that nobody else knows.
What makes this hard to prevent is that handovers feel like they ought to work. The team member who is leaving sits down with whoever is taking over, walks through the projects, hands over the files, explains the open issues. Both sides feel like everything has been covered. The studio thinks the transition is complete. The reality is that no handover conversation can cover what the leaving person doesn't think to mention, because the things that get missed are the things they didn't realise they knew. The contractor who only sends invoices once a quarter. The client who prefers WhatsApp to email. The structural consultant who hasn't been paid yet for the last project. The drawing version that was approved verbally on site. These don't come up in a handover conversation because they don't surface in the leaving person's mind as something worth mentioning. They just are how things work, until they aren't.
The cost of this shows up in three ways. The first is the immediate operational gap, when the studio can't answer a question it should have been able to answer. A contractor calling about a payment. A client asking about a deliverable. A team member trying to continue a project they've inherited. Each of these creates a small failure that the studio has to recover from.
The second is the slower discovery, where the studio finds out, weeks or months after the person has left, that some piece of context has gone with them. A drawing that needs to be referenced. A decision that needs to be confirmed. A vendor relationship that needs to be picked up. By the time the gap surfaces, the leaving person is often unreachable, or it has been long enough that asking them feels strange. The studio either rebuilds the missing context from scratch or works around the absence.
The third is the cumulative cost, which is harder to see but is the largest of the three. A studio that loses three or four team members over a few years, each of whom carried some context that wasn't captured, ends up with a practice full of small unknowns. Where this drawing came from. Who agreed to this scope. Why this decision was made. Why a certain contractor is on this project. The studio's actual operating knowledge degrades quietly, and the principal, who was always the most central holder of context, ends up being the only one who remembers everything because nobody else has been around long enough to absorb it.
This is not a problem that a better handover process fixes. Studios that have tried more rigorous handover checklists usually find the same thing. Some context gets transferred. A lot of it still slips. The checklist captures what the leaving person can articulate, which is a fraction of what they actually know. The rest stays in their head, and walks out with them.
The real shift is to stop treating handovers as the moment to externalise context. By the time the handover happens, it's already too late. The context should have been living somewhere outside the individual all along, captured as part of how the work was being done, not retroactively extracted at the point of departure. When that's true, a team member leaving is just a team member leaving. The work they were doing continues because the context they were working with is still in the studio. The principal can still find the contractor agreement, the client preference, the drawing version, the decision history. Nothing critical departs with the person.
This is what we think about at Projectsmate. The product gives the studio a place for the things people would otherwise carry in their heads, project decisions, payment schedules, deliverables, client communication, vendor information, all sitting where the team can reach them. When someone leaves, what they take is their relationships and their expertise. What stays is the studio's accumulated record of how the work has been getting done. The handover conversation still happens, but it stops being the single point of failure it used to be.
Most studios discover this the hard way, after the third or fourth person leaves and they realise how much of the practice has been quietly held together by individuals rather than by structure. The studios that get ahead of it are usually the ones that have lived through enough departures to see the pattern. The earlier this is built in, the less the studio loses every time someone moves on. Eventually, departures stop being events the studio has to recover from. They just become transitions.