30 60 90 Day Plan Template: Sections, Wording, Examples
A 30 60 90 day plan template is a one-page outline that splits a new role or project into three phases: learn, contribute and own. It exists to show your manager how you will spend your first three months, and it produces a shared, checkable set of commitments.
Most templates give you three empty columns and leave the wording to you. Below are the sections in order, the sentence pattern for each, a plain-text version to copy, three filled-in examples, and the cases where the plan misleads.
Quick answer: what goes in a 30 60 90 day plan?
A 30 60 90 day plan has an objective, three phases and a success measure for each. Days 1 to 30 are for learning, days 31 to 60 for contributing and days 61 to 90 for owning a result. Each phase lists a few specific actions, and the plan ends with risks and the support you need.
A 30 60 90 day plan template is a one-page structure for the first three months of a role or project. It is built from an objective, three phases (learn, contribute, own), three or four verb-led actions in each, one success measure per phase agreed with a manager, and a short list of risks. The test of a good one is that every action names an object and can be checked: meet the five budget owners passes, build relationships does not. Filled in well, it fits on one page.
How we built this 30 60 90 day plan template
The template was assembled against four tests.
Copyable, not a file
Every section below is plain text you can paste into a slide or a document. No download, no sign-up, no template that only opens in one tool.
Wording, not just headings
A blank grid with three column titles is not a template. Each section carries the sentence pattern that makes an entry specific and checkable.
Worked examples from corporate roles
A new finance manager, a new engagement lead and a programme owner. Each example is filled in so you can see what a good entry looks like.
Honest about limits
A 30-60-90 plan is a proposal made before you know the job. The page says where it breaks.
What we ignored: colour schemes, icon sets and the number of columns a design tool offers. None of them decides whether the plan is any good.
Key takeaways
- Split the plan by what you are doing, not by calendar. Days 1 to 30 are learning, days 31 to 60 are contributing, days 61 to 90 are owning. If a 30-day entry says deliver, it belongs later.
- Every entry needs a verb, an object and a way to check it. Meet the five budget owners is checkable. Build relationships is not.
- Add a success measure to each phase, agreed with your manager. A plan nobody has agreed to is a private to-do list.
- Write the 30-day phase as questions and the 90-day phase as commitments. Specificity should rise with information.
- Keep it to one page. A manager reads a one-page plan in two minutes and will discuss it. A five-page plan gets filed.
What are the sections of a 30 60 90 day plan?
Six sections, in this order. Each carries a concrete entry from a new finance manager's plan.
Header and objective. Your name, role, start date and one sentence on what the first 90 days must achieve. Entry: Learn the reporting close, earn trust with the controllers and own the month-end variance pack by day 90.
Days 1 to 30: learn. Listening and mapping. Meetings to hold, systems to learn, documents to read, questions to answer. Entry: Meet the eight people who feed the close and write down where each handoff slips.
Days 31 to 60: contribute. First visible work, kept small and low risk. Entry: Take over one recurring deliverable and fix one problem found in the first 30 days.
Days 61 to 90: own. A deliverable you now run, and a proposal for what comes next. Entry: Run the month-end pack unassisted and present a plan to cut the close by two days.
Success measures. One or two per phase, agreed with your manager. Entry: Day 30, manager confirms the process map is accurate. Day 90, the pack goes out on its due date.
Risks and support needed. What could slow you and what you need from others. Entry: Access to the consolidation system by day 5, or the day 30 map will be incomplete.
The reason for the structure is that onboarding is usually weaker than managers believe. Gallup's research on onboarding found that only 12 percent of employees strongly agree their organisation does a great job of onboarding new hires, and only 29 percent of new hires say they feel fully prepared and supported to excel in their role. Gallup also reports that employees are 3.4 times as likely to rate their onboarding as exceptional when their manager takes an active role. A shared plan is one cheap way to make the manager active.
The trade-off: six sections on one page means every entry is short. That is deliberate, but it pushes detail out of the plan and into the conversation you have about it.
Copyable 30 60 90 day plan template
Paste this into a document, an email or the notes of a slide. Replace everything in square brackets. Delete any line you cannot fill in with something specific.
30-60-90 day plan, plain text
To put it on a slide, use three equal columns, one per phase, each with the goal in bold, the actions beneath it and the success measure in the last line. The objective becomes the action title. The guide to a executive summary slide shows how to write a title that states the point rather than the topic.
Worked 30 60 90 day plan examples
Three filled-in plans from different corporate situations. Each one has actions that can be checked, and each closes with what the plan shows.
Example 1: a new finance manager
A hire joining a corporate finance team that owns the monthly close.
| Phase | Actions | Success measure |
|---|---|---|
| Days 1 to 30 | Map the close end to end. Meet the eight people who feed it. Read the last six variance packs. | Process map confirmed accurate by the controller. |
| Days 31 to 60 | Take over the revenue accrual schedule. Fix the two handoffs that slipped in phase 1. | Accrual schedule delivered on time twice. |
| Days 61 to 90 | Run the full pack unassisted. Present a proposal to cut the close timeline. | Pack issued on its due date; proposal discussed at the finance leadership meeting. |
What it shows: the plan moves from reading to one owned deliverable, and each phase ends in something the controller can verify.
Example 2: a new engagement lead on a transformation programme
A consultant taking over a workstream mid-programme, with a steering committee every fortnight.
| Phase | Actions | Success measure |
|---|---|---|
| Days 1 to 30 | Read the charter and the last three steering decks. Interview the client sponsor and five workstream owners. | Written summary of open decisions agreed with the sponsor. |
| Days 31 to 60 | Own the workstream plan and the weekly status. Close the two oldest open decisions. | Two decisions closed and logged; status issued weekly. |
| Days 61 to 90 | Lead a steering committee session. Propose the scope for the next phase. | Steering committee approves next-phase scope. |
What it shows: a senior hire needs decisions closed, not just relationships built. The measures are client-facing.
Example 3: a new owner of an internal programme
A manager inheriting a cost-reduction programme that has missed two milestones.
| Phase | Actions | Success measure |
|---|---|---|
| Days 1 to 30 | Audit the milestone plan and the benefits tracker. Meet each initiative owner. | Reconciled baseline of planned versus delivered savings. |
| Days 31 to 60 | Reset the milestone plan with owners. Stop or merge initiatives with no named owner. | Revised plan signed off by the sponsor. |
| Days 61 to 90 | Run the first monthly review on the new plan. Report savings against the reset baseline. | First review held; no initiative without an owner. |
What it shows: when you inherit trouble, the 30-day phase is an audit and the 60-day phase is a reset. Promising delivery in 30 days would be unrealistic.
Notice the pattern of ownership. In the programme-owner example the sponsor signs the reset, and the plan names an owner for every initiative. If that role split is unclear, a RACI chart settles it before the 60-day reset.
Why the first 90 days matter
Michael Watkins of IMD, author of The First 90 Days, frames a transition around a breakeven point: the moment the organisation depends on a new leader about as much as that leader depends on it for support. His argument is that the aim of a plan is to reach that point sooner. That is what the three phases do. Learning builds credibility, a small contribution proves it, and owning a result turns it into reliance.
A plan that skips the learn phase and promises results on day 10 reads as confidence but usually lands as a guess. A plan that spends all 90 days learning reads as caution. The balance in the template, roughly a third of effort each, is a starting point you should adjust to the role.
When to use a 30 60 90 day plan
Use one when you start a new role, take over a programme, or interview for a role where the hiring manager wants to see how you think. It also suits a new project with a clear end date, such as a systems migration, when the team needs a shared sense of pace.
For a team engagement it works best next to a project charter, which fixes scope and success criteria, with the plan covering how one person ramps up inside it. Once the first 90 days are done, a strategy roadmap slide is the natural way to show what comes next.
| Format | Best for | Shape | Watch for |
|---|---|---|---|
| 30-60-90 plan | A new role or new programme | Learn, contribute, own | Assumes you can predict the job before you start |
| Project plan or Gantt | Known scope with dependencies | Tasks, dates, owners | Heavy for a personal plan |
| OKRs | A quarter of measurable outcomes | Objectives with key results | Does not show how you will learn the role |
| Strategy roadmap | Multi-quarter direction for a team | Themes and sequencing | Too coarse for a first 90 days |
When a 30 60 90 day plan misleads
A neat three-column page looks more certain than it is. Four specific failure modes:
- It is written before the facts. You draft it with a job description and one interview. By day 20 the real priorities differ, and a plan you defend rather than revise becomes a liability.
- It treats thirty days as equal in every role. A frontline analyst can contribute in week three. A leader inheriting a failing programme may need all 90 days to audit and reset. Equal columns flatter the first case and misrepresent the second.
- It rewards activity. A plan full of meetings and reviews passes every glance and says nothing about results, because meetings are easy to schedule and easy to claim.
- It ignores what the manager wants. Your priorities on paper may not match the ones your manager holds in mind. Agree the objective before you write the phases.
The fix for all four is the same: treat the plan as a draft you review at day 30 with your manager, and change it when the facts change.
How to make a 30 60 90 day plan slide
PowerPoint has no built-in version. You build it from three columns in five steps.
Write the objective as the action title. One sentence that states what the 90 days will achieve.
Draw three equal columns labelled Learn, Contribute and Own, with the day ranges beneath.
Put the goal in bold at the top of each column, then three or four actions, then the success measure in the last line.
Keep the type size the same in all three columns. Shade only the success-measure lines, so the eye lands on what will be checked.
Add a thin strip below for risks and support needed, and cut anything that does not fit on one slide.
If the people involved are not yet clear, a stakeholder map helps you decide whom to meet in the first 30 days.
Can Oria build a 30 60 90 day plan slide for you?
Yes, for the corporate version of the job. Oria is built for corporate documents and consulting presentations: board packs, steering committee decks, diligence exhibits and dense frameworks held to an enforced corporate template. It reaches you two ways: a PowerPoint add-in in the task pane on Windows, macOS and PowerPoint for the web, and a connector for Claude and ChatGPT over MCP, so the slide can be built from the chat you are already in. The columns arrive as native PowerPoint objects on your master, so every entry stays editable.
One-line 30-60-90 slide prompt
Oria will lay out the plan you specify. It will not decide what your priorities should be, which is a conversation with your manager.
The trade-off: Oria is built for the corporate environment and loses on highly visual work. Founder fundraising and pitch decks, launch and campaign decks, student presentations and marketing one-pagers want visual impact more than defensible content, and a design-led tool such as Gamma, Canva, Pitch or Beautiful.ai will beat it there and look better doing it.
Which tool should you use for a 30 60 90 day plan?
It depends on where the plan has to be read.
| If you need | Use | Why |
|---|---|---|
| A one-page plan for a manager | The template above, pasted into a document | Fastest route, and the format managers expect. |
| A plan shown on a slide in a steering committee | A three-column slide in your corporate template | Oria builds it as native PowerPoint on your master. |
| Dependencies and dates across a team | A Gantt or a roadmap, not a 30-60-90 | The plan is personal. Team schedules need task-level detail. |
| A visual deck for a launch or pitch | Gamma, Canva, Pitch or Beautiful.ai | Design-led tools beat Oria on visual impact. |
Common 30 60 90 day plan mistakes to avoid
Frequently asked questions
What is a 30 60 90 day plan?
A 30 60 90 day plan is a one-page outline of what you intend to learn, do and own in your first three months in a role or on a project. It splits the period into three phases: days 1 to 30 to learn, days 31 to 60 to contribute, and days 61 to 90 to own a result. It is usually shared with a manager.
How do you write a 30 60 90 day plan?
Write one objective for the 90 days, then three phases. Under each phase list three or four actions that start with a verb and name an object, and add one success measure your manager can check. Finish with risks and the support you need. Keep it to one page and agree it before you start.
What should a 30 60 90 day plan include?
An objective, the three phases with their goals, specific actions in each, a success measure per phase, and a short list of risks and support needed. Optional additions are the people you will meet and the documents you will read in the first 30 days.
How long should a 30 60 90 day plan be?
One page. A manager can read a one-page plan in a couple of minutes and respond to it. If the plan runs longer, the detail usually belongs in a project plan rather than a personal plan.
Can I use a 30 60 90 day plan in an interview?
Yes. Candidates for senior roles are often asked for one. The interview version leans on the learn phase, because you do not yet have the facts, and states your assumptions openly. Offer commitments only where you have enough information to keep them.
Is there a 30 60 90 day plan template for PowerPoint?
PowerPoint has no built-in one, but the structure is simple: three equal columns with a goal, actions and a success measure in each, under an action title. The text template on this page pastes straight into those columns.