Talent

Performance Review Examples: Templates Canadian Managers Actually Use

Real performance review examples by category and level for Canadian managers. Copy-edit ready phrases for communication, quality, initiative, teamwork, and more.

Mar 30, 2026 · 2:52 PM·12 min read·Matthew Woolley

Based on 25+ years of supporting talent management across hiring, onboarding, performance, and succession planning.

Most performance reviews say nothing. “John is a team player who meets expectations” sounds professional but tells John nothing about what he’s doing well, what he should change, or whether he’s on a path to grow. This post gives you real performance review examples, organized by category and performance level, that Canadian managers can copy, edit, and actually use.

At a Glance
  • Performance review examples organized by category: communication, work quality, initiative, teamwork, reliability, and leadership.
  • Each category has strong, average, and needs-improvement examples you can copy-edit directly.
  • Three full mini-reviews included: a strong performer, a mid-level performer, and a PIP-stage situation.
  • Canadian HR considerations: progressive discipline, human rights obligations, and the ESA connection to termination-linked reviews.
  • Common mistakes managers make and how to avoid them.
  • Workzoom’s Talent Suite handles review forms, tracking, and documentation at $4 CAD/employee/month. No setup fees. No contracts.

The Performance Review Is Broken (And Everyone Knows It)

A survey by Gallup found that fewer than 1 in 5 employees strongly agree their performance is managed in a way that motivates them to do outstanding work. The performance review is often the centrepiece of a company’s talent process, and it’s failing the people it’s supposed to serve.

The reasons are predictable. Managers write reviews in 20 minutes the morning they’re due. HR sends a form with five rating boxes and a comment field, so managers write five generic sentences. No one reads the previous year’s review before writing the current one. The language is vague enough to apply to anyone: “works well with others,” “a reliable contributor,” “could communicate more proactively.”

These phrases communicate nothing. They protect no one legally. They give employees no signal about what to do differently. And when a performance issue escalates into discipline or termination, the lack of specific documented feedback becomes a real HR liability.

The fix is not a longer form or a new rating scale. The fix is specificity.

What Makes a Performance Review Actually Useful

A useful performance review does three things: it documents what actually happened, it names behaviours rather than personality traits, and it creates a clear link between past performance and future expectations.

Documenting what happened means tying feedback to specific situations. “Sarah exceeded her sales target by 18% in Q3” is specific. “Sarah is a strong performer” is not. Behaviours, not traits, means writing “Alex frequently volunteers to support colleagues during high-volume periods” rather than “Alex is a good team player.” Future expectations means ending each category with a clear statement of what the next review cycle should look like.

That’s the structure. The rest of this post is examples.

Performance Review Examples by Category

Communication Skills

Example: Strong Communicator

“Marcus consistently communicates project status before being asked. During the Q2 system migration, he sent weekly updates to all stakeholders, flagged a two-day delay on day three rather than at the deadline, and translated technical issues into plain language for non-technical team members. His written communication is clear, concise, and appropriately calibrated to the audience.”

Example: Average Communicator

“Priya communicates effectively in one-on-one settings and in writing. She would benefit from more proactive communication on project blockers: during the March client onboarding, a scheduling issue went unreported for four days, which required a last-minute team adjustment. The expectation for the coming cycle is that blockers are flagged within 24 hours of being identified.”

Example: Needs Improvement (Communication)

“Communication is an area requiring focused development this cycle. On three occasions between January and March, project stakeholders reported receiving incomplete or conflicting information from James. In two of those situations, the miscommunication required rework that affected team delivery timelines. James has been asked to copy his manager on all external project updates for the next 90 days, and to confirm key decisions in writing before acting on verbal discussions.”

Work Quality and Accuracy

Example: High Work Quality

“Dana’s output consistently requires minimal revision. Her monthly financial reports for Q1 and Q2 were submitted on time, contained no material errors, and were formatted to a standard that is now used as a model for the broader finance team. She catches errors in others’ work during review cycles, which has reduced the team’s overall revision rate.”

