Definition
A handover record is a single document, built while a departing marketer is still at work, that lists everything they own and gives each item one new owner. The tutorial for handing over a departing marketer's work runs the handover itself, from the first list of repeating jobs to the checks once the person has gone; the record is what that process writes down and what survives it.
Three features set it apart from a farewell note or a list of open tickets. It covers everything the person owns, not only what is on their mind that week, so it is built from their calendar, the work system and the accounts in their name rather than from memory. Every row ends in a named owner, or in an explicit decision that nobody will take the item on and what becomes of it instead. And it outlives the leaving date: the coordinator keeps it open and marks a repeating job as handed over only when it has actually run in someone else's hands.
What the record holds and who keeps it
The rows fall into a handful of kinds: repeating tasks, open work, accounts and the admin rights on them, payment methods and integrations, files kept outside shared spaces, relationships with agencies, suppliers and colleagues, the procedures the leaver looked after, and know-how that lives only in their head. Each kind has its own proof that the move worked. A task is handed over when the new owner has run it for real; an account, when someone else can administer it; a relationship, when the new contact has been introduced; a file, when it sits in a shared space or has been disposed of on the say of whoever owns data protection.
One person, in the tutorial the leaver's manager or the operations lead, keeps the record in the team's shared space and chases every row to an owner.
In practice: vacancies, stepping up, new roles and taking over
Vacancies. A handover gives the work owners; it does not give the team back the hours. While the post stands empty, the manager's tutorial for keeping work going through a vacancy begins from the handover record and decides, item by item, what stops or pauses, what a colleague takes on, what is bought in and what waits for the replacement.
Stepping up. A colleague asked to carry part of the role reads the same record from the other side. The careers tutorial on stepping up while a role is vacant builds the list of what is coming to them from it, or from the manager's cover plan where there is one.
New roles. The person who fills the post reads it early. The tutorial on a new starter's plan for their first months puts any record left by a predecessor beside the team's onboarding pack in what to gather before starting.
Taking over. Where nobody handed over at all, the inventory for taking over an existing marketing programme rebuilds the picture from the accounts, the money being spent and the commitments already in the diary, and its inventory document is meant to become the handover record for whoever comes after.
A jewellery brand finds the report nobody had listed
Gynnyar Jewellery, an invented maker of silver jewellery selling online, had a marketing team of 4. Its email lead resigned with 5 weeks to go, and the marketing manager opened a handover record that week. The lead's own list ran to 11 items; her recurring reminders turned up a twelfth, a report of the previous month's best-selling designs that she emailed to the brand's 2 casting suppliers on the third working day of each month so they could plan stock, and that no colleague had heard of. The row named the ecommerce assistant as its new owner. The assistant sent the next report herself before the lead's last day, with the lead checking it. The record stayed open for 6 weeks after the leaving date, until each of the 12 items had run under its new owner, and was then filed.
Related terms
The Coverage MatrixA table of a team's recurring tasks and the accounts behind them, recording who can do each one unaided today, so work only one person can do becomes visible. is maintained while the whole team is present and shows which tasks only one person can do; the handover record is made when that person is going and gives those tasks new owners. A Standard Operating ProcedureThe written way of doing one recurring task: who owns it, what starts it, the steps in order, checks and exceptions, so anyone qualified gets the same result. is where the repeatable part of a handed-over task gets written down, and one the leaver looked after needs a new process owner of its own. An Access ReviewA periodic check of who can use each marketing tool: every account matched to a current person, supplier or integration, with owners, deputies and narrow roles. sets the order for accounts: rights move to someone else first and the leaver's sign-in is removed afterwards. Choices made about the leaver's items, such as stopping a report nobody claims, belong in the team's 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. so the reasoning outlasts the record. The Stack RecordThe live register of every marketing tool: owner, deputy, cost, notice date, users, use cases and status, kept current by onboarding, reviews and retirement. names an owner and a deputy for every tool, which makes it a quick way to find the tools where the leaver held either role.
Common confusions
- A handover record is a handover note. A note holds what the leaver happens to remember; the record is built from calendars, systems and accounts, and every row ends in an owner or a recorded decision.
- It is the same as the cover plan. The record gives each item an owner. The manager's cover plan, made when the role stays empty, decides how much of that work the remaining team can actually carry.
