Image
Workflow
Back office

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

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.

Today

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 reviewWritten from memoryWith an assembled record
What the cycle coveredThe last few weeks, mostlyThe whole cycle, in order
Last cycle's goalsRemembered, or skippedListed, with the work recorded against each
FeedbackWhatever the manager recallsThe notes already written, with who wrote them and when
The employee's viewA summary nobody checksTheir self-review beside the record
The ratingThe manager'sStill 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.

01

Agree the sources first

Before the cycle, you name the systems the packet may draw on: the project tool, the ticket queue, the goals document, the written feedback the company already keeps. Private messages and personal files are out unless the employee adds them.
02

Gather the cycle's work

The agent pulls the work each person delivered in the cycle from those systems, in date order, with a link to each item.
03

Set it against last cycle's goals

It lists the goals agreed at the start of the cycle and places the recorded work under the goal it relates to. Work that fits no goal is listed separately, not dropped.
04

Add the written feedback and the self-review

It includes feedback that was already written down, with its author and date, and the employee's own self-review. It adds no feedback of its own.
05

Human gate: the manager rates, writes and decides

The packet goes to the manager. The rating, the written review, any development plan and anything that touches pay or promotion are the manager's decisions, and the agent drafts none of them. The approval gates page explains why a decision like this carries one name.
06

Let the employee correct the record

Where your process allows, the employee sees the record before the conversation and can add work that is missing or flag an item that is wrong. Corrections are recorded, not overwritten.
07

Keep the packet with the review

The packet is filed with the finished review, so next cycle starts from what was actually discussed.

Never in a 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

Workflow / Automate a Workflow

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?

QuestionStatus reportReview packet
What it coversWhere work stands nowWhat one person delivered over a cycle
Who reads itThe team and its leadsThe manager and the employee
What it leads toThe next piece of workA conversation and a decision by the manager
SensitivityShared widelySeen only by the manager, the employee and those you name
Tier 1 / Prove
How It Works

Questions, answered

No. The packet holds the record and nothing else. The rating is the manager's decision, and no draft rating is offered to anchor it.
AI Opportunity Audit · Review prep

Start every review from the actual record

Bring last cycle's review form and the goals you set and see what the record would have shown.