30-60-90 Day Plan Template Permalink

Use this template to run a new hire’s first three months in Quire: set the phases up before day 1, track every task against a checkable success metric in Table view, and hold the review gates at day 7, 30, 60 and 90.

You can visit the 30-60-90 Day Plan project and duplicate it to your workspace, so you don’t need to build everything from scratch.

You can also explore more ready-to-use templates to speed up your workflow.

Understand 30-60-90 Day Plans

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 the question everyone asks quietly around week six, how is the new person doing, has an answer other than a shrug.

What makes it work is the sequence rather than the calendar. Month one is for learning, month two for contributing with support, month three for owning work outright. The month boundaries themselves are arbitrary, which is why a shorter ramp should be compressed into 15-30-45 days rather than have a phase deleted from it.

The plan is laid out as five sections.

Three of them are the phases themselves. Pre-boarding covers the week before day 1, and Reference holds the material people come back to in month six, which is why it deliberately carries no due dates. In the screenshot above, Pre-boarding shows a count of zero because the sample plan is staged mid-March and those tasks are already completed.

Set Up the Template

The template arrives filled in with a worked sample rather than empty, so the setup work is adaptation rather than authoring.

1. Duplicate the project so you are working in your own copy.
2. Shift the dates. The sample runs 22 February to 28 May 2027 so that nothing ever shows as overdue. Move the whole range onto your hire’s real start date, with pre-boarding landing in the week before day 1.
3. Reset the statuses to To-do. The sample is staged mid-March, so pre-boarding reads as Completed and a few month-one tasks are already In progress.
4. Swap the assignees for your own people.
5. Delete what does not apply to this role.

The sample names map to onboarding roles, so you know who to substitute where.

Step five is the one people skip. A 40-task plan nobody follows is worse than a 15-task plan they do, because the long version leaves everyone with the comfortable impression that onboarding is handled.

The full setup walkthrough ships as a document inside the project.

A second document holds review scripts and 1:1 questions, so the manager running a day-30 review does not have to invent the agenda on the morning of the meeting.

Read the Plan in Table View

Table view is only available in the Professional, Premium, Enterprise plans. More information can be found on our pricing page.

Table view is where the plan is easiest to read, because it puts every custom field beside the task instead of hiding them one panel away.

Seven fields carry the plan.

Progress and status look redundant until the first time they disagree. Status is what the task is doing; Progress is what the manager thinks about it. A task can sit In progress and be Off track at the same time, and that combination is exactly the one worth surfacing early.

Five statuses run the workflow: To-do, In progress, Needs review, Blocked and Completed. Blocked is the one that earns its place. In the sample plan, Get to know the customer is blocked waiting on CRM access, which is how a manager finds out about a stuck new hire without having to ask.

Six tags cut across all of it: Must do, Stretch, Recurring, Quick win, Manager action and Shadowing.

Tip: Filter by Must do in week one. It strips a plan of 70-odd tasks down to the handful that actually cannot slip, which is a far less frightening thing to hand someone on their second day.

Work Through the Phases

Pre-boarding

The week before day 1: run the offer-to-onboarding handoff, provision accounts and hardware, draft the role scorecard, assign a buddy and pre-book week one, and set up the desk and the welcome.

Note: Pre-boarding is the phase that reliably falls through, because it sits between recruiting, IT and the hiring manager and therefore belongs to nobody. Assign every pre-boarding task to a named person before the offer is signed.

Days 1–30: Learn

Month one is for listening. The new hire books a 1:1 with everyone they will work with, learns the product the way a customer meets it, watches how the team actually operates as opposed to how the process document says it does, and gets to know the customer through recorded calls and support tickets.

Two things in month one are real deliverables rather than learning. The first is one deliberately small shipped thing, and the second is the plan itself, rewritten by the new hire and signed off by the manager.

Every task follows the same shape. A description says what the task is actually for, the custom fields carry the phase and the success metric, and subtasks break it into the steps someone can tick off. Ship your first small thing is a good example: the description explains that the point is to run the whole pipeline once rather than to impress anyone, and its three subtasks are picking the work with the lead, getting it reviewed and shipped, and writing a note on what surprised them.

Days 31–60: Contribute

Month two is the handover from being taught to delivering. One end-to-end project scoped to finish inside the month, one recurring responsibility taken over from its previous owner, and the first reviews of other people’s work.

It is also the right month to fix something the new hire found broken in their own onboarding, while they can still remember what was confusing. That task is tagged both Quick win and Stretch, and it is the one that keeps the template from going stale.

Days 61–90: Own

Month three is independent ownership: running a workstream without hand-holding, becoming the person teammates route a particular kind of question to, proving the impact with before-and-after numbers, and setting goals for the next two quarters.

The measure of success for this phase is not a deliverable. It is that the manager hears about problems from the new hire first, every time.

