30-60-90 Day Plan for a New Job: Template and Three Examples

You signed the offer last week, or you have a final interview on Thursday, and someone said the words "bring a plan for your first 90 days." So you opened a 30 60 90 day plan template, saw three empty boxes, and typed "meet the team" and "learn the processes." Then you stopped, because you have never seen this company from the inside and you have no idea what else belongs there.

Most templates you find were written for managers. They tell you to audit the team, review the budget, and reset priorities for your direct reports. If you are an individual contributor, none of that applies, and copying it makes you look like you misread the job title. The blank grid is not the problem. The prompts around it are.

This article gives you the empty template with plain-language prompts for each column, the same template filled in three ways for an office role, a fully remote role, and a move into an unfamiliar industry, plus a one-page version to bring to a final interview and a checklist to run before you send anything.

Quick answer: A 30 60 90 day plan template splits your first three months into learning, contributing, and owning. Days 1 to 30 are about understanding the role, the tools, and the people; days 31 to 60 about delivering small pieces of real work; days 61 to 90 about running your part of the job with less supervision. Fill each block with two or three concrete items and one way to check that you got there.

What a 30-60-90 Day Plan Is and When You Actually Need One

A 30-60-90 day plan is a one-page map of what you intend to learn, do, and take ownership of during your ramp-up period. It is a working document you write for yourself and share with your manager, not an HR form and not a legal commitment. Probation rules vary by country and employer, so treat your plan as a conversation starter rather than a contract about your job.

There are two moments when people need one, and they call for different levels of detail. The first is the final interview, where a hiring manager asks how you would approach the role. You have no internal data, so your plan stays short, general, and framed as questions you would ask.

The second is your first week in the job, when your manager says "sketch out a plan by Friday." Now you have a team, a backlog, and a login, so the plan gets specific. Everything below is written for the second case, with a stripped-down version for the first.

How to Write a 30-60-90 Day Plan: What Goes in Each Block

Each of the three blocks has the same three columns: learning goals, deliverables, and how you check. The columns are what turn a wish list into a plan. Learning goals say what you need to understand. Deliverables say what leaves your hands. The third column says how you and your manager will know the item is done.

That last column is the one most templates skip, and it is the reason plans quietly die. "Understand the reporting process" has no finish line. "Rebuild last month's report on my own and compare it line by line with the previous version" does.

Here is the same task written two ways, so you can hear the difference:

• Vague: "Get familiar with the tools."
• Concrete: "Complete two real tickets in the ticketing system with a teammate reviewing my work before it ships."
• Vague: "Build relationships across the company."
• Concrete: "Have a 30-minute intro call with each of the four people whose work feeds into mine, and write down what they need from me and when."

Two rules keep the plan honest. Write two or three items per block, not ten, because a wall of promises invites questions you cannot answer yet. And do not commit to numbers you do not have: percentages, revenue targets, and ticket volumes belong to people who already know the baseline. If a plan starts to feel like a list of pledges someone will grade you on later, cut it back to actions you control.

Keep manager work out of it too. Reorganizing a team, hiring, and evaluating other people's performance are not your plan, even if the template you downloaded suggests them.

The Blank Template You Can Copy

Copy this into a document and fill the cells. The prompts in each cell tell you what kind of answer belongs there.

Table: blank 90 day plan for a new role, with prompts in every cell.

Two or three lines per cell is enough. If a cell needs more, you are probably writing a task list rather than a plan.

Example 1: A First 90 Days Plan Example for an Office-Based Specialist

This one leans on people and adjacent teams, because being in the building is your advantage. The role here is a generic specialist at a mid-sized company, and every name is a placeholder.

The stakeholder map matters more than it sounds. Sitting with someone for an hour while they do the work you are about to inherit teaches you more than any document. If the office norms themselves are new to you, what business casual means is a smaller worry to settle in week one.

Example 2: A 30-60-90 Day Plan for a Remote Job

Fully remote onboarding removes the hallway conversations that often carry informal context. You replace them on purpose, in writing, and you say so in the plan.

Add one explicit line about your manager: agree on how often you meet one on one, and what "done" looks like for your first tasks. Remote onboarding can get harder when nobody says this out loud.

Example 3: Moving Into a New Industry

Changing industries means the first 30 days really are mostly learning, and that is fine to write down. Frame it as translation, not as starting over: you are moving skills you already have into a context with different vocabulary and constraints.

Saying "I will spend three weeks learning" does not look weak when you attach a deliverable to it. A glossary, a process sketch, or a list of open questions is visible proof that the learning happened.

The 30-60-90 Day Plan Interview Version: One Page, Three Lines

For a final interview, cut the grid to three lines and one sentence each. You do not know their metrics, their tooling, or their backlog, and inventing them is worse than admitting you cannot know them yet.

• Days 1 to 30: learn the product, the tools, and the handoffs, and meet everyone whose work touches mine.
• Days 31 to 60: take a normal piece of the workload end to end with review.
• Days 61 to 90: own that piece and pick up a second one.

Remove three things: numeric targets, criticism of how they currently work, and anything that requires authority you will not have. Add one thing instead, a short list of questions you would want answered in week one. That signals you understand the limits of your information, which is a better look than false precision. If the way the role was advertised already worries you, run it past the red flag phrases in job ads before you invest more in the plan.

Frequently Asked Questions

What if my manager changes priorities two weeks in?

That is normal, and it does not make your plan useless. Bring the plan to your one on one, mark what moved, and rewrite the affected block in five minutes. A plan that gets revised is doing its job; a plan nobody reopens was never real.

Is a 30-60-90 day plan required to pass probation?

No. It is a voluntary tool, and probation processes differ by country and employer. A plan helps you and your manager agree on what matters early, but treat any formal requirement as separate from the document you write for yourself.

How long should the plan be?

One page for the interview version, and one page for the on-the-job version too. Two or three items per block, each with a way to check it. Ten rows of detail before you understand the work reads as guessing rather than thoroughness.

Should I share the plan with my manager or keep it private?

Share it. The value is in the correction you get back, especially on the "how you check" column, where your assumptions about what counts as done are most likely to be off. Send it before your second or third one on one so there is time to adjust.

What if the plan becomes a list of promises used against me later?

Keep commitments to things you control, avoid numbers you cannot verify, and date the document so it reads as a snapshot. If your workplace treats an optional plan as a formal performance instrument, that is a different situation from the voluntary document described here.

Can I write learning as a goal without looking unambitious?

Yes, as long as each learning goal produces something visible. "Understand the workflow" is invisible. "Map the workflow on one page and have my manager correct it" is a deliverable that happens to teach you the workflow.

Before You Send Your Plan: Checklist

Run these before the plan reaches your manager or your interviewer.

• Every item names a specific action, not a state of mind.
• Every block has a "how you check" entry you could show someone.
• No numeric targets based on company data you have not seen.
• No tasks that require authority over other people.
• Two or three items per block, not ten.
• The 30-day block is mostly learning, and that learning produces something.
• The 60-day block contains at least one thing you finish end to end.
• The 90-day block names what you own, not what you hope for.
• One page, readable in two minutes.
• One question at the end for your manager, so the document invites a reply.

Checklist: final pass on your 90 day plan for a new role before you send it.

The plan is a starting position, not a prediction. Rewrite it after your first month, keep the version history, and use it in your one on ones so the conversation is about work rather than impressions. If those early weeks start feeling heavier than a ramp-up should, the signs worth watching are covered in burnout warning signs, and the separate question of a manager who is hard to work with sits in dealing with a difficult manager.