Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Marketing Operations › Process

Handing Over Marketing Work When Someone Leaves

How to hand over a marketer's work before they leave: recurring tasks, work in flight, accounts and admin rights, files, suppliers and unwritten know-how.
Tutorialbeginner11 min readUpdated

Why handovers fail after the leaving date is set

Most handovers are a document written in the last few days and a meeting in the last few hours. The leaver lists what they remember, which is the work on their mind that week. The monthly task that runs after they have gone is missing. So is the admin right they forgot they held, the export they set up long ago and the supplier who will ring them next quarter. Nobody reads the document closely until something breaks, and by then the only person who could explain it has left.

Three things make leavers' handovers harder than other handovers. The person's attention is moving elsewhere, so early effort counts for more than late. Their knowledge is spread across systems, inboxes and habits that no single document captures. And some of what they hold is access: accounts, pages and payment methods in their name, which can be stranded or lost if they are removed in the wrong order.

Several pages cover parts of the departure. The tutorial on reviewing access to marketing tools removes sign-in and replaces accounts that still hold records or keys, handing over first and removing second. The tutorial on reassigning CRM records when someone leaves moves records, routing slots, sender names and alerts. The automation governance guide transfers workflow ownership as a step in the leaver process. The agency offboarding checklist collects what an agency leaves behind. This tutorial puts those in order inside one handover and owns the part none of them covers: the knowledge. When nobody handed over at all, the tutorial on taking over marketing is the inheritor's inventory instead. Employment terms, notice periods and the HR side of a departure follow the organisation's own process and are out of scope.

What leaves with the personCovered by
Sign-in, admin rights and shared loginsReviewing access to marketing tools
CRM records, routing and sender namesReassigning CRM records
Automated workflows they ownAutomation governance
Recurring tasks, work in flight, files, relationships and judgementThis tutorial

Before you start

  • Know the departure date and agree time with the leaver. Handover work needs a share of their remaining time, agreed with their manager, not squeezed around their normal work.
  • Name a handover coordinator. Usually the leaver's manager or the operations lead. One person keeps the handover record and chases each item to a new owner.
  • Open the records. The work system, the access register, the procedure library and the team's coverage matrix if one exists, which shows the tasks only this person could do.
  • Know who owns data protection. Files containing personal data found outside shared systems need a decision that is theirs, not the handover's.
  • Read the SOP tutorial. The SOP tutorial is how undocumented recurring tasks become procedures, and how a procedure the leaver owned gets a new process owner.

