Somewhere between the product team's last stand-up and the client's first support ticket, something slips. It rarely announces itself. It arrives instead as a delayed launch, a miscommunicated brief, a relationship that quietly cools. The handoff — that moment when responsibility moves from one person, team, or function to another — is among the most underexamined seams in organisational life, and also among the most consequential. Most mid-size organisations assume their handoffs are functioning well because no one has formally complained. What the following audit process suggests is that silence is not the same as health. This guide walks through a structured, internally led review that identifies the three most common failure points in handoff sequences, using nothing more than a handful of honest conversations and a single shared document that anyone on the team can maintain.
Before the First Interview: Setting the Scene ¶
The audit begins not with a meeting but with an observation. On a Tuesday morning in October, or a slow Friday in February — the season matters less than the mood — someone needs to sit with the organisation's last three or four project timelines and trace them backward. Not to assign blame, but to notice. Where did the pace change? Where did an email thread go quiet for longer than expected? Where did a deliverable arrive underdone, and who handed it? These are the coordinates of the audit. Before a single interview is booked, the person leading the process should map out no more than six handoff moments they want to examine — transitions between design and development, say, or between sales and account management, or between strategy and execution. Six is enough. More than that and the inquiry loses its precision. The shared document — a plain collaborative file, nothing elaborate — goes live at this stage, with those six moments named and dated at the top.
The First Failure Point: The Assumption of Shared Context ¶
The most common handoff failure is also the quietest. Team A completes their phase of a project and passes it to Team B with the genuine belief that everything Team B needs to know has been communicated. Team B receives the work and proceeds with equal confidence. The gap between those two certainties is where projects lose weeks. In interviews — conducted one-on-one, unhurried, ideally in a room that is not the usual meeting room — the question to ask is simply: what did you know when you received this work, and what did you have to find out yourself? Phrases like 'I assumed they knew' and 'I thought that was already decided' appear reliably in these conversations. They are not signs of carelessness; they are signs of a missing protocol. The audit document should log each instance. By the third interview, patterns become visible. A design team in Manchester might know the client's brand history intimately; the developers in the next building may never have seen the original brief. The handoff passed the files but not the story.
The Second Failure Point: The Disappearing Owner ¶
The second failure arrives when a handoff happens but no one formally accepts it. This is distinct from the context problem — here, the information may be intact, but accountability has gone diffuse. Ask each person interviewed to name who owned the work the moment it left their hands. Then ask the receiving party the same question. A divergence in their answers — and there almost always is one — marks the failure point precisely. In practice, this often happens at the boundary between departments that operate on different planning cycles. A strategy function working in quarterly arcs hands to a delivery function working in weekly sprints. The strategy team considers the handoff complete on the day of the presentation. The delivery team does not consider themselves formally engaged until a project is added to their sprint board, which may be two weeks later. Nothing dramatic occurs in that fortnight — but small decisions get made without the right people, and momentum quietly dissipates. The audit document should record, for each handoff examined, who named themselves as the owner at the point of transfer, and who named themselves as the owner at the point of receipt.
The Third Failure Point: The Feedback Loop That Never Closes ¶
The third failure is structural and often invisible until the organisation has run three or four projects through the same broken sequence. When a handoff produces a problem — a deliverable that needs reworking, a client who is dissatisfied, a timeline that compresses — the people at the receiving end of the handoff rarely have a formal mechanism to communicate that information back to the people who handed off. They fix it, absorb it, or escalate it sideways. The originating team never learns that their handoff was insufficient. During the audit interviews, the question here is: when something arrived to you incomplete, what happened next, and did the team before you know about it? In healthy organisations, the answer involves a named conversation and a change in practice. In most, the answer is a variant of 'we just sorted it out ourselves.' The audit document should flag each instance where corrective action was taken by the receiving party without the originating party's knowledge. This list is the clearest evidence the organisation has of where process design is failing.
Running the Interviews: Pace, Order, and Atmosphere ¶
The interviews are the heart of the audit, and their quality depends on pace. Each conversation should last between forty and sixty minutes — long enough to move past the polished first answers, short enough that the participant remains energised. The order matters: begin with people in the middle of the handoff chain, not at either end. A project manager or account executive who sits between creative and delivery is likely to hold the most unfiltered picture of how information actually moves. Work outward from there toward the originators and the recipients. The atmosphere of the interviews should be genuinely curious rather than investigative. A useful framing at the opening of each conversation: this is a process review, not a performance review, and nothing said here will be attributed by name in the final document. That assurance changes what people say, and how quickly they say it.
What the Shared Document Becomes ¶
By the time the interviews are complete — typically after eight to twelve conversations in a mid-size organisation — the shared document should hold three distinct sections. The first is a log of handoff moments examined, each annotated with the names of the teams involved, the point at which the handoff occurred, and whether context, ownership, and feedback loops were operating. The second is a list of recurring phrases: the language people use to describe confusion, assumption, and relief. These phrases are more diagnostic than any framework — they are the organisation speaking honestly about itself. The third section is a set of no more than five specific proposals for change. Not sweeping structural reforms, but targeted adjustments: a one-page context sheet that travels with every project brief, a named handoff owner recorded in the project management system at the moment of transfer, a fifteen-minute retrospective built into the workflow two weeks after every major handoff. Specific, small, and immediately implementable. The document does not need to be long. The organisations that use it well treat it as a living file, revisited quarterly rather than archived after a single reading.
When the Audit Finds More Than Expected ¶
Occasionally — perhaps one audit in four — the process surfaces something more significant than a missing protocol. A handoff failure that has been running for eighteen months and has cost real money. A relationship between two departments that is nominally functional but practically estranged. A senior figure who has been a consistent bottleneck without anyone having ever said so directly. When the audit finds this, the instinct is often to slow down, to soften the finding in the document, to frame it carefully for a leadership audience. That instinct deserves some respect — timing and relationship matter — but the finding itself should not be obscured. The audit document is the organisation's honest record of itself, and its value is proportional to its accuracy. In these moments, the person leading the audit needs to decide whether the finding belongs in the shared document, in a private memo to a specific decision-maker, or in a conversation that precedes any written record. There is no universal answer. But the decision should be made consciously, not by omission.
The handoff audit, run this way, takes roughly three weeks from the first timeline review to the final document. It costs nothing beyond the hours of the people who care enough to run it honestly. What it returns is rarer than most organisations expect: a clear-eyed picture of where their work actually moves, and where it stalls — not in theory, but in the named, specific, traceable details of their own recent history. That picture is the beginning of something.