Remote Onboarding and Offboarding Without a Visit
Friday, 16:05, at Harbourview Clinic. The onboarding request for Lucia, a medical coder starting on Monday, arrived from HR on Thursday afternoon. The desk has learned to call that "on time" because it is better than Monday morning. Lucia lives in another city and will never come to the clinic. Jonah on the desk has her account ready and her mailbox created. He does not have a laptop in her hands. The one ordered for her is due next week, and the only spare is in a box on its way back from the last swap. HR has just asked, helpfully, whether Lucia could use her own laptop for the first week. Ines, the desk lead, has the lead-time agreement open on her screen and is deciding which part of Monday to save.
The checklist for a new starter does not change because the starter is at home, and neither does the checklist for a leaver. What changes is that every step involving a physical thing now involves a courier. Every step involving a face now involves a call. The whole sequence has to start earlier and end later than it did when the person could walk to the desk. Remote onboarding and offboarding is the starter and leaver routine for a person who never comes to the building. It means the kit shipped before day one and the first-day call that replaces the walk to the desk. On the way out, it means the account disabled on time while the device is still in the person's kitchen and has to come back by post. This article is part of our Supporting Remote Workers series. The checklists themselves live in the onboarding and offboarding series; this article owns the remote differences and the plan that carries them.
It covers what remote changes and what it does not, followed by lead time and the ship date that comes before everything. Next come the box for a starter, the first-day call, and the first week at a distance. Then come the remote leaver and disable-first, the last-day call, and the immediate exit at a distance. A short war story and the remote starter plan to copy come last, in that order.
What Remote Changes, and What It Does Not
The day-one checklist for a remote starter is the same list in the same order. And it is worth saying so before describing the differences. Desks sometimes rebuild the whole routine for remote people and end up with two routines that drift apart. The account comes before the mailbox, the role comes before the access, "ready" means the same thing, and the same person signs it off. All of that is in The Day-One Checklist and does not need a remote version. What the remote starter adds is three things. There is a ship date that sits before the start date, and a first sign-in that happens on a call rather than at a desk. There is also a device whose journey has to be tracked both ways over the whole of the person's employment.
The leaver's list is likewise unchanged in its order. Disable sign-in first, revoke sessions, handle the mailbox, recover the device, reclaim licences, and delete nothing until the hold period ends. The order, and why it is that order, are in The Offboarding Checklist: Disable First, Delete Later. The remote leaver adds a timing problem the office leaver never had: the account is disabled on the last day, correctly. And the laptop is still in the person's house, with whatever is on it, and will be for days. Everything remote-specific about offboarding is about that gap.
Lead Time: The Ship Date Comes Before Everything
For an office starter, the desk's lead time is the time it takes to build a laptop and create the accounts. For a remote starter, it is that plus the courier, plus a buffer for the courier being a courier. The whole sequence has to be counted backwards from the start date. The ship date is the day the kit must leave the desk to reach the person's hands two working days before they start. It is the first date the desk writes on the ticket, before the account is created. It is the one that cannot be recovered if missed. An account can be created in an hour on Monday morning. A laptop cannot be driven three hundred miles in one.
The lead-time ask to HR, the ten working days that let the desk do onboarding as a routine rather than a rescue, is the subject of Lead Time: Getting the Request Before the Start Date. The remote starter is the strongest argument for it the desk will ever have. Two working days of notice means a spare laptop, if there is one, shipped in a hurry to an address nobody has confirmed. Ten means a laptop ordered, built, tested, boxed and delivered with a day to spare, to an address the starter confirmed themselves. Say that plainly to HR, with the courier's timetable in the sentence. Then the remote starter stops being the reason the agreement is broken and becomes the reason it is kept.
The address and the delivery day come from the starter, not from HR's record. And the starter is not yet an employee, which makes this the one conversation in the routine that happens through HR. The desk asks HR to ask the starter. Or HR passes on a personal e-mail address and the desk sends one message with three questions. These ask for the address for the kit, a day they will be in to sign for it, and a phone number for the first-day call. Nothing else goes to the personal address, ever, and in particular no credentials. If you run QuerySolv, the onboarding form the HR department raises tickets on can carry the delivery address and delivery day as fields of its own. The shipping task and the first-day call can also be linked tickets under the starter's parent ticket. That makes the ship date visible as a task with an owner rather than a line in a note. In any tool, the test is whether someone can see on Thursday that the box has not shipped.
The Box for a Starter
The starter's box is the ready box from Shipping and Swapping Hardware with two differences. The card is written for someone who has never seen the organisation, and nothing in the box lets anyone sign in. The card says welcome, says what is in the box, and says how to switch the laptop on and get it to the sign-in screen. It says when the first-day call is and which number the desk will ring. It gives the desk's phone number and portal link for the case where the courier has crushed something. It does not contain a password, a username or a second-factor code. The person who intercepts the box gets a laptop that is useless without a call to a technician who will check who they are.
The kit itself is whatever the role profile says a remote worker gets. That is usually the laptop, a headset, a cable, and the dock and monitor if the role has them. The dock and monitor are shipped as a second parcel when they will not fit the first. Where the ordered laptop will not arrive in time, the spare ships, and a note on the ticket says so and books the swap for later. The spare is what spares are for, and a starter on a spare for a fortnight is a starter who is working. Where there is no spare and no laptop, the honest conversation with HR about a partial day one happens on the day the ship date is missed. It does not wait until the Monday. The lead-time article covers that conversation. (HR's suggestion of the personal laptop is kind and is a security decision. The answer is in the personal-device policy, which the desk points to rather than argues with at five past four on a Friday.)
The First-Day Call
The first-day call is a booked call, at a fixed time on the first morning. The technician walks the starter from a laptop at its sign-in screen to a person who can read their mail and join a meeting. The starter can also reach the files they need and raise a ticket. The call replaces the walk to the desk that an office starter would have made at half past nine. Book it when the kit is dispatched, for a time when the technician is genuinely free. Send the time on the card and in the welcome message. Thirty to forty-five minutes is usual. Phone first, not a video call, because the laptop is the thing being set up and may not be able to join anything yet. Move to video once it can, so the starter sees a face.
The call is also the moment the desk verifies who it is talking to. And the first-sign-in credentials are given on it and nowhere else. The desk rings the number HR provided, rather than accepting a call from a number it cannot check. The manager has confirmed the start, and HR has confirmed the person. The technician confirms the two details that HR gave the desk and the box did not contain. Then come the first password, which the starter changes before the call ends, and the second-factor enrolment on the starter's phone. The enrolment is done on the call so the first "I cannot sign in" ticket never happens. The credentials never go in the ticket. An internal note records that they were given on the call, to whom, and that they were changed. And that is all it records. The ticket is a record of the fact and not of the secret. The verification standard for the desk's harder cases, such as a reset for someone it cannot see, is in the password series and is not repeated here. The first-day call is the easy case, because three people have already vouched for the person before the phone rings.
Finish the call with the starter raising a ticket. It is not a real problem. It is a practice ticket, "first-day call done, all working", raised through the form. That way, the starter has found the portal, used it once and seen the acknowledgment arrive. The technician closes it with a note that says the starter is set up, and the ticket becomes the record that the first day worked. Starters who have raised one ticket on day one raise their second without being told how. Starters who have not, message the technician they spoke to, for months.
Remember: the box never contains a way to sign in, and the ticket never contains the credentials. The first sign-in happens on a call the desk makes to a number HR provided. The password is changed on that call. The note on the ticket records that it happened, not what was said.
The First Week at a Distance
The first week's support for a remote starter is the office version with the face on a screen. The office version is in the onboarding series, with the welcome note, the five-minute briefing on how to ask for help and the check-in on day three. The remote additions are small and worth listing. The welcome note links the home support scope. That way, the starter knows on day one that the desk will check its side of the home connection and will not support the household printer. The day-three check-in is a call, booked on the first-day call, not an e-mail. The question "is everything working" gets an honest answer by voice and a polite one in writing. And the common first-week tickets for a remote starter are predictable enough to head off. They include the VPN that will not connect from a hotel and the second factor on a phone that is not the one enrolled. They include the meeting audio through the wrong device, and the shared folder that was in the access bundle but not in the starter's head.
Watch the starter's tickets for the first month as a set. A remote starter who has raised nothing by day ten has either found the portal unnecessary or has not found it at all. And the day-three call usually tells the desk which. A remote starter who has raised six tickets has a kit problem or an access-bundle problem that the role profile should fix for the next person. Either way, the tickets are the only view of the starter's week the desk has, since nobody will see them in the corridor looking lost.
The Remote Leaver: Disable First, Still
The order for a leaver does not change because the laptop is at home. Sign-in is disabled at the agreed moment on the last day. Sessions and tokens are revoked so that the device's cached sign-in stops working too. Mail is delegated, licences are reclaimed, and nothing is deleted until the hold period runs out. The reason the order does not change is the reason the offboarding series gives. A live account after the last day is the single most dangerous thing a sloppy exit leaves behind. Distance makes that worse rather than better. The office leaver hands over a laptop and a badge and walks out past reception. The remote leaver keeps the laptop, the home network, and a cached session for as long as the desk lets them.
What distance adds is the kitchen-laptop gap: the days between the account being disabled and the device being back at the desk. During that gap, the organisation's laptop sits in a private house holding whatever was on its drive. Three things close the gap, and all three happen before the disable, not after. The return kit, with the box, the label and the ask, is sent so that it arrives before the last day. And the mechanics of that kit are in Getting the Equipment Back. The last-day call, below, makes sure the work on the laptop has reached the organisation's systems before the account that could sync it is switched off. And the device's own protection is confirmed to be in place on that laptop, on the ticket. That protection is the disk encryption and the screen lock that the standard build applies. That way, a box in a hall for a fortnight is a box of ciphertext. The organisation's management profile may allow a device to be locked remotely. If so, whether to use it is the security function's decision for a leaver who does not cooperate, not a step the desk improvises.
The personal phone is the other device in the house, and it is easy to forget because the desk never shipped it. If the leaver's own phone carried a work profile, the second-factor app, or mail, the work parts are removed on the last day as part of revoking access. In that case, the leaver is told in advance what will disappear from their phone and when. That way, the second-factor app vanishing is expected rather than alarming. The desk removes the organisation's data. It does not touch anything else on a device it does not own, and the leaver is told that too.
The Last-Day Call
The last-day call is the mirror of the first-day call: a booked call on the final working day, usually in the afternoon. The technician and the leaver together confirm that work files have reached the organisation's storage and that anything personal has been copied off the laptop. They confirm that the laptop is shut down and packed in the return kit. They also confirm that the leaver knows where and when to hand the box to the courier. The account is disabled at the end of the call or at the time the manager and HR agreed. And the leaver is told that it will be, so that nothing about the exit is a surprise. Twenty minutes, by voice, with the technician's name on the ticket.
The call is practical, and it is also the dignity of the thing. A remote leaver might be simply cut off at five o'clock, with a courier box arriving a week later addressed to "the occupier". That leaver has been treated as a risk and not as a person who worked there, and will treat the return with the same care. A remote leaver might have had a call and packed the box with the technician on the line. They might have heard "thanks, that's everything, the account closes at five as agreed". That is a leaver whose box is at the courier the next morning. The desk cannot make an exit pleasant. It can make it tidy, and a tidy exit is the one where the device comes back.
The Immediate Exit at a Distance
The exit with no notice has its own minute-by-minute in the offboarding series. That is the exit where the desk learns of the termination during or just before the meeting in which it happens. The remote version follows it exactly for the account. Disable during the meeting, revoke sessions and tokens at once, delegate the mailbox, and record every step with its time. What the remote version cannot do is take the laptop at the door. The device stays in the person's house, possibly for some time. And the desk's three moves are the same as for a planned exit, done in a hurry. Confirm on the ticket that the device's encryption and lock are in place. Send the return kit the same day with a message that is short, courteous and addressed to the person by name. Hand the question of what more to do about the device to the security function and HR, who own it.
Discretion matters more at a distance, not less, because the desk is now the organisation's only physical contact with the person, through a box. The message in the kit says what to return and by when and gives one contact at the desk; it does not explain, apologise, or mention why. The technician who prepared the kit records that it was sent and does not discuss the exit with anyone the ticket does not name. The immediate exit is a security ticket with a person in it, and the person is still a person when the account is already disabled.
| The office step | What it becomes for a remote person | When it happens |
|---|---|---|
| Laptop built and left on the new desk | Laptop built, signed in once, shipped in a ready box with a starter card and no credentials | Ship date: start date minus courier time minus a buffer |
| Starter walks to the desk at half past nine | The first-day call, booked at dispatch, phone first then video | First morning, fixed time |
| First password handed over at the desk | Given on the call the desk makes to the HR-provided number; changed before the call ends | During the first-day call |
| Second factor set up at the desk | Enrolled on the starter's phone during the call | During the first-day call |
| "Pop over if anything is wrong" | A practice ticket raised on the call; a day-three call booked | Day one and day three |
| Leaver hands the laptop to the desk on the last afternoon | Return kit arrives before the last day; packed on the last-day call; handed to the courier next morning | Kit sent at least a week before; call on the last day |
| Account disabled as the leaver walks out | Account disabled at the agreed time at the end of the last-day call, with the leaver told | Last day, agreed time |
| Badge and keys collected at reception | Work profile and second-factor app removed from the personal phone; the leaver told what will disappear | Last day, with the disable |
A Short War Story: The Kitchen Laptop at Northgate Retail
At Northgate Retail, a remote merchandiser called Ewan gave a month's notice. The desk did the leaver's list correctly on his last Friday. His account was disabled at five, his sessions revoked, his mailbox handed to his manager. Nobody had sent a return kit, because the technician who usually did it assumed HR had, and HR assumed the desk had. So Ewan's laptop sat in his kitchen for nine weeks until a chaser from finance about a licence prompted someone to ask where it was. When it came back, the desk found that Ewan had kept the following season's range plans in a folder on the laptop. That folder synced to the organisation's storage only when he was signed in. The disable on Friday at five had stopped the last sync on Friday at four, with the final week's work still local. The folder was recovered from the drive, which was encrypted and intact. But the merchandising team had already spent most of a week rebuilding the plans from e-mails. The desk spent a day on recovery that a twenty-minute last-day call would have made unnecessary. The leaver's list had been followed to the letter, and the letter had not mentioned the kitchen. Disable-first is right; the device plan has to run before it, and the sync check is part of the call.
The Remote Starter Plan
The template below is the plan for one remote starter, counted backwards from the start date and forwards from it. The leaver's mirror is in the last section so that the same page serves the exit. The plan is filled in when the onboarding request arrives, the dates are written on the ticket, and each line is ticked by the person who did it. Section A is the dates, B the box, C the first-day call, D the first week, and E the remote leaver's timeline, which uses the same shape in reverse. The one line that must never be skipped is the ship date. And the one line that must never be filled in is the password.
REMOTE STARTER PLAN — ONE PAGE Starter: ______________ Role profile: ______________ Start date: ________ Manager: ______________ A. THE DATES (count backwards from the start date; write them on the ticket on day one of the request) Request received ......... ________ (lead-time agreement: ___ working days) Laptop ordered / spare reserved ... ________ Address, delivery day and phone number confirmed via HR ... ________ SHIP DATE ................ ________ (= start date, minus courier days ___, minus buffer ___) Kit delivered ............ ________ (two working days before the start) First-day call booked .... ________ at ______ Day-three call ... ________ at ______ B. THE BOX [ ] Laptop on the standard build; signed in once at the desk; signed out; charged [ ] Headset, cable, charger; dock and monitor as the role profile says (second parcel if needed) [ ] Starter card: welcome, what is in the box, how to reach the sign-in screen, the call time, the desk's number [ ] NO credentials, usernames or codes anywhere in the box [ ] Shipped tracked and signed-for; tracking number on the ticket; delivery confirmed on arrival C. THE FIRST-DAY CALL (the desk rings the HR-provided number) [ ] Identity confirmed: the two details HR gave the desk and the box did not contain [ ] First sign-in; password changed on the call [ ] Second factor enrolled on the starter's phone [ ] VPN, mail, calendar, meeting audio, the role's shared folders: each opened once [ ] Practice ticket raised by the starter through the form; closed with a note [ ] Internal note: call done, by whom, credentials given and changed (never the credentials themselves) D. THE FIRST WEEK [ ] Welcome message sent with the portal link, the desk's hours and the home support scope [ ] Day-three call made; tickets so far reviewed [ ] Day-ten look: no tickets or many tickets, and what the role profile should learn E. THE REMOTE LEAVER (the mirror) Notice received ..... ________ Return kit sent ..... ________ (to arrive before the last day) Last-day call ....... ________ at ______ Account disabled ... ________ at ______ (agreed with HR and the manager) [ ] Encryption and screen lock confirmed on the ticket before the last day [ ] On the call: work synced, personal files copied off, laptop shut down and packed [ ] Work profile and second-factor app removed from the personal phone; leaver told in advance [ ] Return tracking on the ticket; chase from the day after the drop-off date
Ines sent Lucia's kit on Friday afternoon in the end, using the spare that was due back on Monday. She did it by swapping its booking with the one on the shelf that was reserved for a swap that had not yet been decided. That is the kind of trade a spares sheet makes visible and a memory does not. The first-day call was at 09:30 on Monday, from Jonah, to the number HR had provided. Lucia changed her password at 09:41, enrolled her second factor at 09:50, and raised her practice ticket at 10:12. The ordered laptop arrived the following Thursday and went on the shelf as the next spare. Nobody used their own laptop.
Frequently Asked Questions
Can we send the starter their password by e-mail to their personal address so they can start before the call?
The starter's kit has not arrived and it is the first morning. What do we do?
Should the remote leaver's account be disabled before the laptop is back?
What if the remote leaver will not return the laptop?
Does a remote starter need a video call, or is a phone call enough?
How early should the return kit go to a remote leaver?
From the QuerySolv team: we build self-hosted help desk software for Windows. QuerySolv runs as one Windows service on your own network. It takes requests by web form, e-mail, live chat, social messages and REST API. It is licensed once per installation rather than per agent per month. The free trial runs the full product for 30 days.