How_to_use_this_template

📖 How to use this template

A 30-60-90 day plan is a written agreement about what a new hire will learn, contribute and own in their first three months. It exists so that "how's the new person doing?" has an answer other than a shrug. This one is filled in with a realistic sample plan.

  1. Duplicate this project into your own organization (dropdown next to the project name, then Duplicate)
  2. Shift the dates. The sample runs 22 Feb - 28 May 2027 so nothing shows as overdue. Select all tasks in List view, then drag the date range to your hire's actual start date. Pre-boarding sits in the week before day 1
  3. Reset the statuses. The sample is staged mid-March, so pre-boarding is Completed and a few month-1 tasks are In progress. Select all, then set status to To-do so you start clean
  4. Swap the assignees for your own people. The sample names map to roles, listed below
  5. Delete what does not apply. A 40-task plan nobody follows is worse than a 15-task plan they do. Cut hard

Who the sample names are

Sample name Role in the plan
Sammy Walter The new hire
Katherine Newman Hiring manager
Pak Youngjae Team or tech lead
Jamie Burke Onboarding buddy
Darrell Finley People Ops / HR
Elian Glace IT and workplace ops
Felipe Cross-functional partner

The three phases

Days 1-30 — Learn. Month 1 is for listening. The new hire meets people, learns the product as a customer would, watches how the team actually works, and ships one deliberately small thing. Two real deliverables: the small shipped thing, and a 30-60-90 plan they wrote themselves.

Days 31-60 — Contribute. The handover from being taught to delivering. One end-to-end project scoped to finish inside the month. One recurring responsibility taken over. First reviews of other people's work.

Days 61-90 — Own. Independent ownership, measurable results, and goals set for the next two quarters. By day 90 the plan stops being an onboarding plan and becomes a normal performance plan.

There are two extra sections. Pre-boarding is the week before day 1 — skip it and day 1 gets spent on IT tickets. Reference has no due dates on purpose; it is what people come back to in month 6.


The four milestones

Milestone What it decides
Day 7 Do they have what they need? Cheapest place to catch a bad start.
Day 30 Are they learning at the pace we expected, and what is in the way?
Day 60 Delivering with support, or still being taught? Is the day-90 scorecard still right?
Day 90 Fully ramped, yes or no? Written down.

Write the day-30 and day-60 reviews down. A verbal "yeah, going well" is how a struggling hire reaches day 85 before anyone acts.


The columns in Table view

Switch to Table view to see everything side by side.

Field What it is for
Phase Pre-boarding / 1-30 / 31-60 / 61-90 / Ongoing. Group by this to see one month at a time.
Focus Area Admin, People, Product, Process, Delivery, Feedback. Group by this to spot an unbalanced plan.
Progress On track / At risk / Off track. The manager's read, separate from task status.
Primary Contact Who the new hire asks when stuck. Not the same as the assignee.
Success Metric How you will know it is done properly, not just ticked.
Est. Effort (hrs) Sanity-check the total. If month 1 needs 90 hours of onboarding on top of a full workload, the plan is fiction.
Milestone Checkbox for the four review gates.

Statuses: To-do, In progress, Needs review, Blocked, Completed. Blocked is the useful one — see "Get to know the customer", which is waiting on CRM access. Blocked tasks are how a manager finds out about a stuck hire without asking.

Tags: Must do, Stretch, Recurring, Quick win, Manager action, Shadowing. Filter by Must do in week 1 to strip the plan down to essentials.


The three sublists

Sublists cut across the phase sections, so the same task can appear in more than one.

  • New Hire Checklist — everything the new hire personally owns, all three months in one list. Their home view.
  • Manager and People Ops — the manager, buddy, IT and HR tasks. Use it for the pre-boarding handoff.
  • Milestones and Check-ins — the four review gates plus the weekly 1:1s.

Getting this wrong

A few failure modes worth naming, because they are common:

The manager writes the plan alone. A plan the new hire did not write is a plan they will not follow. Draft the outline, then have them rewrite it in week 3 — that is what "Write your own 30-60-90 plan" is for.

Month 1 is packed with delivery. If someone is shipping real features in week 2, either you hired an internal transfer or you skipped the learning. Both are worth knowing.

Vague success criteria. "Understand the product" is not measurable. "Can demo the 3 core user journeys unaided" is. Every Success Metric here is written to be checkable by someone else.

Nobody owns pre-boarding. It falls between recruiting, IT and the manager, so it falls through. Assign every pre-boarding task to a named person before the offer is signed.

The day-90 goalposts move. Write the scorecard in pre-boarding, then score against it. Inventing new criteria at day 88 is how a fine hire gets a bad review.


Adapting it

Remote hire? Add explicit time zone overlap hours, and double the number of intro 1:1s — the hallway conversations that happen automatically in an office do not happen at all remotely.

Senior or leadership hire? Push everything one phase earlier and add a "listening tour" in month 1: 15-20 conversations across the org, then a written read-out of what they heard in month 2.

Internal transfer? Cut pre-boarding and most of month 1. Keep the relationship-building and the domain learning. They know the company; they do not know this team.

Short ramp needed? Compress to 15-30-45 rather than deleting phases. The sequence — learn, contribute, own — is what makes it work. The month boundaries are arbitrary.


Sample dates run to May 2027 so this template never shows overdue tasks. Reset them to your own start date in step 2.


Project: 30-60-90 Day Plan