Project handover documentation is the written record that lets someone else carry on your work without having to ask you what you meant. It covers scope, status, deliverables, contacts, access, open risks and the decisions behind them, and it is organised for the person who will use it, not the person who wrote it. For a marketing agency, the most important handover is often the first one: the client's information and files passing to the delivery team before work starts.
This guide covers both senses. It explains what goes in a handover pack, how the process runs from planning to sign-off, what a handover email should say, and how to stop missing inputs from stalling a kick-off.
TL;DR
- A good handover pack covers scope, status, deliverables, timeline, budget, contacts, access, risks and open actions, written for whoever will use it next.
- Plan handover from day one. The APM treats it as a gradual transfer, not a date in the diary.
- Make review explicit: a named approver, dated versions and written sign-off.
- In agencies, most handover pain comes from chasing missing client inputs. Track each item as requested, received or not applicable.
- Use a single checklist and a short handover email so nothing lives only in someone's head.
Table of Contents
- What project handover documentation actually is
- What documents are required for a project handover?
- Write the pack for the person who will use it
- The project handover process, step by step
- Agency handover: from sales to delivery
- How to track missing inputs and follow-ups
- Review and sign-off: make approval explicit
- What should a handover email say?
- Common mistakes in project handover documentation
- Our perspective
- Where Clientovo fits
- A ready-to-use handover checklist
- FAQ
- Sources
What project handover documentation actually is
There are two common situations, and they need slightly different documents.
Delivery handover is when a finished project, or a project mid-flight, passes to another team or to the client. In construction this means manuals, certificates and drawings. In marketing it means logins, brand files, campaign set-ups, reports and a record of what was agreed.
Intake handover is when a new client's information moves from sales or account management to the people who will do the work. It is the point where agencies most often lose time, because the brief is thin, the logins are missing and nobody is sure who approved what.
The APM describes handover as an incremental transfer of knowledge and operation from the project team to business as usual, planned from the start. That framing matters for documentation: if you only write things down on the last day, you will forget half of what you know.
What documents are required for a project handover?
The answer depends on the industry, so start from the people receiving the work.
In construction and property, the list is formal. A building handover guide from BC Housing lists operation and maintenance manuals, as-built drawings, commissioning documents, fire safety plans, keys and warranties. In UK public-sector building projects, the University of Glasgow's Soft Landings procedures require a handover plan checklist, completed by all relevant parties, confirming training, certification and document handover.
In services, software and marketing, there is no statutory list, but the same logic applies. A practical handover pack contains:
- Project overview: what the work is for, the goals and what success looks like.
- Scope and exclusions: what was agreed in writing, and what was explicitly left out.
- Current status: what is done, what is in progress, what is blocked.
- Deliverables: files, links and locations, with version numbers or dates.
- Timeline and milestones: what is next and when.
- Budget and commercial terms: fees, payment structure, notice terms.
- People and contacts: who decides, who approves, who to call.
- Access and assets: logins, platforms, brand guidelines, templates, with who owns each.
- Risks, red flags and open actions: the things a newcomer would otherwise discover the hard way.
- Decision log: why things were done the way they were.
The last item is easy to skip. APM guidance recommends collating lessons learned as the project progresses, because they give you a decision log and stop information disappearing when staff change.
Write the pack for the person who will use it
The same APM guidance says handover documentation should be meaningful, applicable and relevant to end-users, and that different users may need different sets. That is the single most useful rule for organising the pack.
In an agency, that usually means three layers:
| Reader | What they need | Format that works |
|---|---|---|
| Account lead or project manager | Scope, commercial terms, contacts, risks, decision history | One-page summary plus the signed documents |
| Specialists (SEO, paid media, design, development) | Goals, brand assets, platform access, existing performance, constraints | A section per discipline, with files linked |
| Client stakeholders | What was agreed, what happens next, what you still need from them | A short plain-English recap with dates |
Do not send everyone the full folder. A designer does not need the payment terms, and a finance contact does not need the analytics logins. Put a summary at the top, and keep the evidence behind it in clearly named folders.
A simple folder structure
- 01 Summary and contacts
- 02 Agreement and commercial terms
- 03 Brief and goals
- 04 Brand assets
- 05 Access and tools
- 06 Work to date
- 07 Open actions and risks
Numbered folders keep the order stable, and the summary is always the first thing anyone opens.
The project handover process, step by step
One online project management course provider splits handover into pre-handover, handover and post-handover phases, with responsibility for deliverables passing from the project manager to an operational manager. It is a simple model and it works for agencies too.
Before handover: agree what "done" means
The APM's research says defining handover is necessary to align everyone around a common goal, and that dates, priorities and responsibilities need to be clearly communicated. In practice:
- Agree the information requirements with the receiving team early.
- Name one person responsible for the transition. The APM's Fusion Point guidance says a single Business Change Manager should manage transition activities, coming from the part of the organisation that will use the outputs.
- Involve the people who will use the work. The APM recommends involving end-users from the outset so the right people are trained at the right time.
- Decide who has authority to approve the handover.
During handover: transfer, explain, confirm
Hold a short walkthrough, not just a file drop. A document tells people what exists. A conversation tells them what matters. Cover status, the awkward bits, the stakeholders to handle carefully and anything promised verbally.
Then confirm in writing. The APM says sign-off should cover the work, the documentation and the training, not just the deliverable itself.
After handover: stay reachable for a defined period
Handover does not end at the meeting. The Department for Education's Soft Landings guide describes a 12-month rectification period after school building handover, with the contractor's representative on site one day a week for six weeks. Your agency project will not need that, but the principle carries over: agree a short, defined window in which the previous owner answers questions.
Agency handover: from sales to delivery
If you run a marketing agency, the handover that costs you most is the one between "client signed" and "team starts". Details agreed in sales calls do not reach the people doing the work, and nobody owns the chase for missing logins.
The ISBA, the UK body for advertisers, recommends briefing in three stages: clarify the brief, write it down, then meet collaboratively. Clarification defines objectives, expectations and project goalposts before agency work starts. The written brief should state the problem, brand fundamentals, business and marketing goals, communications objectives, target audience, budget and KPIs.
That is a good template for the core of your intake pack. ISBA also frames the written brief as a shared contract, because recording objectives and KPIs cuts ambiguity between the client's stakeholders and the agency.
A US industry briefing guide from the Mirren group adds a useful discipline: the basic information is collected from the client, documented by the account lead and approved by the client before the team begins. Its six pre-work questions cover the assignment, the final decision-maker, objectives and measurable KPIs, key deliverables, budget, timeline and critical notes.
What to confirm before kick-off
A UK agency operations toolkit suggests confirming the following before kick-off: written scope, fees, payment structure, cancellation or notice terms, signed or acknowledged documents, client contacts, brand assets, tools and access, goals, deadlines and communication preferences. Missing answers should be chased, and red flags noted for the kick-off agenda.
Our client onboarding checklist for marketing agencies turns that list into something you can use on the next signed client.
How to track missing inputs and follow-ups
The usual failure is not that agencies do not know what they need. It is that nobody owns the chasing. Requests go out once, the client is busy, and the kick-off drifts.
A simple tracker fixes most of it. For each item, record:
- What: the specific input, for example Google Analytics access or logo files in vector format.
- Owner on the client side: a named person, not "the client".
- Status: requested, received, or not applicable. The same toolkit recommends exactly this three-way split for access, and "not applicable" matters because it stops a closed question looking like an open one.
- Date requested and next chase date.
- Impact if missing: what the team cannot do without it.
Review the tracker before the kick-off meeting. Items still open go on the agenda, with a named owner and a date. Red flags, such as a client who has not confirmed the budget, belong in the client record, not in someone's memory.
If you want to see how this works when it is handled for you rather than by your account team, how managed agency client onboarding works walks through the stages.
Review and sign-off: make approval explicit
Handover goes wrong quietly when approval is informal. ProCopywriters, the UK alliance of commercial writers, recommends making review explicit: identify the authorised approver, give context and the points needing decisions, request written approval, and keep dated versions and feedback records.
The reasoning is simple. If someone says "looks good" on a call, nobody can later prove which version they meant. Written sign-off, tied to a dated version, closes that gap.
A workable sign-off routine for an agency:
- The team lead reviews the pack against the checklist, and notes gaps.
- The account lead confirms the summary matches what was sold.
- The client approves the key facts in writing: scope, goals, contacts and timeline.
- The approved version is saved with a date, and earlier versions are archived.
The team review step is where many agencies skip ahead. Someone other than the person who collected the information reads it cold. If they cannot start work from it, neither can anyone else.
What should a handover email say?
A handover email has two jobs: transfer the work, and ask for what is still missing. Keep it short, specific and easy to answer. Here is an outline you can adapt.
Subject line: name the project and the purpose, for example "Project name: handover pack and three outstanding items".
Body, in this order:
- Purpose in one sentence: what is being handed over, and to whom.
- Where everything is: a single link to the pack, not ten attachments.
- Status in two or three lines: done, in progress, blocked.
- Open items: a short numbered list, each with an owner and a date.
- Next step: who does what, and the date of the walkthrough.
- Contact window: how long you are available for questions, and how to reach you.
- Ask for confirmation: a clear request to reply with approval or questions by a stated date.
When the email is going to a client asking for inputs, make each ask tiny. "Please send admin access to your analytics account by Friday" gets answered. "We still need a few things" does not. Many sample handover emails online follow a similar pattern: a subject line naming the project, a list of attached documents, and a request to review and reply.
Common mistakes in project handover documentation
- Writing it on the last day. Keep notes and a decision log as you go.
- One giant document. Use a summary on top and layered detail below.
- No named owner. Handover without a person responsible falls between teams.
- Assuming access is sorted. List every platform and who holds the admin rights.
- Verbal agreements missing from the record. If it was promised, it is written down.
- No sign-off. Without written approval, you cannot show what was accepted.
- No contact window. Questions arrive after handover, so plan for them.
Our perspective
Most agencies we speak to do not lack an onboarding process. They lack someone whose job it is to run it. The form goes out, the client answers half of it, and a busy account manager is left to chase the rest between other tasks.
Our view is that handover quality is decided long before the kick-off meeting, in how information is collected, chased and checked. That is why we built Clientovo as a managed service rather than another set of forms: our team handles the follow-ups on missing inputs, organises the materials and puts a team review step in before the handover is complete.
The result we design for is a structured handover pack, with a full summary and reviewed client files, delivered through your agency portal. You keep the relationship with your client. We take the repetitive admin that slows it down. For agencies that want faster, clearer project starts, we think that division of labour is the right one.
the author
Where Clientovo fits
If collecting and chasing client information is where your handovers stall, Clientovo is built for that stage. We automate the follow-ups, organise the files, run a team review and deliver a structured handover pack, while you stay in control of the client relationship.
Pricing is simple: £14 one-off per onboarding on pay as you go, or £34 per month on the monthly plan, and the first client onboarding is free to try. You can see both options on the Clientovo homepage. If you are weighing a managed approach against doing it with forms, onboarding forms compared with a managed service sets out the difference.
For the wider picture of who does what at each stage, our guide to the marketing agency workflow, stages and handovers is a good next step, and our piece on digital client onboarding for agencies covers the intake side.
A ready-to-use handover checklist
Copy this into your own template and tick through it before sign-off.
Information
- Project overview and goals recorded
- Scope and exclusions confirmed in writing
- Budget, fees and notice terms noted
- Signed or acknowledged documents filed
People
- Client decision-maker and approver named
- Day-to-day contacts listed
- Internal owner of the handover named
- Communication preferences recorded
Assets and access
- Brand guidelines, logos and templates received
- Each platform listed with status: requested, received or not applicable
- Admin rights and owners recorded
Review
- Second team member has read the pack cold
- Red flags noted for the kick-off agenda
- Client has approved key facts in writing
- Dated version saved, older versions archived
After
- Walkthrough held
- Question window agreed
- Open actions have owners and dates
FAQ
What documents are required for a project handover?
It depends on the sector. Construction handovers typically include operation and maintenance manuals, as-built drawings, commissioning documents, fire safety plans, keys and warranties. For agency and service projects, expect a summary, scope, deliverables, timeline, budget, contacts, access details, risks and open actions.
What is the handover procedure?
It runs in three phases: plan before handover, transfer during it, and support afterwards. Before, you agree requirements and name an owner. During, you share the documents, walk the receiving team through them and get written sign-off. Afterwards, you stay available for questions for a set period.
How do you hand over a project to a colleague?
Put everything in one organised location, lead with a one-page summary and hold a short walkthrough. List open actions with owners and dates. Agree how long you will be reachable for questions, and confirm the handover in writing.
How do you write a handover email?
Name the project in the subject line, say what is being handed over and link to the pack. Summarise status in a few lines and list outstanding items with owners and dates. Close with a clear request for confirmation by a stated date.
Sources
- How to Successfully Handover Projects, APM
- How can we hand over projects better? APM, 2017
- Fusion Point Guidance: Transition to Operations, APM
- Guide to Building Handover, BC Housing
- Soft Landings Policy, Process and Procedures, University of Glasgow
- Soft Landings Guide, Department for Education
- How to brief your agency, ISBA
- Handover and Sign-off, ProCopywriters
- The Mirren Project Kick-Off Briefing Guide
- What are the 3 Phases of an Effective Project Handover?