Same-Day and Immediate Exits: The No-Notice Runbook

Wednesday, 11:05, at Bellweather Logistics. Nadia runs a desk of four and her phone shows the HR manager's name, which is unusual, because Clare normally e-mails. "Can you come to the small meeting room? Bring nothing. Don't mention it to anyone." In the room are Clare and the operations director, and the news is short. A dispatcher called Kurt is being let go at two o'clock this afternoon. He must not have access to anything from the moment the meeting starts. He currently has a company laptop on his desk in the dispatch office, and a company phone in his pocket. He also has a login to the routing system that half the warehouse uses. It is now 11:09. Nadia has two hours and fifty-one minutes. The first thing she has to do is walk back past Kurt's desk looking exactly as she did on the way in.

An immediate exit is a departure with no notice period. In that case, a person's access has to end at the moment they are told, or before, rather than at the end of a planned last day. A same-day exit is the slightly gentler cousin where the person is told in the morning and leaves in the afternoon. For the desk the two are the same runbook run at different speeds. Both are the planned offboarding compressed into an hour, with the person still in the building and still holding the devices. There are emotions in the room that the planned exit does not have. This article is part of our Employee Offboarding series. The ordinary last-day order is in The Offboarding Checklist: Disable First, Delete Later. This article is about the day when there is no last day.

It covers what makes an immediate exit different, and who calls whom and who is allowed to know. Then come the hour of preparation that leaves no trace, and the minute-by-minute from an hour before to the next morning. Next come disabling during the meeting, the device still in the person's hands, and the discretion that protects everyone, including the leaver. It ends with the walk-out and the resignation with immediate effect, a short war story, and the immediate-exit runbook to copy, in that order.

What Makes an Immediate Exit Different

The planned exit has a window of days in which to prepare and a last day on which the person expects their access to end. The immediate exit has neither, and three things follow from that. The first is that the preparation has to happen while the person is still working, in the same building, often within sight of the desk. They must not notice that anything is being prepared. The second is that the moment access ends is not the end of a working day but the start of a conversation in a meeting room. The end of access has to be timed to that conversation to the minute. The third is that the devices are not on a return shelf but on the person's desk and in their pocket. Getting them back is part of the same hour.

There is a fourth difference that the runbook has to respect even though it is not technical. The person being told has not chosen this, may be shocked or angry, and will go on to have a life in which this afternoon is a bad memory. The colleagues around them will watch what happens and draw conclusions about how the organisation treats people. An immediate exit done well is quick, quiet, and leaves the leaver with as much dignity as the situation allows. An immediate exit done badly is a story told in the warehouse for years. The desk's part in the difference is larger than it looks. The desk is the function that has to move around the building during the hour. It is also the function whose chat messages and ticket titles the whole organisation can sometimes read.

The risk the runbook guards against is specific: the window between the person learning the news and their access ending. In a planned exit that window is zero, because the last day was agreed and the access ends when it ends. In an immediate exit, if the desk is told after the meeting rather than before, the window is however long it takes someone to walk to the desk. An upset person with a live account and a laptop can do a great deal in twenty minutes. Most do nothing of the kind. The runbook exists for the ones who do, and it costs the others nothing.

Who Calls Whom, and Who Is Allowed to Know

The immediate exit starts with a phone call from HR to one named person on the desk. The first thing to agree with HR, long before the first one happens, is who that person is and who stands in when they are away. It is a phone call or a conversation, never an e-mail to the queue and never a ticket submitted through the form. The queue is visible to the whole desk and sometimes to more than the desk. The named person is usually the desk lead. The stand-in is the next most senior technician. HR has both numbers written down somewhere that is not the help desk.

The circle of people who know before the meeting is as small as the work allows, and the desk's rule is three. It is the named person on the desk, the person who will do the technical steps if that is somebody different, and nobody else. The leaver's manager is told by HR, not by the desk, and the desk does not confirm or deny anything to anyone. The colleague who sits next to the leaver and asks "is something going on with Kurt?" is told "not that I know of". That is the one evasion the runbook permits and which protects the colleague as much as anyone. If the desk is a desk of one, the circle is one. In that case, the stand-in is a named person outside the desk who can at least disable an account, agreed in advance with HR.

