Good evaluator feedback is short, specific, and useful to product or engineering. It says what happened and why it matters.
Strong notes
Good note:
Why it works:
- names the failure
- points to the prompt
- explains the behavioral problem
- gives the team something to fix
Pass note
Use this when the response should be repeated as a pattern.
Borderline note
Use this when the response has value but needs refinement.
Fail note
Use this when the response misses the job even if it sounds pleasant.
Escalation note
Use this when the risk needs a more experienced reviewer.
Keep notes lean
One useful sentence is better than a long explanation that hides the signal.