Start dates are contractual commitments. When a new employee arrives to find no laptop, no email access, or no system credentials, the message delivered is that operational readiness did not match the recruiting promise. That gap does not disappear with orientation slides—it compounds through early tenure and shapes how the employee calibrates trust in the organization.
The provisioning runbook converts start-date readiness from a set of distributed hopes into a managed process with explicit owners, timed deadlines, and escalation paths.
#The anatomy of a provisioning failure
Most day-one failures are not hardware problems. They are coordination problems. Three parties—IT, HR, and the hiring manager—each assume one of the others owns the critical path. No one does.
"Provisioning failures rarely happen because the tasks are hard. They happen because no one owns the deadline." — Field observation from HR operations reviews at mid-market employers.
Three failure modes repeat across organizations:
Late hardware requisition. The manager submits the IT ticket the week before the start date rather than three to four weeks prior. Shipping delays and imaging queues cascade directly into day-one gaps that no amount of goodwill recovers.
Access provisioning not triggered. The HRIS record is created, but the downstream signal to IT for system access is not automated—or the automation depends on a field that HR entered two days late. The record exists; the access does not.
No manager first-week plan. The runbook ends at desk and device setup. The new hire has tools but no agenda, no clarity on week-one deliverables, and no indication the manager expected them. Orientation fills the gap inadequately.
Each failure is recoverable in isolation. Combined, they produce an early-tenure experience that is difficult to reverse regardless of subsequent manager effort.
#Runbook structure: T-minus timeline
A production runbook uses fixed columns and T-minus offsets from the confirmed start date. Offsets eliminate ambiguity. "Before start" is not an owner; "T-20" is actionable:
| Task | Owner | Offset | Escalation Contact |
|---|---|---|---|
| Submit hardware order | Hiring manager | T-20 | IT Director |
| Create HRIS record | HR Ops | T-15 | HR Ops Lead |
| Provision email and directory | IT | T-10 | IT Director |
| Assign core application access | IT | T-7 | IT Director |
| Badge and physical access | Facilities | T-5 | Office Manager |
| Manager completes first-week plan | Hiring manager | T-3 | HRBP |
| Confirm all access — IT sign-off | IT | T-1 | IT Director |
| Orientation session confirmed | HR Ops | T-0 | HR Ops Lead |
Every task has one named role—not a team—as owner, and one escalation contact if the deadline slips. When a task is late, the escalation contact is responsible for resolution, not mediation.
The same governance model that applies to new hire provisioning applies symmetrically to exits. Access revocation, equipment recovery, and HRIS termination require the same rigor as provisioning—a point explored more fully in managing employee lifecycle transitions.
#Day-one readiness checklist
Run this verification before 8:00 AM on start date. Any unchecked item means a runbook step failed at or before T-1:
- Laptop powered on, enrolled in MDM, and staged at workstation
- Email account active; new hire can authenticate with temporary credentials
- Core applications accessible: HRIS self-service, communication tools, project management
- Building badge functional; parking or transit access confirmed if applicable
- First-week calendar populated by hiring manager with at least three structured touchpoints
- HR orientation session confirmed with room or video link
If any item is unchecked at T-0, escalation has already failed at the T-1 stage. Use the gap as a retrospective trigger, not a triage event. The root cause is in the runbook, not on the start date.
#Closing the feedback loop
The runbook improves only if failure data flows back into it. Two mechanisms make this reliable without adding process overhead.
Manager survey at end of week one. Four questions: What was missing at start? What caused the most friction in the first week? What was ready ahead of expectation? What would you change for the next hire on your team? Aggregate responses quarterly. Update the runbook template when a gap appears more than twice.
Retrospective on every failed start date. Treat a provisioning gap the same way engineering treats a production incident: root cause, contributing factors, owner of the fix, and a target date. Written, tracked, and reviewed at the monthly ops meeting.
High-growth teams face compounding risk because the volume of start dates scales faster than the informal coordination mechanisms that worked at smaller headcount. Runbook discipline becomes a prerequisite for governance in high-growth environments, not an operational nice-to-have that can wait until the next scaling threshold.
#Related guides
Sources
- Society for Human Resource Management. New Employee Onboarding Guide
- U.S. Department of Labor. Form I-9, Employment Eligibility Verification
- Harvard Business Review. To Retain New Hires, Spend More Time Onboarding Them
This article is operational education only—not legal advice. Work with qualified counsel for compliance, compensation, and termination decisions in your jurisdiction.