30-60-90 Day Plan Template (Copy-Paste + Example)

A 30-60-90 day plan sets out what you will learn, contribute, and take ownership of during your first three months in a new role. A useful plan names concrete outcomes, how progress will be checked, and what support you need. The first 30 days emphasize understanding the work, the next 30 emphasize contribution, and the final 30 emphasize greater ownership.

Use the template below as a starting point. Agree the priorities with your manager, then turn the next few weeks into specific tasks rather than trying to predict every day of the full 90.

Free 30-60-90 Day Plan Template

Copy this section into a document, notes app, or task manager. Replace the bracketed fields and remove anything that does not fit your role.

Plan overview

Name: [Your name]

Role and team: [Job title and team]

Manager: [Name]

Start date: [Date]

Day 30, 60, and 90 review dates: [Dates]

Purpose of the role: [One sentence explaining the work you are responsible for and who benefits from it]

Three priorities agreed with my manager:

1. [Priority one]
2. [Priority two]
3. [Priority three]

By day 90, successful progress will look like: [Describe the responsibilities you should be able to handle and the evidence that will demonstrate this]

Days 1-30: understand the role and establish a baseline

Main outcome: [What you should understand or be able to demonstrate by day 30]

Learning priorities:

• [Understand the team's goals and how your role contributes]
• [Learn the relevant tools, processes, and quality standards]
• [Meet the people you depend on and the people who depend on you]
• [Review examples of successful work]

Actions:

• [Action, target date, and expected output]
• [Action, target date, and expected output]
• [Action, target date, and expected output]

Deliverables or evidence:

• [A completed task, written summary, process map, demonstration, or other output]
• [A baseline for a relevant measure, if appropriate]

How progress will be checked: [Who will review the work and what “good enough” means]

Support or dependencies: [Access, training, introductions, approvals, or information needed]

Day-30 review: [What you learned, what remains unclear, and what should change in the next phase]

Days 31-60: contribute and test your approach

Main outcome: [A useful contribution you can realistically make in this period]

Contribution priorities:

• [Take responsibility for a defined piece of work]
• [Apply what you learned in the first month]
• [Test one improvement or approach with the relevant people]

Actions:

• [Action, target date, and expected output]
• [Action, target date, and expected output]
• [Action, target date, and expected output]

Deliverables or evidence:

• [A completed contribution with clear acceptance criteria]
• [Feedback or results from the work]

How progress will be checked: [Quality standard, agreed measure, or reviewer]

Support or dependencies: [What must happen for the work to proceed]

Day-60 review: [What worked, what needs adjustment, and what you are ready to own]

Days 61-90: take ownership and demonstrate progress

Main outcome: [A responsibility or workflow you should be able to handle with an agreed level of independence]

Ownership priorities:

• [Manage the agreed responsibility consistently]
• [Resolve routine issues and identify when to escalate]
• [Document useful improvements and remaining gaps]

Actions:

• [Action, target date, and expected output]
• [Action, target date, and expected output]
• [Action, target date, and expected output]

Deliverables or evidence:

• [Completed work showing the responsibility you have taken on]
• [A short recap of results, feedback, and unresolved issues]

How progress will be checked: [Evidence and reviewer]

Support or dependencies: [Remaining training, decisions, or resources]

Day-90 review: [What you can now own, what still needs support, and the next agreed priorities]

Weekly check-in notes

Week ending: [Date]

Completed: [Main finished work]

Learned: [What changed your understanding]

Blocked: [Issue, its effect, and the help needed]

Feedback received: [Specific feedback and how you will apply it]

Next week's focus: [One to three priorities]

Agreed changes to the plan: [Change, reason, and date]

How to Fill in the Template

Keep the first version short enough to discuss in a meeting. The detailed task list can live elsewhere.

Start with the role's purpose

Before setting goals, ask your manager what the role is meant to make easier, faster, more reliable, or more effective.

“Learn the tools” is a learning activity. “Prepare an accurate weekly client update using the team's tools” connects learning to a useful responsibility.

Useful questions include:

• What should I be able to handle by day 30?
• Which responsibility matters most by day 90?
• What does good work look like here?
• Which decisions can I make independently?
• What should I bring to you before acting?

Give each phase a main outcome

You can have several actions, but make the purpose of each phase easy to explain.

For example:

• Day 30: Understand the handoff process and produce an accurate summary of the current work.
• Day 60: Run a small part of that process with review.
• Day 90: Own the agreed process and escalate exceptions appropriately.

Adapt the progression to the role. A senior hire may need to contribute immediately, while a highly specialized role may require longer training.

Define evidence before choosing a metric

Some goals suit numerical measures. Others need a reviewed deliverable or a demonstrated skill.

“Build relationships” becomes more concrete when you name the people to meet and the questions you need answered. “Understand the product” becomes more useful when you can explain a customer workflow accurately or complete a relevant task.

Where you use a numerical target, establish the starting point and agree the target. Avoid promising a percentage improvement before understanding the current process.

Filled Example: A New Operations Coordinator

The following example is fictional. The person, company, goals, and milestones illustrate how to write a plan; they are not reported results.

Name: Alex Morgan

Role: Operations coordinator at a small software company

Purpose: Keep client onboarding organized so the team can see what is ready, what is missing, and who needs to act.

Agreed priorities:

1. Understand the current onboarding process.
2. Make handoffs clearer on a small pilot.
3. Take ownership of routine onboarding coordination.

Day-90 definition of progress: Alex can coordinate a standard onboarding from kickoff to handoff, maintain an accurate status record, and escalate exceptions to the correct person.

Alex's first 30 days

Main outcome: A reviewed understanding of how onboarding currently works.

Actions:

• By day 7, obtain required access and meet the people responsible for sales, delivery, and support.
• By day 14, review five recent onboardings and document the steps, owners, and recurring gaps.
• By day 21, shadow an active onboarding and draft its status update for review.
• By day 30, present a simple process map and a proposed checklist to the manager.

Evidence: A process map, reviewed status update, and list of open questions.

Acceptance criteria: The relevant team members confirm the process map is accurate, and the manager approves what to test next.

Dependency: Access to project records and time with the people who handle each stage.

Alex's days 31-60

Main outcome: A tested checklist for routine onboarding handoffs.

Actions:

• Agree the pilot scope and checklist with the manager before using it.
• Use the checklist on three suitable onboardings, subject to client availability.
• Record missing information, repeated questions, and unclear ownership during the pilot.
• Review the findings with delivery and support, then revise the checklist.

Evidence: Three pilot records and a revised checklist with an agreed owner for each step.

Acceptance criteria: The manager and delivery lead approve the revised checklist for routine use.

Dependency: Enough suitable onboardings occur during the period. If they do not, agree a smaller pilot rather than claiming work that did not happen.

Alex's days 61-90

Main outcome: Ownership of standard onboarding coordination within agreed boundaries.

Actions:

• Coordinate routine onboardings using the approved checklist.
• Keep each onboarding's next action, owner, and blocker up to date.
• Bring exceptions to the delivery lead using the agreed escalation process.
• Prepare a day-90 recap with examples of completed work and remaining process gaps.

Evidence: Current onboarding records, completed handoffs, and the day-90 recap.

Acceptance criteria: The manager reviews a sample of records and confirms that routine coordination can continue with the agreed level of supervision.

This plan makes progress observable without pretending Alex can control client timing or every team's workload.

Turn the Plan Into Dated Tasks

The plan gives direction. Your task system should show what to do next.

Take Alex's day-14 milestone: “Review five recent onboardings and document recurring gaps.” Break it into actions such as:

• Ask the delivery lead which examples to review.
• Read the first two onboarding records.
• Note where information was missing.
• Review the remaining records.
• Draft the summary.
• Ask the delivery lead to check the findings.

Put those actions on realistic dates. A milestone at day 14 should not first appear in your task list on day 14.

Keep meetings, training, and normal responsibilities in view when deciding how much to schedule. Your onboarding plan shares time with the rest of the job.

How to Manage a 30-60-90 Day Plan in SelfManager.ai

SelfManager.ai organizes work by date, with tables for tasks and supporting notes. You can use that structure to connect the high-level plan with the days on which you carry it out.

1. Keep the overall plan accessible

Create a table called “First 90 days: [role]” and put the agreed plan in its notes. Pin the table so it remains accessible while you work on different dates.

Update the plan when priorities change, and record the reason. For example: “Manager moved the checklist pilot to phase two because access was delayed.”

2. Schedule the next actions

Create dated task tables for the work ahead, such as “Role onboarding” or “Onboarding pilot.” Keep each task concrete enough to complete and check.

Use notes or comments to record feedback, decisions, and blockers. If you track time, the built-in task timer can help you understand where effort went.

If you want your plan and work record in one place, try SelfManager.ai's seven-day trial with no credit card required. Start with the first week rather than filling all 90 days immediately.

3. Use AI Plan for manageable periods

AI Plan supports a date range of up to 31 days per generation. Build the 90-day plan in separate periods, adjusting later periods as you learn.

A useful sequence is:

1. Schedule the agreed work for days 1-30.
2. Review progress and feedback at day 30.
3. Schedule days 31-60 using the revised priorities.
4. Review again, then schedule days 61-90.

For the first period, you could use a prompt like:

Plan my first 30 days as an operations coordinator. Use the agreed actions below. Schedule work on weekdays, allow time for normal responsibilities, and keep tasks small enough to complete. Do not invent company processes or numeric targets. Leave approval-dependent work clearly identified.

Add your real start date, milestones, and agreed actions. Review the editable preview, correct assumptions, and approve the plan only when the dates and tasks make sense.

For tables created by AI Plan, time tracking is off by default. Enable it on the relevant tables if you intend to record time.

4. Review the recorded work at each checkpoint

At days 30, 60, and 90, compare the original outcomes with your task records and feedback.

Instant AI Review supports a custom period of up to 90 days, so it can help draft a recap of the recorded work across the full plan.

Check the recap against your records before sharing it. Add evidence of outcomes that happened outside the app, and remove any interpretation the records do not support.

The review is useful input for a conversation with your manager. Your manager still decides whether the work meets the role's expectations.

What to Cover in Your Day-30, Day-60, and Day-90 Reviews

Use the same questions at every checkpoint:

• What did I commit to completing?
• What did I finish, and what evidence shows it?
• What changed my understanding of the role?
• Which work is blocked, and what decision or support is needed?
• What feedback have I applied?
• What should I continue, change, or stop in the next period?

Bring a few concrete examples. A reviewed document, completed handoff, or resolved issue is easier to assess than a long list of activities.

Distinguish “completed the task” from “achieved the intended outcome.” Drafting a checklist is a task. Having it reviewed and adopted is a separate outcome.

Common Mistakes to Avoid

Planning activity without a result

“Attend meetings” says little about why those meetings matter. Name the information, decision, or relationship you need to establish.

Promising results outside your control

Your plan should identify dependencies. If another team must grant access or approve a change, make that visible and agree a fallback.

Treating the first version as fixed

A new role exposes information you did not have on day one. Revise the plan with your manager instead of quietly working toward outdated priorities.

Scheduling all 90 days in detail immediately

Keep later phases at the outcome level until you know enough to schedule them responsibly. Detailed near-term tasks and adaptable later milestones can coexist.

Waiting until day 90 to collect evidence

Record short notes as work happens. It is easier to explain a changed deadline when the reason is captured on the relevant day.

Final Takeaway

A useful 30-60-90 day plan connects learning, contribution, and ownership to evidence your manager can assess.

Agree the outcomes, schedule the next actions, and review what changed at each checkpoint. The plan should help you make decisions during the role transition, not sit untouched until a final review.

SelfManager.ai can support that process with dated tasks, notes, time tracking, and AI-assisted planning and reviews. Start a seven-day trial and use the template to plan your first week of real work.

FAQ

What should a 30-60-90 day plan include?

Include the role's purpose, agreed priorities, an outcome for each phase, specific actions, evidence of progress, dependencies, and review dates. Keep the overall plan concise and put detailed daily actions in your task system.

Are the 30, 60, and 90 days calendar days or working days?

State the convention explicitly and agree it with your manager. This template uses calendar days from your start date, with tasks scheduled on your actual working days. Holidays, leave, and training may require adjustments to milestones.

Can I use this template for a job interview?

Yes. Present it as a proposed approach based on what you know about the role. Make assumptions explicit and include questions you would need answered after joining. Avoid presenting internal processes, baselines, or targets as established facts.

What if priorities change before day 90?

Review the change with your manager, update the affected outcomes and tasks, and record the reason. Keep enough context to explain why the new plan differs from the original.

Can SelfManager.ai generate the full 90-day plan at once?

AI Plan generates up to 31 days at a time. Use separate periods for the full 90 days and review each before approving it. Instant AI Review can cover a selected period of up to 90 days to help recap the work you recorded.