Example: Average Work Quality

“Work quality is generally strong, with some variability in periods of high volume. Three of the six client reports delivered in H2 contained minor formatting inconsistencies that required correction before client distribution. The content itself was accurate. The expectation for the next cycle is that all deliverables are self-reviewed against the team’s checklist before submission, regardless of workload.”

Example: Needs Improvement (Work Quality)

“The accuracy of work submitted by Liam has not met the required standard this cycle. Six of the fourteen payroll batches processed in Q3 contained errors that were caught during the verification step, and two required reprocessing after distribution. This is an improvement from Q2 (nine errors), but the target for this role is no more than one error per quarter. Liam and his manager have agreed on a 60-day accuracy plan that includes a second-check process for all batches before final submission.”

Initiative and Ownership

Example: Strong Initiative

“Without being asked, Fatima identified a gap in the new employee orientation process that was causing confusion around IT access provisioning. She documented the issue, proposed a three-step fix, coordinated with IT and HR, and had the revised process running before the next onboarding cohort. The change reduced first-week IT tickets by roughly 40%. This is representative of how she approaches problems: she sees gaps, owns the fix, and closes the loop.”

Example: Average Initiative

“Carlos reliably completes his assigned work and is responsive when asked to take on additional tasks. He is less likely to identify and self-assign work that falls outside his defined scope, even when it is clearly within his capability. The expectation for the next cycle is that Carlos brings at least one proactive process improvement recommendation per quarter, rather than waiting for improvement opportunities to be assigned.”

Example: Needs Improvement (Initiative)

“During this review period, the expectation was that the analyst role would require minimal supervision on standard tasks after the six-month mark. At nine months, Nicole’s manager is still checking in on routine deliverables weekly to ensure they are on track. Nicole is encouraged to develop a self-management approach that includes flagging her own workload, setting internal deadlines for recurring tasks, and communicating proactively rather than waiting to be asked for updates.”

Teamwork and Collaboration

Example: Strong Collaborator

“When two members of the operations team were on concurrent medical leaves in October, Ryan absorbed a significant portion of their workload without a drop in quality or attitude. He also provided informal mentorship to the two new hires who joined during this period, orienting them to team processes and answering questions that would otherwise have gone to the manager. Multiple team members named Ryan specifically in the team survey when asked who most contributed to a positive working environment.”

Example: Average Team Collaboration

“Wei works well within her own project team and maintains positive relationships with her direct colleagues. Collaboration across departments is an area for growth: two cross-functional project leads noted that information requests directed to Wei took longer to receive than expected, and in one case the delay pushed a project milestone. The expectation for the next cycle is a 48-hour turnaround on cross-team requests, unless a longer timeline is communicated upfront.”

Example: Needs Improvement (Collaboration)

“Feedback from three colleagues and two project leads this cycle raised consistent concerns about how Dominic engages during team disagreements. Specifically: interrupting others during meetings, dismissing suggestions from junior team members without explanation, and on two occasions, using language in Slack that other team members described as demeaning. Dominic has been made aware of this feedback directly. The expectation is that these behaviours are not repeated. A follow-up conversation is scheduled for 60 days from this review date.”

Meeting Deadlines and Reliability

Example: Highly Reliable

“Over the past 12 months, Simone has not missed a single deadline on file. When she anticipated a potential delay on the August client deliverable due to a supplier delay, she flagged it eight days in advance with a contingency plan already drafted. Her manager has never needed to follow up on a committed deliverable. This level of reliability has earned her the trust to manage her own project timelines without check-ins.”

Example: Average Reliability

“Tom meets most deadlines and is generally dependable. Four deliverables over the past year were submitted late, two of which were communicated in advance and one of which required a client extension. Reliability is not a significant concern, but the pattern of same-day or next-day deadline slippage suggests a planning gap rather than a capacity issue. The goal for the next cycle is zero unannounced missed deadlines.”

Example: Needs Improvement (Reliability)

