30 60 90 Day Onboarding Plan for Managers: Checklist and Example

The pre-boarding checklist for hiring managers

Pre-boarding is the part the manager controls most. Run through this list one to two weeks before the start date.

If any line is still open three days before the start, move that task to the first morning and tell the new hire in the welcome note. Telling them up front is better than letting them find the problem on their own.

• Equipment and access: laptop, phone or other hardware ordered and shipped, with a delivery date before Day 1.
• Equipment and access: email, chat, calendar and every role-specific system requested.
• Equipment and access: permissions checked, with read and edit rights where the job needs them.
• Equipment and access: a test login planned for Day 1 morning, or the day before for remote hires.
• People: buddy chosen, briefed and given time in their own calendar.
• People: team told about the start date, the role and what the new hire will own.
• People: introduction meetings booked for the first two weeks.
• HR and company steps: paperwork, contract and payroll details completed with HR.
• HR and company steps: required training and policy reading listed, with due dates.
• HR and company steps: any legal or compliance steps for the role confirmed with HR.
• The plan itself: Day 90 success statement written.
• The plan itself: three priorities drafted for each phase.
• The plan itself: three review dates booked.
• The plan itself: draft sent to the new hire with a note that it is theirs to edit.

What the manager owes the new hire in each phase

A 30 60 90 day plan often lists the hire's goals only. When the plan fails, it is often because the manager's side was never written down. Add a short "manager commitments" line under each phase.

Days 1 to 30. You commit to the introductions, the weekly 1:1 and the context. A new hire can learn tools alone. They cannot find out alone why a project was stopped last year or which stakeholder expects updates on a Friday.

Days 31 to 60. You commit to handing over real work and to fast feedback. If you hold on to the tasks, the hire stays in learning mode and the Day 60 review has nothing to judge.

Days 61 to 90. You commit to letting go. Name the area, tell the team, and stop approving each step. Ownership that only exists in the plan, while you still sign off on everything, does not count.

Writing these commitments down also makes reviews fair. If a goal was missed because access arrived in week five, the plan shows it.

Worked example: an IT support specialist's first 90 days

Here is the plan filled in for a new IT support specialist joining an internal help desk of four people. Change the systems and names to match your team, and keep the structure.

Day 90 success statement: the specialist resolves one ticket category alone, owns the maintenance of the meeting room equipment, and has updated the knowledge base articles for their category.

For other roles, each phase keeps the same shape: learn by shadowing, take one area with checks, then own it without checks. A new account manager might go from shadowing calls, to a small set of accounts, to a full portfolio. A new operations hire might go from mapping a process, to running it with approval, to running it alone.

• Pre-boarding, manager tasks: admin rights for the ticketing system and device management tool requested and tested. Buddy: the most senior help desk technician, with 30 minutes a day in week one. Shadowing slots booked with each of the three colleagues.
• Days 1 to 30, specialist goals: shadow tickets with each colleague for at least two half days, learn the ticket categories, priorities and escalation rules, and resolve simple password and access tickets with the buddy reviewing. Day 30 deliverable: a list of the five most common ticket types and the gaps they found in the knowledge base.
• Days 1 to 30, manager commitments: introduce the specialist to the facilities lead and the security contact, and explain which incidents in the last year changed how the team works.
• Days 31 to 60, specialist goals: take all tickets in one category, such as hardware requests, with spot checks, and rewrite the knowledge base articles for that category. Day 60 deliverable: the category handled for four weeks with only rare reassignment.
• Days 31 to 60, manager commitments: review a sample of closed tickets each week and give feedback the same week, and approve the knowledge base changes quickly so they go live.
• Days 61 to 90, specialist goals: own the category with no spot checks, take over meeting room equipment maintenance, including the monthly check, and track two metrics the team already uses, such as time to first response and reopened tickets. Day 90 deliverable: a one-page report on the category and a proposal for the next quarter.
• Days 61 to 90, manager commitments: announce the ownership change to the team and to frequent requesters, then stop the weekly ticket sampling and move to the monthly team review.

How to spot a slow start before Day 30

The Day 30 review is the first formal checkpoint, but you can usually see trouble earlier. Watch for these signs in the weekly 1:1.

For each sign, fix the setup first. Chase the access, book the missing meeting, free up the buddy's time. If the plan itself is too heavy, cut the phase goals to the three that matter most and keep the review date.

• The same blocker appears two weeks in a row, often an access or a missing contact.
• The new hire asks no questions, which usually means they do not know who to ask.
• Introductions keep getting moved by the other side.
• The buddy has not met them that week.

Questions for the Day 30, 60 and 90 reviews

Use the same 45 to 60 minute structure each time: the hire presents the phase milestone, you go through each goal together, you share feedback from the buddy and colleagues, then you both adjust the next phase.

Also ask the last question to yourself. Each new hire shows you which items on your pre-boarding checklist were missing.

• Day 30: What is still unclear? Who have you not met yet? What did I forget to tell you?
• Day 60: Which task takes longer than it should? Where do you need fewer approvals from me?
• Day 90: What do you want to own next quarter? What should we change in pre-boarding for the next hire?