The steps

  1. List the person's recurring tasks and when each runs

    Sit down with the leaver and list everything they do on a repeating basis, with how often and when it next runs: weekly reports, monthly list refreshes, quarterly budget reconciliations, annual renewals, seasonal campaigns. Walk through their calendar, their recurring reminders and the work system's history to find what they forget to mention. Ask specifically about tasks that run after the leaving date, because those are the ones that fail first. Note for each whether a written procedure exists. A task with no procedure and no one else who has done it is the highest priority for the steps that follow.

  2. List their work in flight and its next step

    From the work system, list every open item the person owns or is working on: campaigns in build or review, briefs waiting for sign-off, requests in triage, approvals they are due to give. For each, write the current state and the next step, in enough detail that someone else could take it on without asking. The work management guide explains why work that lives in the work system is easier to hand over than work that lives in an inbox; anything the leaver is working on that is not in the system should be added now.

  3. List accounts, pages and admin rights held in their name

    List every account, page and tool where the person is an administrator, an owner or the only user with a particular role: ad accounts, social pages, the email platform, the CRM, the website, the tag container (GTM), analytics, the asset library. Include payment methods on their card, domains or subscriptions registered to their email, and integrations connected with their credentials. The company pages guide warns against a page left with a single super admin, and the same applies everywhere. Hand these over first, following the access review tutorial: a new administrator added, payment and integrations moved to lasting accounts, and only then the leaver's sign-in removed. The removal across every tool, on the last day, follows the marketing tool access request SOP.

  4. Find files and exports kept outside shared spaces

    Ask the leaver where they keep things that are not in the shared systems: personal drives, desktop folders, email attachments, notes apps, browser bookmarks. Look especially for spreadsheets and exports, such as contact lists, event attendees or audience files, because these often contain personal data. Move what the business needs into the shared space where it belongs, such as the asset library for approved creative, and decide with whoever owns data protection what happens to files of personal data. The GDPR entry summarises the principles that personal data is kept secure and no longer than necessary; a contact list on a departing person's drive meets neither, and the decision about it is not the handover's to make alone.

  5. List the suppliers, agencies and colleagues who rely on them

    List the people inside and outside the business who contact this person to get things done: agencies, printers, freelancers, platform account managers, event venues, sales colleagues, product managers. For each, note what they come to the leaver for and how often. Then introduce the new owner to each of them before the leaving date, by name, so nobody discovers the change by sending an email to an address that bounces. Where an agency's work depends on this person's approval, say who approves from now on. When the person leaving manages others, each of their reports also holds agreements with them that this list does not capture, such as objectives, authority levels and a development plan, and the guide for a marketer whose manager is changing covers getting those written down before the leaving date. The manager's own half of that handover, covering each report's agreements, the plan and its promises, the partner agreements and who decides what from the last day, is set out in the tutorial on handing a marketing team to the next manager.

  6. Capture what they know that is not written down

    For each recurring task and each relationship, ask the questions that draw out judgement: what do you check that is not in any procedure, what has gone wrong before and how did you fix it, which stakeholder must see this before it goes out, which numbers need a footnote, what would you warn your replacement about? Record the answers in the handover record. Turn the repeatable parts into procedures, or add them to existing ones, through the SOP tutorial. Put context that applies to everyone, such as an approval nobody else knew about, where it belongs: the approval matrix, the intake form or the team's onboarding material.

  7. Assign a new owner to every item

    Go through the handover record and give every item one new owner: each recurring task, each open piece of work, each account, each relationship and each procedure the leaver owned. Use a RACI matrix where an item needs more than one role, with one accountable owner per item. Procedures the leaver owned need a new process owner as well as a new task owner, as the SOP tutorial requires. Where no one can take an item on, say so and decide what happens to it, rather than leaving it assigned to someone who has gone. Then run the CRM reassignment and the automation ownership transfer from their own tutorials. If the post will stand empty for a while, the tutorial on covering an empty role takes those decisions further, sorting each item into stop, pause, cover, buy in or wait until the replacement starts.

  8. Shadow the recurring tasks before they go

    For each recurring task, have the new owner run it for real while the leaver watches and corrects, then compare the result with what the leaver would have produced. A procedure the leaver wrote in their last weeks will have gaps, and shadowing is how they are found while someone can still fill them. Prioritise the tasks that run soonest after the leaving date and those with no procedure. Where a task will not come round before the person leaves, walk through it step by step with the new owner and record the walk-through.

  9. Check after they have gone that nothing has stopped

    After the leaving date, check the handover record item by item as each recurring task comes due: did it run, did the output look right, did anyone receive an email from the leaver's name or a bounce from their address? Check that sign-in has been removed on the timing the access review sets and that no integration or scheduled export failed. Ask the people on the relationships list whether anything has gone unanswered. Keep the record open until every recurring task has run at least once under its new owner, then close it and file it with the team's operational records.

What the handover record holds

The handover record is one document, kept by the coordinator in the team's shared space, with one row per item. Its value is that every item has a new owner and a status that can be checked after the person has gone. A handover record kept this way also tells whoever covers the gap or fills the post what the role carried.