“Deadline adherence has been a recurring concern this cycle. Of the 22 deliverables tracked in Q2 and Q3, nine were submitted late, and five of those were not communicated in advance. This pattern has affected client relationships on two accounts and has required other team members to cover during the gaps. Anika and her manager have discussed a structured task management approach; the expectation is a measurable improvement by the 90-day checkpoint.”

Leadership (For Managers Being Reviewed)

Example: Strong Manager

“Under Keisha’s leadership, team attrition dropped from 28% to 11% year-over-year. She introduced a structured one-on-one cadence, advocated for two internal promotions on her team, and redesigned the onboarding process for new team members so that they reach full productivity in six weeks instead of twelve. Her team’s performance scores are consistently in the top quartile across the department. She is ready for expanded scope.”

Example: Developing Manager

“Andre has strong technical credibility and his team respects his subject matter expertise. The development area for this cycle is delegation: Andre frequently absorbs tasks that should be assigned to team members, which creates a bottleneck and limits the development of his direct reports. The expectation for next year is that Andre can demonstrate three or more examples of structured delegation where he coached a team member through a task rather than completing it himself.”

Example: Manager Needing Significant Improvement

“Three direct reports on Patricia’s team have raised concerns through the HR channel this cycle about communication style and inconsistent expectations. Patricia has been informed of this feedback. In addition, two performance issues on her team went undocumented for longer than the 60-day standard, creating gaps in the HR file. The expectation is that Patricia complete the manager training module before the Q1 checkpoint and that all performance conversations are documented in the system within five business days of occurring.”

Three Full Mini-Reviews You Can Model

The examples above are category-level. Here are three complete short-form reviews to show how the pieces fit together.

Strong Performer: Sales Account Manager

Jordan exceeded his annual revenue target by 22%, finishing at $1.32M against a $1.08M goal. He closed four net-new accounts in Q3 alone, the highest single-quarter result on the team. His pipeline management is disciplined: his close rate (34%) and average deal size ($41K) are both above team averages.

Beyond the numbers, Jordan has been a positive influence on two newer reps, sharing his outreach templates and making himself available for deal strategy conversations without being asked. His manager has observed no gaps in professionalism or client communication.

For the next cycle: Jordan is ready to take on a named enterprise account. The recommended next step is a conversation with the sales director about scope expansion and associated compensation adjustments.

Mid-Performer: Operations Coordinator

Brittany’s core responsibilities are executed reliably. Scheduling, vendor coordination, and administrative reporting are all handled with minimal supervision and generally on time. She is well-liked by the team and approachable when colleagues need support.

The development area for this cycle is taking ownership of process gaps rather than routing them upward. On four occasions, Brittany identified a recurring problem in the supply ordering process, flagged it to her manager, and waited. The expectation is that at the coordinator level, identifying a problem comes with a proposed solution, not just a notification.

For the next cycle: Brittany should bring one documented process improvement proposal per quarter. Her manager will schedule monthly one-on-ones to coach through the ownership gap. With that shift, she has the profile to move into a senior coordinator role within 12-18 months.

Performance Improvement Situation: Customer Support Specialist

Over the past two review periods, the standard for this role has been clearly communicated: a maximum of 5% escalation rate on handled tickets, full adherence to response time SLAs, and professional tone in all written communications. Marcus’s current metrics are: 14% escalation rate (Q2-Q3 average), SLA adherence at 71% against a 90% target, and two formal complaints received from clients regarding tone in email exchanges.

Marcus and his manager have had direct conversations about these gaps on three documented occasions since June. A performance improvement plan has been put in place with 60-day checkpoints. The specific targets, support measures, and timelines are documented separately in the HR file.

The intent of this review is to acknowledge the current performance gap clearly, document the support being provided, and establish that sustained performance at the required standard is expected. Marcus has confirmed he understands the expectations and the timeline.

Canadian HR Considerations for Performance Reviews

Performance reviews carry legal weight in Canada that many managers don’t fully appreciate. Here are the four areas that matter most.

Progressive Discipline and Documentation

