At senior level the resignation letter is only half the document. What decides whether you leave with a reference and a relationship is the handover plan attached to it — and the person who writes their own handover plan controls how their departure is remembered. Three samples: a manager, a technical lead, and a department head.
A senior operations role with a long notice period. The letter is short; the value is in the plan it proposes.
I am writing to give formal notice of my resignation as Operations Manager. My contractual notice is two months, placing my final working day on Friday, 9 October 2026.
Five years here, and the last two running the three centres, have been the best stretch of my working life. I am leaving for a regional role with wider scope, not because anything here has gone wrong.
I would like to use the notice period properly rather than let it drift. My proposal, subject to whatever you prefer: weeks one to three, document every process I own and complete the quarter-end reporting. Weeks four to six, run the recruitment and shadowing for my successor if you appoint internally. Weeks seven and eight, step back into a support role so the new person is actually running it while I am still here to be asked.
I will have the full handover pack ready by the end of month one so you can see it early rather than at the end. Whatever you decide, I would rather leave this in good order than leave quietly.
The dangerous kind of departure — the person who knows how things work. The letter addresses the risk explicitly, which is what a technical manager most needs to hear.
This is my formal notice of resignation. My notice period is one month and my final working day will be Friday, 11 September 2026.
I know the payments integration and the API layer are largely in my head, and I would rather fix that before I go than leave you to discover it in October. I have started writing it down already.
By the end of week two I will have three documents ready: the payments integration runbook including the failure modes we hit last year, an architecture note on the API layer covering the read-replica work and why it is shaped the way it is, and the on-call playbook for the services I own. I will then walk two engineers through each one, so it is in two other heads and not just on paper.
I am happy to remain contactable for urgent questions for a month after I leave, and I mean that as a genuine offer rather than a formality. Four years here have been good ones.
Leaving a school mid-year is disruptive by nature, so the letter is built around protecting the students rather than the department.
I am writing to resign from my position as Head of Science, with three months notice as my contract requires. My final working day would fall on 12 November 2026.
I am conscious that this falls mid-term. If it is workable for the school, I would prefer to stay to the end of the winter term on 19 December, so that the O-Level sections are not handed over between mocks and the final examination. I have discussed this with my next employer and they have agreed to it if we need it.
Whatever we decide, I will leave the department in order: the schemes of work for all three subjects are current, the practical programme is documented with the technician schedule, and I will write handover notes on each of the nine teachers including where each is in their appraisal cycle.
Five years here have mattered a great deal to me, and the science department is in far better shape than I found it, which is largely down to the freedom you gave me to rebuild it.
Most people treat the notice period as a countdown. The organisation treats it as the last evidence of what kind of colleague you were, and that evidence is what a reference call three years later is actually based on.
There is a practical argument too. If you do not define the handover, someone else will define it for you — usually as an open-ended series of interruptions, meetings you did not schedule and questions after you have gone. A written plan converts that into a finite, controllable piece of work.
And it protects your reputation in the one place it is most fragile. Departments remember the people who left things broken far longer than they remember the people who did the job well.
Write it for someone competent who knows nothing about your job specifically. That is exactly who will be reading it.
A structured notice period has three phases, whatever its length.
Propose the phases in your letter, subject to your manager's preference. Even if they change it entirely, you have set the tone of the departure in the first paragraph they read.
All three samples are free to read and copy. Want them as editable Word files, or a resignation letter and handover plan built around your own notice period? Both take a minute.
Build mine with Hexa → Download all three · FreeThe people above are illustrative examples written for teaching purposes. Names, employers, registration numbers and figures are invented and should not be copied into a real application — use them as a shape to pour your own verified numbers into.