How to hand over an agency client without losing context
A useful agency client handover gives the next owner the agreed scope, current status, key decisions and next actions in one place. Review it together, confirm who owns the relationship and tell the client what changes.
Make the handover usable without the original owner
A colleague taking over a client needs more than access to the email history. They need to know what was agreed, what has changed, what the client is waiting for and what to do next. The handover should let them continue the work without asking the client to repeat the brief.
This applies when sales passes work to delivery, when an account lead changes and when someone takes leave. The amount of detail can vary. The test stays the same: can the next person explain the current situation and take the next action?
Use a short handover record
| Section | What to include |
|---|---|
| Relationship | Main contact, decision-maker, other stakeholders and preferred contact method. |
| Agreed work | Current scope, deliverables and a link or location for the approved version. |
| Current position | What is complete, in progress, waiting or not yet started. |
| Decisions | Important choices, who made them and where the confirmation is recorded. |
| Commitments | Dates or promises already made to the client. |
| Open issues | Unresolved questions, dependencies and risks that need attention. |
| Next actions | Specific action, one owner and a due date for each open item. |
Separate fact, interpretation and uncertainty
Write “The client asked for the launch date to move to 18 November” rather than “They keep changing their mind”. The first version gives your colleague something to check and act on. The second passes on an opinion without useful context.
Label uncertainty directly. If you do not know whether the client approved the latest copy, record “Approval not yet confirmed” and name the person who will check. Do not let an assumption become a promise during the handover.
Complete the transfer in four steps
- Prepare the record
Bring the scope, status and next actions up to date. Link to the current files and decisions. Archive or label older versions so the new owner does not start from the wrong one.
- Walk through exceptions
Spend the conversation on what the record cannot explain easily: a sensitive deadline, an unresolved disagreement or a dependency on another supplier. Add any new decisions to the record.
- Confirm ownership
Name the incoming relationship owner and the people responsible for immediate tasks. Agree when the outgoing owner stops handling routine replies and what backup remains available.
- Tell the client
Introduce the new contact and explain any practical change. Reassure them with the agreed next step and date, rather than a vague promise that everything has been passed over.
Example: the sales-to-delivery handover
Consider an illustrative branding project. The proposal includes a brand identity and a short guideline document. During the sales call, the client also asked about social templates, but those were not added to the agreed scope.
The handover should show social templates as an open request, with an owner to clarify them. If it simply says “client needs social templates”, the delivery team could mistake the request for included work.
Record the first review date, the person who signs off and the files needed before design begins. The delivery lead can then confirm readiness without re-running the sales conversation.
Use a lighter version for leave cover
For a short absence, focus on work likely to move while the owner is away. List the expected client replies, approaching deadlines and decisions the covering colleague may make. Explain which questions should wait for the owner and who can handle an urgent exception.
Give the covering colleague access before the absence begins. Ask them to find the next deliverable and latest decision. That small check can reveal a missing file or permission while there is still time to fix it.
Keep the record current after the meeting
A handover becomes unreliable if the outgoing owner keeps a separate version of the truth. Put subsequent decisions and client replies where the incoming owner works, and update ownership if the plan changes.
Stack brings client management, contacts, conversations and tasks into one workspace. That provides a place to keep the relationship and its work together. The team still needs to write clear decisions and confirm responsibilities.
Before closing the handover, ask the new owner to describe the next client-facing action. If they cannot say what it is, who is doing it and when it is due, the transfer needs one more clarification.