Canadian courts and labour arbitrators have consistently held that employers must follow a progressive discipline process before terminating an employee for performance-related reasons, except in cases of serious misconduct. That process typically includes verbal warning, written warning, final written warning or suspension, and then termination. Performance reviews are part of that chain.

If a performance review documents a concern, the documentation needs to be specific, signed, filed, and followed up. A review that says “needs improvement in communication” and then does nothing else for a year does not constitute a paper trail that supports a subsequent termination. The follow-up matters as much as the initial documentation.

Human Rights Obligations

Performance reviews must not, directly or indirectly, penalize employees for characteristics protected under the Canadian Human Rights Act or applicable provincial codes. Protected grounds include disability, family status, pregnancy, religion, age, and others.

This has practical implications. If an employee’s performance dipped during a period of illness, family caregiving, or accommodation needs, the review language needs to reflect the context. Documenting a performance gap without acknowledging an accommodation request that was in place at the same time creates legal exposure. If a performance issue is connected to a protected characteristic, the employer’s obligation is to explore accommodation to the point of undue hardship before moving to discipline.

ESA Connection to PIP and Termination

Under most provincial employment standards legislation, an employee who is terminated without cause is entitled to notice or pay in lieu. In Ontario, the entitlement under the Employment Standards Act is based on years of service, but common law entitlements are often substantially higher. A performance improvement plan that leads to termination is a termination without cause unless the employer can demonstrate just cause through a documented, fair process.

This means the PIP itself needs to be fair: clearly written targets, a realistic timeline, genuine support provided, and a process that was actually followed. A PIP written two weeks before a planned termination will not be read by a court or arbitrator as a good-faith performance management process.

Probationary Periods

Many provinces allow a shorter notice period or no notice period during a probationary period (typically the first three months). Performance reviews conducted at the 30-, 60-, or 90-day marks during probation carry different legal weight than reviews for permanent employees. Use them to set expectations clearly, document concerns early, and make a deliberate decision about the permanent relationship before the probationary period expires.

The Most Common Mistakes Managers Make in Performance Reviews

These show up constantly, and each one has a concrete fix.

Recency bias. The review covers the full cycle, but the manager only remembers the last six weeks. The employee who had a strong Q1 and Q2 but a rough Q3 gets reviewed on Q3. Fix: keep a running file on each direct report throughout the year. Two minutes per week is enough.

Trait language instead of behaviour language. “Brendan has a negative attitude” is a trait judgment. “In three team meetings, Brendan interrupted colleagues and rejected two proposals without offering an alternative” is observable behaviour. Trait language is not defensible; behaviour language is. Rewrite every trait statement as a behaviour.

No rating-comment alignment. Rating an employee as “exceeds expectations” and then writing comments that describe average work confuses the employee, undermines the rating scale, and creates inconsistency in compensation decisions downstream. The comment should explain the rating.

Skipping the forward section. A performance review that only looks backward is half a review. Every review should end with specific, agreed expectations for the next cycle. Without that, the employee has no direction, and the manager has no basis for the next review.

Avoiding hard conversations in writing. Managers sometimes give a mediocre employee a satisfactory rating because they do not want the discomfort of documenting a concern. This is unfair to the employee (who deserves honest feedback) and creates a paper trail that contradicts a subsequent performance issue. Write what is true.

Generic positive reviews for strong performers. High performers read vague praise as a signal that no one is actually paying attention. Specific, detailed recognition for what a strong performer actually did is a retention tool. Use it.

Workzoom Talent Suite: Reviews That Are Actually Filed

Writing a good performance review is one problem. Making sure the review is stored, linked to the employee record, and accessible if you ever need it is a different one. Email PDFs and shared drives are not a system.

Workzoom’s Talent Suite includes configurable performance review forms, manager and employee views, e-signature workflows, and a complete audit trail that connects to the HR record. When a review is completed, it is filed, timestamped, and retrievable. If a performance management situation escalates, the documentation is already in order.

