What changes for you when your manager changes
A manager can change in several ways. They resign and leave the organisation, move to another role inside it or are replaced while staying on in a different job; or the team is reorganised and you are moved to report to someone else. In each case this guide assumes your own role carries on. What is at risk is the record of the agreements that shape it. Some of it sits on paper: an objective sheet, a development plan, notes from one-to-ones. The rest exists only as conversation: the level of authority you were trusted with for a channel, the stretch responsibility you were told would come next, the gap your manager said stood between you and the next level. The written parts can survive the change, if they are kept where the next manager can find them. The spoken parts survive only if someone writes them down before the person who holds them leaves.
This guide is for a contributor at any level below head of function who stays while the manager changes. It sits beside several pages written from other chairs. The marketing management guide covers the incoming manager's side, which begins by listening to each member of the team before diagnosing anything or deciding what to change. The operations tutorial on a leaver's handover moves the leaver's own recurring work, open projects, accounts and relationships to new owners; it does not record the agreements a departing manager holds with each person who reports to them, and that gap is what this page covers. If you are the one joining a new team under a new manager, the tutorial for a marketer starting in a new role is the plan to follow instead.
Some questions raised by a change of manager are not yours, or this guide's, to settle. An assurance about promotion, grading or pay that the departing manager gave you, anything touching a performance process or a formal record, and any reorganisation that changes your job itself are matters the organisation's own policy and its people team settle. The rest of this guide leaves them there.
Before your manager leaves
Once you know your manager is going, the window for getting agreements written down is the time before their leaving date, while the person who made them can still confirm them. The handover tutorial notes that a leaver's attention fades as the date approaches, so ask early and make the request specific. A short note in their words, or in yours with their corrections, is enough. What it needs to cover:
| Agreement | Where it may sit now | What to ask the departing manager to confirm in writing |
|---|---|---|
| Objectives for the current period | The objective sheet, if the team keeps one | Each objective, its measure and starting reading, the latest reading and any change agreed but not yet recorded |
| Authority you hold | A delegation note, or nothing written | The level agreed for each area of your work, and any decision they asked to see before you act |
| Development plan | Notes from one-to-ones, or nothing written | The skills you are building, the stretch work agreed and how progress was to be judged |
| The progression conversation | One-to-one notes, or memory alone | What they said the next level requires, what they have seen you do towards it and the gap still to close |
| Feedback | One-to-one notes or your own log | The main points of recent feedback, especially on any work you did at the next level |
| Work awaiting their decision | Their inbox or the team's work system | Each item waiting for their approval, and who approves it once they have gone |
| Commitments not yet started | Conversation | Any stretch responsibility, training or change to your scope that was agreed but has not begun |
Writing these down is more than tidiness. The guide to hiring and developing marketers, which covers one-to-ones and development plans from the manager's chair, points to the emphasis the Chartered Institute of Marketing places on continuing professional development, where a person grows through practice that is deliberate and recorded rather than through the odd training day. A development record kept in that way does not depend on one manager remembering it, and that is exactly the property it needs when the manager changes.
If someone is coordinating the departing manager's handover, ask whether the items awaiting their decision can be listed in that record with a new approver for each. If the manager leaves without warning, write your own version from your notes and ask the person they reported to to confirm what they can. The manager's own side of the handover, from each report's agreements to the plan, the partner dates and the decisions that need a named holder, is set out in the tutorial on handing a marketing team to the next manager.
Who you answer to while the post is empty
If there will be a gap between one manager leaving and the next arriving, get a named answer, before your manager's last day, to each of these: who holds your one-to-ones, who approves the work your manager used to approve, and whom you go to when something urgent falls outside your authority. The person your manager reported to may take some or all of it, or a colleague may be asked to cover part of the role. Confirm the names rather than assuming them, and write the answers into the same note as your agreements. Where approvals are split between people, record which kinds of decision go to whom, so a question does not sit unanswered while two people each think it belongs to the other.
If you are the one asked to take on part of your manager's role while it stands empty, that is a different job with its own terms, and the tutorial for the person asked to hold an empty post sets them out from the side of the person covering. If a colleague covers instead, ask which of the items that affect you they hold and at what level of authority, so that you know which questions go to them and which go to the person above.
A brief of your role for the new manager
As noted above, the management guide has an incoming manager start by listening to the team. A short written brief of your role gives that listening something concrete to work from. Send it before your first proper conversation if you can.
Write the brief around outcomes rather than tasks. For each outcome you own, give the KPIA metric tied directly to an objective. that shows it, the definition and the report you read it from, and its BaselineAn estimate of what a metric would have done without a given change, campaign or promotion, against which the effect is measured., so the new manager can check any figure against its source rather than take it on trust. Keep it short enough to read before a meeting; detail can stay in the documents it points to.
| Section of the brief | What it holds |
|---|---|
| Purpose | Why the role exists and what changes for the business when it is done well |
| Outcomes and measures | Each outcome you own, with its measure, definition, source and starting reading |
| Ongoing work | The recurring tasks and channels you run, and where each procedure is written down |
| Authority | The level agreed for each area, as the departing manager confirmed it |
| Objectives | The current objective sheet, with the latest readings |
| Work in flight | Each open item, its next step, its deadline and who approves it |
| People you work with | The colleagues, agencies and suppliers the role depends on, and what passes between you |
| Development | Your development plan, its current goal and where the progression conversation had reached |
| Decisions you need | Anything waiting for a decision from the new manager, with your recommendation |
For the measures, the what, so what, now what framework offers a compact way to write each line: what the measure reads against its comparison, what that means for the outcome and how confident you are about what caused it, and what you plan next, or that you plan to leave it alone.
Use the first conversations with the new manager to walk through the brief and confirm what it lists, item by item. Is this outcome still yours? Does this level of authority stand? Is it measured this way? Are these the items in flight? Note each answer as confirmed, changed or held over for later, and send a short written summary afterwards so that you both work from the same version.
Authority, objectives and work in flight
The authority you held was granted by the departing manager, and it is the new manager's to confirm. The delegation guide describes a scale of levels, from deciding alone and reporting afterwards down to doing the preparation while the manager makes each call, and your brief should place each area of your work on it. Ask the new manager to confirm or change each level and write the answer down. A new manager may reasonably pause a level while they learn the work. If that happens, note the date, what you will now bring for decision instead and what they would want to see before restoring it. A 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. showing the decisions you made at the earlier level, with your reasons and what happened, is direct evidence you can offer. For spend, and for approvals involving brand, claims or legal risk, ask who now approves what your manager approved; those routes are set by the organisation and by finance, not agreed between you and any one manager.
Objectives come next. The management tutorial on individual objectives expects objectives to change during the period when the plan behind them changes, and asks for each change to be dated and explained on the sheet, with a new baseline recorded if the measure itself changes. A new manager may want to rewrite an objective once they have read the plan. Ask for the change to be made in that way rather than agreed in passing, so that the old objective, the reading it had reached and the reason it changed all stay visible. Keep your development goal on the sheet too, unless you and the new manager agree to change it.
Work in flight needs a named approver for every item. Anything that was waiting for the departing manager's sign-off should have been given a new approver before they left; check each one in the first conversation and chase any that were missed. Once the new manager has agreed who decides what, tell the agencies, suppliers and colleagues who used to go through your manager, so that nobody keeps sending requests to an empty inbox.
Restarting the progression conversation from the record
The conversation about your next level does not pass to the new manager by itself. Whatever the departing manager saw of your work, the new one has not yet seen, and encouragement that was spoken rather than written gives them nothing to weigh. Restart it from the record.
The guide to career ladders and levels advises keeping a running record of your work and who saw it, since memory fades before a review comes round. It draws on management writing in the Harvard Business Review, which describes a career as growth in what a person is responsible for and the judgement they exercise, not as a progression of job titles. It notes that promotion usually rewards next-level work already being done. Once recorded, that work can be shown to a manager who did not see it. Its section 'Preparing for the next level' recommends beginning with a conversation about what the next level requires, and 'Making the case for promotion' builds the case from evidence, from the level description and from the support of others. Use both with the new manager rather than rebuilding them from scratch.
Bring what you have:
- The departing manager's note of where the conversation had reached and the gap they named.
- Your work log and the feedback written beside it. The guide to a first job in digital marketing sets up both in 'Keeping a work log' and 'Asking for feedback'; the habit serves at any level, and after a change of manager it is what lets you point to specific decisions rather than general impressions.
- Your record of results, with your part stated as the guide to stating your part in a result honestly sets out: your work separated from the team's, and the result separated from what would have happened anyway.
- The objective sheet with its change log, so that work towards a rewritten objective is still on view.
Ask the new manager what they would need to see, and agree when to return to it once they have seen enough of your work to judge it. Treat the departing manager's earlier view as context; it is for the new manager to form their own view, and an assurance of the kind set aside at the start of this guide is not part of the case. If it becomes clear over time that the room you need is not there, the progression hub covers the choice between progressing where you are and moving on.
An email executive's manager leaves a locksmith and security firm (illustrative)
Brevskarn Locksmiths' email executive works through a change of manager
Brevskarn Locksmiths, an invented regional locksmith and security firm with 7 branches, has a marketing team of 3: a marketing manager, an email and CRM executive and a content executive. The email and CRM executive is part-way through a conversation about the next level when the marketing manager resigns, with 4 weeks to go before leaving. The operations director, to whom the manager reported, agrees to hold the team's one-to-ones and approvals until a replacement starts.
Before the leaving date, the executive drafts a note and asks the manager to correct it. It lists her objective for the quarter, service reminder bookings from email with a baseline of 160 a month, and her development goal of presenting the quarterly email results to the operations director. It lists her authority levels: "act and tell me afterwards" for routine sends to existing customers, "act, then tell me straight away" for win-back offers of up to 10% off a lock service, and "propose and wait for a decision" for any change to how the customer list is segmented. It records the gap the manager named for the next level: owning the email budget line and leading a review with the CRM supplier. The manager adds 1 item the executive had missed: the CRM contract renewal falls due in 3 months and needs a new approver, which the operations director takes on.
The new marketing manager starts 6 weeks after the old one leaves. In the first week the executive sends a brief on 1 page: the role's purpose, her 2 outcomes, reminder bookings and win-back orders, with their measures, sources and baselines, her 3 authority levels, 5 items in flight and the 2 decisions she needs. At their first meeting they walk through it item by item. The new manager confirms the routine-send and segmentation levels, pauses the win-back level and asks to see each offer before it goes. The executive shares her decision log, which holds 26 entries since January, including the 4 win-back offers she sent and what each produced. The new manager reads it and restores the level 3 weeks later.
The firm then adds commercial access control to its services, and the new manager rewrites the bookings objective as enquiries for commercial security surveys. The sheet records the date, the reason and a new baseline of 12 enquiries a month, with the old objective and its last reading, 171 bookings a month, kept beside it.
The departing manager had told her in passing that she "should be a manager by the spring". She does not raise it as a commitment and treats any promotion as a matter for the firm's own process. At a one-to-one 8 weeks after the new manager starts, she brings the departing manager's note of the gap, her work log with the feedback beside each entry, a record of her part in the reminder programme and the objective sheet with its change log. The new manager agrees to read the next level's description with her, adds leading the CRM supplier review to her development plan as a first stretch towards the gap the departing manager named, and sets a date to review it.
The figures are invented; the sequence is the point. The agreements are written down and corrected by the departing manager before the leaving date, one named person holds one-to-ones and approvals in the gap, the brief lets the new manager confirm the role item by item, a paused level of authority comes back on the evidence of a decision log, an objective changes on the sheet rather than in passing, and the progression conversation restarts from a record with the earlier encouragement left out of it.
Common mistakes
- Trusting memory with the agreements. What was agreed in conversation leaves with the person who agreed it. Get it written down and corrected before the leaving date.
- Waiting for the new manager to ask. A brief you send early puts your role in front of them in your own words, with its measures and sources attached.
- Asking the departing manager to commit their successor. They can describe what they saw and agreed; the next person's decisions are not theirs to promise. Ask for an account, not a promise.
- Treating spoken encouragement as a decision. Encouragement is not a commitment the new manager inherits. Leave it out of the case and bring evidence instead.
- Assuming your authority carries over unchanged. The levels were granted by the previous manager. Ask the new one to confirm each, and record any pause together with what would restore it.
- Letting objectives change in passing. A rewritten objective with no date, reason or new baseline hides the work done towards the old one. Ask for the change to be made on the sheet.
- Writing the brief as a task list. The brief is for outcomes, measures and the decisions waiting for the new manager, not a diary. Lead with what the role is for.
- Opening with the promotion case. A new manager cannot judge work they have not seen. Confirm the role first, then restart the progression conversation from the record.
- Letting the record lapse while the post is empty. Decisions taken during the gap are the ones the new manager will need explained. Keep the log going.
