Employee Comments on Appraisal: 8 Practical Examples
Strong employee comments on appraisal describe observable evidence, impact, context and a constructive next step. UK evidence shows why this matters: a 2013 survey found that 65% of 2,000 workers actively disliked annual performance reviews, while 66% didn't believe yearly reviews accurately appraised their work. ACAS appraisal guidance
What makes an appraisal comment constructive? It explains what happened, why it mattered and what should happen next. “Excellent team player” is pleasant but vague. “You brought operations and engineering together to resolve the production issue, which protected the delivery plan. Continue documenting the decision so the team can reuse the approach” gives the employee something credible to understand and repeat.
The eight examples below cover competencies, outcomes, behaviours, development, multiple perspectives, talent decisions, self-reflection and context. They aren't mutually exclusive. A fair review may combine all of them, provided the wording remains evidence-based and avoids personality labels, discriminatory assumptions or unnecessary personal detail.
For UK and EU organisations, employee comments on appraisal also need controlled handling. Appraisal records should be confidential, access-limited and retained only for a documented purpose under UK GDPR principles. European Data Protection Supervisor evaluation guidance says employees must have the possibility to add comments directly to relevant evaluation reports.
HRManagement365.com is a UK and EU HR solution powered by Hubdrive and Microsoft technology, built in Power Platform, Dynamics 365 and Dataverse. HRManagement365 extends Hubdrive and Microsoft with its own expertise, integrations, customisations, workflows and HR applications. Standard configuration should be distinguished from customer-specific development, which can address processes that aren't covered by standard functionality.
Competency-based comments assess an employee against the skills and behaviours required for the role, rather than relying on a manager's general impression. They work best when the framework describes observable actions at each level. “Shows leadership” invites inconsistent interpretation. “Allocates work clearly, explains decisions and supports colleagues when priorities change” gives managers and employees a shared reference point.
A useful comment should connect the competency to evidence:
Practical rule: Name the behaviour, give the work context and explain the capability the employee should strengthen next.
For a production engineer, a manager might write:
“You applied the quality-control procedure consistently during the equipment changeover and identified a recurring fault before it reached final inspection. Your technical diagnosis was strong. The next step is to record the troubleshooting method in the team knowledge base and coach a colleague through it.”
That wording recognises competence without turning one event into a permanent label. It also separates technical ability from development action.
Keep each role framework manageable. Use a small group of core competencies, define behavioural indicators clearly and train managers before launch. A competency record becomes less useful when every role has an overly detailed catalogue that managers complete mechanically.
HRManagement365 can help standardise competency fields, connect assessments with training records and support development workflows through Power Platform and Dynamics 365. Power BI can then help HR identify recurring capability themes, provided the organisation has configured the relevant data and reporting. For practical follow-through, managers can connect the comment to a training plan for employees, a mentoring action or a supervised assignment.
Avoid using competencies to penalise different but effective working styles. Communication, leadership and collaboration criteria should describe outcomes and observable conduct, not preferences such as being highly extroverted, always available or constantly vocal in meetings.
2. Goal Achievement and Objectives Comments
Goal comments should show the relationship between an agreed objective, the work completed and the result achieved. They shouldn't reduce performance to a single output measure. Quality, risk, collaboration and changes in business circumstances may all affect how an objective should be interpreted.
A strong employee comment might say:
“I completed the customer-data migration within the agreed delivery window and created a validation process for the handover. The project met its operational objective, although integration work took longer than planned because the source data required additional cleansing. For the next cycle, I recommend agreeing data-quality criteria at project initiation.”
The sentence gives evidence, acknowledges a barrier and proposes a process improvement. It doesn't claim that every delay was outside the employee's control.
Managers should avoid setting too many competing objectives. Include both individual delivery and contribution to wider team priorities where collaboration matters. Output goals should sit alongside quality, compliance or capability objectives, so employees aren't encouraged to hit a target by creating avoidable risk.
At review time, compare the comment with the original objective and the records that support it. Power BI can present progress from connected systems, while integrations with Dynamics 365 Finance & Operations, project tools or Business Central may help validate financial, operational or delivery information where that integration has been implemented.
Context belongs in the comment, not in an informal conversation that disappears. If a role changed materially, resources were withdrawn or an external event disrupted delivery, record the effect and explain what the employee did within those constraints. Don't alter the meaning of the goal after the event.
For managers, a useful structure is:
Objective: State the agreed outcome in plain language.
Evidence: Refer to the deliverable, milestone or verified record.
Impact: Explain the effect on customers, colleagues, cost, quality or risk.
Next step: Agree what should continue, change or be reviewed.
HRManagement365 can support objective records, review stages, approvals and employee comments. The exact data connection and workflow will depend on the customer's processes, with custom Power Apps, Power Automate flows or integrations available where standard configuration isn't enough.
3. Behavioural and Values-Based Comments
A results-only review can miss how work was delivered. Behavioural and values-based comments add that dimension by examining collaboration, integrity, customer focus, inclusion, innovation or responsible decision-making. The risk is that values become vague cultural preferences, so each value needs behavioural descriptors.
Compare these two comments:
“You don't demonstrate ownership.”
“When the supplier missed the agreed handover, you notified the project group, proposed two recovery options and kept stakeholders updated until the revised plan was approved.”
The second comment is more defensible because it describes conduct. It also gives the employee a behaviour worth repeating.
A UK technology business might assess how an engineer handles customer-impacting incidents. A relevant comment could be:
“You explained the service issue to the customer in clear language, avoided speculation and coordinated the technical response through the agreed process. This protected trust during a difficult interaction. Continue using the incident summary template so that learning is shared across the support team.”
For constructive criticism, describe the observable action and its effect without assigning motive. “You were dismissive” may be accurate as an experience but needs supporting detail. “During the design discussion, you interrupted two colleagues and the meeting ended before their alternatives were considered” creates a basis for dialogue.
Values frameworks also need an inclusion check. A preference for rapid verbal debate may disadvantage neurodivergent employees, people working across languages or colleagues in hybrid roles. Assess whether the person achieved the expected outcome and treated others appropriately, not whether they match one manager's preferred style.
HRManagement365 can provide configurable appraisal forms and workflows. A customer may also choose to develop a custom Power App for values evidence, peer input or approval controls. Where feedback comes from several perspectives, restrict access and avoid including unnecessary personal information. CIPD's performance feedback evidence review explains that employees' perceptions of fairness and usefulness affect whether feedback is accepted and acted upon.
4. Developmental Comments
Developmental comments are forward-looking. They recognise current strengths, identify a capability that would support the employee's aims and convert that observation into a realistic development action. They shouldn't imply that promotion is guaranteed or that a development need is a personal deficiency.
Instead of writing, “You lack stakeholder-management skills”, write:
“To prepare for a role involving larger client accounts, developing your stakeholder-management capability will be valuable. You handled internal coordination effectively on the current project. Next period, lead one client planning meeting with preparation support from your manager, then review the outcome together.”
The wording protects dignity while remaining clear. It also defines what development looks like in practice.
For an early-career analyst, the comment could connect technical strength with a stretch opportunity:
“Your analysis is accurate and well structured. The next growth area is explaining recommendations to non-specialists. Present the next findings summary to the operations group, ask for written feedback and include the learning in your development review.”
Formal courses are only one route. Mentoring, job shadowing, project ownership, coaching and structured practice may be more relevant to the capability being developed. Record the method, owner, support required and review point rather than adding “attend training” to a plan.
HRManagement365 can connect performance comments with skills, training, certifications and development records where those modules and fields have been configured. Power Automate may support reminders or approval steps, while Power BI can report on development activity. HRManagement365 can also build customer-specific workflows where a standard development process doesn't reflect the organisation's career architecture.
Use career language carefully. A manager can say that a capability would support a possible future role, but shouldn't promise a promotion that depends on business need, vacancies or a fair selection process. Employees should understand what evidence would demonstrate readiness and when the discussion will be revisited. Guidance on making appraisal conversations more useful is available in this overview of appraisals at work.
5. 360-Degree Feedback Comments
360-degree comments bring together relevant perspectives from managers, peers, direct reports, customers or project partners. They can reveal patterns that a line manager can't see, particularly around leadership, collaboration and the experience of working with someone across team boundaries.
The value comes from synthesis, not from pasting every comment into the appraisal. A manager might write:
“Feedback from colleagues consistently recognises your willingness to share specialist knowledge and your calm approach during incidents. Several responses also describe delayed delegation, which can leave colleagues unclear about ownership. Agree a delegation plan at the start of each project and revisit it in the next one-to-one.”
This approach protects the discussion from becoming a contest between individual opinions. Conflicting feedback should be explored as a pattern, a context issue or a prompt for further evidence, rather than treated as proof that one anonymous statement is correct.
Before launch, explain the purpose and the confidentiality model. Raters should know how their input will be used, who can see it and whether comments will be aggregated. Avoid using 360-degree feedback as the sole basis for pay or promotion decisions if doing so would undermine candour. A development-focused process is often easier for employees to trust.
HRManagement365's performance-management capability can support 360-degree and continuous-feedback processes, including one-to-ones, appraisal comments and ratings, subject to the configured solution. The organisation should define its own question set, rater rules, access controls and retention approach. Reporting in HR can help teams think through how feedback themes should be presented to managers and HR.
A practical 360-degree comment should identify the theme, explain the impact and agree an action. It shouldn't expose a colleague unnecessarily or reproduce sensitive information that isn't needed for the development conversation. For another perspective on prompt design, see these 360 feedback prompts.
6. Performance and Potential Matrix Comments
A performance and potential discussion can help HR make differentiated development and succession decisions, but it carries a serious fairness risk. A matrix is a decision aid, not an identity label. “High potential” can become shorthand for similarity to current leaders unless potential is defined through observable evidence and reviewed by more than one decision-maker.
A balanced comment might read:
“You delivered the agreed operational outcomes and built strong relationships across the service team. Your readiness for a broader role is developing, particularly in strategic planning and influencing outside your immediate function. A cross-functional project would provide evidence for the next career discussion.”
That is more useful than writing “future leader”. It describes present performance, a capability gap and an opportunity to gather evidence.
Performance and potential should be assessed separately. A person may perform strongly in their current role but want to deepen technical expertise rather than move into management. Another employee may show learning agility but need support to meet current expectations. Neither conclusion should be hidden behind a single grid position.
Use multiple inputs where available, such as objectives, competency evidence, employee reflection and feedback themes. HRManagement365 can centralise those records and support talent workflows, while Power BI can help HR review patterns by role, location or business area. Any reporting should be access-controlled and interpreted carefully. A distribution pattern may reflect inconsistent manager calibration rather than an objective view of talent.
Avoid writing the matrix category into the employee's permanent narrative unless there is a clear reason and appropriate governance. Explain the current development decision instead:
Current contribution: What evidence supports the performance assessment?
Future capability: What behaviour or skill indicates potential?
Development need: What must improve before a wider role is considered?
Action: What assignment, coaching or support will create useful evidence?
Review decisions periodically because roles, business priorities and employee circumstances change. Don't allow an informal talent label to influence access to opportunities without transparent criteria and a route for challenge.
7. Self-Assessment and Employee-Reflective Comments
Self-assessment gives employees a formal opportunity to record achievements, explain barriers, identify support needs and state development priorities before the manager completes the review. It can reveal work that is less visible in management reporting, especially in hybrid roles or cross-functional projects.
A useful employee comment might say:
“I completed the process-mapping work and supported the implementation team during the transition. My strongest contribution was translating operational feedback into changes the project team could use. I found it harder to protect development time during peak workload, so I want to agree a learning plan and raise capacity concerns earlier.”
That comment is confident without being inflated. It names contribution, learning and a practical adjustment.
Managers should read the self-assessment before forming a final view. A difference between employee and manager ratings isn't automatically defensiveness or poor self-awareness. It may indicate unclear objectives, missing evidence, different access to information or a genuine coaching opportunity. The right response is curiosity: “Help me understand how you assessed this result” is more productive than “You have rated yourself too highly.”
Useful prompts include:
Contribution: Which work had the clearest impact, and what evidence supports that?
Challenge: What made delivery harder than expected?
Support: What should your manager or team change?
Development: Which capability would improve your effectiveness?
Future focus: What work would you like to experience next?
HRManagement365 can capture employee comments, manager responses, objectives and approvals in a connected appraisal process. Employee access can be provided through familiar Microsoft interfaces such as Teams or browser-based self-service, depending on the configured implementation. Customer-specific prompts, escalation routes or integrations can be developed where standard fields don't meet the process.
Employees should avoid putting sensitive health information or accusations into a general comment field. They can record the work impact factually and use the appropriate confidential HR or occupational-health route for personal details. Self-assessment is a working document for a fair conversation, not a substitute for evidence or a place to make unsupported claims. A separate new hire experience guide also illustrates why structured employee input can improve lifecycle conversations beyond the annual review.
8. Contextual and Circumstantial Comments
Contextual comments prevent managers from judging results in a vacuum. They acknowledge organisational change, resource constraints, altered priorities, system disruption or other relevant circumstances, while still examining what the employee did and what accountability remains.
The strongest wording separates facts from excuses:
“The team operated with reduced resource during the implementation period, and the original delivery sequence changed after the system dependency was identified. You raised the issue promptly, protected the highest-risk work and kept stakeholders informed. The original timetable wasn't met, but your response reduced disruption. For the next project, flag dependency risks during planning and agree an escalation point.”
This recognises context without removing responsibility. It also avoids recording unnecessary personal information. If an employee's health, family situation or disability affects work, document only what the appraisal process needs and use the appropriate confidential support route for further detail.
Context should be comparable across employees. If two people faced the same operational disruption, managers should apply consistent principles when evaluating outcomes. HRManagement365 can provide structured context fields, adjustment notes, approvals and audit history, subject to the customer's configuration and governance requirements.
A UK employee might be assessed during a merger, where role ambiguity and system changes affected delivery. An EU team might need to account for different local working arrangements or regulatory processes across jurisdictions. Those differences should be documented objectively, without assuming that an employee's location or personal circumstances explain performance.
The comment should answer four questions:
What changed: Identify the business or operational condition.
What was within control: Describe the employee's choices and actions.
What was achieved: Assess the outcome against the adjusted reality.
What happens next: Agree a support, improvement or resilience action.
Avoid vague phrases such as “because of personal issues” or “due to the difficult year”. They don't help the employee, the next manager or an HR reviewer understand the decision. UK records guidance states that performance-related records should be kept for seven years from the end of the performance year, then reviewed for a further three years where operationally relevant, before disposal when no longer needed. UK Government human resources records guidance
📊 Fairer ratings, transparent rationale for adjustments, wellbeing support
💡 Document specifics objectively, distinguish control vs external factors, protect privacy
Turn Better Comments into Better Conversations
The best employee comments on appraisal follow a simple discipline. Anchor the statement in evidence, describe the impact, acknowledge relevant context, use respectful language and finish with a specific next step. A comment should help someone understand what to continue, what to change and when the conversation will be revisited.
The eight approaches serve different purposes, but strong reviews often combine them:
Competencies clarify the skills and behaviours required for a role.
Goals show delivery against agreed business outcomes.
Behaviours and values explain how results were achieved.
Development converts feedback into learning and career action.
360-degree feedback adds relevant perspectives beyond the line manager.
Performance and potential supports careful succession discussions.
Self-assessment gives the employee a meaningful voice.
Contextual comments protect fairness when circumstances affect results.
UK evidence continues to show a credibility problem. In a 2019 survey of 2,000 UK employees in organisations with 50 or more staff, the average feedback-quality score was 6.32 out of 10, 33% rated their feedback 5 out of 10 or lower, and 10% said they never received feedback. PeopleSense survey evidence This makes follow-through as important as wording. A polished comment that nobody revisits won't improve performance.
Before submitting a review, managers should check that each comment is:
Specific: Does it refer to an observable action, deliverable or conversation?
Fair: Have objectives, evidence and relevant circumstances been considered consistently?
Inclusive: Does it avoid assumptions about personality, disability, culture, caring responsibilities or working style?
Confidential: Does it exclude unnecessary health, personal or third-party information?
Consistent: Would another manager understand the standard and reasoning?
Actionable: Is there an owner, support action or check-in date?
HRManagement365 can centralise performance records, objectives, feedback, development plans and approvals through Power Platform, Dynamics 365 and Dataverse. Depending on the implementation, it can connect with Microsoft 365, Teams, Power Automate and Power BI, and support links with Business Central and Finance & Operations. Standard functionality should be separated from custom development. HRManagement365 can provide implementation and consultancy, custom workflows and approval processes, integrations, custom HR applications, employee lifecycle automation, reporting and Power BI services.
The practical objective isn't to produce longer appraisal forms. It's to create a reliable record that the employee can understand, the manager can act on and HR can govern. Use the comment as the start of a conversation, then record the agreed action and return to it.
For managers who want to strengthen the conversation itself, these active listening techniques can support a more balanced exchange.
Speak to an HRManagement365 specialist. Discover how HRManagement365, powered by Hubdrive and Microsoft, can help improve and automate your HR processes across the UK and EU. Phone +44 1522 508096 today. Send us a message: https://www.hrmanagement365.com/contact/
HRManagement365 can structure appraisal comments around objectives, competencies, feedback, development actions and employee reflection, with workflows and reporting configured for your organisation. Visit HR Management 365 to discuss how its Microsoft Power Platform, Dynamics 365 and Dataverse-based HR solution can support fairer, more actionable performance conversations.
Chris PicklesDirector | Dynamics 365, Power Platform & HR Solutions Architect
I help HR leaders get off the admin hamster wheel with a Dynamics-based HR Management solution built on Hubdrive.
HRManagement365 gives organisations a flexible HR platform within the Microsoft ecosystem that can be easily customised around the way they already work — rather than forcing teams into rigid, one-size-fits-all processes.
It can be tailored to your HR workflows, integrated with Microsoft Dynamics 365 Business Central (BC) and Finance & Operations (F&O), and extended with Microsoft Power Platform to automate processes and connect HR more closely with the wider business.
For employees, the experience stays familiar. They can interact with HR processes through the Microsoft tools they already know and use every day, including Teams, Outlook, Word and Power BI, helping drive adoption without introducing another unfamiliar system.
The goal is simple: less manual admin, better-connected processes and an HR solution that fits your organisation.
If you’re using Microsoft Dynamics and want HR to work as part of the same ecosystem, ask me about HRManagement365.
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
Employee Comments on Appraisal: 8 Practical Examples
Strong employee comments on appraisal describe observable evidence, impact, context and a constructive next step. UK evidence shows why this matters: a 2013 survey found that 65% of 2,000 workers actively disliked annual performance reviews, while 66% didn't believe yearly reviews accurately appraised their work. ACAS appraisal guidance
What makes an appraisal comment constructive? It explains what happened, why it mattered and what should happen next. “Excellent team player” is pleasant but vague. “You brought operations and engineering together to resolve the production issue, which protected the delivery plan. Continue documenting the decision so the team can reuse the approach” gives the employee something credible to understand and repeat.
The eight examples below cover competencies, outcomes, behaviours, development, multiple perspectives, talent decisions, self-reflection and context. They aren't mutually exclusive. A fair review may combine all of them, provided the wording remains evidence-based and avoids personality labels, discriminatory assumptions or unnecessary personal detail.
For UK and EU organisations, employee comments on appraisal also need controlled handling. Appraisal records should be confidential, access-limited and retained only for a documented purpose under UK GDPR principles. European Data Protection Supervisor evaluation guidance says employees must have the possibility to add comments directly to relevant evaluation reports.
HRManagement365.com is a UK and EU HR solution powered by Hubdrive and Microsoft technology, built in Power Platform, Dynamics 365 and Dataverse. HRManagement365 extends Hubdrive and Microsoft with its own expertise, integrations, customisations, workflows and HR applications. Standard configuration should be distinguished from customer-specific development, which can address processes that aren't covered by standard functionality.
Table of Contents
1. Competency-Based Performance Comments
Competency-based comments assess an employee against the skills and behaviours required for the role, rather than relying on a manager's general impression. They work best when the framework describes observable actions at each level. “Shows leadership” invites inconsistent interpretation. “Allocates work clearly, explains decisions and supports colleagues when priorities change” gives managers and employees a shared reference point.
A useful comment should connect the competency to evidence:
For a production engineer, a manager might write:
That wording recognises competence without turning one event into a permanent label. It also separates technical ability from development action.
Keep each role framework manageable. Use a small group of core competencies, define behavioural indicators clearly and train managers before launch. A competency record becomes less useful when every role has an overly detailed catalogue that managers complete mechanically.
HRManagement365 can help standardise competency fields, connect assessments with training records and support development workflows through Power Platform and Dynamics 365. Power BI can then help HR identify recurring capability themes, provided the organisation has configured the relevant data and reporting. For practical follow-through, managers can connect the comment to a training plan for employees, a mentoring action or a supervised assignment.
Avoid using competencies to penalise different but effective working styles. Communication, leadership and collaboration criteria should describe outcomes and observable conduct, not preferences such as being highly extroverted, always available or constantly vocal in meetings.
2. Goal Achievement and Objectives Comments
Goal comments should show the relationship between an agreed objective, the work completed and the result achieved. They shouldn't reduce performance to a single output measure. Quality, risk, collaboration and changes in business circumstances may all affect how an objective should be interpreted.
A strong employee comment might say:
The sentence gives evidence, acknowledges a barrier and proposes a process improvement. It doesn't claim that every delay was outside the employee's control.
Managers should avoid setting too many competing objectives. Include both individual delivery and contribution to wider team priorities where collaboration matters. Output goals should sit alongside quality, compliance or capability objectives, so employees aren't encouraged to hit a target by creating avoidable risk.
At review time, compare the comment with the original objective and the records that support it. Power BI can present progress from connected systems, while integrations with Dynamics 365 Finance & Operations, project tools or Business Central may help validate financial, operational or delivery information where that integration has been implemented.
Context belongs in the comment, not in an informal conversation that disappears. If a role changed materially, resources were withdrawn or an external event disrupted delivery, record the effect and explain what the employee did within those constraints. Don't alter the meaning of the goal after the event.
For managers, a useful structure is:
HRManagement365 can support objective records, review stages, approvals and employee comments. The exact data connection and workflow will depend on the customer's processes, with custom Power Apps, Power Automate flows or integrations available where standard configuration isn't enough.
3. Behavioural and Values-Based Comments
A results-only review can miss how work was delivered. Behavioural and values-based comments add that dimension by examining collaboration, integrity, customer focus, inclusion, innovation or responsible decision-making. The risk is that values become vague cultural preferences, so each value needs behavioural descriptors.
Compare these two comments:
The second comment is more defensible because it describes conduct. It also gives the employee a behaviour worth repeating.
A UK technology business might assess how an engineer handles customer-impacting incidents. A relevant comment could be:
For constructive criticism, describe the observable action and its effect without assigning motive. “You were dismissive” may be accurate as an experience but needs supporting detail. “During the design discussion, you interrupted two colleagues and the meeting ended before their alternatives were considered” creates a basis for dialogue.
Values frameworks also need an inclusion check. A preference for rapid verbal debate may disadvantage neurodivergent employees, people working across languages or colleagues in hybrid roles. Assess whether the person achieved the expected outcome and treated others appropriately, not whether they match one manager's preferred style.
HRManagement365 can provide configurable appraisal forms and workflows. A customer may also choose to develop a custom Power App for values evidence, peer input or approval controls. Where feedback comes from several perspectives, restrict access and avoid including unnecessary personal information. CIPD's performance feedback evidence review explains that employees' perceptions of fairness and usefulness affect whether feedback is accepted and acted upon.
4. Developmental Comments
Developmental comments are forward-looking. They recognise current strengths, identify a capability that would support the employee's aims and convert that observation into a realistic development action. They shouldn't imply that promotion is guaranteed or that a development need is a personal deficiency.
Instead of writing, “You lack stakeholder-management skills”, write:
The wording protects dignity while remaining clear. It also defines what development looks like in practice.
For an early-career analyst, the comment could connect technical strength with a stretch opportunity:
Formal courses are only one route. Mentoring, job shadowing, project ownership, coaching and structured practice may be more relevant to the capability being developed. Record the method, owner, support required and review point rather than adding “attend training” to a plan.
HRManagement365 can connect performance comments with skills, training, certifications and development records where those modules and fields have been configured. Power Automate may support reminders or approval steps, while Power BI can report on development activity. HRManagement365 can also build customer-specific workflows where a standard development process doesn't reflect the organisation's career architecture.
Use career language carefully. A manager can say that a capability would support a possible future role, but shouldn't promise a promotion that depends on business need, vacancies or a fair selection process. Employees should understand what evidence would demonstrate readiness and when the discussion will be revisited. Guidance on making appraisal conversations more useful is available in this overview of appraisals at work.
5. 360-Degree Feedback Comments
360-degree comments bring together relevant perspectives from managers, peers, direct reports, customers or project partners. They can reveal patterns that a line manager can't see, particularly around leadership, collaboration and the experience of working with someone across team boundaries.
The value comes from synthesis, not from pasting every comment into the appraisal. A manager might write:
This approach protects the discussion from becoming a contest between individual opinions. Conflicting feedback should be explored as a pattern, a context issue or a prompt for further evidence, rather than treated as proof that one anonymous statement is correct.
Before launch, explain the purpose and the confidentiality model. Raters should know how their input will be used, who can see it and whether comments will be aggregated. Avoid using 360-degree feedback as the sole basis for pay or promotion decisions if doing so would undermine candour. A development-focused process is often easier for employees to trust.
HRManagement365's performance-management capability can support 360-degree and continuous-feedback processes, including one-to-ones, appraisal comments and ratings, subject to the configured solution. The organisation should define its own question set, rater rules, access controls and retention approach. Reporting in HR can help teams think through how feedback themes should be presented to managers and HR.
A practical 360-degree comment should identify the theme, explain the impact and agree an action. It shouldn't expose a colleague unnecessarily or reproduce sensitive information that isn't needed for the development conversation. For another perspective on prompt design, see these 360 feedback prompts.
6. Performance and Potential Matrix Comments
A performance and potential discussion can help HR make differentiated development and succession decisions, but it carries a serious fairness risk. A matrix is a decision aid, not an identity label. “High potential” can become shorthand for similarity to current leaders unless potential is defined through observable evidence and reviewed by more than one decision-maker.
A balanced comment might read:
That is more useful than writing “future leader”. It describes present performance, a capability gap and an opportunity to gather evidence.
Performance and potential should be assessed separately. A person may perform strongly in their current role but want to deepen technical expertise rather than move into management. Another employee may show learning agility but need support to meet current expectations. Neither conclusion should be hidden behind a single grid position.
Use multiple inputs where available, such as objectives, competency evidence, employee reflection and feedback themes. HRManagement365 can centralise those records and support talent workflows, while Power BI can help HR review patterns by role, location or business area. Any reporting should be access-controlled and interpreted carefully. A distribution pattern may reflect inconsistent manager calibration rather than an objective view of talent.
Avoid writing the matrix category into the employee's permanent narrative unless there is a clear reason and appropriate governance. Explain the current development decision instead:
Review decisions periodically because roles, business priorities and employee circumstances change. Don't allow an informal talent label to influence access to opportunities without transparent criteria and a route for challenge.
7. Self-Assessment and Employee-Reflective Comments
Self-assessment gives employees a formal opportunity to record achievements, explain barriers, identify support needs and state development priorities before the manager completes the review. It can reveal work that is less visible in management reporting, especially in hybrid roles or cross-functional projects.
A useful employee comment might say:
That comment is confident without being inflated. It names contribution, learning and a practical adjustment.
Managers should read the self-assessment before forming a final view. A difference between employee and manager ratings isn't automatically defensiveness or poor self-awareness. It may indicate unclear objectives, missing evidence, different access to information or a genuine coaching opportunity. The right response is curiosity: “Help me understand how you assessed this result” is more productive than “You have rated yourself too highly.”
Useful prompts include:
HRManagement365 can capture employee comments, manager responses, objectives and approvals in a connected appraisal process. Employee access can be provided through familiar Microsoft interfaces such as Teams or browser-based self-service, depending on the configured implementation. Customer-specific prompts, escalation routes or integrations can be developed where standard fields don't meet the process.
Employees should avoid putting sensitive health information or accusations into a general comment field. They can record the work impact factually and use the appropriate confidential HR or occupational-health route for personal details. Self-assessment is a working document for a fair conversation, not a substitute for evidence or a place to make unsupported claims. A separate new hire experience guide also illustrates why structured employee input can improve lifecycle conversations beyond the annual review.
8. Contextual and Circumstantial Comments
Contextual comments prevent managers from judging results in a vacuum. They acknowledge organisational change, resource constraints, altered priorities, system disruption or other relevant circumstances, while still examining what the employee did and what accountability remains.
The strongest wording separates facts from excuses:
This recognises context without removing responsibility. It also avoids recording unnecessary personal information. If an employee's health, family situation or disability affects work, document only what the appraisal process needs and use the appropriate confidential support route for further detail.
Context should be comparable across employees. If two people faced the same operational disruption, managers should apply consistent principles when evaluating outcomes. HRManagement365 can provide structured context fields, adjustment notes, approvals and audit history, subject to the customer's configuration and governance requirements.
A UK employee might be assessed during a merger, where role ambiguity and system changes affected delivery. An EU team might need to account for different local working arrangements or regulatory processes across jurisdictions. Those differences should be documented objectively, without assuming that an employee's location or personal circumstances explain performance.
The comment should answer four questions:
Avoid vague phrases such as “because of personal issues” or “due to the difficult year”. They don't help the employee, the next manager or an HR reviewer understand the decision. UK records guidance states that performance-related records should be kept for seven years from the end of the performance year, then reviewed for a further three years where operationally relevant, before disposal when no longer needed. UK Government human resources records guidance
8-Point Comparison: Employee Appraisal Comments
Turn Better Comments into Better Conversations
The best employee comments on appraisal follow a simple discipline. Anchor the statement in evidence, describe the impact, acknowledge relevant context, use respectful language and finish with a specific next step. A comment should help someone understand what to continue, what to change and when the conversation will be revisited.
The eight approaches serve different purposes, but strong reviews often combine them:
UK evidence continues to show a credibility problem. In a 2019 survey of 2,000 UK employees in organisations with 50 or more staff, the average feedback-quality score was 6.32 out of 10, 33% rated their feedback 5 out of 10 or lower, and 10% said they never received feedback. PeopleSense survey evidence This makes follow-through as important as wording. A polished comment that nobody revisits won't improve performance.
Before submitting a review, managers should check that each comment is:
HRManagement365 can centralise performance records, objectives, feedback, development plans and approvals through Power Platform, Dynamics 365 and Dataverse. Depending on the implementation, it can connect with Microsoft 365, Teams, Power Automate and Power BI, and support links with Business Central and Finance & Operations. Standard functionality should be separated from custom development. HRManagement365 can provide implementation and consultancy, custom workflows and approval processes, integrations, custom HR applications, employee lifecycle automation, reporting and Power BI services.
The practical objective isn't to produce longer appraisal forms. It's to create a reliable record that the employee can understand, the manager can act on and HR can govern. Use the comment as the start of a conversation, then record the agreed action and return to it.
For managers who want to strengthen the conversation itself, these active listening techniques can support a more balanced exchange.
Speak to an HRManagement365 specialist. Discover how HRManagement365, powered by Hubdrive and Microsoft, can help improve and automate your HR processes across the UK and EU. Phone +44 1522 508096 today. Send us a message: https://www.hrmanagement365.com/contact/
HRManagement365 can structure appraisal comments around objectives, competencies, feedback, development actions and employee reflection, with workflows and reporting configured for your organisation. Visit HR Management 365 to discuss how its Microsoft Power Platform, Dynamics 365 and Dataverse-based HR solution can support fairer, more actionable performance conversations.
Related Posts
10 Incentives for Employees That Actually Work
The most popular advice about incentives for employees is to put more money on the table. Cash matters, but it isn't automatically
Time and Attendance Systems: A UK HR Guide
The most common advice about time and attendance systems is also the least useful: install a clocking terminal, capture every minute, and