The Talent Suite is $4 CAD per employee per month. No setup fees. No contracts. For organizations running HR, Workforce, or Payroll on Workzoom, adding Talent connects performance documentation directly to the rest of the employee record without re-entry.

Key Takeaway

The examples in this post work because they are specific. They name behaviours, reference real situations, and set clear expectations for what comes next. That specificity is what turns a performance review from a formality into a tool that actually serves the employee and protects the organization. Copy-edit these examples to fit your situation, replace the placeholder names and metrics with real ones, and file the result somewhere it can be found.

Tell Us What You Need to See

If you’re managing performance reviews across a team and the current process is more compliance exercise than useful feedback, show us your setup. We’ll walk through how Workzoom’s Talent Suite handles review forms, documentation, and the HR file connection.

Tell Us What You Need to See

ShareLinkedInX

Frequently Asked Questions

A complete Canadian performance review should include: a summary of performance against specific, documented expectations from the prior cycle; behavioural examples (not personality judgments) tied to observable situations; a rating that is consistent with the written comments; acknowledgment of any accommodation or leave periods that affected the review cycle; and a clear forward section that sets expectations for the next period. For employees on a performance improvement plan or where disciplinary action is possible, the review should be reviewed by HR before delivery.

Write specifically about the gap between the required standard and the actual performance. Reference the number of occurrences, the timeframe, and the impact on the team or client. Avoid trait language like ‘bad attitude’ or ‘not motivated.’ Instead, document the observable behaviours: missed deadlines, specific errors, incidents reported by colleagues. State clearly what the expectation is and what the timeline is for improvement. Note what support has been provided or will be provided. In Canada, this documentation is part of the progressive discipline chain that must be in place before a performance-related termination.

Yes. Performance reviews are regularly used as evidence in wrongful dismissal claims, human rights complaints, and grievance arbitrations. A review that rates an employee as satisfactory and then a termination six months later for performance reasons creates a direct contradiction. Conversely, a clear, documented, progressive record of specific performance concerns with documented follow-up supports an employer’s position. The quality and consistency of documentation in performance reviews is often the deciding factor in how these cases resolve.

There is no required length, but a useful performance review for most roles is 300 to 600 words of actual written commentary, beyond the rating fields. It should be long enough to document specific examples for each category and set clear expectations for the next cycle. It should not be so long that managers default to generic filler to meet a word count. For employees on a performance improvement plan, more detailed documentation is appropriate and should be supplemented by the PIP document itself.

Employees have the right to request access to their personnel file under most provincial privacy legislation, which includes performance reviews. The standard practice is to provide the employee with a copy of the signed review at the time it is completed. This is both good HR practice and a practical safeguard: if an employee signs the review acknowledging receipt, there is no dispute later about whether they received it or what it said. Some organizations use e-signature workflows to automate this process and maintain the audit trail.

Workzoom’s Talent Suite includes configurable performance review forms, manager and employee review workflows, e-signature collection, and a documented audit trail tied to the employee’s HR record. When a review is completed, it is stored, timestamped, and linked to the employee’s profile. For organizations managing performance improvement processes or preparing documentation for potential disciplinary action, having all review history in a single retrievable location significantly reduces the administrative burden and the risk of lost documentation. Pricing is $4 CAD per employee per month, with no setup fees and no contracts.

Get insights like this in your inbox

Practical HR, payroll, and workforce tips for employers across Canada and the Caribbean. No spam, unsubscribe anytime.

You’re in! Watch your inbox.
Ready to simplify?

See Workzoom in Action

One platform for HR, workforce, payroll, and talent. $4–$16/employee/month depending on which suites you need. No setup fees, no contracts.

25+ years in business7 countries supportedNo contracts required

Get a Walkthrough

No credit cardMonth-to-month100% Canadian
Matthew Woolley

Matthew Woolley
Technical Sales Executive at Workzoom
Matthew leads marketing and sales operations at Workzoom, where he works with employers across Canada and the Caribbean on HR, payroll, and workforce management. He writes about the systems and strategies that actually move the needle for mid-market organizations.
01/01