Employee Onboarding SOP.
A role-first onboarding process that gives a new employee or contractor context, access, expectations, and a useful first deliverable.
Editable DOCX · Copy in one click · No email gate
Operating standard
Control without the corporate sludge.
Owner
The hiring manager, with operations owning records and the system owners granting access.
Response
Plan ready three working days before start. Core access available by the start of day one. Blocking issues resolved within four business hours.
Metric
At least 90 percent of new starters complete core setup on day one and deliver the agreed first-week outcome.
If nobody owns the process, the founder owns every emergency.
Purpose
Make a new team member productive and secure without depending on the founder to remember every setup task.
When it applies
Use from signed offer or contractor agreement through the end of the person's first 30 days.
Do not start blind.
Trigger to outcome. No meeting required.
- 01
Confirm the signed agreement, start date, role, manager, and worker classification.
- 02
Create the onboarding plan and first-week calendar at least three working days before start.
- 03
Prepare equipment and request least-privilege access through the access-management SOP.
- 04
Send the welcome note, company context, operating norms, and required reading.
- 05
Complete identity, payroll or invoice, confidentiality, security, and policy steps on day one.
- 06
Explain the role scorecard, decision rights, communication expectations, and 30-day outcomes.
- 07
Assign a small real deliverable that can be completed during the first week.
- 08
Hold check-ins at the end of week one and days 14 and 30; close gaps and record completion.
Authority must be explicit.
Know when to stop.
Escalate missing contracts, identity checks, payroll details, equipment, or critical access to operations and the hiring manager. Do not permit work without the required agreement and security controls.
If it is not recorded, it did not happen.
Make the generic parts real.
How teams break the process.
Making onboarding a tour of random documents
Granting every tool before defining the role
Waiting weeks before assigning meaningful work
Related startup SOPs.
Make the process executable.
Download it, assign the real owners, set the thresholds, and test it with someone who did not write it.