
Performance review assembly from the work that actually happened
Reviews get written from the last few weeks and whatever the manager remembers. An agent assembles the cycle’s actual record, every line linked to its source, and stops there. The rating, the words and the conversation stay with the manager.
The short answer
An agent prepares a performance review by gathering the cycle's actual record for each person: the work they shipped, the goals set last cycle, and the feedback already written down, each line linked to where it came from.
It writes no rating and no judgment. The manager reads the packet, decides, writes the review and holds the conversation.
Why do reviews end up describing the last few weeks?
Review season arrives and the manager has a blank form and a memory that favours whatever happened recently. The project that went well in the spring is half forgotten. The goals agreed last cycle sit in a document nobody reopened. The employee's own summary arrives the night before, and the manager has no time to check it against anything. So the review rests on recollection, and both sides can feel it.
Who is this for?
A manager or people lead at a company that has outgrown writing reviews from memory but has no HR team building packets for each manager. It suits teams whose work leaves a record in project tools, tickets or documents. It is not monitoring software, and it reads nothing about how people spend their time minute to minute.
What changes when the record is assembled first?
| Part of the review | Written from memory | With an assembled record |
|---|---|---|
| What the cycle covered | The last few weeks, mostly | The whole cycle, in order |
| Last cycle's goals | Remembered, or skipped | Listed, with the work recorded against each |
| Feedback | Whatever the manager recalls | The notes already written, with who wrote them and when |
| The employee's view | A summary nobody checks | Their self-review beside the record |
| The rating | The manager's | Still the manager's, and only the manager's |
How it works, step by step
The agent assembles and cites. The manager judges. Nothing in the packet is a verdict about the person.
Agree the sources first
Gather the cycle's work
Set it against last cycle's goals
Add the written feedback and the self-review
Human gate: the manager rates, writes and decides
Let the employee correct the record
Keep the packet with the review
What does the agent never do in a review?
Rate, rank or compare people
The packet has no score and no ranking.
Write judgments. It describes recorded work. Words like strong, weak, exceeds or misses are the manager's.
Watch people
It reads the sources you named, never activity logs, keystrokes or private messages.
Touch pay
Compensation and promotion stay entirely with the manager and the business.
Collect more than it needs. Keeping the packet to the named sources is a privacy choice. NIST offers its Privacy Framework as a voluntary tool for organizations to identify and manage privacy risk while protecting individuals' privacy.
Where this fits
A review cycle is one repeatable process, the territory of Tier 1, Automate a Workflow. The readiness checklist is the quickest test of whether your goals and records are written down well enough to assemble. Running it alongside your current cycle first, in shadow mode, shows managers what the packet adds before they rely on it. For the agent's own governance, NIST presents its AI Risk Management Framework as voluntary guidance for building trustworthiness into the design, use and evaluation of AI systems. Project records that feed the packet are kept current by job and project status reporting. The full list is in the use case library.
How does a review packet differ from a status report?
| Question | Status report | Review packet |
|---|---|---|
| What it covers | Where work stands now | What one person delivered over a cycle |
| Who reads it | The team and its leads | The manager and the employee |
| What it leads to | The next piece of work | A conversation and a decision by the manager |
| Sensitivity | Shared widely | Seen only by the manager, the employee and those you name |
Related reading
- Job and project status reporting, continuously: the record of work that the packet draws on.
- Status meetings replaced by status agents: how that record gets written in the first place.
- When not to automate: why the judgment in a review stays human.
