What “Pre-boarding” Is (and What It’s Not)
Pre-boarding is the structured set of actions that happen after a candidate accepts an offer and before their first day. The goal is to remove predictable friction—missing accounts, incomplete paperwork, unclear logistics—so Day One can focus on people, context, and meaningful work rather than administrative catch-up.
Effective pre-boarding does two things at once: (1) reduces anxiety by setting expectations and providing clear next steps, and (2) reduces administrative burden by completing compliance and setup tasks asynchronously with clear owners and service-level expectations.
Common Day-One Friction Pre-boarding Prevents
- New hire arrives without a laptop, badge, or workspace.
- System access is missing (email, SSO, HRIS, payroll, ticketing, CRM, code repos).
- Payroll or tax forms are incomplete, delaying pay.
- Background check is still pending with no contingency plan.
- Policies are introduced all at once, creating cognitive overload and missed acknowledgments.
- New hire doesn’t know where to go, who to ask, what to wear, or how the first week will look.
Design Principles for Low-Friction Pre-boarding Workflows
1) One intake, many downstream actions
Collect key data once (legal name, address, start date, role, location, manager, equipment needs) and route it automatically to HR, IT, Facilities, and Security. Avoid asking the new hire to re-enter the same information across multiple tools.
2) Clear ownership and SLAs
Every task should have: Owner (a role, not a person), due date, SLA (how quickly the owner must act once triggered), and escalation path if the SLA is missed.
3) Separate “must-have by Day One” from “nice-to-have by Week One”
Not everything needs to be perfect on Day One, but the essentials do: pay readiness, identity verification, core system access, equipment, and a clear schedule. Use a tiered approach to prevent bottlenecks.
Continue in our app.
You can listen to the audiobook with the screen off, receive a free certificate for this course, and also have access to 5,000 other free online courses.
Or continue reading below...
Download the app
4) Reduce cognitive load with sequencing
Instead of sending a large packet of policies and forms at once, sequence tasks across days with short instructions and estimated completion time (e.g., “5 minutes,” “15 minutes”).
What to Include in Pre-boarding (with Practical Guidance)
Collecting paperwork (payroll, tax, identity, emergency info)
Objective: ensure the employee can be paid correctly and the organization meets legal requirements.
- Bundle forms into a single digital flow (HRIS or secure portal) with progress indicators.
- Ask only what’s necessary pre-start: bank details, tax withholding, legal name verification, address, emergency contact, direct deposit, required work authorization steps.
- Provide a “what you’ll need” list before the form link (e.g., bank routing number, ID documents).
- Set a completion deadline (e.g., T-7) and automate reminders.
Tip: If your process requires in-person verification (e.g., identity documents), schedule it as a Day One appointment rather than leaving it ambiguous.
Equipment provisioning (laptop, peripherals, phone, badge, workspace)
Objective: the new hire can work productively on Day One without waiting on hardware.
- Standardize role-based kits (e.g., “Customer Support Kit,” “Engineer Kit,” “Sales Kit”) to reduce custom back-and-forth.
- Confirm shipping details early for remote hires (address validation, delivery window, signature requirements).
- Include peripherals (headset, monitor, adapters) based on role needs.
- Plan for contingencies: loaner devices, local pickup options, or “Day One access via VDI” if hardware is delayed.
System access requests (accounts, permissions, groups)
Objective: ensure access to core systems and least-privilege permissions are ready by Day One.
- Use role-based access profiles (RBAC) to predefine groups and permissions.
- Separate core access (email/SSO, HRIS, payroll, messaging) from role tools (CRM, repo, analytics).
- Require manager approval for elevated permissions, but keep it lightweight (one-click approval).
- Timebox access provisioning with SLAs (e.g., core accounts within 2 business days of request).
Practical example: Create an “Access Pack: Sales Associate” that automatically provisions SSO, email, calendar, messaging, CRM basic role, shared drive folders, and ticketing access. Any exceptions (admin roles, finance systems) require a separate request and approval.
Background checks (status tracking and start-date readiness)
Objective: complete screening requirements without leaving the new hire uncertain or the team unprepared.
- Trigger immediately after offer acceptance to protect the start date.
- Provide transparent status updates (e.g., “initiated,” “in progress,” “needs info,” “complete”).
- Define a contingency plan for pending checks (e.g., delayed start, restricted access, or conditional start depending on policy and local law).
- Assign an owner for follow-ups with the vendor and the candidate.
Policy acknowledgments (sequenced, trackable, auditable)
Objective: ensure required policies are acknowledged without overwhelming the new hire.
- Prioritize required-by-start policies (code of conduct, confidentiality, security, acceptable use).
- Defer non-critical policies to Week One with a clear deadline.
- Use a single acknowledgment hub with timestamps and version control.
- Add short summaries (“What this means in practice”) to reduce misinterpretation.
Pre-start “What to Expect” packet (reduce anxiety, set logistics)
Objective: answer the questions new hires often hesitate to ask and set a predictable first-day experience.
Include these sections
- Day One logistics: start time, location/virtual link, parking/transit, building entry, dress expectations, who greets them.
- First-week schedule snapshot: key meetings, orientation blocks, manager 1:1, team intro.
- How communication works: messaging norms, response expectations, meeting etiquette.
- What to prepare: IDs for verification, quiet workspace for remote, internet requirements.
- Who to contact: HR contact, IT help, manager, buddy (if assigned).
- What “good” looks like in the first few days: simple, reassuring milestones (e.g., “You’ll have accounts, meet your team, and complete required setup”).
Format tip: Keep it to 1–2 pages or a single well-structured email with links. The goal is clarity, not volume.
Build a Pre-boarding Timeline (T-14 to T-1) with Owners and SLAs
Use a timeline anchored to the start date. Adjust the “T-14” start point based on your hiring volume and background check lead times. The key is that each step has an owner, an SLA, and an escalation path.
| Time | Task | Owner | SLA / Due | Notes / Escalation |
|---|---|---|---|---|
| T-14 | Send “Offer Accepted” welcome email + pre-boarding portal link | HR | Within 1 business day of acceptance | If not sent, manager is notified at T-12 |
| T-14 | Initiate background check | HR / Recruiting Ops | Same day | Escalate to HR lead at T-10 if no status update |
| T-13 | Open IT ticket for equipment + core accounts | HR (trigger) / IT (fulfill) | Ticket created within 1 business day | Include role-based kit + shipping details |
| T-12 | Manager confirms role-based access profile + any exceptions | Manager | 48 hours | Escalate to manager’s leader at T-9 if not approved |
| T-10 | Facilities/Security: badge request, building access (if applicable) | Facilities/Security | 3 business days | Remote hires: skip or create visitor instructions |
| T-9 | New hire completes payroll/tax/personal info forms | New hire (supported by HR) | Due by T-7 | Auto-reminders at T-8 and T-6 |
| T-7 | IT provisions core accounts (SSO/email/messaging) and confirms shipment tracking | IT | Core access ready by T-3; shipment sent by T-5 | Escalate to IT lead at T-4 if not shipped |
| T-6 | HR assigns buddy (if used) and shares intro note | HR / Manager | 48 hours | Buddy receives expectations for first week touchpoints |
| T-5 | Policy acknowledgments: required-by-start set | HR / Compliance | Due by T-2 | Track completion; escalate at T-2 if incomplete |
| T-4 | Manager drafts Day One agenda + first-week calendar holds | Manager | Due by T-2 | Include team intro, 1:1, and setup blocks |
| T-3 | IT validates access (test login) + creates “Day One support” contact path | IT | Within 1 business day | Provide a single help link and hours of coverage |
| T-2 | Send “One week out” (or “Two days out”) expectations email with logistics + schedule snapshot | HR | Due by T-2 | Include where to go, what to bring, who to contact |
| T-1 | Send “Day-before” email + confirm equipment delivery + first-day start instructions | HR (or Manager for personal touch) | By end of day | Escalate immediately if equipment/access not ready |
How to Set Practical SLAs
- Define SLAs in business days and align them to your start-date cadence (e.g., Monday start dates require earlier cutoffs).
- Use “ready-by” dates rather than “start working on” dates (e.g., “Core access ready by T-3”).
- Make escalation automatic: if a task is overdue, notify the next-level owner and provide a clear action request.
Templates
Template 1: Pre-boarding Checklist (HR / IT / Manager)
Use this as a shared checklist in your ticketing system, HRIS task list, or project tracker. Keep it role-based where possible.
| Category | Task | Owner | Due | Status | Notes |
|---|---|---|---|---|---|
| HR | Send offer-accepted welcome email + portal access | HR | T-14 | Include “what happens next” and support contact | |
| HR | Initiate background check and track status | HR | T-14 | Escalate if “needs info” > 48 hours | |
| HR | Collect payroll/tax/personal details | New hire / HR | T-7 | Provide checklist of required info/documents | |
| HR | Policy acknowledgments (required-by-start) | New hire / HR | T-2 | Track completion and send reminders | |
| HR | Prepare “What to Expect” packet | HR | T-2 | Logistics, schedule snapshot, contacts | |
| IT | Create accounts: SSO, email, messaging | IT | T-3 | Confirm login works; MFA instructions ready | |
| IT | Provision role tools (CRM/repo/ticketing/etc.) | IT | T-2 | Manager approves exceptions | |
| IT | Prepare equipment kit and ship/provide pickup details | IT | Ship by T-5 | Include tracking number and setup guide | |
| IT | Day One support plan (help link, hours, priority path) | IT | T-3 | Ensure rapid response during first login window | |
| Manager | Confirm start time, location/virtual link, and Day One agenda | Manager | T-2 | Calendar invites sent to new hire | |
| Manager | Confirm access profile and any special permissions | Manager | T-12 | Use RBAC; avoid ad-hoc permissions | |
| Manager | Assign buddy (if applicable) and align expectations | Manager | T-6 | Buddy schedules intro touchpoint | |
| Manager | Prepare team announcement (internal) timed for Day One | Manager | T-1 | Include role, start date, how to welcome them |
Template 2: Welcome Email Series
These templates are designed to be short, reassuring, and action-oriented. Replace bracketed fields as needed.
Email A: Offer Accepted (send within 1 business day)
Subject: Welcome to [Company], [First Name] — next steps before your start date Hi [First Name], We’re excited to have you joining as [Role] on [Start Date]. To make your first day smooth, here’s what happens next: 1) Pre-boarding tasks (about [X] minutes total) Complete your details and required forms here: [Secure Link] What you’ll need: [e.g., bank details, address, ID info] Deadline: [T-7 date] 2) Background check (if applicable) You’ll receive an email from [Vendor] to begin. If you don’t see it within 24 hours, reply here and we’ll help. 3) Equipment and access IT will prepare your equipment and accounts. If you have any special needs (e.g., monitor, accessibility tools), tell us by [date]. Questions anytime: HR contact: [Name, Email, Phone] We’ll send a “what to expect” note closer to your start date with Day One details. Welcome again, [HR Name] [Title]Email B: One Week Out (send at T-7, or adjust to your cadence)
Subject: One week until your first day — what to expect Hi [First Name], You’re one week away from starting on [Start Date]. Here are the key details so you know exactly what to expect: Day One start: [Time] [Time Zone] Location/Link: [Office address + entry instructions OR video link] Who you’ll meet first: [Name, Title] Dress: [Guidance] Equipment: [Shipping status / pickup plan] If you haven’t received tracking details by [date], contact: [IT contact/link]. First-week snapshot: - [Day 1] [Orientation / team intro / setup] - [Day 2] [Training / manager 1:1] - [Day 3] [Role tools / shadowing] If you haven’t completed your pre-boarding forms yet, please do so by [date]: [Secure Link] Looking forward to your first day, [HR or Manager Name]Email C: Day-Before (send at T-1)
Subject: See you tomorrow — your Day One plan Hi [First Name], We’re ready for you tomorrow. Here’s everything you need for a smooth first day: Start time: [Time] [Time Zone] Where to go / how to join: [Office entry steps OR meeting link] Your first meeting: [Calendar invite name + time] Equipment and login: - If your laptop arrived: please keep it boxed until tomorrow (we’ll guide setup), or follow this setup guide: [Link] - If it hasn’t arrived: contact IT here now so we can activate a backup plan: [IT link/phone] What to bring (if onsite): [ID, parking info, etc.] What to have ready (if remote): [quiet space, internet, phone for MFA] If anything changes or you’re running late, text/call: [Manager phone] See you tomorrow, [Manager Name] [Title]Operationalizing the Workflow (So It Runs Without Heroics)
Use a single “Pre-boarding Intake” form
Capture the minimum data needed to trigger downstream tasks. Recommended fields: legal name, preferred name, personal email, start date, location (onsite/remote), shipping address, manager, department, role, equipment kit selection, special accommodations, and required systems (choose from role-based list).
Automate task creation and reminders
When the offer is accepted, automatically: (1) create an IT ticket, (2) create HR tasks for forms and policies, (3) notify the manager to confirm access profile and Day One schedule, and (4) start the email series schedule.
Define an exception path
Document what happens if any of these are not ready by T-1: equipment delay, background check pending, missing payroll forms, or access provisioning failure. Assign a decision-maker and a same-day response SLA.
Track readiness with a simple dashboard
Track a small set of readiness indicators per new hire: Forms complete, Background check status, Equipment shipped/received, Core access ready, Policies acknowledged, Day One schedule sent. Use red/yellow/green to focus attention where it’s needed.