The call from HR gives the desk the same facts the planned trigger would, with a time attached to the minute. It gives the person's name as it appears in the directory, the time the meeting starts, the room, and what the person holds. It also gives whether the person is in the office or remote, and a way to signal "now" during the meeting. Write them down on paper, not in a ticket yet, not in a chat message, and not in a document anyone else can open. Nadia's notes for Kurt were on the back of an envelope, which is not a document management strategy. It was the right place for them for the next three hours.

The Hour of Preparation That Leaves No Trace

The preparation for an immediate exit is the planned exit's "before the last day" block done in an hour. The discipline is that nothing in it is visible to the leaver or to anyone else. List every account and service the person holds. Include the directory account, the mail service, the file service, the VPN, and the second factor. Include the routing system or whatever line-of-business system the role uses, and the shared accounts and shared passwords the team uses that the person knows. List the devices, from what the desk's records say, and confirm by looking from a distance rather than asking. Open the administrative screens for each service in advance, find the person's account in each, and stop there. The screens are ready. Nothing has been clicked.

Three temptations arise in the hour and all three are refused. The first is to disable early, "just in case". That tells the person something is wrong when their mail stops at half past one and turns a controlled meeting into a corridor confrontation. The second is to look at the person's files or mail "to see if there is anything". That is both an invasion of privacy with legal weight and an act the desk has no authority for. If there is a concern about what the person has done, HR and the security function decide what is examined, after the account is disabled and the data is preserved. The third is to tell a colleague, because the hour is stressful and the desk is a team. It is refused because every person who knows is a person who might be asked. The leaver also deserves to hear it from HR in a room rather than guess it from the way the desk is behaving.

Prepare the device collection as well. Decide who collects the laptop from the person's desk and when. That is usually the manager or HR during or immediately after the meeting, never the desk walking into the dispatch office in front of the team. Decide where the devices go, which is the quarantine shelf with a label. For a remote person, prepare the courier kit address and the message that will accompany it, using the shipping routine in Remote Onboarding and Offboarding. That way, it goes out the same day. The hour is for staging, and a well-staged exit takes five minutes to execute.

The Minute-by-Minute

The table below is the runbook's timeline, from an hour before the meeting to the next morning, written for an exit at two o'clock. Every desk adjusts it; the shape is what matters. The "T" is the minute the meeting starts, which is the minute HR said. It is confirmed by a signal from the room rather than by the clock, because meetings start late. An account disabled at the scheduled time while the person is still walking to the room is disabled early.

The timeline looks like a lot and executes in about ten minutes of actual work, spread over three hours of waiting. The waiting is the hard part. The desk lead who has staged everything and now has to sit in plain view doing something ordinary for an hour has my sympathy. They should bring a ticket that genuinely needs doing.

Disabling During the Meeting

At the signal, the technician disables the account and revokes the sessions in the order the checklist already gives. The only thing that changes in an immediate exit is the speed and the fact that the person is, at that moment, sitting in a room with their phone. In plain words: the directory sign-in is disabled first, because it is the switch that stops new sign-ins everywhere. The sessions are revoked in each service next, because they are what the phone in the person's pocket is using. The VPN profile and the second factor are removed, because they are the routes that do not go through the directory. The line-of-business systems that keep their own accounts, such as Kurt's routing system, are disabled last, because they are usually reachable only from inside. Each step takes seconds. Say the time out loud to yourself and write it on the paper.

Two things happen on the person's devices during the meeting, and HR should know to expect both. The phone's mail app stops receiving new messages and may show a sign-in prompt. The laptop on the person's desk keeps working with whatever it already has open until it next checks in, which can be minutes or hours. It then starts asking for a password it will no longer accept. Neither is a problem. The person is in a meeting room with HR and will not be at the laptop again. If the person glances at their phone during the meeting and sees the prompt, they now know the conversation is real. HR would rather that happen in the room than at the desk afterwards.

Resist the urge to do more than the runbook says while the meeting is on. Do not start reading the mailbox, do not begin the hold-period tidying, do not change the person's job title in the directory, and do not post anything anywhere. The meeting may yet go differently from the plan. People are occasionally offered a different role, or placed on leave rather than dismissed. Or the meeting is postponed because the person is unwell. A disabled account can be enabled in seconds. A mailbox that has been read cannot be unread, and an announcement cannot be unsent. The runbook does the reversible things and waits.

The Device Still in the Person's Hands

