16 items

Employee Onboarding

Most new hires decide whether they'll stay long-term within their first 90 days — and many form that impression in their first week. This checklist walks managers and HR teams through every phase from offer acceptance through the 90-day review, with the reasoning behind each step. For more background and examples, see the guidance below; for built-in tools and options, use the quick tools guide.

Author

Checklistify Editorial Team

Last Updated

Checklist Items

0 done•16 left•4 of 5 sections collapsed

Send a personalized welcome email from the hiring manager within 24 hours of offer acceptance.

The period between offer acceptance and the start date is when competitive counter-offers and second-guessing are most common. SHRM estimates approximately 17% of new hires leave within the first 90 days, and a meaningful subset never reach Day 1 — primarily because the pre-boarding period feels transactional or silent. The welcome email should come from the hiring manager (not HR alone) and answer practical questions: exact arrival time and location, who to ask for at reception or the link to the Day 1 video call, dress code if not obvious, and what the first few hours will look like. The tone carries as much weight as the logistics — a warm note that says 'The team is genuinely looking forward to having you' reduces the anxiety that fuels second-guessing. If the start date is more than two weeks out, schedule a light mid-point check-in: a brief message asking if they have everything they need before Day 1 maintains the relationship without overwhelming them.

Provision all equipment, accounts, and software access before Day 1 — verify by logging in as the user.

An IT failure on Day 1 is disproportionately damaging because the new hire has no frame of reference for whether it's a one-off or a signal of organizational disarray — and most assume the latter. The pre-boarding IT checklist: corporate email account created and tested for send and receive, SSO identity provider account configured with the new hire's credentials, communication platforms (Slack, Teams, or equivalent) provisioned with relevant channels joined, role-specific software licensed and confirmed accessible, code repositories or shared drives granted at the correct permission level, and hardware staged at the workspace or shipped for remote hires. The step most teams skip: log in as the user to verify each access point works — confirming in the admin console that an account was created is not the same as confirming it functions correctly. For remote hires, ship hardware to arrive at least two business days before the start date. Delivery delays happen; a 48-hour buffer allows for reshipment or contingency planning without a Day 1 failure.

Send all HR paperwork digitally at least 10 days before the start date — include a plain-language benefits summary.

Completing I-9 employment eligibility verification, W-4 federal withholding elections, state tax forms, direct deposit authorization, and policy acknowledgments before Day 1 ensures the first day is an orientation and relationship-building experience rather than an administrative processing session. Digital HR platforms — BambooHR, Rippling, Gusto, Workday, or DocuSign — allow completion from home at the new hire's convenience. Sending 10 days out (not 1 or 2) allows time to resolve problems: I-9 documentation requirements occasionally require a new hire to locate specific identification documents they may not have immediately on hand, and working through that over email is far better than holding them at reception on Day 1. Benefits enrollment deserves particular attention — most health insurance and FSA plans have enrollment windows that close 30 days after the hire date. Alongside the enrollment forms, send a plain-language one-pager that explains the options in plain terms, not just the vendor PDFs. A new hire who doesn't understand their options may default to no coverage or make an election they'll regret.

Assign an onboarding buddy from the peer team before Day 1 — brief them specifically on their role and responsibilities.

An onboarding buddy is a peer — not the new hire's direct manager — who serves as an informal guide and social anchor for the first 30 to 90 days. Microsoft research found that new hires with onboarding buddies rated their onboarding experience 36% higher and reported reaching productivity faster than those without one. The buddy's role is explicitly different from a mentor's or a manager's: they are not responsible for formal training, performance feedback, or career development. They are the person the new hire can ask 'Is it normal that this meeting always runs over?' or 'Who actually knows how the expense system works?' without any concern about being judged. Ideal buddy profile: someone 6 to 24 months into the same or an adjacent role — experienced enough to be genuinely useful, recent enough to remember what it felt like to be new, and visibly positive about the organization's culture. The buddy brief should cover the new hire's role and professional background, a suggested minimum check-in cadence (end of Day 1, daily for the first week, weekly through Month 1), and 2 to 3 specific colleague introductions to make on the new hire's behalf that they might not encounter organically.

Send a first-week schedule and practical logistics guide 3 to 4 days before the start date.

