How to use the Performance Review Generator.
Performance reviews should tie conclusions to specific work and agreed expectations. Separate a missed outcome from assumptions about a person's motivation.
Make the workflow fit your task.
Compare specific work with the agreed expectations for the review period. Describe strengths and improvement areas through examples, separating an observed outcome from assumptions about motivation and ending with an actionable development discussion.
- What you provide
- Verified work examples and evaluation rubric.
- What you get
- Balanced review tied to observable contributions.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Employee delivered two reports by the agreed dates. In one handoff, the notes did not identify who owned the next action. Draft balanced feedback without inferring motivation.
Completed example
You delivered both reports by their agreed dates, providing reliable support for the reporting schedule. In one handoff, the next action did not have a named owner. For future handoffs, please include the action owner and confirm that they understand the next step. Let's discuss whether a short handoff checklist would help.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should a review infer attitude from one missed outcome?
Describe what happened and its impact, then seek context. A missed handoff does not establish the person's motivation or character.
Why does the review feel unfair despite accurate examples?
Check the period, role expectations and balance of evidence. Isolated examples should not silently become claims about consistent behavior.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