30 60 90 Day Plan New Hire Kit: Template and Sample
10 min read ยท 2026-11-21
A 30 60 90 day plan new hire kit is the set of documents a manager or HR hands a new employee on day one. It has six parts: a one-page 30-60-90 plan, a pre-start checklist, a stakeholder map, a weekly 1:1 agenda, a mentor brief and a 90-day review script. The plan sets the goals. The other five documents make sure someone checks those goals every week, so the plan doesn't sit forgotten in a shared folder.
This guide is for the person who builds the kit: a hiring manager, an HR partner or a team lead. Every document below is ready to copy, with an IT systems administrator as the worked example. The plan itself stays short here. This guide is about the documents around it. Build the kit in the week before the start date, then run it for 90 days.
The roadmap at a glance
Goal: Build a complete new hire kit before day one and use it to run check-ins and the final review across the first 90 days. Duration: About 14 weeks (1 week of kit building, then 90 days of use)
Write the plan summary (2 days, the week before day 1)
Set 2 or 3 goals per phase, each with a measure someone else can check.
- Write one learning goal, one delivery goal and one ownership goal.
- Add a measure and a target date to each goal.
- Keep the whole plan on one page.
Milestone: The plan summary fits on one page and every goal has a measure.
Build the support documents (2 days)
Prepare the checklist, the stakeholder map, the mentor brief and the review script.
- Fill the pre-start checklist and assign an owner to each item.
- List 6 to 10 stakeholders with the first question to ask each one.
- Pick a mentor from outside the reporting line and send the brief.
- Adapt the review script to this role's goals.
Milestone: All six documents are finished and stored in one place.
Send the kit and book the calendar (1 day)
Make sure every meeting already exists before the new hire arrives.
- Book weekly 1:1s for the first 30 days, then every two weeks.
- Book the day 30, 60 and 90 reviews in both calendars.
- Book the first stakeholder meetings for week one.
- Test every login on a short call the day before the start.
Milestone: The new hire starts with the kit in hand and every review already in their calendar.
Run the check-ins (Days 1 to 90)
Use the same 1:1 agenda every week and update the plan as you go.
- Run the 1:1 agenda without changing its order.
- Write changes into the plan on the same day.
- Check in with the mentor once a month.
Milestone: The day 30 and day 60 reviews happen on their booked dates and the plan shows only one current version.
Close with the review script (Day 90, plus 1 week)
End onboarding and turn the plan into regular performance goals.
- Run the 90-day review script.
- Move next-quarter goals into the normal review cycle.
- Update the kit template with the new hire's feedback.
Milestone: Goals move into the regular review cycle and the template is ready for the next hire.
What goes in a 30 60 90 day plan new hire kit
Most templates stop at three columns of goals. In practice, plans fail because nothing brings anyone back to them. Each document in the kit keeps the plan alive in a different way.
- The plan summary: 2 or 3 goals per phase, each with a measure and a date.
- Pre-start checklist: access, equipment, the first-week agenda and the day 1 contacts.
- Stakeholder map: who matters to this job and what to ask them first.
- 1:1 agenda: the same five items every week, so check-ins stay short.
- Mentor brief: a few lines that tell the mentor what to cover and how often.
- 90-day review script: fixed questions, so the review compares results to the plan instead of drifting into general impressions.
Document 1: the plan summary
Keep it to three lines, one per phase: learn (days 1 to 30), contribute (days 31 to 60) and own (days 61 to 90). Make every goal SMART: specific, measurable, achievable, relevant and time-bound. The test is simple: could someone other than the new hire confirm the goal was met? "Understand the infrastructure" fails that test. "A written map of critical systems, reviewed by the manager" passes it.
If you need the full phase-by-phase layout with fields to fill in, use a standard 30-60-90 day plan template. The kit only needs the short version, because the other five documents do the follow-up.
30 60 90 day plan new hire kit sample: IT systems administrator
Here is the plan summary filled in for a systems administrator joining a mid-size IT team.
The documents below use the same role.
- Days 1 to 30, learn: get admin access to the identity system, the ticketing tool and the backup console, and shadow the on-call engineer for one week. Measure: a written map of critical systems, with the owner and backup schedule for each, reviewed by the manager.
- Days 31 to 60, contribute: handle one ticket queue alone and document one restore procedure that only one person knew. Measure: two weeks on the queue with no escalation on routine tickets, and the restore document tested once.
- Days 61 to 90, own: take a primary on-call shift and lead one small change, such as a patching schedule for a group of servers. Measure: the change finished on its planned date and a risk list agreed with the manager.
Document 2: the pre-start checklist
Give each line an owner (manager, HR or IT) and tick it before day one. The list is grouped into access, equipment, the first-week agenda, the day 1 contacts and admin.
- Access: email, single sign-on and chat accounts created and tested.
- Access: password manager or vault access set up.
- Access: VPN or remote access working from the new hire's location.
- Access: role tools opened. For the IT example: ticketing tool, identity admin console, backup console, monitoring dashboard.
- Access: HR system login for payroll, benefits and leave.
- Equipment: laptop configured with the standard image and the role's software.
- Equipment: charger, monitor, headset and keyboard ready, or shipped to arrive before day one.
- Equipment: badge or building access ready.
- Equipment: phone or authenticator app set up if on-call duties need it.
- First-week agenda, day 1 morning: welcome with the manager, walk through the kit, check every login.
- First-week agenda, day 1 afternoon: team introduction, read the plan summary and the stakeholder map.
- First-week agenda, days 2 and 3: first stakeholder meetings, required compliance and tool training.
- First-week agenda, day 4: shadowing session on the core process (on-call or ticket triage in the IT example).
- First-week agenda, day 5: first weekly 1:1, using the agenda below.
- Day 1 contact: the manager, for the welcome and the plan walkthrough.
- Day 1 contact: the mentor, for lunch or an informal coffee.
- Day 1 contact: a teammate in the same or a close role, for the practical "how we do things" talk.
- Day 1 contact: the colleague they will work with most in month one. For the IT example, that's the on-call engineer they will shadow.
- Admin: start time, address or video link sent to the new hire.
- Admin: signed paperwork received.
- Admin: every 1:1 and review booked in both calendars.
Document 3: the stakeholder map
Use one row per person, with six columns: name, role, why they matter to this job, what they need from this role, first question to ask and meeting date.
Below are two example rows for the systems administrator. Add the business application owners, the infrastructure manager and the on-call engineer to reach 6 to 10 rows.
- Service desk lead. Why they matter: sends escalated tickets to the systems team. What they need: clear handoff notes and fast replies on escalations. First question: "Which escalations do you see most often, and which ones keep coming back?" Meeting: week 1.
- Security lead. Why they matter: approves admin rights and owns incident response. What they need: changes logged and patches applied on time. First question: "Which open findings from the last audit touch the systems I'll manage?" Meeting: week 1.
Document 4: the weekly 1:1 agenda
Use the same agenda every time.
Meet weekly for the first 30 days. Once the new hire is doing real work, every two weeks is usually enough.
- Progress on this phase's goals, one line each.
- What is blocking you, and who can unblock it.
- Who you met this week and what you learned.
- One piece of feedback in each direction.
- Any change to the plan, written into the plan the same day.
Document 5: the mentor brief
Send this to the mentor during the prep week:
"Thanks for agreeing to mentor our new systems administrator for their first 90 days. Please meet for 30 minutes every week until day 30, then every two weeks. Focus on what the plan and I can't cover: how decisions really get made here, who to ask about what, and the team's unwritten rules. What you discuss stays between you two, but if you see a blocker they can't clear alone, let me know that same week."
Document 6: the 90-day review script
Send the questions a few days ahead, so the new hire brings evidence. Run the review from the plan, not from memory.
Opening (manager reads): "Today we close your onboarding. We'll go through the plan goal by goal, then set your goals for next quarter."
Close (manager reads): "These goals now move into your regular reviews. Your answer on what would have made it easier goes into the kit for the next hire."
- Which goals were met, and what is the proof for each?
- Which goals were missed or changed, and why?
- What do you own fully today that you didn't own on day one?
- What should we stop, start or keep doing as a team?
- What would have made your first 90 days easier?
- What are your three goals for the next quarter?
How to adapt the kit by role
The six documents stay the same for every hire. Only the goals and the stakeholder list change.
For a new manager, swap the shadowing week for 1:1s with every direct report and peer, and make the ownership goal about team decisions. A dedicated manager onboarding guide covers that case in full.
- Product manager: stakeholders are customers, support and engineering leads. Ownership goal: present a quarterly roadmap.
- Project manager or PMO: stakeholders are sponsors and project leads. Ownership goal: lead a steering meeting.
- Consultant: stakeholders are the client's decision makers. Ownership goal: run a client meeting alone.
- Marketing: stakeholders are sales and the channel owners. Ownership goal: own a channel and its monthly report.
- Data: stakeholders are the owners of the main dashboards. Ownership goal: own a recurring report.
- HR: stakeholders are hiring managers and payroll. Ownership goal: own a program.
Remote and hybrid new hires
Remote hires miss everything that happens by chance in an office. The kit has to plan those moments on purpose. Ship equipment so it arrives before day one, and test logins on a call the day before.
Add three lines to the checklist for remote hires: video introductions booked with every stakeholder, a named "first question" contact for the first two weeks, and written rules on which channel to use for urgent and for routine questions. For hybrid teams, put the in-office days on the dates of the most important stakeholder meetings.
Common mistakes to avoid
- Writing goals that can't be checked, such as "learn the business", instead of "list the top five customers and their main issue".
- Handing over the kit with no meetings booked. Book every check-in and review during the prep week.
- Leaving the checklist without owners, so access requests wait until day one.
- Loading days 1 to 30 with deliverables. Keep month one to one small output at most.
- Keeping several versions of the plan. Update the same document at each 1:1.
- Treating day 90 as a formality instead of a scripted review that sets next quarter's goals.
Frequently asked questions
Who should write the 30-60-90 day plan, the manager or the new hire?
The manager or HR writes the first draft as part of the kit, because the new hire doesn't know the role yet. The new hire then revises it at the day 30 review, once they have met the stakeholders. Sharing ownership after month one keeps the plan current.
What are the phases of a 30 60 90 day plan for a new hire?
There are three: learn (days 1 to 30), contribute (days 31 to 60) and own (days 61 to 90). First the new hire understands the role and the people around it. Then they find where they can help and deliver a first piece of work. Then they take charge of part of the job. The kit adds a prep week before day one.
What should be on a new hire checklist before day one?
Working access to every account and tool, equipment delivered and tested, a first-week agenda, the day 1 contacts and every 1:1 and review booked. Give each item an owner, so nothing waits until the new hire arrives.
Can a 30-60-90 day plan be used for an internal promotion?
Yes. The kit works the same way, but the learning phase is shorter because the person already knows the company. Put more weight on new stakeholders, handing over the old role and the decisions that come with the new scope.