Work

30-60-90 Day Plan Template

A 30-60-90 day plan splits your first three months into learn, contribute and lead, with goals your manager agrees to and a review at the end of each phase. Copy the template, or start from the example closest to your role.

Updated 2026-10-27

Copy and adapt

The template

30-60-90 day planTemplate

30-60-90 day plan: {{author}}, [Role]

Start date: [YYYY-MM-DD] Manager: [name] Reviews: day 30 [date], day 60 [date], day 90 [date] Related: [[Your name]], [[Team name]]

What success looks like at day 90

[One to three outcomes, written the way your manager would say them]

Days 1 to 30: learn

Focus: [one sentence]

Learning goals

[What you will understand, and how you will show it] @due(YYYY-MM-DD)

People to meet

[Name, role]: [the one question you want answered]

Early win

[One small, visible thing you will ship or fix] @due(YYYY-MM-DD)

Day 30 review

Done:
Not done, and why:
What changed in the plan:

Days 31 to 60: contribute

Focus: [one sentence]

Performance goals

[Measurable outcome] @due(YYYY-MM-DD)

Work I own end to end

[Project or responsibility] @due(YYYY-MM-DD)

Day 60 review

Done:
Not done, and why:
What changed in the plan:

Days 61 to 90: lead

Focus: [one sentence]

Goals

[Outcome] @due(YYYY-MM-DD)

Proposal

[The change you will recommend, based on what you learned] @due(YYYY-MM-DD)

Day 90 review

Done:
Not done, and why:
Goals for the next quarter:

Support I need

[Access, introductions, training, and who provides each]

Open questions for my manager

[Question]

5 examples

Examples for different situations

The same structure, filled in for the situations people actually bring to it. Copy the one closest to yours.

1.Senior engineer joining a payments team

When it fits: Use this when you are an experienced individual contributor in a system that moves money, and the real risk is changing something before you understand why it works the way it does.

Senior engineer joining a payments teamExample 1

2.New manager inheriting a team

When it fits: Use this when you take over a team someone else built, one of your reports wanted your job, and the temptation is to fix the process before you have earned the right to.

New manager inheriting a teamExample 2

3.Interview version for a sales role

When it fits: Use this when the hiring panel asked you to present a 30-60-90 day plan in the final round and you only have the job description and two conversations to build it from.

Interview version for a sales roleExample 3

30-60-90 day plan: Priya Raman, Account Executive (Mid-Market)

Prepared for: final panel, 2026-11-05. Built from the job description and calls with Tom (hiring manager) and Aisha (current AE).

What success looks like at day 90

At 100 percent of monthly quota ($55,000 new ARR), with a pipeline that covers the next month three times over.

Assumptions I made (please correct me)

Ramp quota is 0 percent in month 1, 50 percent in month 2, 100 percent in month 3. Aisha said this is the norm.
Territory is the Southeast mid-market list (about 400 accounts). The job post says mid-market; Tom mentioned two enterprise accounts. I have planned for mid-market only.

Days 1 to 30: learn

Pass product certification and run the standard demo for Tom by day 14
Listen to 20 recorded calls: 10 won, 10 lost, and write down why each was lost
Book 40 discovery calls from the territory list, starting with the 60 accounts that went cold last year
Target: 12 qualified opportunities in the CRM

Days 31 to 60: contribute

Close first two deals, at least $27,500 new ARR (50 percent of quota)
Pipeline of $165,000 for month 3
Shadow Aisha on three negotiations before running my own

Days 61 to 90: lead

Hit $55,000 new ARR for the month
One healthcare customer willing to be a reference, since the job post names healthcare as the growth vertical
Share one written objection-handling note with the team, from what I learned in the lost calls

What I will need

A list of the accounts that churned in 2026 and the reason recorded for each
Thirty minutes with a sales engineer per week in month 1

Questions for the panel

Are the two enterprise accounts Tom mentioned part of this role, or a later step?

4.Operations director with a decision due at day 60

When it fits: Use this when you are hired at director level with one large question already on the table, and the plan has to show how you will answer it rather than how you will settle in.

Operations director with a decision due at day 60Example 4

5.Internal transfer with a plan revised at day 30

When it fits: Use this when you move to a new team inside the same company, your old manager still sends you work, and the day 30 review is where the plan has to change in writing.

Internal transfer with a plan revised at day 30Example 5

