Preboarding Sequence Template: Offer-Accepted to Day One

A regional manager signs off a strong candidate for a busy store on a Thursday. The offer is accepted, the start date is two and a half weeks out, and then — nothing. No one talks to the hire again until a reminder text the night before. Half the time it works. The other half, a competitor's counter-offer lands, or the hire simply cools off, and the manager learns on day-1 morning that the body they planned a rota around is not coming. The role goes back to square one, and the shift runs short.

That silence is the most expensive thing in frontline hiring, and it is entirely avoidable. A preboarding sequence is the structured set of touchpoints between offer-accepted and day one that keeps a signed hire engaged, prepared and expected. This template lays it out as a timeline any operator can run — what to send at each moment, who owns it, and why it matters — built for teams that hire across more than one site and cannot rely on a single manager remembering to check in.

This is for operations and people leaders who keep losing signed hires in the gap, or who arrive at day one with a stranger who needs a day of paperwork before they can be useful. Adapt the messages to your brand and your sector; keep the timeline and keep an owner on every step.

How to use this preboarding template

A preboarding sequence works when three things are true, and falls apart the moment one of them slips.

• Every touchpoint has an owner. "The team will reach out" means no one does. Each step below names a role — recruiter, hiring manager, or the assigned mentor — so a busy week never swallows a message silently.
• It is a sequence, not a single notification. One welcome email and a reminder text is not preboarding. The point is a light, steady rhythm that keeps the hire warm across the whole gap. Preboarding is not a notification — it is a short, structured journey.
• The same sequence runs at every site, in every language your floor speaks. A hire joining store 12 should get the same warm, organised run-up as one joining store 1. Authoring it once and running it everywhere is what keeps the standard from depending on which manager is on.

In onboarding.team this lives as the preboarding columns on the hire's kanban: each step is a card, each send is triggered automatically against the start date, and the mentor's tasks surface as approvals. You can run the same template by hand from a shared calendar — the structure matters more than the tool — but the owner and the trigger on every step are what stop it quietly lapsing. For the day-one-onward half of the journey, pair this with the frontline onboarding checklist.

The preboarding sequence, step by step

The timeline below assumes a typical two-to-three-week gap between offer and start. Compress or stretch the middle as your notice periods require, but keep the four anchors: the moment they accept, the countdown, the day before, and day-1 morning.

Step 1 — The moment they accept (within hours)

What to send: a same-day welcome from a named person — ideally the hiring or shift manager, not a no-reply address. Confirm the role, the start date, the site and a genuine "we're glad you're joining". Keep it human and short.

Who owns it: the hiring manager or recruiter who made the offer.

Why: the hours just after signing are when a hire feels most certain and most flattered — and when a counter-offer is most likely to arrive. Silence here reads as indifference and opens the door to second thoughts. A warm, prompt note from a real person closes it. This first step is the single highest-leverage moment in the whole sequence; the offer is most fragile right after it is accepted, which is the heart of why frontline hires ghost on offers.

Step 2 — The first 48 hours: confirm the practicals

What to send: the exact logistics in plain terms — start date and time, which site and which door, who to ask for on arrival, what to wear, where to park or which entrance to use. Attach or link any right-to-work, payroll and emergency-contact forms to complete before day one.

Who owns it: recruiter or people-ops for the paperwork; the hiring manager confirms the arrival details.

Why: a no-show on day one is more often confusion than cold feet — a hire who does not know where to go or who to ask often simply does not come. Getting the practicals out early removes that risk and signals an organised employer. Collecting paperwork now also frees the first shift for the actual job rather than a clipboard.

Step 3 — T-minus one week: set the standard early

What to send: one short context module — the brand, the basics, what good service looks like on your floor — plus a clear "what your first day will look like" outline. Keep the module light: a few minutes, not a course.

Who owns it: the assigned mentor or shift manager, who is also introduced to the hire here by name.

Why: this is where preboarding stops being admin and starts being onboarding. A short context module begins the standard before day one and signals this is a real job worth preparing for, not a gap-filler. Introducing the mentor now means the hire arrives knowing who has them — and the mentor knows a new starter is coming, rather than discovering it on the rota. Knowing what day one holds removes the anxiety that quietly turns good hires into no-shows.

Step 4 — The day before: confirm and reassure

What to send: a brief, friendly confirmation — "looking forward to seeing you tomorrow at 10, ask for Sam at the back entrance". Re-state the essentials, invite any last questions, and confirm everything physical is ready their end and yours.

Who owns it: the mentor or shift manager who will receive them.

Why: the day-before touch is the cheapest insurance against a day-1 no-show. It catches last-minute wobbles, gives the hire a named person to reply to, and makes them feel expected. On your side, it is the prompt to check that the uniform, locker, till or system logins and access are actually provisioned — so the hire is not learning on arrival that the company is disorganised.

Step 5 — Day-1 morning: a prepared welcome

What to send (and do): ensure the shift is briefed that the hire is coming and who is mentoring them, the workstation and logins are ready, and the mentor is free to greet them. The "send" here is internal — the handover to the floor — as much as anything to the hire.

Who owns it: the mentor, backed by the shift manager running the day.

Why: preboarding's whole job is to make this morning unremarkable — the hire walks in expected, equipped and owned, and the first shift goes straight to orientation and a first real task rather than scrambling for a login. A hire handed to whoever is free is a hire nobody owns; a prepared welcome is the payoff for every step above, and the clean handover into onboarding proper.

A worked example: keeping the gap warm

Take an anonymised retail operator — a composite, with scaled numbers — running a network of stores with steady seasonal hiring. Before any change, preboarding was a welcome email at offer and a reminder text the night before. Across a typical month of ~20 signed hires, roughly 3 never started: a ~15% offer-to-start drop, each one sending a vacancy back to the start of the funnel.

They put the sequence above in place — same-day welcome, practicals within 48 hours, a short context module and mentor introduction at T-minus one week, a day-before confirmation — authored once and run identically at every store.

Recovering ~2 starts a month is two fewer re-runs of sourcing, screening and interviewing, and two fewer short-staffed openings while the role is re-filled. The sequence cost no extra headcount and no spend — only the discipline of owning each touchpoint and triggering it on time. Across a year of steady hiring, that gap is where a meaningful slice of recruitment effort is either saved or thrown away.

Make the sequence run itself

A preboarding template on a shared doc is better than silence, but it still depends on someone remembering to send each message on a busy week — and the busiest weeks, peak hiring, are exactly when it gets dropped. The point of the timeline above is that it should hold without anyone watching the calendar, which only happens when each step has an owner and an automatic trigger.

That is the gap onboarding.team is built to close: the preboarding sequence runs as triggered steps on one kanban per hire — welcome, practicals, context module, day-before confirmation, mentor handover — in each language your floor speaks, so a signed hire stays warm from the moment they accept to the morning they arrive. You author the words once; the platform runs them at every site. For the wider picture of how preboarding feeds into the full journey, the frontline employee onboarding guide walks it end to end. When you are ready to stop losing hires in the gap, start a free trial and build the sequence behind your next starter this week.