Free Self-Evaluation Phrase Catalog | 200+ Phrases by Skill, Role & Rating
Free Self-Evaluation Phrase Catalog | 200+ Phrases by Skill, Role & Rating
This survey helps you gather consistent, skills-based input that you can turn into fair performance review phrases for HR roles. It makes “invisible HR work” visible: stakeholder trust, compliance judgment, and process quality. You get early warning signals, clearer review conversations, and a clean basis for development actions.
If you already use structured performance cycles, you can run this as a short 360 pulse after key milestones. For a ready reference on what employees experience in review cycles, align timing and comms with performance review survey questions and keep follow-up tight.
Survey questions for performance review phrases for HR roles
2.1 Closed questions (Likert scale 1–5)
Scale: 1 = Strongly disagree, 2 = Disagree, 3 = Neither, 4 = Agree, 5 = Strongly agree.
- Q1. This HR colleague is clear about priorities, even when requests compete.
- Q2. I understand what “good” looks like for this HR role in our context.
- Q3. They set realistic expectations on timelines, dependencies, and decision owners.
- Q4. They communicate trade-offs early when capacity or policies limit options.
- Q5. They document decisions and next steps so work does not get lost.
- Q6. They respond within agreed SLAs or proactively renegotiate deadlines.
- Q7. They make it easy for stakeholders to know where a request stands.
- Q8. They reduce back-and-forth by asking the right clarifying questions upfront.
- Q9. They close loops consistently (updates, outcomes, and rationale).
- Q10. Stakeholders experience them as solution-oriented, not gatekeeping.
- Q11. They deliver HR processes with few errors and predictable cycle times.
- Q12. They manage projects with clear milestones, risks, and owners.
- Q13. They spot process gaps and fix root causes, not just symptoms.
- Q14. They balance speed and quality when operations get busy.
- Q15. They handle handovers cleanly so work continues without rework.
- Q16. They build trust with managers and employees through consistent judgment.
- Q17. They coach stakeholders effectively (framing, options, consequences).
- Q18. They challenge decisions respectfully when risks or fairness issues arise.
- Q19. They manage conflicts calmly and keep conversations constructive.
- Q20. They influence outcomes without relying on hierarchy or escalation.
- Q21. They use people data appropriately to support decisions and prioritization.
- Q22. Their reporting is accurate, understandable, and used in real decisions.
- Q23. They define metrics that reflect outcomes, not just activity volume.
- Q24. They identify patterns (e.g., bottlenecks) and propose practical fixes.
- Q25. They communicate uncertainty and limitations in the data transparently.
- Q26. They handle sensitive information with strong confidentiality and discretion.
- Q27. They consider GDPR/data minimization in daily HR work and tooling choices.
- Q28. They involve the right governance partners when needed (e.g., DPO, legal, Betriebsrat).
- Q29. They apply policies consistently while considering individual context fairly.
- Q30. They keep audit trails that are clear enough to explain decisions later.
- Q31. Their hiring or workforce recommendations improve quality, not just speed.
- Q32. They strengthen candidate or employee experience through clear communication.
- Q33. They improve enablement (templates, training, comms) so teams self-serve more.
- Q34. They contribute to culture and psychological safety through respectful interactions.
- Q35. Overall, their work increases clarity, fairness, and execution quality across the business.
2.2 Optional overall / NPS-style question (0–10)
- Q36. How likely are you to recommend working with this HR colleague to another team? (0–10)
2.3 Open-ended questions
- Q37. What should this HR colleague start doing to increase their impact?
- Q38. What should they stop doing because it creates friction or risk?
- Q39. What should they continue doing because it works well?
- Q40. What is one concrete example (situation + outcome) that supports your ratings?
| Question area | Score / threshold | Recommended action | Responsible (Owner) | Target / deadline |
|---|---|---|---|---|
| Priorities & documentation (Q1–Q5) | Average <3,0 | Run a 45-minute role-clarity reset; agree top 5 recurring deliverables and a request intake rule. | HR Manager | Plan within 7 days; implemented within 21 days |
| Service & responsiveness (Q6–Q10) | Average <3,5 or ≥20% ratings of 1–2 | Define SLAs by request type; publish a simple status tracker; introduce weekly stakeholder update slot. | People Ops Lead | SLAs within 14 days; first review after 30 days |
| Execution quality (Q11–Q15) | Average <3,5 | Do a process audit on the top 2 workflows; add checklist controls and handover steps. | Process Owner (HR Ops) + HRBP Partner | Audit within 21 days; controls live within 45 days |
| Stakeholder partnering (Q16–Q20) | Average <3,5 | Coaching plan: shadow 2 partner meetings; practice “options + risks” scripting; monthly feedback check. | HR Manager | Start within 14 days; reassess in 60 days |
| People data & analytics (Q21–Q25) | Average <3,0 | Agree 3 decision metrics; standardize definitions; set a monthly reporting cadence with interpretation notes. | HR Analytics Owner | Metrics within 30 days; first monthly pack within 45 days |
| Compliance, GDPR, Betriebsrat readiness (Q26–Q30) | Any item <3,0 | Mandatory governance review: data flows, retention, access; update SOPs and run a refresher training. | DPO + HR Compliance Owner | Review within 14 days; training within 30 days |
| Enablement & experience impact (Q31–Q35) | Average <3,5 | Create 2 enablement assets (template + FAQ); test with 3 stakeholders; iterate based on feedback. | Functional Lead (TA Lead or HRBP Lead) | Draft within 21 days; re-test within 45 days |
| Overall risk signal (Q36 + comments Q37–Q40) | Q36 ≤6 or any comment indicates safety/legal risk | Escalation triage: log issue, assess urgency, define containment steps, and assign investigator. | Head of People + HR Compliance Owner | Triage within ≤24 h; action plan within 7 days |
Key takeaways
- Use question groups (Q1–Q35) to turn feedback into specific development actions.
- Trigger follow-up automatically when any area drops below Score <3,0.
- Require one concrete example (Q40) to reduce opinion-only ratings.
- Segment results by stakeholder type to spot “who experiences what”.
- Close the loop within 30 days or trust in the survey drops fast.
Definition & scope
This survey measures observable performance inputs for HR roles: execution quality, stakeholder partnership, data literacy, and governance. It is designed for 360-style raters (internal customers, peers, leaders) and works for HR Ops, Recruiters, HRBPs, and People Leads. The results support review wording, calibration, targeted coaching, and process fixes where system constraints drive performance outcomes.
When and who to survey (so the data is usable)
Collect feedback close to real work. Run it after major cycles like hiring pushes, compensation rounds, or policy rollouts. Use at least 5 raters per person if you report averages, or keep it qualitative.
If you can’t reach that rater count, treat results as manager-only input and focus on comments. For broader performance-cycle hygiene, align the pulse with your performance management cadence so actions land before the next review.
Simple process (4 steps): pick rater groups, send survey, review results with evidence, decide actions with owners.
- HR Manager selects rater groups (manager, peers, stakeholders) within 5 days of survey launch.
- People Ops sends survey and 2 reminders; close after 10 days.
- HR Manager reviews results with employee using 2 examples per low-scoring area within 14 days.
- Employee + HR Manager agree 3 actions max, each with a deadline within 21 days.
| Rater group | Best for | Minimum rater count | Anonymity rule |
|---|---|---|---|
| Line managers / leaders | Prioritization, risk judgment, role scope | 2 | Show themes only if group size ≥3 |
| Hiring managers / internal customers | Responsiveness, partnership, quality of enablement | 3 | Aggregate scores; quote comments only with redaction |
| HR peers | Handoffs, execution quality, documentation | 2 | Show averages; suppress if group size <3 |
| Employee representatives (optional) | Governance, fairness perceptions, works council interactions | 1–2 | Qualitative themes only, no attributions |
How to turn results into performance review phrases for HR roles
Use scores to pick the topic, then use comments to pick the evidence. That prevents vague feedback like “great stakeholder management” with no proof. It also protects HR from being judged on outcomes they don’t control.
Rule of thumb: only write a “strength” phrase when the area is ≥4,0 and you have 2 examples. Only write a “needs development” phrase when the area is <3,5 and you can name a fixable behavior.
Practical 5-step workflow: map scores to a domain, select 1–2 behaviors, add a business impact, then agree the next practice.
- HR Manager drafts 3 review bullets using Q-groups + evidence within 7 days of results.
- Employee adds context on constraints (capacity, tooling, approvals) within 5 days.
- HR leadership calibrates across the team using the same domains within 14 days.
- HR Manager finalizes wording and links it to goals/IDP within 21 days.
- People Ops tracks action completion rate; follow up at 30 and 60 days.
Calibration rules for performance review phrases for HR roles
HR roles attract bias because the work is cross-functional and often unpopular. Calibration makes sure two HRBPs are not rated differently just because their stakeholders are louder. Use the survey as one input, not the verdict.
Set two numeric guardrails: flag any rater variance ≥1,5 points on the same domain, and any domain average difference ≥0,7 between stakeholder groups. Investigate before final ratings lock.
Keep calibration structured: review evidence, name constraints, decide what changes next cycle.
- Facilitator (HR Director) sends a 1-page evidence pack request 7 days before calibration.
- Managers bring 2 examples per low domain and 2 per high domain to the meeting.
- Facilitator pauses on coded language; replace with observable behaviors during the session.
- People Ops logs decisions and follow-ups in a single tracker within 24 h.
- HR leadership reviews bias patterns quarterly and updates guidance within 30 days.
If you want a ready checklist of common rating errors, use the same bias language rules described in performance review biases and apply them to HR-specific feedback.
Using the survey for development plans (not just ratings)
The fastest win is turning one low-scoring domain into one practice change. Don’t create a 12-item improvement list. HR work is already context switching.
Thresholds that work: for any domain <3,5, define 1 practice change within 14 days. For any domain <3,0, add training or shadowing within 30 days. Re-run a mini pulse after 60 days to see movement.
Keep development evidence-based: link practice changes to Q-items and one measurable indicator.
- Employee proposes 2 development actions tied to one domain within 7 days.
- HR Manager approves one action and defines success criteria within 10 days.
- Peer mentor supports practice (shadowing or review) twice within 30 days.
- People Ops schedules a 60-day pulse; same Q-group only, not the full survey.
- HR Manager updates the development plan in the HR system within 7 days post-pulse.
To connect development actions to skills and levels, align domains with a role-based skills framework like an HR skills matrix, then ask for evidence that matches the expected level.
Scoring & thresholds
Use a 1–5 Likert scale from “Strongly disagree” (1) to “Strongly agree” (5). Treat Score <3,0 as critical, 3,0–3,9 as needs improvement, and ≥4,0 as strong. Convert scores into decisions by mapping each low domain to one behavior change, one owner, and one deadline, then re-check progress with a 60-day pulse.
Follow-up & responsibilities
Assign follow-up by signal strength. Very low scores and risk comments need fast triage. Medium gaps need a practical coaching plan. High scores should still produce one “keep doing” commitment so strengths stay visible.
- HR Manager reviews any domain Score <3,0 with the employee within ≤7 days.
- Head of People triages any safety/legal risk comment within ≤24 h and assigns an investigator.
- People Ops publishes an action register (no names, just themes) within 30 days.
- Functional lead (TA/People Ops/HRBP) sponsors process fixes within 45 days.
- Employee and HR Manager confirm completion of agreed actions within 60 days.
If you run surveys in a platform, keep follow-ups as tasks, not reminders in someone’s inbox. A talent platform like Sprad Growth can help automate survey sends, reminders and follow-up tasks, while keeping audit trails for who owns what by when.
Fairness & bias checks
Always review results by relevant groups before drawing conclusions. Common cuts: location, function, seniority of rater, remote vs. office, and stakeholder type (HR peer vs. hiring manager). Use minimum-group reporting of ≥5 to protect anonymity and reduce over-interpretation.
Three patterns you will see and how to react:
Pattern 1: HR Ops scores high with HR peers, low with internal customers. Action: fix request intake, SLAs, and comms cadence within 30 days.
Pattern 2: Recruiter scores high on service, low on data quality (Q21–Q25). Action: standardize funnel definitions and review them weekly for 6 weeks.
Pattern 3: HRBP scores low on “challenge respectfully” (Q18) in one business unit only. Action: check for structural constraints, leadership sponsorship, and escalation rules before labeling it a skill gap.
- People Analytics reviews group gaps ≥0,7 points and flags them within 10 days.
- HR leadership validates whether constraints explain gaps within 21 days.
- Managers rewrite any coded language into behaviors during calibration within 14 days.
- HR Manager asks for one concrete example per low domain (Q40) within 7 days.
- Head of People audits outcomes (ratings, promotions) by group after each cycle within 30 days.
Examples / use cases
Use case 1: Low “Service & responsiveness” scores for a People Ops Specialist
Situation: Q6–Q10 average is 2,9 and comments mention “no updates”. Decision: treat it as an operating model issue, not attitude. Action: People Ops Lead implements SLAs by request type and a weekly status update message. After 60 days, re-run Q6–Q10 only and check whether scores rise above 3,5.
Use case 2: HRBP gets mixed stakeholder feedback across teams
Situation: HR peers rate Q16–Q20 at 4,3, while one business unit rates 3,1. Decision: investigate constraints and stakeholder expectations before rating down. Action: HR Director joins one monthly meeting for that unit, clarifies decision rights, and agrees escalation paths. Review the same domain again after 90 days.
Use case 3: Strong compliance scores, weaker enablement impact for a People Lead
Situation: Q26–Q30 average is 4,5, but Q31–Q35 average is 3,4. Decision: keep governance as a strength, add an enablement goal. Action: People Lead ships 2 manager toolkits (FAQ + template) and tests them with 3 teams. Re-check Q33 and Q32 after the next HR cycle milestone.
Implementation & updates
Start small, then scale. A pilot gives you clean feedback on question wording, anonymity, and follow-up load. Treat the survey like a product: you maintain it, prune it, and adjust thresholds when your org matures.
Simple rollout steps: pilot in one HR sub-team, expand to HR-wide, train managers on interpretation, then review annually.
- People Ops runs a pilot with 10–20 raters across 3 HR roles within 30 days.
- HR Director reviews item clarity and removes redundant questions within 14 days post-pilot.
- HR Manager training (60 minutes) covers scoring, bias, and action planning within 45 days.
- Company-wide HR function rollout happens in the next review quarter, within 90 days.
- Annual review updates questions and thresholds based on outcomes within 30 days of cycle close.
| Metric | Target | How to measure | Owner | Review cadence |
|---|---|---|---|---|
| Participation rate | ≥70% | Completed surveys / invited raters | People Ops | Each survey close |
| Action plan completion rate | ≥80% within 60 days | Completed actions / planned actions | HR Managers | Monthly |
| Critical threshold rate | <10% domains with Score <3,0 | Count of domains below threshold | Head of People | Quarterly |
| Rater variance | <1,5 points variance per domain | Max–min rater average per domain | People Analytics | Each cycle |
| Time to follow-up | ≤14 days | Survey close to first 1:1 discussion date | HR Managers | Each cycle |
Conclusion
This survey gives you a consistent way to translate day-to-day HR impact into review-ready language: what happened, what changed, and what should happen next. You spot issues earlier because domains like responsiveness, governance, and partnering drop before bigger problems appear. You also get better conversations because you can point to specific behaviors and examples, not vibes.
To start, pick one HR team for a 30-day pilot, set up the Q1–Q35 items in your survey tool, and name owners for follow-up and analytics. Then decide your thresholds upfront (Score <3,0 and <3,5), so actions do not depend on who shouts loudest. Keep the loop tight: share themes, assign actions, and re-pulse the key domain after 60 days.
FAQ
How often should you run this survey?
Run it 1–2 times per year for stable teams, and after major HR cycles for high-change environments. A good pattern is one annual deep run (Q1–Q40) and one 60-day follow-up pulse for the lowest domain only. If you run it more often than quarterly, fatigue rises and comments get shorter, which weakens usefulness.
What should you do when scores are very low (Score <3,0)?
Treat it as a structured intervention, not a debate. First, check if the issue is scope, capacity, tooling, or unclear decision rights. Then agree on 1 behavior change and 1 operating change, each with an owner and deadline. Use Q40 to anchor on examples. Re-run only the affected domain after 60 days to see movement.
How do you handle critical comments without breaking trust?
Separate “theme sharing” from “comment policing”. Share themes with the employee and manager, redact identifying details, and focus on what can change. If a comment indicates legal or safety risk, triage within ≤24 h and document the steps taken. For privacy expectations in the EU, align handling with European Data Protection Board (EDPB) guidance and your internal governance.
How do you involve a Betriebsrat / works council in DACH?
Bring them in before you launch, not after complaints. Share the purpose (development vs. evaluation), question set, anonymity rules, and who can see what. Agree reporting thresholds (for example, no group reports under ≥5) and retention periods. Clarify that qualitative comments will be redacted and used for improvement actions, not surveillance.
How do you keep the question bank up to date over time?
Review the items once per year, right after you finish follow-ups, while lessons are fresh. Remove questions that do not drive decisions, and refine items that raters misunderstand. Keep domain structure stable (Q1–Q35) so you can compare trends. Update thresholds only if you also update manager training, otherwise teams will lose confidence in consistency.
Jürgen Ulbrich
Jürgen Ulbrich has more than a decade of experience in developing and leading high-performing teams and companies. As an expert in employee referral programs as well as feedback and performance processes, Jürgen has helped over 100 organizations optimize their talent acquisition and development strategies.
