30-60-90 Day Performance Plan

Use it for new hires, internal transfers, or employees stepping into a new scope where early expectations need to be explicit. It works best when a manager needs to define what success looks like across the first 90 days. It is also useful for HR teams standardizing onboarding across departments. The template is not meant for annual review scoring.

Review it at the start, then at 30, 60, and 90 days, with shorter check-ins if the role is complex or highly cross-functional. The cadence should match the pace of the work and the amount of support the employee needs. If priorities change, update the plan instead of waiting for the next formal checkpoint. That keeps the document useful as a working agreement, not a static form.

The manager usually drafts the initial plan, and the employee should add their own perspective on learning needs and progress. The employee signature and manager signature sections create a clear record that both sides reviewed the expectations. In some organizations, HR may also review the plan for consistency across roles. The key is that ownership is shared, not left entirely to one person.

Each goal should be specific, measurable, and tied to the actual responsibilities of the role. Include learning priorities, stakeholder meetings, independence milestones, and business impact outcomes that can be observed or verified. Avoid vague phrases like "get up to speed" without defining what that means. The best entries describe behaviors, deliverables, or decisions the employee should be able to make by each checkpoint.

It creates a dated record of expectations, progress, and sign-off that can support later performance conversations. That is especially helpful when managers need consistent documentation of what was assigned, reviewed, and completed. It also helps reduce ambiguity if there are concerns during the ramp period. Keep the language factual and tied to work outputs rather than personality traits.

Yes. You can tailor the objectives, stakeholders, training resources, and business impact section for sales, operations, customer support, HR, finance, or technical roles. The structure stays the same, but the content should reflect the actual work and dependencies of the position. For example, a customer-facing role may emphasize relationship building, while a technical role may emphasize systems access and process ownership.

A common mistake is making the plan too broad, such as listing general learning goals without a clear outcome. Another is skipping the 60-day independence milestone, which is where many ramp plans lose momentum. Teams also forget to update the plan after check-ins, so the document no longer reflects reality. Finally, avoid using subjective labels instead of concrete behaviors and deliverables.

Ad hoc notes are easy to start but hard to track, especially when multiple people are involved in onboarding. This template gives you a repeatable structure for goals, learning, support, and sign-off across the full 90-day period. It also makes it easier to compare ramp progress across hires without forcing every role into the same content. If you need consistency and accountability, the template is the better starting point.