The device problem in an immediate exit is that the laptop is on the person's desk and the phone is in their pocket. The solution is that the desk does not collect either one from the person directly. The laptop is collected from the empty desk by the manager or HR while the person is in the room, and brought to the desk. The company phone is asked for in the room by HR as part of the conversation, along with the badge and keys, and handed to the desk afterwards. The desk is not security staff and does not confront anybody, ask anybody to turn out their bag, or stand in a doorway. If a device is not handed over in the room, the desk's job is the same as for any device that has not come back. It is in Getting the Equipment Back: a receipt for what was returned, a dated request for what was not, and a note.

The phone needs one more step. A company phone handed over in the room goes on the quarantine shelf with the laptop. A personal phone with company mail on it stays with the person, as it should. The desk removes the work data from it remotely through the management profile, if the organisation enrols personal phones in one. Many do and many do not. In plain words, the management profile is the arrangement that lets the organisation remove its own mail, files and applications from a phone without touching the person's photographs or messages. The practice around it, and what to do when there is no profile, is in Lost and Stolen Devices, which handles the same removal for a different reason. Where there is no profile, the sessions revoked at the signal are the protection. In that case, the next morning's check confirms the phone is no longer reading mail.

Personal items on a company laptop are handled by HR's policy and not by the desk's judgement. If the policy allows the person to retrieve personal files, that happens later, supervised, with a copy made by the desk onto a medium HR provides. It never happens by handing the laptop back. If the policy does not allow it, the desk says so politely and refers the person to HR. The desk never deletes personal files to be tidy, and never reads them to be helpful.

The Discretion That Protects Everyone

Discretion in an immediate exit is not politeness. It is what keeps the organisation, the technician and the leaver out of trouble, and it is practised in four specific places. The first is chat. Send no message, in any channel, about the exit, before or after, including "can someone cover dispatch?" and "which laptop is Kurt's?". The organisation's chat is read by more people than anyone intends. A message sent at 13:50 is a message that told the warehouse before HR did. The desk's coordination for the hour is by phone and in person.

The second is the ticket. The exit gets a ticket, because every exit gets a ticket, but it gets one after the signal rather than before. Its title says "leaver" and a name and nothing about the reason. It is in a queue that only the people who need to see it can see. If you run QuerySolv, a separate department with its own permissions, visible to the desk lead and HR, is a natural home for exits of this kind. That way, the record exists and the wider queue never reads it. In any tool, the principle is that the ticket is complete and the audience is small. Everything that goes in the ticket follows the rule in What Not to Write in a Ticket: facts, times and actions. The ticket never includes the reason for the exit, a characterisation of the person, or a guess at what they might have done.

The third is the auto-reply and the directory. The auto-reply says that the person is no longer with the organisation and names the new contact, in exactly the words HR approves. The same words are used for every immediate exit and every planned one, so that the wording itself tells nobody anything. The directory entry is disabled, not renamed to anything descriptive, and not hidden in a way that a colleague would notice before HR's announcement. The fourth is the technician's own mouth. When asked, at the coffee machine, by someone who has noticed Kurt's empty desk, the answer is "you would need to ask HR". That is the answer every time, including to people the technician likes. The leaver is entitled to have their story told by nobody but themselves. The technician is entitled not to be the person who told it.

Discretion also protects the organisation legally, which is a reason HR will give and the desk should take seriously. A chat message calling the leaver a thief, or a ticket note speculating about what they copied, can each become evidence in a dispute. So can a technician telling the warehouse that "he was marched out". It is a dispute the organisation would rather not have. The runbook's answer is simple. The desk records what it did and when. It records nothing about why.

The Walk-Out and the Resignation With Immediate Effect

The runbook also covers the exit the organisation did not plan. That could be the person who resigns on the spot and leaves, or who walks out after an argument, or who is found to have already left. Here the trigger comes from the manager rather than HR, usually by phone and usually flustered. The desk's first act is the same signal step, done the moment the call ends. The person is now outside the building with the laptop and a live account. Disable, revoke, VPN, second factor, shared passwords, in that order, and then phone HR, who may not yet know.

The device is now outside and the person is not coming back to the room, so the device steps go straight to the remote version. That means a polite written request for the return, a courier kit sent the same day, and the chasing sequence from the equipment article. The data on the device is protected by the revoked sessions and, where there is one, the management profile. What is on the laptop's own disk is the reason the organisation encrypts laptop disks. A desk that does not yet do so should take this scenario as the argument. The manager who phones in a panic should be met with calm, because the runbook has already decided everything. The only question is whether the signal has been given yet.

