Leaving the Staff Room
A teacher resigning in July, followed to the last evening — the notice period and the file it is recorded on, the exit interview that is the only honest feedback a school ever gets, the reference and service letter they will need in September, and the difference between ending an account and deleting a person.
The account that still works six months later
Every school has one. An email address that still receives, a login that still opens the gradebook, belonging to somebody who left in July — because offboarding a member of staff is a checklist nobody owns, spread across a bursar, an IT contractor and whoever happens to remember. And the opposite failure is just as common: the record deleted along with the login, so when the reference request arrives in September there is nothing left to write it from. This walkthrough follows one resignation from the notice letter to the evening the account stops working: what HR records, what the leaver is asked, what they are owed, and exactly what survives them. Every screen is the real application.
On this page
Notice, and the file it lands on
A resignation is a date before it is anything else. Everything downstream — the cover arrangements, the exit interview, the last payroll run, the day the account closes — is counted backwards from one day, so that day belongs on the employment record rather than in an inbox.
People Operations
The workforce register, and the place the lifecycle actions live — activate, deactivate, initiate offboarding. It is deliberately not the same page as the staff directory: the directory maintains records, this composes a workforce, and the figures above each are different questions asked of the same people.
Their record, with an end date on it
Bisi Ogunlade’s file. Seven years, two classes, a supervisor and a mentor, qualifications with the certificates attached — and now an end date. Nothing is removed at this point and nothing needs to be: the record is what the reference will be written from, and the leaving is one more fact on it.
Ready to run your school on this?
Every screen in “Notice, and the file it lands on” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.
The two things a leaver owes, and is owed
Between the notice and the last day sit two registers pointing at each other. One is the school asking the leaver a question it will never get a more honest answer to. The other is the leaver asking the school for the paperwork that outlives the job.
The exit interview
Structured feedback from somebody with nothing left to lose: why they are leaving, what management was like, what the work was like, what development they did or did not get, and whether they would recommend the school. One interview is an anecdote. Four are the row of figures above the table — and two of these leavers would not recommend the school, both for reasons specific enough to act on.
And the paperwork they will need
The office’s queue of what staff have asked it for — a reference letter, a confirmation of service, a payslip history, a tax certificate. Two of the rows here belong to the leaver, and they are the two every leaver needs. Filing them as tracked requests rather than emails is what stops a reference request in September becoming an archaeology exercise.
See this on your own school’s data.
Every screen in “The two things a leaver owes, and is owed” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.
The same requests, from their side
The single most common complaint from somebody working out a notice period is not knowing whether anybody has picked anything up. There is one screen that answers that, and it belongs to them rather than to HR.
Asking for the letter, and watching it move
The employee’s own document screen: what they have asked for, what state each request is in, and what has been issued. The same records the HR queue was working two steps ago — one register, two views — so nobody has to ring the school to find out whether anything is happening.
Set this up for your team.
Every screen in “The same requests, from their side” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.
And then the access ends — not the record
The final act is one switch, and the whole design of this platform is arranged so that throwing it is safe. Portal access and employment record are separate things: ending the first is an evening’s work, and the second is what the school will still be answering questions from in five years.
The staff directory, and the access column
Every employee with one honest answer to the only question that matters at this point: can this person sign in? It is a computed column rather than a status field — a school with an account it never issued, an invitation nobody accepted and a deactivated login all read differently here, and “No portal access” counts all three.
Ready to run your school on this?
Every screen in “And then the access ends — not the record” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.
Run your whole school on one connected platform
Start with the base package, switch on the modules you need, and give every parent, student and staff member a single place to log in.