Performance improvement plan: a 30-60-90-day guide

A performance improvement plan defines a gap between expected and observed work, the support available and the evidence that will be reviewed. A 30-60-90-day structure can organize that work, provided the checkpoints fit the situation and are not treated as legal deadlines or an automatic disciplinary sequence.

Files keep coming back incomplete, rework grows and a manager begins describing someone as unmotivated. Yet nobody has checked whether the standards were explained, a procedure changed or competing assignments made the work unrealistic. The proposed approach starts with those questions. Its purpose is to make improvement practical and observable, with commitments for the manager as well as the employee.

Performance improvement plan: what gap can you actually describe?

Choose an expectation connected with the role and a few dated examples. Record what was required, what happened and how it affected the work. “The file is missing the agreed approval” gives the conversation a starting point. “You are unreliable” turns an observation into a broad label without explaining what should change.

BDC recommends specific feedback focused on performance rather than personality. Use that distinction to prepare a private conversation. Explain the observation and the expectation, then ask what contributed to the gap. Hear the response before settling on a remedy.

Separate an unclear method, missing resources, conflicting priorities and a skill that still needs practice. Those possibilities call for different responses, and more than one may be present. Do not turn an impression about motivation into a diagnosis. Ask what the person understands, where the work stops and what they think would help them try a different approach.

Your regular performance review process may provide useful evidence. A targeted improvement plan then concentrates on a defined gap, practical actions and closer observation. It does not need to turn every routine management conversation into another lengthy form.

Days 1 to 30: how do you agree on achievable expectations?

Prepare a short working record with the employee: expected result, starting point, quality criteria, available support and review points. Keep the initial priorities limited enough to work on properly. Check that the standards fit the role, tools and available time, rather than one manager’s personal preference for how to perform a task.

Ask the employee to explain the expectation using an example. Show what acceptable work looks like and identify the checks that matter. State the manager’s commitments too: a demonstration, access, practice time or help resolving competing priorities. Give each commitment an identifiable owner and a realistic review date.

The Quebec workplace regulator’s guidance on management rights emphasizes clear requests, objective and respectful supervision, and the means and time to meet expectations. This supports the quality of a management conversation; it does not decide which measure is appropriate in an individual employment situation.

Arrange an early check so a misunderstanding does not continue for weeks. If promised support is unavailable, record that fact and consider its effect on the plan. A deadline maintained without the agreed resources cannot, on its own, explain what the employee had a fair opportunity to practise or demonstrate.

Days 31 to 60: how do you practise and observe progress?

Create comparable opportunities to apply the method. At each check-in, examine a specific result, ask about the reasoning and identify one improvement or remaining gap. Avoid changing the criteria between meetings. Where a change is needed, explain it and confirm that the person understands the revised expectation.

The following table is an original planning aid. Its periods are suggested checkpoints, rather than a universally appropriate duration.

Proposed period	Employee practice	Manager support	Useful evidence
Days 1 to 30	Explain and try the method	Demonstrate and protect practice time	Criteria understood in a straightforward case
Days 31 to 60	Apply it to comparable files	Give feedback and remove an obstacle	Work reviewed against consistent criteria
Days 61 to 90	Consolidate in the agreed situations	Review facts and clarify next steps	Progress, limits and support still needed

Entirely fictional example: a Sherbrooke distribution business notices missing checks on orders. In this exercise, four of ten files need rework. The team chooses an illustrative target of nine conforming files out of ten in a comparable sample. These invented numbers demonstrate how to define a criterion; they are neither industry benchmarks nor a customer result.

The manager discovers that two versions of the procedure are circulating. They have the current method confirmed, demonstrate a complete check and arrange practice. Follow-ups also consider changes in order type and interruptions. Without that context, a comparison might attribute an organizational or process problem entirely to the employee.

Days 61 to 90: how do you choose next steps without an automatic outcome?

Compare observations with the expectations agreed at the start. Ask what has become consistent, where help is still needed and what has not been tested. Progress on simple cases does not establish readiness for every exceptional situation. Describe that limit instead of reducing the entire period to one overall score.

For each review, retain relevant examples, the employee’s explanation, support provided and the next action. Keep observations, interpretations and decisions distinct. Our guide to OKRs for small businesses can help define an observable result without treating a single number as the whole performance picture.

Reaching a proposed checkpoint does not trigger a sanction in this model. Before considering a disciplinary notice, a significant employment change or termination, have the situation and applicable rules reviewed by a qualified labour relations professional or lawyer. If health, safety or accommodation concerns arise, obtain appropriate support before deciding what happens next. This guide makes no legal finding about an individual case and does not provide a disciplinary letter.

How can M360 Compass support the plan and follow-through?

M360 Compass is a people management operating system for SMBs. RoleAlign describes documented responsibilities connected with objectives. Its performance and development capabilities link feedback, skills, development priorities and follow-ups. These reference points can help managers find the expectation, agreed action and next conversation.

Ask to see a workflow using your own criteria and authorized roles. Confirm how follow-ups would be recorded and how necessary access would be managed. The platform supports the people responsible for the process; it does not automatically determine the cause of underperformance or establish that a sanction is appropriate.

If the difficulty mainly concerns learning a new role, our 30-60-90-day onboarding plan addresses that initial transition. This article begins with an observed performance gap. In either situation, the manager’s promised support should remain as visible as the actions expected from the employee.

Frequently asked questions about supporting improvement

Does the plan always need to last exactly 90 days?

No. The three periods are suggested checkpoints. Adapt the pace to the work’s complexity, practice opportunities and available support. Seek appropriate advice on timing where a formal process or an employment decision is being considered.

How do you distinguish skill from motivation?

First check understanding, resources and opportunities to practise. Ask what helps or prevents the expected work. Observations let you test possible explanations; they do not automatically reveal someone’s intentions or personal circumstances.

What if the employee disputes the examples?

Return to the evidence, known criteria and context. Record their response without presenting it as agreement. Verify uncertain information and get appropriate support before making a decision that goes beyond routine performance support.

Is a development plan enough to close the gap?

It organizes expectations, actions and support but guarantees no outcome. Examine the method and organization of the work too. Review progress using comparable evidence and identify what still needs to happen rather than assuming the document itself solves the problem.

Choose one expectation you can explain and one form of support you can actually provide. To connect those commitments with follow-through, request a M360 Compass demonstration.