Employee Onboarding Checklist: Employee + Manager Guide
A new hire’s laptop arrives. Slack fills with welcome GIFs. Someone mentions “we’ll figure out the rest as we go.” Three weeks later the tools work, the swag arrived, and the new person still asks permission for decisions peers make in five minutes. That is not a personality problem. It is an onboarding problem.
A useful employee onboarding checklist is dual: what the new hire owns, and what the manager owns. Logistics and relationships matter. The piece that usually goes missing is role clarity, especially decision rights. This guide covers pre-day one through day 90 for new hires, managers, and people ops building a lightweight process.
See also the first 90 days at work and the 30-60-90 day plan template.
The insight most checklists skip
Onboarding fails less from missing swag and more from missing decision rights. New hires who do not know what they can decide alone, what needs a peer, and what needs the manager stay slow even when tools work. Put a one-page decision map in week one. Without it, every small choice becomes a status check, and “ramping” turns into dependency.
Before day one
Work done before Monday is the difference between a calm first morning and a scavenger hunt.
Employee pre-day-one checklist
- [ ] Confirm start time, location or remote setup, and dress or camera norms
- [ ] Complete paperwork on the timeline HR gives you
- [ ] Test laptop, MFA, VPN, email, and chat if IT ships gear early
- [ ] Save HR, IT, and manager contacts for day-one blockers
- [ ] Ask your manager for the week-one schedule and who you will meet
- [ ] Skim any handbook or benefits link you were sent
Manager pre-day-one checklist
- [ ] Request accounts, licenses, badge or building access, and hardware with IT (build in lag time)
- [ ] Assign a buddy and brief them on what “helpful” means this week
- [ ] Draft a first-week agenda: setup, intros, shadow time, and short 1:1s
- [ ] Send warm intros to people the hire must meet in week one
- [ ] Prepare a role one-pager: mission of the seat, top outcomes, and how success will be reviewed
- [ ] Clear calendar space; onboarding is not a hallway chat
- [ ] Confirm with HR what training is due in week one vs later
HR vs hiring manager: HR usually owns offer paperwork, benefits windows, policy access, and required training. The hiring manager owns role clarity, team intros, work priorities, and the quality of the first 90 days. People ops can build the template; the manager still runs the relationship.
First-week checklists
Employee first-week checklist
- [ ] Get core tools working; escalate blocked access by day two
- [ ] Confirm with your manager: top priorities for two weeks, update style, and what not to touch
- [ ] Meet your buddy, closest teammates, and one or two handoff partners
- [ ] Capture how work enters, moves, and finishes on this team
- [ ] Ask for the decision map (or draft one and ask your manager to correct it)
- [ ] Ship one small, low-risk proof of reliability
- [ ] End the week with a written recap: what you learned, open questions, next week plan
Useful prompts live in questions to ask in your first week.
Manager first-week checklist
- [ ] Meet on day one to set expectations, not only to say welcome
- [ ] Walk the decision map out loud: alone / peer / manager / escalate
- [ ] Make intros happen; do not make the hire cold-message strangers
- [ ] Protect focus time for setup and learning
- [ ] Point to “source of truth” docs and name which ones are outdated
- [ ] Schedule week-two and week-four feedback on the calendar now
- [ ] Check IT and HR blockers until the basics work
Sample first-week agenda
| Day | Employee focus | Manager focus |
|---|---|---|
| Mon | Setup, HR/IT, team hello, expectations 1:1 | Expectations, people list, decision map draft |
| Tue | Shadow a core workflow; jargon notes | Unblock access; buddy check-in |
| Wed | Peer intros; one small helpful task | Warm intros to adjacent partners |
| Thu | Cross-functional partner; how-work-works notes | Confirm 30/60/90 draft direction |
| Fri | Written week recap with manager | Feedback on pace, clarity, next week |
Adjust for role and company size. The shape matters more than the exact grid.
Role expectations and the decision map
By the end of week one, write down what the role exists to deliver, what “on track” looks like at day 30/60/90, how work will be reviewed, and decision rights for common choices. A job description describes hiring hopes. Onboarding docs describe how this team works now.
Decision map one-pager (example fields)
| Decision type | Decide alone | Check a peer | Ask manager | Escalate further |
|---|---|---|---|---|
| Day-to-day task order inside agreed priorities | Yes | If conflicting asks | If clash persists | Rare |
| External customer or exec commitment | No | Draft language | Yes before sending | Per policy |
| Tool or process change affecting others | No | Socialize draft | Approve | If cross-team |
| Spend / discount / policy exception | No | n/a | Yes | Finance/HR as required |
Fill the cells for your team. The point is shared language, not a legal matrix.
30 / 60 / 90 goals that stay realistic
Co-create goals. The employee drafts. The manager edits for constraints and priority. Prefer outcomes you can show, not soft adjectives.
Day 30: a clear map. Explain the team’s purpose, customers, workflow, and what “good” means in your lane. Finish small reliable work. Retire “attend everything to learn” as a default.
Day 60: scoped contributions inside the existing system. Two or three finished pieces with clear done criteria beat ten half-owned threads.
Day 90: one owned outcome with a success measure and evidence. Ownership means a finish line, not “I was generally helpful.”
For fillable tables and stop-doing lists, use the 30-60-90 day plan template. Do not invent fake-precise metrics you cannot measure yet.
Who to meet in the first month
Build a meeting map, not a random coffee tour.
| Circle | Who | Why |
|---|---|---|
| Core | Manager, buddy, closest teammates | Daily work and norms |
| Adjacent | People you hand work to or from | Handoff pain and expectations |
| Context | Skip-level or key stakeholders | Goals and constraints from above |
| Support | HR / people ops, IT, ops partners | How to get help fast |
| Customers | Internal or external users when relevant | What “done well” feels like |
Aim for breadth early and depth later. Short 20–30 minute intros beat marathon coffees. Warm intros are part of the manager onboarding checklist, not a favor.
Remote and hybrid changes
Remote onboarding needs more structure, not a new philosophy: over-communicate the week-one calendar; use shorter, frequent check-ins early, then taper; document walkthroughs; create social hooks on purpose; ship equipment early enough to test before day one; write response-time and decision-logging norms. For hybrid, say which days matter in person for learning, not only for optics.
Feedback loops in weeks 2, 4, and 8
Do not wait for a formal 90-day review that may not exist.
Week 2: Are tools fine? Is the decision map usable? Is the hire stuck on unspoken norms?
Week 4 (around day 30): Does the work map match reality? What learning can retire? What should the hire stop attending? What contribution targets fit days 31–60?
Week 8 (into day 60): Which contributions landed? Is the day-90 ownership scope right? Where is the hire still acting like an observer?
Keep feedback specific and pair it with a living 30/60/90 doc. See how to run a 1:1.
Team norms and manager failure modes
Cover norms early: mandatory vs optional meetings; where decisions get written; what “urgent” means; how disagreement works; which channels carry commitments. A 30-minute “how we work” talk in week one beats weeks of guessing.
Common manager failure modes: vanishing after day one and assuming HR “handles it”; intros without priorities or decision rights; day-90 standards on day 12; no warm intros; weekly priority whiplash; feedback only after something breaks; treating remote hires as self-serve. If several new hires stall the same way, fix the system.
When is someone “ramped”?
“Ramped” is a shared judgment, not a calendar date. Decide together using signals like: core work without constant manager translation; decision rights used correctly most of the time; tradeoffs explained with a recommendation when escalating; owned outcomes with evidence; peers treating the person as a reliable handoff partner.
Hold a short day-90 talk on ownership evidence, what continues next quarter, and what support is still needed. Training modules alone do not equal ramp.
Lightweight ownership (HR + manager + hire)
| Area | HR / People Ops | Hiring manager | New hire |
|---|---|---|---|
| Paperwork, benefits, required training | Owns | Points hire to HR | Completes on time |
| Equipment and accounts | Partners with IT | Requests early; escalates | Reports blockers fast |
| Role clarity and decision map | May provide template | Owns content | Drafts questions and updates |
| First-month meeting map | Optional help | Owns intros and priorities | Shows up prepared |
| 30/60/90 goals | May offer framework | Co-creates and course-corrects | Drafts and gathers evidence |
| Culture and norms | Company-level | Team-level | Asks and adapts |
A shared checklist beats a portal nobody opens.
Start this week
Manager: block time before day one for access, intros, the role one-pager, and the decision map. Calendar week 2, 4, and 8 feedback before Monday.
Employee: bring week-one questions and ask for the decision map by Friday. Write a short Friday recap for the first month.
People ops: publish dual checklists, a blank decision map, and a 30/60/90 stub, then coach managers to use them.
Onboarding is not a welcome week. It is how a company transfers the ability to decide and deliver. Write the decision rights early, and the rest of the checklist has somewhere to land.
FAQ
What should a new employee first week checklist prioritize if everything feels urgent?
Access, manager expectations, a small reliable task, and the decision map. Meetings without those four create motion without ramp.
How is a manager onboarding checklist different from the employee list?
Managers own the environment: access requests, warm intros, priority clarity, decision rights, and feedback cadence. Employees own learning capture, questions, and early delivery evidence.
Do we need a formal onboarding agenda template for every role?
A simple week-one grid is enough for most teams. Specialize for high-risk or regulated roles; do not invent heavy process for a small team.
How does a remote onboarding checklist differ?
Same outcomes, more written structure: earlier equipment testing, shorter frequent check-ins, documented walkthroughs, and explicit chat norms.
When should HR step back and let the manager lead?
After logistics and required training are on track. Role clarity, work quality, and team norms stay with the manager for the full ramp.