Why a manager's handover needs its own record
When a marketer leaves, the tutorial on handing over marketing work collects what the person owns, from the jobs that repeat and the work in flight to the accounts, files, relationships and know-how, and gives every item a new owner. The page is called the leaver tutorial from here on; it serves a manager's own tasks as well as anyone's. But at the point where it lists the people who rely on the leaver, it says that a manager's reports also hold agreements that its list does not capture, and it sends the reader to a guide written for the report. The guide written for a marketer whose manager changes is that guide: it asks the report to get the agreements written down and confirmed before the leaving date, and it leaves the incoming manager's side to this site's management section, which begins by listening. The programme inventory for a new owner covers accounts, tracking, spend and contracts, and it too sends the people side to the management hub. Each page assumes that someone else records what the manager held. This tutorial is that someone else: the outgoing manager's half.
The reason a manager needs a record of their own is what the role holds. The delegation guide lists the work that stays with a manager because it depends on the position rather than the skill: setting the team's priorities with stakeholders, hiring, development and people decisions, and representing the team's results to leadership. The marketing management pillar describes the move into management, in the Chartered Institute of Marketing's terms, as a shift away from doing the work towards directing it.
The tutorial is written for the manager who is leaving or moving to another role. It serves equally the person the manager reports to when the manager goes without warning; the same record is then built from what exists and confirmed by the people who were in the conversations. It records agreements and facts. Pay, grading, assurances about promotion, any formal performance process and employment records are for the people team to settle, working under the organisation's rules, and the record leaves them there. The sheet for each report, the dated list of promises, the named holder and level for each decision, the leaving manager's own view kept apart from the facts and the check after the leaving date are general practice built on the pages linked here, not a standard.
Before you start
- A coordinator and a date. The leaver tutorial asks for one named person to keep the handover record and names the leaver's manager or the operations lead; for a leaving manager that means the person above them or the operations lead. Begin when the departure is known, as the leaver tutorial advises.
- The manager's own handover record, begun through the leaver tutorial's steps.
- Each report's objective sheet with its change log, the authority levels agreed and their development plan. Where one of these does not exist, writing it is part of the work.
- The planning documents: the plan on a page, the roadmap, the backlog and the register of recurring work.
- Every agency and freelance agreement, with the calendar of notice dates if the team keeps one.
- The decision log, or the decisions the manager can recall.
- The person the manager reports to. Several steps end with them confirming who holds a decision, and they may be the only person who can.
- A contact in the people team, for the matters the record leaves out.
The steps
Decide who receives the handover and what it covers
Name the person the record is for: the successor, if one has been chosen, and otherwise the person the manager reports to, who holds it until someone starts. Name the coordinator, who keeps the record and chases what is missing. Then write the scope in a few lines: the manager's own work, the agreements with each report, the plan and what was promised around it, the partner agreements, the commitments to leadership and other teams, the decisions only the manager takes and the people matters still open. Add what the record leaves out, which is pay, grading, promotion assurances and formal performance records. If the manager is moving to another role inside the organisation instead of leaving, agree who may put questions to them; that is for the organisation to settle, and the record should not lean on it.
Hand over the manager's own work through the leaver tutorial
A manager has tasks and access like anyone else: a report to leadership, a planning meeting, approvals waiting in a queue, administrator rights on tools and accounts, files kept outside the shared spaces. Run the steps of the leaver tutorial for all of it, and begin the manager's own handover record there. Two of its rules matter more for a manager. Hand over first and remove sign-in second, using the access review tutorial, so that no record, integration or account is stranded; and say for each approval who approves from now on, since an agency's work can wait on a manager's sign-off. The rest of this tutorial adds the parts of the job that the tutorial's record cannot see.
Write down each report's agreements
For each person who reports to the manager, write one sheet that the person can read and correct. It holds the current objective sheet with its change log, which the objectives tutorial builds from outcomes, measures, baselines and sources, shared results with named co-owners and one development goal; the level of authority for each area of the person's work, on the scale in the delegation guide, from acting alone and reporting later down to preparing material for each of the manager's decisions; the check-ins that go with each level; the development plan; and what was agreed in conversation and not written down. The guide written for the report sets out the same agreements from the report's side, in a table that runs from objectives and authority to feedback and commitments not yet started, and asks each person to send the new manager a brief of their role. Use that table as the checklist for every sheet, ask each person to correct theirs, and keep their brief beside it.
Record what was agreed, not any assurance given. An assurance about promotion, grading or pay is for the people team to settle, as the guide written for the report says, so the sheet notes that a conversation took place and when, and anything formal stays with the people team.
Record the plan, the work and what was promised around it
Gather the documents that carry the quarter. The plan on a page comes from the quarterly planning session: objectives, key results with BaselineAn estimate of what a metric would have done without a given change, campaign or promotion, against which the effect is measured. and owners, the initiatives above the line, the risks and what was deferred. Add the roadmap, with the work under way, the work next in line and the items being considered, and the backlog with the reason each item sits below the line, including requests that were declined and what would change the answer, as the prioritising guide asks. Add the record of urgent requests and the register of recurring work with the outcome of its last review, from the tutorial on reviewing recurring work. Write down the dates the plan keeps, as the quarterly planning session tutorial sets its cadence: the weekly meeting, the monthly review and the next quarterly session.
Then list what the manager told requesters and leadership to expect, such as a launch date given to sales, a reply promised to a regional team or a request deferred to next quarter. Promises made in conversation are the part of a plan that may sit in no document, so each one goes into the work system with an owner, as the leaver tutorial does for work in flight. Include the Decision LogA running record, one row per decision, of what changed and why, what was expected, who decided and when the result will be checked., or start one from the marketing decision log template, and mark the decisions still open with the manager's recommendation for each.
List every partner agreement and its dates
List every agency, freelancer and platform partner the manager works with. For each, write the scope with what it excludes and the measures it is judged on, the fee model and the change requests raised so far, the notice date and the owner of the review that comes before it, the date and findings of the last review, any open dispute or promise, and who approves work and spend on each side. The renewal tutorial asks for the notice date and a named owner of each review in its calendar, because agreements renew by default when nobody is watching, and a notice date that falls before the successor arrives needs a holder named now.
Add the register of the accounts each partner works in and who owns each one. The diagnosis of an agency holding the business's ad accounts finds that nobody had kept such a register; writing it now gives the successor the record that diagnosis found missing. Where agencies share one customer journey, say who owns the joins between them, as the coordinating guide describes. Introduce the successor, or whoever holds the relationship meanwhile, to each agency lead by name, and tell each agency who approves what from the last day.
List the commitments to leadership and other teams
List what the manager reports and to whom: the reports, their audiences, the KPIA metric tied directly to an objective. set each one carries, the questions each one answers, who signs the monthly pack and what has been promised for the next one. The reporting cadence playbook gives the head of marketing the list of who sees which report and what each one must answer, so those pass to a named person as well. List the interfaces outside marketing that the team models guide says need a named owner: the handover of leads with sales, positioning and launch readiness with product, and budget conversations with a named finance partner. Hand the finance relationship over by the walk-through that the finance partner guide sets out for a change of marketing lead. Finally list the standing commitments to other teams, since each is a promise that continues after the manager has gone.
Name who decides what from the last day
Make a list of the decisions that the manager takes and nobody else does. The delegation guide names three that depend on the position: setting the team's priorities with stakeholders, hiring, development and people decisions, and representing the team's results to leadership. Add the approvals the manager holds in the approval route; the settling of disputes about priorities, which the prioritising guide sends to the person who set the objectives, through the escalation path it asks the team to agree; the money decisions that the table in the spending authority guide gives the marketing head as a starting structure, such as shifting budget from one line to another, drawing on contingency, handing unspent money back and committing beyond the budget year together with finance; and the agency decisions: renewal, notice and the appointment of a new partner.
For each decision, name who holds it from the last day until the successor starts, and at what level. Use the levels in the delegation guide and choose by what a wrong call would cost. Sort the list by how costly each decision would be to reverse, using one-way and two-way doors as the sorting test: a colleague can hold the reversible ones, such as scheduling and creative, at a high level of authority, while a commitment that cannot be taken back, such as leaving a channel, a long contract or a change to the brand, stays with the person above or waits for the successor. A notice to an agency belongs with the second group, as general practice, because it is hard to take back. Spending authorityThe written answer to who may make each decision that commits money, such as an order, invoice or budget change, and how far before someone else must agree. and approval rights come from the organisation and finance, not from the leaving manager, so ask the person above, and finance where money is involved, to confirm who holds each; name roles rather than people, as the spending guide advises, and keep one accountable role for each decision, as the RACI matrix requires. Then tell everyone who sends decisions upwards or sideways, the reports, the agencies and the requesters, who decides what now.
Record the people matters still open and leave employment matters alone
List the people matters in motion that the successor would otherwise inherit blind: a recruitment in progress, with the scope the advert was built from, the assessment task set and where each candidate stands, as the hiring guide lays out the stages; a recent starter and the owner of their onboarding plan; any cover plan in force and its end date, from the tutorial on covering an empty role; the development steps agreed for the coming quarter; and who holds the one-to-ones and the approvals while the post is empty. If it will stand empty for a while, the person above gives those answers before the last day, which is what the guide written for the report tells each person to ask for. Write down facts and agreements. Leave out pay, grading, promotion assurances, performance processes and every employment record: those are for the people team, working under the organisation's rules, to settle.
Walk the successor through the record and make the introductions
Walk the successor through the record one part at a time, over as many sittings as it needs, which is general practice. The finance partner guide's walk-through for a change of lead is the model. Ask for each item whether it is confirmed, changed or held over, the way the report's guide does for a role brief. Then introduce the successor by name to each report, agency lead, stakeholder and finance partner, with the leaving manager present where possible, and say to each what the successor now decides. If no successor is in post, the person above reads the record in the same sittings and holds it, and the walk-through is repeated when someone starts.
Add the leaving manager's own view of what the team needs, labelled as a view and kept apart from the facts. The successor is not bound by it. The management pillar's advice to a new manager is to listen to each person and diagnose before changing anything; the team models guide adds that a sharper decision matrix or a better rhythm of planning may remove a problem without moving a single person, and Chesterton's fence asks for the reason a thing exists before it is removed. A record that holds the reasons behind the team's shape gives the successor something to listen against.
Check after the leaving date and close the record
After the last day, check the record item by item as each date comes due, as the leaver tutorial does for a leaver's tasks. Did the planning meeting and the report to leadership run, and under whose name? Did each agency review or notice date have its named owner? Was each decision on the list taken by the person named for it, and does the log show it? Ask each report whether the sheet held by the successor, or by the person above until one starts, matches the one they corrected, and ask partners, requesters and leadership whether anything has gone unanswered. Where a colleague holds part of the manager's seat meanwhile, the tutorial written for the colleague who covers the seat shows the same period from their side. Close the record once the successor has confirmed, changed or knowingly held over every item, moving each held-over item onto the successor's own list with an owner, and once every date has passed under its new owner. Keep it where the team stores its working documents. The changes the successor makes are recorded with a date and a reason, as the objectives tutorial asks for any changed objective, so that the next handover starts from a record that was kept.
The team handover record at a glance
Keep the parts in one document that the coordinator holds, with a status against every item. The columns are a working layout, not a standard, and can change to fit the team.
| Part of the record | What it holds | Source | Who confirms |
|---|---|---|---|
| The manager's own work | Recurring tasks, work in flight, accounts, files and approvals | The leaver tutorial's handover recordOne document, kept by a coordinator, listing everything a departing marketer owns: tasks, open work, accounts, suppliers and know-how, each with a new owner. | The new owner of each item |
| Each report's agreements | Objective sheet and change log, authority levels, check-ins, development plan, agreements not yet written | Objective sheets, delegation notes and one-to-one notes | The report, then the successor |
| The plan and its promises | Plan on a page, roadmap, backlog with reasons, urgent requests, recurring work register, review dates, what was told to requesters | The planning documents and the work system | The successor, with the person above |
| Partner agreements | Scope, fee model, notice date and review owner, last review, open issues, accounts register, who approves | The renewal calendar and the agency files | The holder of each review |
| Commitments to others | Reports and their audiences, interface owners, the finance relationship, standing commitments to other teams | The reporting calendar and the interface list | The person each commitment was made to |
| Decisions and authority | Each decision, who holds it from the last day and at what level | The manager's list, confirmed by the person above and finance | The person above |
| People matters in progress | Recruitment stage, onboarding owner, cover plan, development steps, who holds one-to-ones | The hiring files and the cover plan | The person above, with the people team |
| Open questions | Items held over, and the leaving manager's views labelled as views | The walk-through | The successor |
A handcart maker hands over its marketing team (illustrative)
Orquelan Handcarts hands over its marketing team
Orquelan Handcarts, an invented maker of wheelbarrows and handcarts for gardeners and market traders, sells through its own online shop and 40 dealers. Its marketing team has 6 people: a head of marketing, a paid media and email marketer, a content marketer, a designer, a dealer marketing executive and a web and data executive. It works with a search agency on a retainer and a freelance photographer. The head of marketing resigns with 7 weeks' notice. The managing director, to whom she reports, agrees to coordinate the handover and to hold the team's decisions until a successor starts, 9 weeks after her last day.
The head of marketing begins with her own work through the leaver tutorial and builds the rest in 3 weeks. Each of the 5 reports receives one sheet. Four confirm theirs as written; the dealer marketing executive corrects the authority level for dealer discount codes, which the head had recorded as "act and tell me afterwards" and the executive remembers as "act, then tell me straight away". The plan on a page holds 3 objectives and the roadmap 11 items, and the backlog holds 14 items with their reasons. While listing promises she finds one that is in no document: she told the dealers in conversation that a spring display kit would be ready before the trade day. It goes onto the roadmap with an owner and a date. The partner list shows that the search agency's notice date falls 5 weeks after her last day, 4 weeks before the successor is due, and the managing director takes the review. Nine decisions are listed with holders. Among them, the managing director takes priorities, escalations and the agency notice; the web and data executive, who already runs the weekly meeting, signs the monthly pack and takes the weekly triage as the named deputy at "recommend, then act unless I object"; moving money between lines and releasing the contingency line stay with the finance director under the company's own delegation; hiring waits for the successor.
Four weeks after the last day the managing director, who still holds the record, checks it. The monthly report ran under the web and data executive's name and the search review took place before its notice date. One dealer request had waited 6 days because nobody knew who approved a larger display budget, so that line is added to the decisions list.
The successor starts 9 weeks after the last day and reads the record in 3 sittings. Of 44 items, 38 are confirmed, 2 are changed and 4 are held over, among them whether to keep the freelance photographer; the 4 move onto the successor's own list. The successor changes nothing in the team's structure while the record is open, and the head's view that the designer's role should move under the content marketer is read, noted and left for later. The record is closed 12 weeks after the last day.
The team structure hub maps the other common team problems to the guides that deal with them.
Common mistakes
- Handing over only the manager's own tasks. A record built for a contributor shows tasks and accounts. It cannot show the agreements, the plan or the decisions that only a manager holds. Add the parts in this tutorial.
- Waiting for each report to write their own brief. A report's brief is welcome, but the manager holds the other half of every agreement. Write the sheet and ask the person to correct it.
- Passing on assurances about promotion, grading or pay. These are for the people team to settle. Record only that a conversation took place.
- Naming a holder without a level. A colleague who holds a decision with no stated level is left unsure whether to act or to ask. Set the level for each decision, and keep hard-to-reverse decisions higher.
- Treating authority as the manager's to give. Money and approval rights come from the organisation and finance. The person above confirms who holds them.
- Missing the notice date. A review that has no owner when the date arrives becomes a renewal by default. Name the holder before the last day.
- Writing verdicts into the record. Opinions about individuals can colour the successor's reading of each person. Keep facts and agreements in the record, label views as views and let the successor judge from the work.
- Closing the record on the last day. The gaps show as dates come due. Keep the record open until every item has run under its new owner.
- Starting late. The leaver tutorial's advice is to start when the departure is known. Start then.
