This 30 60 90 day plan template connects each phase to a useful contribution and a manager conversation. The filled example moves from understanding a role to preparing real work with support, then planning the next cycle. It also shows how a review changes the next phase.
Start with the role's work
The original fictional example is for a new community-program coordinator helping prepare monthly workshops. The existing coordinator continues to make operational decisions until the manager agrees to hand over particular responsibilities. The plan is a proposed work agreement, not a record of completed onboarding or permission to act.
| Phase | Priority and contribution | Evidence to bring to the review | Support and checkpoint question |
|---|---|---|---|
| Days 1–30 | Understand workshop preparation. Produce a handoff map and a draft facilitator brief from the team's current process. | Walk the map through with the existing coordinator; bring the brief to the manager. | Access to approved process material and the current coordinator. Ask: does this describe the work clearly enough to help prepare a session? |
| Days 31–60 | Prepare one workshop with the existing coordinator reviewing the work. Produce the session preparation pack and a short handoff note. | Review the pack before use; discuss the handoff afterward with the coordinator. | Current coordinator retains operational decisions. Ask: which preparation tasks can I handle next time, and where do I still need support? |
| Days 61–90 | Propose the following workshop cycle's preparation plan using what the first cycle revealed. | Bring a draft plan, reasons for changes, and the support needed to deliver it. | Manager agrees the next scope and resources. Ask: what should I own in the next cycle? |
The outputs belong to this role: a handoff map, a usable preparation pack, and a next-cycle plan. Replace them with work that matters in your own job. Attending a set of meetings can help you learn, but it does not by itself show what you are ready to contribute.
Asana's 30-60-90-day template separates the three phases and connects learning and performance milestones with measures of success and manager check-ins. Use the structure to agree expectations for your role. A calendar boundary is a useful review point; it does not establish that every employee should reach the same level of independence by that day.
Make a goal something you can discuss
Compare “understand workshop preparation” with “walk through the handoff map with the current coordinator and identify where the facilitator needs each instruction.” The second gives both people an artifact to inspect and a question to answer.
Choose Days 1–30 in the example to read the output beside its review question. Then inspect Days 31–60. The expected contribution changes from describing the process to preparing a session with a reviewer. That is a change in work and support, rather than the same checklist under a later date.
If your role already has agreed measures, include their definitions, baseline, data source, and review window. A target such as “increase sign-ups by 20%” needs a starting figure and a reason it belongs to your responsibility. Do not add an impressive percentage to a template when those facts are absent.
An output can also need qualitative review. The facilitator brief should be usable during setup, so ask the person using it to walk through a setup with the draft. Agree the review method with your manager before treating that output as accepted.
Change the next phase after the check-in
The example includes a separate fictional day-30 feedback note:
The handoff map follows the preparation sequence. The facilitator brief is too long to use during setup. Shorten it and walk through the revised brief with the current coordinator before preparing the next session.
Choose Compare phase-two plans. The original phase-two plan starts with preparing the workshop pack. The revised plan first calls for a shorter facilitator brief and a walkthrough with the current coordinator, then continues with the supported workshop preparation.
The review changes the sequence of work. It does not turn the feedback note into proof that the shorter brief is already usable. Bring the revision to the next agreed review, and keep the current coordinator's responsibilities visible until the manager changes them.
For your own check-in, discuss what you produced, what the reviewer observed, what support you used, and what should change next. Keep the earlier plan beside the revision long enough to explain the change. If the actual work or available support differs from the starting assumptions, revise the plan together.
Copy a prompt for your role and manager review
Create one complete HTML 30/60/90-day role plan.
Role, team and agreed purpose of the first 90 days: [PASTE]
Current responsibilities and boundaries of authority: [PASTE]
Phase priorities, useful outputs and review evidence: [PASTE]
Agreed success measures with definitions/baselines, if any: [PASTE]
Manager/reviewer, support, dependencies and check-in arrangements: [PASTE]
Actual feedback and agreed revisions, if already available: [PASTE]
Use my supplied facts. Give each phase a priority, contribution,
output/evidence, support/dependency and manager-review question.
Keep proposed work separate from completed/reviewed work. Do not
invent performance baselines, targets, achieved results, dates,
manager agreement or permission to act. Do not calculate success
from elapsed days. Leave missing arrangements to confirm.
Include this separate original fictional example:
Role: new community-program coordinator preparing monthly workshops.
The existing coordinator retains operational decisions until the
manager agrees a specific handover. All phase work below is proposed.
Days 1–30: understand preparation; create a handoff map and a draft
facilitator brief from the current process. Walk the map through
with the existing coordinator and bring the brief to the manager.
Needs approved process material and coordinator time.
Review: does this describe the work clearly enough to help
prepare a session?
Days 31–60: prepare one workshop with the current coordinator
reviewing. Produce a session preparation pack and handoff note;
review the pack before use and discuss the handoff afterward.
The existing coordinator retains operational decisions.
Review: which preparation tasks can the new coordinator handle
next time, and where is support still needed?
Days 61–90: propose the following workshop cycle's preparation plan
from the first cycle's experience. Bring the draft, reasons for
changes and needed support. Manager agrees scope and resources.
Review: what should the new coordinator own in the next cycle?
Include this separate fictional day-30 feedback:
The handoff map follows the preparation sequence. The facilitator
brief is too long to use during setup. Shorten it and walk through
the revised brief with the current coordinator before preparing
the next session.
Provide phase selection and Compare phase-two plans. Show the
original phase-two sequence alongside a revised teaching sequence:
first shorten the brief and walk through it with the coordinator;
then prepare the workshop with the existing review and decision
boundaries. Do not claim the revision has already been accepted,
the workshop has occurred or responsibility has been transferred.
Keep outputs, review questions and support readable together.
Add a separate blank role-plan scaffold and a local writing area
for check-in questions. Preserve typing when phases switch and
ask before reset. No automatic employee score, completion badge,
employment decision, calendar booking, sending or pretend export.
Use at least 16px text, labeled native controls and visible focus.
Stack labeled phase records at 360px without page overflow.
Inline CSS/JavaScript only; no external assets, network or storage.
State that typing is for this open page only. Return full HTML.
Read the generated plan as the employee and the manager. Each phase should say what work is proposed, what someone will inspect, and what support makes the work possible. Agree any actual dates and responsibility changes through your employer's normal process.
Take the next-phase question to your manager
Share the plan before the check-in so your manager can read the proposed contribution alongside the support it needs. If you prepared it as HTML, put the reading copy in your NOS workspace. Use the page to discuss the original and revised phase-two sequence together.
After that discussion, correct the static role-scope explanation or review question on the saved page in visual editing mode. Your manager can reopen the existing link to read the correction. Reflect agreed responsibility changes in your maintained work plan too; the HTML review copy does not grant access or change your employer's records.
Leave the meeting with a specific next contribution, the person who will review it, and the help you can ask for. Those agreements give the next thirty days a clearer purpose than a longer list of onboarding activities.