Uncertainty about what to expect on Day 1 is one of the most consistent sources of new hire anxiety — and one of the easiest to address with minimal effort. A first-week schedule should answer: what time each day starts and ends, where to be and when, what the Day 1 and Day 2 agenda looks like, which meetings are mandatory versus optional, and when there is unstructured time for setup or reading. The logistics guide addresses questions new hires are often embarrassed to ask: where to park or how to access the building, bathroom and kitchen location, whether lunch is provided or what nearby options exist, how to submit expenses, and what the unwritten norms around working hours and after-hours communication are. Sending this 3 to 4 days before the start date gives the new hire time to review it and ask follow-up questions before Day 1. A simple, well-organized email is better than no communication — the goal is that the new hire arrives on Day 1 knowing what to expect, not discovering it in real time.

Keep Day 1 focused on relationships and orientation — not training modules, policy walkthroughs, or deliverable pressure.

The most common Day 1 design failure is treating it as a training day. New hires subjected to hours of compliance modules, product briefings, and policy walkthroughs on their first day retain very little of the material — the Ebbinghaus Forgetting Curve shows approximately 50% of new information is lost within 24 hours without reinforcement — and frequently leave the day feeling overwhelmed rather than welcomed. What Day 1 should accomplish: the new hire knows their immediate colleagues by name and has had at least one genuine, non-logistical conversation with them; they know where to find what they need for the first week; they feel genuinely expected and welcome. What Day 1 does not need to accomplish: complete policy knowledge, product mastery, or any measurable output. Every piece of training that can wait until Week 2 should wait — the new hire will absorb it better when they have the context to understand why it matters. The goal of Day 1 is that the new hire goes home feeling like a person who belongs there, not a person who has just been processed.

Brief the immediate team before the new hire arrives — ensure no one is surprised by their presence.

The specific failure to avoid: a new hire arriving while colleagues are clearly unaware they're starting. Team briefing content: the new hire's name, their role and reporting line, their start date and approximate arrival time, a sentence or two about their professional background (shared with their consent), and a specific ask of the team ('Please make a point of introducing yourself in Slack this week' or 'We have a brief welcome coffee at 11am on Monday'). For remote teams, a pinned introduction message in the team Slack or Teams channel and a calendar invite for a short optional welcome call serve the same function. A casual team lunch or 30-minute informal gathering during the first week creates a social anchor and gives the new hire a chance to put faces to names in a lower-pressure context than a full team meeting.

Walk the new hire through only the tools and spaces they will need in the next five working days.

Full-scope tool onboarding on Day 1 — covering every platform, integration, and workflow the role will eventually involve — produces cognitive overload without proportional benefit. The practical approach: identify the 3 to 5 tools the new hire will actually need in their first week and walk through only those, ideally in the context of a real task they'll perform soon. For most roles, this means the email client, the team communication platform, the project management tool, and the document storage system. Advanced platforms, analytics dashboards, and secondary tools can be introduced when the new hire is ready to use them in context. Round out the setup with a brief 'where to find things' guide: the internal wiki or knowledge base, the IT help desk process, and the HR portal for reference. Keeping this to the essentials respects the new hire's cognitive bandwidth and signals that the organization is thoughtful about not overwhelming people.

Co-create explicit 30-day goals with the new hire — focus on learning milestones and relationships, not deliverables.

Thirty-day goals calibrate expectations and reduce the anxiety of not knowing what 'good' looks like during the learning phase. Well-designed 30-day goals are learning- and relationship-oriented: 'Have a 1-on-1 introductory conversation with each direct team member,' 'Shadow three customer interactions to understand the end-user perspective,' 'Be able to walk through the product's core workflow independently,' and 'Complete all required compliance and systems training.' Avoid output-based 30-day goals — a new hire asked to produce significant deliverables before they understand organizational context and norms makes decisions with incomplete information, requiring correction that creates net negative productivity compared to a clean learning phase. The 30-60-90 framework: 30 days to learn, 60 days to contribute under guidance, 90 days to execute independently toward agreed goals. Bring these goals to the new hire as a draft in the first week, not as a handout — adjusting them based on the new hire's self-assessment of their starting point produces goals they're genuinely invested in meeting.

Schedule introductory 1-on-1s with 5 to 8 key cross-functional stakeholders during the first two weeks.