A Short War Story: The Drawings at Redbrook Engineering

Redbrook Engineering dismissed a design engineer called Hugo for reasons that never reached the desk. The desk learned of it when the engineering manager walked over after the meeting and said, "Hugo's gone, can you sort his account out?" The meeting had started at ten and finished at half past. Hugo had returned to his desk to collect his coat, sat down for what colleagues later described as "a few minutes", and left at a quarter to eleven. The desk disabled the account at 11:20, when the manager arrived. In the fifty minutes between the meeting starting and the account being disabled, sixty-one drawing files for a client's project had been sent from Hugo's mailbox to a personal address. They were in four messages, the last of them at 10:41. The firm's lawyers wrote letters. The client had to be told under the terms of the contract. The drawings were in any case Hugo's own work and he may simply have wanted a portfolio. None of that made the client meeting any easier. The cost that the firm could count was about forty hours of management and legal time and a contract renewal that became a negotiation. The cost it could not count was the client's view of its security. The lesson, written into Redbrook's process by HR and the desk together, was a single sentence: the desk is told before the meeting, by phone, and disables at the signal, and no manager ever again says "can you sort his account out" after the fact.

The Immediate-Exit Runbook

The runbook below is kept on paper, in the desk lead's drawer and in HR's. It is the document the named person opens the moment the phone call ends. The first block is the call itself, so that the facts are taken down in the same order every time. The second is the hour of silent preparation. The third is the signal and the ten minutes after it. The fourth is the same day and the next morning. It deliberately contains nothing about the reason for the exit and nothing that would help anyone defeat it. It is a list of switches and the order to throw them in.

IMMEDIATE-EXIT RUNBOOK — ONE PAGE, PAPER
Named desk person: ______________   Stand-in: ______________   HR contact: ______________

1. THE CALL (by phone, from HR; written on paper, not in a ticket)
   Name as in the directory: ______________________   Role: ______________
   Meeting time: ________   Room: ________   Office / Remote
   Devices held: laptop ____  phone ____  other ____________
   Signal for "now": ______________________   Who collects the laptop: ______________
   Who else knows (max three): ______________________

2. THE HOUR BEFORE (silent; nothing changed; nothing read; nothing posted)
   [ ] Accounts listed: directory, mail, files, VPN, second factor, identity system
   [ ] Line-of-business systems with their own sign-in listed: ______________________
   [ ] Shared accounts and shared secrets the person knows listed (from the team list)
   [ ] Administrative screen open for each service; person's account found in each
   [ ] Quarantine shelf label written; courier kit staged if remote
   [ ] Signal confirmed with HR; laptop collection agreed

3. THE SIGNAL (in this order; note the time of each on paper)
   [ ] Directory account disabled                         ________
   [ ] Sessions revoked: mail ____  files ____  identity ____
   [ ] VPN certificate or profile revoked                 ________
   [ ] Second-factor registration removed                 ________
   [ ] Line-of-business sign-ins disabled                 ________
   [ ] Shared secrets changed, from the list              ________
   [ ] Mailbox rules checked; outside forwards removed    ________
   [ ] Auto-reply set, HR-approved neutral wording        ________

4. THE SAME DAY
   [ ] Laptop received from HR or the manager; receipted; labelled; on the shelf
   [ ] Company phone received; receipted; on the shelf
   [ ] Personal phone: work data removed through the management profile, if enrolled
   [ ] Remote: return request sent; courier kit dispatched; date noted
   [ ] Ticket opened in the restricted queue; neutral title; paper notes copied in with times
   [ ] Manager's mailbox access: only on HR's written instruction, with an end date
   [ ] Nothing read, nothing investigated; concerns passed to HR and the security function

5. THE NEXT MORNING
   [ ] Each service checked for an active session or a sign-in attempt; noted
   [ ] Ordinary checklist resumed from the hold band; hold end date set
   [ ] Paper notes shredded once the ticket holds them

Nadia's afternoon went to the runbook. Clare's message said "now" at 14:03. The account was disabled at 14:03 and the sessions, VPN and routing system were done by 14:06. The operations director brought the laptop at 14:20 and the phone at 14:35. The ticket was opened at 14:50 under a title that said "leaver" and a name. Kurt, as it turned out, had done nothing at all, before or during, and left without fuss. Nobody in the warehouse knew until HR told them, which is the whole point, and which took Nadia three hours of looking ordinary.

Frequently Asked Questions