What goes in a 30-60-90 day plan

A 30-60-90 day plan template has one job: turn a vague expectation ("get up to speed") into goals that you and your manager can check at three agreed points. Every section in the template above exists for that.

The day 90 sentence. What your manager would need to see to call the hire a success. Write it in their words, because yours will be more generous.
Learning goals in the first phase. Things you will understand, with a way to show it: a diagram, a written summary, a demo. "Learn the codebase" is not checkable. "Trace one payout end to end and write it up" is.
People to meet, each with a question. A list of names is a calendar. A list of names with the one thing you want to learn from each is a plan.
One early win. Small, visible, and ideally something the team already complains about.
Performance goals in the second phase. Measurable outcomes with dates. This is where the plan moves from what you know to what you deliver.
A proposal in the third phase. By day 60 you know enough to recommend one change. Writing it down is how a new hire shows judgment.
A review record per phase. Done, not done, and what changed. This is the section most templates leave out, and it is the one that makes the plan useful after day 30.

The interview plan and the real plan are different documents

Many people search for a 30-60-90 day plan because a hiring manager asked for one in the final round. That version is a pitch: one page, built from the job description, with your assumptions stated so the panel can correct them. It should end with questions, because the questions show more about how you think than the goals do.

The real plan is written in your first week, with your manager, and it changes. Keep the interview version if you have one, and use it as a first draft. Expect half the goals to move once you see the team's actual problems.

When the plan meets the job

Every guide to 30-60-90 plans describes the three phases. Few say what to do when the job turns out to be different, which it usually does. Access takes two weeks instead of two days. The project you were hired for is paused. The holidays eat a third of the second phase.

Treat each review as a renegotiation, not a grade:

Bring the record, not a summary. Show what is done, what is not and why. A missed goal with a reason is information. A missed goal you hoped nobody would notice is a problem.
Change the plan in writing. If your manager agrees to move a goal, write the new version and the date it changed into the review section. The fifth example shows what that looks like.
Protect the day 90 sentence. Goals can move. The outcome your manager cares about should only change if they say so explicitly. If it does, rewrite the top of the plan.
Ask what you do not know yet. At day 30, ask what your manager wishes you had asked about. At day 60, ask what would make them worried at day 90.

How to fill it in during your first week

Spend an hour on the first draft before your first proper 1:1. Fill in the day 90 sentence as your best guess and mark it for your manager to correct. List the people you think you should meet and ask your manager who is missing. Leave the second and third phases thin: you will write them properly at the day 30 review, when you know enough. Then book the three reviews.

Common mistakes

Too many goals. Ten goals per phase means nothing is a priority. Three to five is enough.
Goals nobody can check. "Build relationships" has no finish line. "Meet all seven reports by day 10" does.
Changing things before learning why they exist. The first phase is for understanding. Proposals belong at day 60, after you know the history.
No manager actions. Access, introductions and decisions often depend on your manager. Put them in the plan with their name, as the support section does.
Dropping the plan after day 30. The plan is most useful at day 60 and 90, when it shows how far you came and what changed on the way.

When to use a different template

The company's side of the first weeks (laptop, accounts, training) belongs in an onboarding checklist template. The weekly conversations where you review this plan belong in a one on one meeting template. To sharpen individual goals, the SMART goals examples page shows how to make them measurable. And once the 90 days are over, a personal development plan template is the place for the longer arc.

Customization tips

Write the day 90 sentence first
Ask your manager what would make them say the hire was right, and write it down in their words. Every goal in the three phases should trace back to that sentence. Goals that do not are nice to have, and the first to drop when the job gets busy.
Book all three reviews on day one
Put the day 30, 60 and 90 reviews in your manager's calendar in your first week. A review that has to be requested in week eleven tends to become a hallway chat, and the plan quietly stops being a plan.
Keep the what-changed line honest
Plans change because the job is different from the job description. That is normal. What is not normal is a plan that changes silently. One line per review that says what moved, and who agreed, turns a missed goal into a renegotiated one.
For interviews, one page and no dates
A plan you present before you are hired should fit on one page, list the assumptions you made from the job description, and end with questions. Interviewers are judging your reasoning, not your calendar.
Change the phase names to fit the role
Learn, contribute, lead works for most jobs. A sales role might use pipeline, first deals, full quota. An executive role might spend 45 days learning, not 30. Keep three checkpoints; change what they are called.
One early win, picked by someone else
The best early win is a small problem the team already complains about, not one you chose to show off. Ask for it in your first round of conversations and ship it before day 30.

