Preboarding
Stage
The stretch between someone accepting a job and their first day, used to get equipment, accounts and a first-week schedule ready before they arrive.
Why it exists
A new hire's first day used to be mostly waiting. The laptop was still in transit, the account request had been filed but not granted, and the desk was a corner of another team's meeting room. At Pagedeck, everything Theo managed on his first morning was borrowing a neighbor's machine to read public documents. The laptop didn't arrive that afternoon either.
Preparation runs late for reasons that have little to do with effort and a lot to do with sequencing. Ordering hardware and provisioning accounts crosses several desks, and the person responsible typically started on the day they were told a start date existed. A task that takes two weeks was begun three days out. Nothing in the chain is hard; it just cannot be compressed once it has started late.
The bigger gap sits earlier. Three to six weeks usually pass between accepting an offer — the set of terms presented to someone you want to hire — and showing up, because notice periods and handovers at the previous job take that long. Fill those weeks with silence and the decision to join cools off. People do change their minds before the first day, and when they do, a hiring process that ran for months resets to zero.
Preboarding is the name given to that stretch so it stops being empty. The preparation that used to pile up on day one moves earlier, and contact continues in the meantime. Neither half is new work — it is the same work, scheduled where there is room for it.
What this stage looks like
The boundaries are exact: it opens the day the acceptance arrives and closes the evening before the first day. One condition shapes everything inside it. The person is not an employee yet. No employment relationship has started, so a company can prepare and inform but cannot assign work.
What the company does here splits four ways.
- Get equipment and accounts ready. Order the laptop, provision email and the collaboration tools, and for an engineer, repository access as well. Some hardware takes two weeks from order to delivery, which is why this starts the day the acceptance lands rather than the week of the start date.
- Exchange the paperwork. Signing the employment contract, submitting payroll and insurance details, and the confidentiality agreement all finish here. Spend the first morning filling in forms and you've spent it not meeting anyone.
- Build and send the first-week schedule. An hour-by-hour table of who they'll meet and what they'll read. With the first morning written down, nobody has to ask what time to arrive or which room to find, and the people on the schedule have already blocked the time.
- Stay in contact. Across four weeks between acceptance and arrival, reach out once or twice. A short note about what the team is working on, or dinner with the people they'll sit with, are the usual forms. The point is not the content of the message but the fact that the company is still visible.
The first three happen inside the company; only the fourth touches the person directly. And the fourth is the one that keeps the hire from falling through. Execute the other three perfectly and four silent weeks still leave the company feeling distant.
What moves you to the next one
Four things being true on the morning of day one closes this stage. The laptop boots and signs into a company account, the contract and paperwork are complete, the first-week schedule is in hand, and a senior colleague has been assigned. Many companies run that last item as a buddy system, where the buddy isn't there to teach the job but to be the person small questions go to — which printer works, whether it's normal to skip a meeting.
Anything missing from those four rolls into the next stage, and what rolls over eats the first week. No account means no access to the documents they were meant to read, and no access means the first week teaches less than it could have. That delay extends ramp-up time directly — the stretch before a new hire carries their own weight, commonly two to three months for an engineer.
From the first day the character changes. Getting ready gives way to actually learning the work, and the probation period starts at the same moment. Probation is the window, usually three months, for confirming the fit before employment becomes permanent. The difference between the two stages is whether a judgment is attached. Preboarding carries no evaluation; it only checks whether preparation is finished.
How it sounds at work
"Where are we on preboarding for next week's start? Has the laptop shipped?"
Checking in advance that nothing is missing for day one, with the long-lead item named specifically.
"Get the contract signed during preboarding. I want day one spent meeting people."
Pulling the administrative work forward to free up the first day.
"There's a month between acceptance and the start date, so reach out at least once in between."
Leaving the gap empty is treated as a risk to the hire.
Pagedeck reordered this after Theo's first day. Now, on the day an acceptance comes in, Grace opens the checklist and places the hardware order first, because that is the item with the longest tail. Paperwork comes back a week before the start date, and the first-week schedule goes out three days ahead.
The salesperson who joined last month had a laptop at nine on the first morning and was sitting in on a customer call with Sofia by ten. Not because there was no preparation to do, but because the preparation had already happened.
What people get wrong
Preboarding often gets read as paperwork. Most of the visible activity is ordering, provisioning and forms, so the impression is fair. But half the reason the stage exists is the contact. Fill four weeks with silence and a counter-offer from the current employer, or a call from another company, carries more weight. Complete paperwork is worth nothing if the person doesn't turn up, and a withdrawn acceptance costs more than every hour spent on the forms.
The other common misreading is treating it as a head start on the work. It's tempting to send a pile of documents to speed up day one, but assigning work to someone whose employment hasn't begun is unpaid labor rather than preparation. What's fine to send is introductory material they can read if they feel like it — with nobody checking whether they did and no assignment attached. Cross that line and the bad impression forms before the first day.
Easily confused with
| Term | Which stretch it covers | How it differs |
|---|---|---|
| Employee onboarding | The two or three months after the first day | The stage where the work actually gets learned. Preboarding only finishes the preparation ahead of it |
Where to go next
- Employee onboarding
see the stage that begins when preboarding ends
- Buddy system
how the senior colleague for day one gets assigned
Last updated 2026-09-16