Stakeholder meetings in the first two weeks are context-gathering sessions, not status updates. The new hire should arrive prepared with 3 to 5 questions: 'What are your team's top priorities this quarter?', 'How does my role typically interact with your work?', 'What would it look like if my function made your job easier?', and 'What should I know about how things work here that isn't written down anywhere?' These questions surface information that no onboarding document contains — the real organizational priorities, the informal influence structure, and the historical context behind current decisions. The hiring manager's role: identify the 5 to 8 most important stakeholders for this specific role, reach out to them in advance to explain the purpose of the meeting (orientation and context, not deliverable discussion), and keep the format at 30 to 45 minutes per conversation. Covering these in the first two weeks — while the new hire is still in learning mode and stakeholders have realistic expectations — gives the new hire an organizational map built from multiple perspectives, not just their manager's.

#10

Hold structured weekly 30-minute check-ins with the new hire throughout the first 30 days.

Early check-ins serve a different purpose than ongoing 1-on-1s: they are primarily a two-directional diagnostic, not a status update session. The agenda should consistently cover what has gone well, what has been confusing or unexpectedly difficult, what support the new hire needs from the manager or team this week, and a brief forward look at the next week's focus. The manager's role is to listen more than to assign — new hires in the first month frequently have observations that would surface problems early if given explicit permission to raise them: a tool that doesn't work as described, a process that contradicts what was said in the interview, a stakeholder who seems to have different expectations about the role's scope. The most common early-manager failure pattern is strong Day 1 investment followed by two to three weeks of low-contact independence, leaving the new hire navigating uncertainty alone at the exact moment they most need guidance.

#11

Enroll the new hire in a structured training sequence with defined deadlines and completion tracking.

The default at many organizations is ad hoc training: 'Ask someone if you have questions,' 'There are some docs in the wiki,' or 'You'll pick it up as you go.' This approach produces inconsistent outcomes and leaves new hires unsure whether they've missed something important. A structured training sequence defines what the new hire needs to know, in what order, by what point, and how completion is confirmed. The sequence should include: compliance training (legal deadlines vary by jurisdiction but are typically required within 30 days — sexual harassment prevention, data privacy, workplace safety), role-specific product or technical training, process walkthroughs for the workflows they'll own, and any certifications required for their function. Learning management platforms such as Workday Learning, Lessonly, or TalentLMS allow completion tracking without manual follow-up from managers. For smaller teams without an LMS, a shared checklist with assigned due dates works well — the key is that completion is visible to both the new hire and their manager, creating mutual accountability without surveillance.

#12

Transition the new hire to active contribution with a first real project that has defined scope and a designated reviewer.

The transition from learning mode to contributing mode should be made explicit — a new hire who completes the first 30 days in learning mode needs a clear signal that the expectations have shifted. The first real project should have: a defined deliverable (not 'help with X' but 'produce Y by Z date'), a scope that is achievable given what the new hire has learned so far, a named person who will review and give directional feedback on the output, and explicit permission to ask questions without it reflecting on their competence. The manager's role in this phase shifts from orientation provider to active coach: the new hire shares drafts or progress checkpoints, the manager gives directional feedback before significant effort has been invested in the wrong direction, and the final work product improves through iteration. Avoid the pattern of assigning the project, then only reviewing the final submission — the value of a 60-day contributor stage is the feedback loop, not the output itself.

#13

Identify and address skill or knowledge gaps that emerged during the first 30 days — frame it as coaching, not evaluation.

