New Hire Onboarding Checklist: Complete Template
A new hire checklist is the difference between an employee contributing in week one versus feeling lost for a month. Most managers create an onboarding checklist template as an afterthought, dumping a list of links into a Slack message on Monday morning.
This guide shows you how to build a structured onboarding process. You will get a complete template for standardizing day one, week one, and month one, plus practical advice on how to document the actual workflows your new hires need to learn.
What Should Be Included in a New Hire Checklist?
A comprehensive new hire checklist should include pre-boarding IT setup, day-one orientation tasks, week-one role-specific training, and month-one performance milestones. It must cover both administrative compliance and actual workflow documentation.
Most companies split onboarding into two distinct categories. HR owns the administrative side, which includes payroll, benefits, and company policies. The hiring manager owns the functional side, which covers software access, role-specific standard operating procedures (SOPs), and team integration.
If you only document the HR side, your new hire will know how to enroll in dental insurance but won't know how to merge a pull request or respond to a customer ticket. A functional checklist bridges that gap.
The Complete Onboarding Checklist Template
Below is a structured template you can copy into your project management tool. It separates tasks by timeline and assigns clear ownership so nothing falls through the cracks.
Phase 1: Pre-boarding (Days Before Start)
The goal of pre-boarding is to ensure the employee can actually log in and start working at 9:00 AM on their first day.
| Task | Owner | Required Documentation |
|---|---|---|
| Order and ship company laptop | IT / Ops | Hardware request form |
| Create email address and Slack account | IT / Ops | Account provisioning SOP |
| Send welcome email with day-one schedule | Hiring Manager | Welcome email template |
| Grant access to core software (Notion, Jira, etc.) | IT / Ops | Role-based access matrix |
| Schedule intro meetings with key team members | Hiring Manager | Department org chart |
Phase 2: Day One (Orientation and Access)
Day one should be light on actual work and heavy on context. The objective is to make the new hire feel welcome and verify that all their tools function correctly.
| Task | Owner | Required Documentation |
|---|---|---|
| Host 1:1 welcome meeting and office tour | Hiring Manager | Day one agenda |
| Verify hardware and software access | IT / Ops | Troubleshooting guide |
| Complete I-9, payroll, and benefits enrollment | HR | Benefits overview deck |
| Review company handbook and core values | HR | Employee handbook |
| End-of-day check-in | Hiring Manager | N/A |
Phase 3: Week One (Workflow and Tools)
This is where functional onboarding begins. The employee shifts from reading company history to learning how their specific job is done.
| Task | Owner | Required Documentation |
|---|---|---|
| Review department-specific goals and KPIs | Hiring Manager | Department OKRs |
| Complete software tool training | Peer Mentor | Tool-specific SOPs |
| Shadow a peer on a common daily task | Peer Mentor | Shadowing checklist |
| Perform first guided task (e.g., draft a reply) | Hiring Manager | Task review rubric |
| Friday week-in-review meeting | Hiring Manager | Feedback form |
Phase 4: Month One (Independence and Review)
By the end of month one, the new hire should be executing standard tasks independently using your company's documentation.
| Task | Owner | Required Documentation |
|---|---|---|
| Assign first independent project | Hiring Manager | Project brief |
| Review 30-day performance metrics | Hiring Manager | 30-60-90 day plan |
| Gather feedback on the onboarding process | HR | Onboarding survey |
| Transition from daily to weekly 1:1s | Hiring Manager | 1:1 meeting template |
Where Traditional Onboarding Checklists Fall Short
A spreadsheet checklist tells a new hire what to do. It rarely tells them how to do it.
You can add a checkbox that says "Process a customer refund in Stripe," but checking that box requires actual knowledge of the workflow. When companies rely on generic templates, they usually end up pairing the new hire with a senior employee for hours of screen-sharing. This burns out your best performers and relies entirely on tribal knowledge.
The alternative is linking step-by-step documentation directly inside the checklist. Every time a task is assigned, the instructions for completing that task are attached to the ticket.
Creating that documentation used to take hours of manual screenshotting. Today, you can automate it. Glyde is a Chrome extension that records your screen while you execute a workflow and generates a step-by-step SOP automatically. It captures the DOM state, click targets, and screenshots to write contextual descriptions of what you are doing.
Scribe and Tango offer similar automatic documentation features, though they often default to generic "click here" captions. Glyde's multimodal approach builds instructions that explain the context behind the click, which is usually what a new hire actually needs to understand the task. You generate the guide once, export it, and link it in your new hire checklist permanently.
How Do You Document Workflows for New Hires?
To document workflows for new hires, you need to capture the exact steps, clicks, and context of a task. Avoid dumping generic manuals; instead, record the actual processes they will perform daily using standard operating procedures.
Start by identifying the five most common tasks the new hire will do in their first two weeks. If you are hiring a customer support representative, those tasks might be:
- Logging into the Zendesk dashboard
- Categorizing and tagging an inbound ticket
- Processing a standard refund
- Escalating a technical bug to engineering
- Updating a customer's billing address
Document these five workflows completely. Do not assume the software's UI is intuitive enough to figure out. What seems obvious to someone who has used the platform for three years is entirely foreign to someone on day two. Include visual aids, highlight the specific buttons they need to click, and explain what happens after they complete the task.
What Tools Do You Need to Manage a New Hire Checklist?
Managing a new hire checklist requires an HRIS for compliance, a project management tool for task tracking, and a documentation platform for workflow instructions. Relying solely on email or chat leads to lost information and inconsistent onboarding.
Project Management Software Tools like Asana, Monday, or Jira are ideal for hosting the checklist itself. You can create a master template project and duplicate it every time a new employee signs their offer letter. This allows you to assign specific due dates and tag the IT or HR personnel responsible for pre-boarding tasks.
Knowledge Bases Your checklist needs a home base for long-form reading. Notion and Confluence are the standard choices here. This is where you store the employee handbook, the company architecture diagrams, and the cultural guidelines.
Process Documentation Tools As mentioned earlier, you need a way to show new hires how to use their software. Glyde, Scribe, or even a well-organized Google Doc can serve this purpose. The key is ensuring these tactical guides are linked directly from the project management tasks so the employee doesn't have to search the entire knowledge base to find out how to reset a password.
How Long Should Employee Onboarding Take?
Effective employee onboarding takes between 30 and 90 days. While administrative setup and basic orientation happen in the first week, reaching full productivity in a specific role requires at least a month of structured workflow training and feedback.
Many operations managers use the 30-60-90 day framework to measure onboarding success.
In the first 30 days, the focus is entirely on learning. The employee is consuming documentation, shadowing peers, and completing heavily supervised tasks. Mistakes are expected and corrected.
Between days 31 and 60, the focus shifts to execution. The employee should be handling standard daily workflows independently. They will still need help with edge cases or rare problems, but the core job description is being fulfilled.
By day 90, the employee is fully integrated. They are hitting standard performance metrics, contributing to team meetings, and perhaps even updating the documentation they used during their own onboarding to help the next person.
Honestly, most teams overthink the format of their checklist. Whether you use a complex Jira board or a simple Notion table matters less than the consistency of the information provided. Start by writing down exactly what your next hire needs to do on day one, build the documentation to support those tasks, and iterate as your team grows.
Learn More About Employee Onboarding Documentation
For a complete framework on building your team's training materials, see our guide on the complete guide to employee onboarding documentation, including how to scale these checklists as your company grows and transitions to remote work.
