You are the only one who knows how the pricing model works. You are the only one who knows the API key rotation. You are the only one the biggest client will email at 9pm. And now you are leaving. Here is how to resign cleanly when you are the single point of failure, without sabotaging the exit or carrying guilt that was never yours to carry.
Your irreplaceability is not your problem to solve alone
Read this part twice. If you are the only person who can do your job, that is a staffing failure, not a personal obligation. Companies are responsible for not having single points of failure. You are responsible for giving reasonable notice and a competent handover. That is the deal.
The guilt you feel is real, but it is being weaponised by a situation the company allowed to develop. You do not owe an extra three months because no one was cross-trained. You do not owe weekends. You do not owe a promise to "be available" indefinitely after you leave. Decide that now, before the conversation starts, because once you are in the room the pressure to concede will be heavy.
Before you resign, do a quiet audit
Two weeks before you plan to hand in your notice, start a private document. Not for the company. For you. You need to know exactly what you are walking away from before you sit in the resignation conversation, because your manager is going to ask, and your answers will shape the next month.
List the things only you currently do or know:
- Live systems you maintain that have no documentation
- Recurring deliverables that depend on knowledge in your head
- Relationships where you are the named contact and no one else has met the person
- Credentials and access tied to your personal accounts or your name
- Workarounds for broken processes that no one has ever written down
- Decisions in flight that will need someone to own them next week
This list becomes the spine of your handover. It also tells you the truth about the scope of the problem, which you need to know honestly. If the list is genuinely long, your notice period probably needs to focus on documentation and cross-training, not on finishing your normal work.
The resignation conversation
Lead with the decision. Do not open with the problem. Your manager will jump to "but how will we cope" within thirty seconds, and if you let them frame the conversation around the company's gap, you will spend an hour negotiating your own concessions.
The order matters:
- State that you are resigning and give your last day based on contractual notice.
- Say you have thought about the handover and have a plan for it.
- Then, and only then, offer to walk through how you will use the notice period.
If you open with "I know this is going to be hard for the team," you have already given away your leverage. You are not a co-conspirator in solving the company's coverage gap. You are a professional giving fair notice. The framing in the resignation conversation script applies here too.
Handle the pressure to extend your notice
This is the trap. Your manager will say something like: "Look, we genuinely can't replace you in four weeks. Can you do three months? Two months? Even six extra weeks?" The request will sound reasonable. It will be wrapped in flattery. It will appeal to your loyalty to the team.
You can say yes. You can say no. Both are valid. But decide based on what is good for you, not what feels least uncomfortable in the moment. A few rules to hold onto:
| If you extend | Conditions to set |
|---|---|
| Extra weeks of notice | Confirmed in writing, with a hard end date you control |
| Post-departure consulting | Paid at a daily rate, capped hours, written contract |
| "Just being reachable" | Do not agree. It will become unpaid on-call support. |
| Training a new hire who hasn't been hired yet | Decline. Your notice period cannot be conditional on their recruitment. |
If you do agree to extend, get it in writing the same day, with the new end date stated explicitly. Verbal agreements drift. Email beats memory.
Design the handover for someone who does not exist yet
In most irreplaceable-person situations, there is no successor on day one of your notice. Possibly none on your last day either. This changes how you write the handover.
Do not write it for a colleague who already knows the context. Write it for a stranger reading it cold in three months' time, with no one to ask. That means:
- Explain why, not just what. Every workaround, every odd decision, every named contact gets a sentence on the reasoning.
- Link, do not summarise. Where the system has documentation, point at it. Where it does not, write the missing doc once, not in the handover and again somewhere else.
- Make it searchable. Headings, bold key terms, a clear contents page. The reader will arrive with one specific problem, not curiosity.
- Flag the time bombs. The contract that auto-renews in eight months. The certificate that expires in October. The annual report due in Q3. Anything time-sensitive deserves its own section.
If no successor has been named, the same approach in the no-replacement handover guide applies: write a two-layer document, with an interim plan for the next ninety days and a full reference document underneath.
Prioritise ruthlessly: you cannot transfer everything
If you have built up years of context, you cannot move all of it into another head in four weeks. Trying will exhaust you and produce a worse handover than focusing.
Sort your knowledge into three buckets:
The three buckets
- Critical and immediate. Things that will break in week one if they are not handled. Document these fully and walk someone through them live.
- Important but not urgent. Things that will matter in the first three months. Write these down clearly. Do not insist on a meeting to cover each one.
- Nice to know. History, context, your opinions. Capture in a "notes from the previous holder" section at the end of the document. Anyone curious will read it. No one will be blocked if they do not.
Most people in your position spend too long on bucket three because it is emotionally satisfying to explain everything you have learned. Spend the time on bucket one instead.
Cross-train at least one person, even imperfectly
Push your manager hard to nominate someone, anyone, who can shadow you for the notice period. Even a junior colleague who only absorbs 30% of your knowledge is better than no living memory of your role on the team.
Frame the request in your manager's interest: "If no one shadows me, every question for the next year comes back to you." That usually gets a name within a week. Once you have a person, structure the sessions around their need to act, not around your need to explain. Sit with them while they do the work. Resist the urge to take over when they fumble.
Protect yourself after you leave
The day after your last day, the questions will start. A Slack message. A LinkedIn DM. A frantic email from a former colleague who cannot find the file. How you handle the first one sets the pattern for all of them.
Decide your policy before you leave:
- A clean break. "I'm no longer at the company and can't help with operational questions. Everything I knew is in the handover document at [link]." Polite, short, repeated verbatim.
- A grace period. "Happy to answer questions for the first two weeks. After that, please refer to the handover document." Set the date. Hold the line.
- A paid arrangement. If they want ongoing access to you, it is a consulting engagement with a contract and a rate. Free advice on demand is not a category that exists.
Whichever you pick, do not feel guilty about it. The handover document is the artefact that proves you did your job. Anything they ask after that is the company's failure to read what you left them.
The handover document is the evidence
When you are irreplaceable, the handover document is not just a courtesy. It is the record of your professionalism. It is the thing your old manager will reference for years. It is what shapes the story other people tell about how you left.
Get it right and the narrative becomes: "She left a brilliant handover. Honestly, more than we deserved given how little we had documented." Get it wrong, or skip it, and the narrative becomes: "She walked out and left us in the lurch," whether that is fair or not.
If you work in Google Workspace, OneLast.Day reads your Gmail, Drive, and Calendar and drafts the handover from your actual work data, so the deep context buried in years of emails and meetings is captured without you having to remember it all by hand.
Leave a handover only you could write
OneLast.Day reads your Google Workspace and drafts the handover from your actual work data, so years of context land on the page.
Create my handover documentOne-time payment · $20 USD · No subscription