The first 30 days reliably reveal gaps that weren't visible in the interview process — not because anything was hidden, but because interviews cannot simulate the full complexity of a role in context. Common gap categories: technical tool proficiency (the new hire understands the concept but not this organization's specific implementation), domain knowledge (industry context assumed by colleagues that the new hire doesn't have yet), process familiarity (the way this team does things differs from the new hire's previous experience), and relationship gaps (key collaborators whose work intersects with the role but who haven't been formally introduced). Identifying gaps at 30 days rather than 90 leaves time to address them through targeted training, mentorship pairings, or adjusted scope before the new hire is expected to perform fully independently. The framing matters: a 30-day gap review is a coaching conversation about what support the new hire needs, not a performance warning. At this stage, gaps are an expected output of the learning process, not a cause for concern.

#14

Verify the new hire has the relationships, resources, and role clarity needed for independent performance before reducing active support.

Before tapering check-in frequency and pulling back active support, confirm three foundations are in place. Relationships: the new hire knows who to go to for different types of help, has established working rapport with key collaborators, and has a peer they trust enough to ask informal questions without concern about judgment. Resources: they have access to everything the role requires — tools at the right permission level, documentation, budget authority if relevant, and a clear escalation path when they encounter a blocker they cannot resolve independently. Role clarity: they can articulate what success looks like in their role at six months, understand how their work is evaluated, and know how to prioritize when multiple things compete for attention. A 10-minute structured conversation that explicitly covers these three areas at the 60-day mark surfaces problems that would otherwise show up as underperformance at 90 days — when they're harder to address quickly.

#15

Hold a structured 90-day review with clearly separate sections for performance assessment and onboarding quality feedback.

The 90-day review serves two distinct purposes that are often conflated. The performance section: what has the new hire accomplished relative to the 30-60-90 day goals set at the start? What are the assessed strengths in the role so far? What are the agreed goals and focus areas for the next quarter? This is a forward-looking goal-setting conversation as much as a backward evaluation — the new hire should leave with clear direction about what the next 90 days should produce. The onboarding quality section: how did the new hire experience the onboarding process? What was missing, confusing, poorly timed, or unhelpfully time-consuming? What would have made the first 30 days more effective? This second section is how organizations improve their onboarding systematically over time — the new hire is the most recent user of the process and holds the clearest perspective on where it fell short. BambooHR research found that employees who experienced effective onboarding were 69% more likely to remain with the company for three years; the 90-day conversation is the moment to assess whether that trajectory is on track and what, if anything, still needs to be addressed.

#16

💰 What a failed first 90 days actually costs

SHRM estimates the total cost of replacing a single employee at 50–200% of their annual salary — a figure that accounts for recruiting fees, interviewer time, background checks, lost productivity during the vacancy, the investment sunk into the failed onboarding, and the ramp-up period for the replacement hire. For a $80,000-per-year role, that's a conservative floor of $40,000 and a realistic ceiling above $100,000 when management time is included.

Example: $80,000/yr role — conservative 1.5× replacement multiplier

Recruiting fees and job posting ........ $8,000–$16,000
Interviewer time (6 hrs × 4 people) .... $2,400–$6,000
Sunk onboarding investment .............. $3,000–$8,000
Productivity gap (3–6 month ramp) ...... $20,000–$40,000
Manager coaching and rework time ........ $5,000–$10,000
Total estimated exposure ............. $38,000–$80,000+

These numbers make the business case for structured onboarding straightforward. A manager investing 2 to 3 hours per week in active support over 90 days — roughly 25 hours total — is a rounding error against the cost of restarting the hiring process.

🚨 Warning signs onboarding is failing mid-process

Silence after Week 1 — a new hire who stops asking questions hasn't figured everything out; they've learned it feels risky to ask, which is worse.
Unvarying positive check-ins — "Everything's great" with no specifics is not confidence; it's a signal that the new hire doesn't feel safe raising concerns.
Social withdrawal — skipping optional team events, going quiet in team channels, or not joining informal conversations after initially engaging.
Buddy contact stalls — if the buddy relationship goes cold after Day 2, the new hire almost certainly has unresolved questions with no other avenue for them.
Visible LinkedIn activity — profile updates, new external recruiter connections, or a sudden burst of endorsement exchanges can signal active searching.

✅ Signs onboarding is on track

Specific, contextual questions — "How does the approval process work for X specifically?" signals genuine engagement, not surface compliance.
Proactive stakeholder outreach — the new hire is scheduling introductions on their own initiative, not just when assigned by the manager.
Cultural observations — sharing what they've noticed about how the team operates signals they're integrating mentally, not just physically present.
Constructive pushback — a new hire comfortable enough to respectfully question a process or propose an alternative is genuinely invested.
Buddy relationship is reciprocal — the new hire is contributing value to the buddy, not just receiving — sharing an outside perspective or a skill.

📖 Orientation and onboarding are not the same thing — and confusing them is expensive

Most organizations run an orientation program — forms, a building tour, a welcome lunch, and a stack of compliance modules — and call it onboarding. Orientation is a single event, typically complete by the end of Week 1. Onboarding is a process measured in months. The distinction matters because they answer different questions. Orientation answers logistical questions: where is the kitchen, what is the expense submission process, here is your ID badge. Onboarding answers strategic ones: do I belong here, am I capable of doing this job well, does the reality of this role match what I was told in the interview, and does this organization treat people the way I want to be treated? A new hire can complete orientation flawlessly and still leave at month three because no one answered the strategic questions.

Orientation answers

Where, who, how — logistics and access. Correctly complete by end of Week 1.

Onboarding answers

Why this company, what excellence looks like, how the culture actually operates day-to-day. Takes 90 days minimum.

Belonging is built by

Real relationships, visible contribution, and earned clarity — none of which orientation can manufacture alone.

🏠 What physical co-location provided for free — and what remote onboarding must engineer deliberately

In a traditional office, much of onboarding happened accidentally. A new hire overheard how a senior colleague handled a difficult client call. They absorbed cultural norms by watching who spoke freely in all-hands meetings and who deferred. They were introduced to adjacent teams by walking past their desks. Remote and hybrid onboarding produces consistently weaker outcomes when it digitizes the in-person checklist without replacing these accidental learning mechanisms with deliberate equivalents.

⚠️

The invisibility problem

A remote new hire can go effectively invisible for 48 hours without anyone noticing. Build in mandatory touchpoints for the first two weeks — not optional drop-ins that a new hire may feel awkward initiating. The burden of outreach should fall on the team, not on the person who is least familiar with the norms.

⚠️

Video call fatigue on Day 1

A remote Day 1 designed as eight hours of back-to-back video introductions is more exhausting than a physical equivalent and creates a worse first impression. Cap structured video calls at four to five hours and build in unstructured setup time. A Day 1 that ends with an overwhelmed, drained new hire is a net negative against the goal of making them feel welcomed.

💡

Replace ambient culture transmission deliberately

Record and share 2 to 3 short informal videos of senior team members talking about how the team operates, what they wish they'd known in their first month, and what doing this job well actually looks like from the inside. These 5-to-10-minute videos replace some of the overheard-conversation learning that physical presence provides for free, and cost almost nothing to produce.

🔍 When 90-day patterns reveal a hiring problem, not an onboarding problem

Not every onboarding gap is an onboarding failure. When multiple consecutive hires in the same role struggle with the same issue at 90 days — consistently underestimating the technical complexity required, repeatedly misreading stakeholder communication norms, or arriving with skills that don't match what the role demands in practice — the root cause is often upstream in the hiring process: a job description that understates requirements, interview questions that don't screen for the relevant competency, or hiring manager presentations of the role that set expectations the reality cannot match.

Track 90-day review themes across hires in the same role. If the same gap appears across three or more consecutive hires, treat it as a diagnostic signal to review the hiring process, not as a reflection on the individuals. The onboarding process can compensate for minor expectation mismatches. It cannot consistently close a structural gap between what the role requires and what the hiring funnel selects for.

Master This Checklist Quickly

Every important button and option for this pre-made checklist, shown in a glance-friendly format.

Start Here

1
Click any item row to mark it complete.
2
Use the note row under each item for quick notes.
3
Use the tool row for undo, redo, reset, and check all.
4
Use Save Progress when you want to continue later.

Checklist Row Tools

UndoRedoResetCheck allCollapse/Expand sectionsShow/Hide detailsInline notes

Top Action Buttons

Open all sharing and export options in one menu.

Email DraftContinue on another devicePrint or Save as PDFPlain Text (.txt)Word (.docx)Excel (.xlsx)

Add & Ask

Open one menu for apps and AI guidance.

NotionTodoist CSVChatGPTClaude

Copy and customize

Create a new editable checklist pre-filled with your chosen content.

Save Progress

Adds this checklist to My Checklists and keeps your progress in this browser.

Most Natural Usage

Track over time

Check items -> Add notes where needed -> Save Progress

Send or export

Open Share -> Choose format -> Continue

Make your own version

Copy and customize -> Open create page -> Edit freely

Employee Onboarding

Checklist Items

Pre-Boarding — Between Offer Acceptance and Day 1

Day 1 — Welcome First, Information Later

First 30 Days — Learning Before Contributing

Days 31–60 — Contributing Under Guidance

Days 61–90 — Independent Work and Review