How to reduce handovers in an agency

To reduce handovers in an agency, cut the number of times work changes hands, then make the remaining ones short and written down. Keep the sales conversation, the proposal and the project in one record, give each client a single named owner, and use milestones and status reports so nobody has to be briefed from memory.

A handover is any point where responsibility for a client or task passes from one person to another: sales to delivery, account manager to producer, one team to another, or a person to their cover during leave. Each one is a chance to lose something the client said.

Why handovers hurt

Most of what makes a client relationship work is small and unwritten. The client mentioned a launch date on the first call. They dislike phone calls. The managing director wants any change in scope approved by her, not her assistant. When work passes to someone new, those details travel only if someone remembers to pass them on.

The client experiences the loss as repetition. They are asked again what they want, what was agreed, who signs off. It signals that nobody was listening the first time.

Count your handovers first

Map one real client from enquiry to delivery. Mark each point where a different person takes over. A typical agency finds five to eight: sales to account lead, account lead to project manager, project manager to designer, designer to developer, and back again for review. Then ask of each: is this change of person necessary, or is it a habit?

Some are necessary because skills differ. Many exist because the sales team and the delivery team keep separate records and have to talk to each other to bridge the gap. Those are the ones you can remove.

Keep one record from enquiry to delivery

The most effective change is structural. When the lead, the proposal, the agreed scope and the project all live in one record, the person who picks up the work reads what was promised instead of being told a summary of it.

Practical steps:

Log every conversation and decision on the client’s record, not in a personal inbox or notebook.
Write the proposal so its phases and deliverables are specific enough to become the project plan.
When the client accepts, create the project from the accepted phases. Do not retype them.
Attach questions the client answered, so the answers travel with the work.

This is where an engagement helps. Treat the agreement, with its fee, term and deliverables, as the record that the whole team works against, and keep it attached to the client rather than filed away after signature.

Turn the proposal into milestones

The proposal already describes what you will deliver, in phases. Convert each phase into a milestone with a due date and a gate: the condition that says it is finished. A new team member who opens the project sees what was agreed, what is done and what is next, without a briefing.

Where the statement of work lists exclusions, keep them visible in the project. That is the first thing a new person needs when the client asks for something extra.

Give each client one owner

Spread responsibility thinly and every handover multiplies. Name one person per client who is accountable for the relationship, even if several people do the work. The owner is the one the client calls and the one who knows the full story. When that person changes, treat it as a formal event with a written brief.

Write handovers down in a fixed shape

When a handover has to happen, use the same template every time. One page is enough:

Who the client is and what they want, in two sentences.
What was agreed: scope, fee, dates, exclusions.
Where things stand: what is done, what is next, what is blocked.
People: who decides, who approves, who to avoid surprising.
Preferences and history: how they like to communicate, past issues.
Open questions and anything promised but not yet done.

Then hold a short call between the outgoing and incoming person with the client’s record open. Ten minutes beats a long email that nobody reads.

Replace briefing meetings with status reports

Much internal briefing exists only because nobody can see the state of a project. A regular status report built from the milestones as they stand gives the client and the team the same view. It also forces a weekly check that the plan and the reality match. When the report is published to the client, nobody needs to ask a colleague “where are we on this?”

Plan for leave and sickness

The hardest handovers are the ones nobody planned. Make sure at least two people can open any client record and understand it. If the only way to know the state of a project is to ask one person, you have a single point of failure, not a team.

Measure it

You will know it is working when:

Clients stop being asked questions they already answered.
A new person can run a client’s next week after reading the record for fifteen minutes.
Questions to a colleague about “what was agreed?” become rare.
Sales and delivery stop disagreeing about scope.

Where software helps

In Kervol, the lead, proposal and project share a client record. Accepting a proposal turns its phases into the project’s milestones, each with its gate and due date, and a status report built from those milestones can be published to the client. Engagements with terms, fees and status and a task list are built. A timeline and resourcing are planned and not yet available. A tool only shortens the handover if the team writes things down in it.

Checklist

You have mapped the handovers on one real client.
Sales, proposal and project share one record.
Accepted phases become milestones without retyping.
Every client has one named owner.
A one page handover template exists and is used.
Regular status reports replace briefing meetings.
At least two people can read any client record.
Exclusions stay visible in the project.