In the app

How to do this in Scribelet

Open Desk Settings, then Templates, tap Add Template, paste the template above and set the category to Planning. Keep {{author}} in the title and Scribelet fills in your name each time.
Write goals as - [ ] Goal @due(2026-12-18). They appear in the Tasks view and on your daily note until you tick them, so the plan stays in front of you instead of in a document you opened once.
Add - [ ] Day 30 review with Chris @remind(2026-12-01 09:00) for each checkpoint. Scribelet sends a push reminder in your local time.
Write a short note after each intro meeting and link it with [[Nadia Petrov]] or the team name. The plan's backlinks panel then lists every conversation that fed into it.
Before a review, ask the AI chat "what did I learn about the refund retry logic in my first month?" It answers from your own notes, with citations.

Templates, template variables and AI generation are documented in Note templates.

Frequently asked questions

What format should a 30-60-90 day plan be?

Three sections, one per 30-day phase, each with a focus sentence, a short list of goals with dates, and a review at the end. A one-page document or a single note works better than slides because you will update it every few weeks. The template above is plain Markdown and pastes into any editor.

What is the 30-60-90 rule in an interview?

Some hiring managers ask final-round candidates to present how they would spend their first 90 days. They want to see that you read the job description closely, know what you would need to learn, and can set goals that are realistic. Keep it to one page, state your assumptions, and end with questions, as the third example does.

What is the 30-60-90 day rule and how does it work?

It splits the first three months of a new role into phases that build on each other: roughly learn in the first 30 days, contribute in the next 30, and lead or own something in the last 30. Each phase ends with a check-in with your manager, where you compare what happened with what you planned and adjust the next phase.

What is the 30-60-90 rule in sales?

In sales the phases usually follow a quota ramp: building pipeline in month one, a partial quota (often around 50 percent) in month two, and full quota in month three. Exact ramps vary by company, so ask. The sales example above shows the ramp written as dollar targets.

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

One page for an interview. For the real job, one to two pages: three to five goals per phase, plus the review notes you add as you go. If a phase has ten goals, it has no priorities.

What happens if I miss a goal in my 30-60-90 day plan?

Say so at the review, with the reason, and agree what changes. Most missed goals in the first 90 days come from access delays, holidays or a job that differs from the description, and a manager would rather hear that at day 30 than discover it at day 90.

Ninety days, three reviews, one record

Save this plan as a template in Scribelet, set reminders for your day 30, 60 and 90 reviews, and link every intro conversation back to the plan so the review writes itself. Encrypted, free to start.

Start your 90-day plan

or get the app

Download on theApp Store

Free plan, no credit card. See pricing

Work

Onboarding Checklist Template

Most onboarding checklists list tasks. This one gives each task an owner and a due date, adds a Done when section so everyone knows when onboarding is over, and keeps open issues in one place. Copy it, or start from the filled-in checklist closest to the hire you are making.

Meetings

One on One Meeting Template

A 1:1 belongs to the report, not the manager. This template gives the report the first word, carries last meeting's actions forward, and keeps a growth conversation on the calendar. Copy it, or start from the one on one notes example closest to your situation.

Planning

SMART Goals Examples

A SMART goal is specific, measurable, achievable, relevant and time-bound. The quickest way to write one is to see a vague goal rewritten next to it. Below are five, for very different lives, each with the baseline, checkpoints and a plan for when it slips. The worksheet walks you through your own.

Work

Personal Development Plan Template

A personal development plan names where you are, where you want to be in a year or so, and no more than three things you will work on to get there. This template adds what most plans skip: a monthly check, a quarterly rewrite, and a rule for plans that stall. Copy it, or start from the example closest to your situation.

Work

Performance Review Template

A performance review template is only as fair as its rating scale and its evidence. This one defines each rating level in the template itself, ties every goal to a result and a source, and leaves room for the employee to disagree in writing. Copy it, or start from the example closest to the review you have to write.

Planning

Goal Setting Template

Most goal templates are a page you fill in once in January. This one is a chain: a few life goals, three for the year, one milestone each per quarter, and three weekly goals that move them. Copy it whole, or use only the level you need today.