Performance Review Examples: Specific Feedback for Managers

"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."

"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."

"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."

"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."

"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."

"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."

"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."

"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."

"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."

"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."

"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."

"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."

"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."

"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."

"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."

"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."

"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."

"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."

Expectation and evidence. The agreed goal was to grow the existing account portfolio while maintaining renewal quality. The account manager exceeded the growth target and documented how two at-risk renewals were recovered through earlier customer planning.

Conversation. The employee wants more complex accounts. The manager agrees that the renewal work supports that discussion, while noting that readiness for a larger portfolio needs a separate decision.

Next action. Review a proposed account plan with the sales director next month, then agree on scope and support. Do not imply that a promotion or compensation change has already been approved.

Expectation and evidence. The coordinator kept schedules and vendor updates current. When a supply-ordering issue recurred, they flagged it promptly, but the team had no agreed owner for the follow-up.

Employee perspective. Vendor response times made the issue hard to resolve without an approval route for an alternative supplier.

Manager perspective. The issue was flagged promptly, but no one owned the next step. The manager needs to clarify approval authority before treating the delay as an individual ownership gap.

Next action. Write the escalation route together and review the next two orders at the monthly check-in. Assess whether the new route works before setting a broader improvement target.

Expectation and evidence. The role requires timely replies and accurate handoffs. The manager identifies specific tickets where a handoff lacked an owner or next action, along with the standard that applied at the time.

Conversation. Ask the employee what happened, including whether workload, training or another support need affected the work. Record their response fairly. Keep any confidential accommodation information in the appropriate process, not in a general review.

Next action. Agree on a handoff checklist, training support and a follow-up date. If formal discipline is contemplated, involve HR and obtain jurisdiction-specific advice rather than treating this example as a ready-made plan.