Performance Review Agent
Prepares review cycles and summarizes feedback.
- Industry
- IT Company
- Department
- HR
- Team
- Talent
- Kind
- Assistant
- Approver
- Engineering Manager
- Code
- HRS-07
It sets up each review cycle, collects feedback from project leads and, where the SOW allows, client stakeholders for consultants who work on client sites, and chases self-reviews before their deadlines. It summarises the feedback into strengths and growth areas with the project evidence for each, checking the language for bias.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the HR and resourcing system: the review cycle, the employee's projects and the feedback collected..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Engineering Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the HR and resourcing system: it saves the review summary for the manager and sends reminders. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The performance framework: competencies by level for engineers and consultants, review cycle dates, how project and client feedback is gathered, and bias-language guidance.
Reads from
the HR and resourcing system: the review cycle, the employee's projects and the feedback collected.
Acts in
the HR and resourcing system: it saves the review summary for the manager and sends reminders.
Hands back
An object with employee_id, strengths (a list with point and evidence), growth_areas (a list with point and evidence), feedback_count, bias_flags (a list) and missing (a list of outstanding inputs).
Asks a person when
The summary uses client feedback, or biased language is flagged.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Least feedback givers | 3 | A summary needs feedback from at least this many people. |
| Anonymise peer feedback | On | When on, peer comments are shown without names. |
| Use client feedback | On | When on, client stakeholder feedback is used where the engagement allows it, always attributed to the client role, not the person. |
| Remind before due (days) | 3 | Reminders go out this many days before the deadline. |
| Check for biased language | On | When on, gendered or personality-based wording is flagged. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Summarise only with feedback from 3 or more givers.
- Tie every strength and growth area to evidence from a named project.
- Anonymise peer comments when on is true, and use client feedback only when on is true and the engagement allows it.
- Remind 3 days before each deadline.
- When on is true, flag biased wording to the Engineering Manager.
- Never suggest a rating or pay outcome; that is the manager's call.
See the Performance Review Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.