How to Write a 30-60-90 Day Plan (With Template and Example)

A 30-60-90 day plan is a structured set of goals for a new hire's first three months, split into three phases: learn, contribute, own. It gives the hire and the manager a shared definition of what a successful ramp looks like, which removes the single biggest source of early-hire anxiety, not knowing whether you are doing well. This guide shows how to build one, with a template structure and a worked example you can adapt. For where the plan fits in the bigger picture, see our complete employee onboarding guide.

Why use a 30-60-90 day plan?

Because unclear expectations are a top cause of early turnover. A new hire without a plan is guessing at what good looks like, and guessing breeds doubt. A plan replaces "am I doing okay" with "here is exactly what I am working toward," which is calming for the hire and clarifying for the manager. It also gives the manager a ready structure for one-on-ones and a fair, shared basis for the 90-day conversation. We cover the retention link in how to reduce new hire turnover.

How do you write a 30-60-90 day plan?

1. Define the day-90 outcome first. Decide what full productivity looks like, then work backward so the earlier phases build toward it rather than being filler.
2. First 30 days: learn. Absorb the role, the people, the tools, and the processes. Early tasks should be low-stakes and confidence-building.
3. Days 31 to 60: contribute. Real work with support. The hire owns small pieces end to end.
4. Days 61 to 90: own. Independent ownership of outcomes. The manager shifts from directing to coaching.
5. Review at each milestone. Check in at 30, 60, and 90 days, celebrate wins, and course-correct early.

The template structure

A worked example

Here is the structure filled in for a new account executive, to show what real goals look like.

• Days 1 to 30 (Learn): Complete product and pitch training. Shadow five sales calls. Learn the CRM and the sales process end to end. Understand the ideal customer profile. Have first one-on-ones with the manager and key teammates.
• Days 31 to 60 (Contribute): Run discovery calls with support. Manage a small pipeline of early-stage deals. Deliver the pitch independently. Contribute in team meetings. Hit a small activity target.
• Days 61 to 90 (Own): Own a full pipeline independently. Close first deals. Hit a defined quota ramp. Operate without day-to-day direction, with the manager moving to coaching.

The same pattern works for any role. For engineering specifically, see the ramp plan in how to onboard software engineers.

Where 30-60-90 plans fall down

They get written once, saved in a doc, and never looked at again. The plan only works if the milestones actually trigger a conversation. A plan nobody revisits at day 30 is just a document, not a tool. The fix is to treat the 30, 60, and 90 day marks as scheduled check-in points, not optional reminders.

How Sakha keeps the plan alive

Sakha can deliver the 30-60-90 milestones inside the onboarding flow and prompt check-ins at each marker, so the plan turns into scheduled moments instead of a forgotten file. The hire gets a nudge and a clear view of what each phase expects, and the manager gets a prompt to have the conversation. Pair it with the broader employee onboarding best practices and the plan becomes a living part of the ramp rather than a formality that fades after week one.