Item typeWhat to recordNew owner confirms
Recurring taskWhat it is, when it runs, where the procedure is, who shadowed itRan it for real at least once
Work in flightCurrent state, next step, deadlineHas taken it on in the work system
Account or admin rightThe tool, the role, what was moved and when sign-in was removedCan administer it
Payment or integrationWhat runs on it and the lasting account it moved toNothing failed after the move
File or exportWhere it was, where it went or how it was disposed of, who decidedCan find it, or knows it is gone
RelationshipWho, what they rely on, when they were introducedHas been in contact
Procedure ownedThe procedure and its new process ownerAccepts ownership and the review date
Know-howWhat the leaver explained and where it was written downHas read it

A coffee roaster's paid media specialist leaves (illustrative)

Illustrative example — not a real result

Calvizzo Roasters hands over paid media

Calvizzo Roasters, an invented specialty coffee roaster selling subscriptions online and beans to cafés, had a marketing team of 5. Its paid media specialist resigned with 4 weeks before her last day. The marketing manager coordinated the handover and set aside half of each Friday for it.

The first list of recurring tasks had 9 items. Walking through her calendar found a tenth: on the first working day of each month she refreshed the customer audience used to exclude existing subscribers from acquisition ads, by uploading an export from the subscription platform. Nobody else knew it happened. Without it, the business would have paid to show acquisition ads to its own subscribers within a month.

The accounts list found 2 risks. The ad accounts' payment method was her company card, and one of the business's 2 social pages had her as its only administrator. The manager was added as a second administrator on the page and the payment moved to a company account in the first week, before anything else changed.

She also kept a spreadsheet of 140 wholesale café contacts on her personal drive, built from trade show conversations. The manager and the director who owned data protection agreed that the contacts the business needed would be added to the CRM with their source recorded, and the spreadsheet was deleted from her drive before she left.

The digital marketer who took over paid media shadowed the audience refresh twice, once while she watched and once from the procedure she wrote. Three days after her leaving date, the access review removed her sign-in. On the first working day of the next month, the refresh ran on time.

Common mistakes

  • Starting in the last week. The leaver's attention and availability are already elsewhere. Start as soon as the departure is known.
  • Listing only current work. The monthly or annual task that runs after they leave is the one that fails. List recurring tasks from the calendar and the records, not from memory.
  • Removing access before handing over. Records, integrations and admin rights are stranded. Hand over first, remove second.
  • Leaving payment methods in the leaver's name. Campaigns stop when the card is cancelled. Move payment early.
  • Ignoring personal drives. Files there are invisible to everyone else and often hold personal data. Ask, move or dispose of them with whoever owns data protection.
  • A handover document with no owners. Every item needs one new owner, or it belongs to nobody.
  • No shadowing. A procedure written in the last weeks always has gaps. Have the new owner run the task while the leaver can still correct it.
  • Closing the handover on the leaving date. The real test is the first run of each task afterwards. Keep the record open until each has run, and use what it found to reduce key-person risk before the next departure.

Frequently asked questions

When should a marketing handover start?

As soon as the departure is known. The person leaving is the only source for much of what needs to be handed over, and their attention fades as the leaving date approaches. Starting early leaves time to shadow recurring tasks that run only weekly or monthly, and to find the accounts and files nobody else knew about. The HR and contractual side of a departure is separate and follows the organisation's own process.

Should a leaver's access be removed before the handover is finished?

The order matters. Hand over first and remove second: records, integrations and administrator rights are moved to their new owners while the person can still help, and sign-in is removed afterwards, on the timing the access review sets for leavers. Removing access first can strand records, break integrations that run under the person's account or lock an account that only they administered.

What should happen to files a leaver kept on a personal drive?

Find them before the person goes, then move them into the business's shared systems or delete them, deciding which with whoever owns data protection where the files contain personal data. The GDPR principles include keeping personal data secure and no longer than necessary, as the site's GDPR entry summarises, and a contact list on a personal drive meets neither. The person leaving can usually say what each file is and whether a copy exists elsewhere.

Terms used on this page

Frameworks

Where this page is used

Also related

Sources

  1. Regulation (EU) 2016/679 (GDPR) — EUR-Lex

Related