Timeline view is only available in the Professional, Premium, Enterprise plans. More information can be found on our pricing page.

Timeline view shows the phases stepping forward, which makes an overloaded month visible at a glance.

If two phase bars overlap heavily, the plan is asking someone to learn and deliver at the same time, which is usually a sign that month one was skipped rather than compressed.

Track the Four Review Gates

Four milestones sit in the plan at day 7, day 30, day 60 and day 90. They are the review gates, and each one decides something different.

Alongside the gates sits a recurring task for weekly 1:1s through month one, tagged Recurring, with a success metric of zero canceled 1:1s in the first 90 days. That metric looks trivial and is not. A canceled 1:1 in week three is the most common first symptom of an onboarding that is drifting.

Note: Write the day-30 and day-60 reviews down. A verbal “yeah, going well” is how a struggling hire reaches day 85 before anyone does anything about it, and it is also how a good hire arrives at day 90 with no evidence behind them.

The day-90 gate is scored against the scorecard written during pre-boarding, and against nothing else. Adding new criteria at day 88 is how a perfectly good hire ends up with a bad review.

Split the Plan by Role

In the Free Subscription plan, you can create two sublists for each project, and this template ships with 3. Keep the two your team opens most after duplicating, or upgrade your subscription plan to use all three. More information can be found on our pricing page.

The phase sections answer “when”. Three sublists answer “who”, cutting across all three months so the same task can appear in more than one place.

• New Hire Checklist is everything the new hire personally owns, all three months in one list. This is their home view.
• Manager and People Ops holds the manager, buddy, IT and HR tasks, which makes it the right thing to hand over during the pre-boarding handoff.
• Milestones and Check-ins holds the four gates plus the weekly 1:1s.

The new hire opens one list and sees their own work without the provisioning tickets and review admin that belong to somebody else.

Because sublists are views rather than copies, a task ticked in the New Hire Checklist is ticked everywhere. Nobody has to reconcile two lists.

Adapt the Plan to the Hire

The template is written for an external hire joining an established team. Four common variations need different handling.

• Remote hire. Set explicit time zone overlap hours and roughly double the intro 1:1s. The hallway conversations that happen by accident 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 one: 15 to 20 conversations across the organization, then a written read-out in month two.
• Internal transfer. Cut pre-boarding and most of month one. Keep the relationship-building and the domain learning, because they know the company and not this team.
• Short ramp. Compress to 15-30-45 rather than deleting a phase. Learn, contribute, own is the part that makes it work.

One failure mode cuts across all four. If someone is shipping real features in week two, either you hired an internal transfer or the learning phase was skipped, and both of those are worth knowing about before the day-60 review rather than after it.

Frequently Asked Questions

What is a 30-60-90 day plan?

A 30-60-90 day plan is a written agreement about what a new hire will learn, contribute and own across their first three months. Month one is for learning, month two for contributing with support, and month three for owning work independently.

What should be in each phase of a 30-60-90 day plan?

Days 1 to 30 cover meeting the team, learning the product and shipping one deliberately small thing. Days 31 to 60 cover one end-to-end project and one recurring responsibility taken over. Days 61 to 90 cover independent ownership, measurable impact and goals for the next two quarters.

Who writes the 30-60-90 day plan?

Both, in sequence. The hiring manager drafts the outline and the day-90 success criteria before the start date, then the new hire rewrites the plan themselves in week three. A plan the new hire did not write is a plan they will not follow.

How long should a 30-60-90 day plan be?

Short enough that the new hire actually reads it. A 40-task plan nobody follows is worse than a 15-task plan they do, and the Est. Effort field exists so you can catch a month one that needs 90 hours on top of a full workload.

What are the review milestones in a 30-60-90 day plan?

Four gates at day 7, day 30, day 60 and day 90. Day 7 catches a bad start cheaply, day 30 checks the learning pace, day 60 asks whether the day-90 scorecard is still right, and day 90 answers whether the person is fully ramped.

What is pre-boarding and why does it matter?

Pre-boarding is the week before day 1: the onboarding handoff, provisioning, the role scorecard, the buddy and the welcome. It matters because it sits between recruiting, IT and the manager, so it belongs to nobody and reliably falls through.

How do you write a good success metric?

Write something a third person could check without asking you. “Understand the product” fails that test. “Can demo the three core user journeys unaided by the end of week three” passes it, because there is a demo or there is not.

How do you adapt a 30-60-90 day plan for a remote or senior hire?

For a remote hire, set explicit time zone overlap hours and double the intro 1:1s. For a senior hire, shift everything one phase earlier and add a listening tour of 15 to 20 conversations in month one, with a written read-out in month two.

Is there a ready-made 30-60-90 day plan template in Quire?

Yes. Visit the 30-60-90 Day Plan project and duplicate it to your workspace to get the five phase sections, seven custom fields, four review-gate milestones, six tags, three role-based sublists and two reference documents already set up.