Inspect sources
- Where did this example come from?
- Is the source specific enough to use?
- Does it belong in this review period?
Template
Review evidence should be specific, inspectable, and tied to the period being reviewed. Use this checklist before turning examples into review language.
Use this manually, or let EvalSuite capture it automatically from real meetings.
Use the prompts to make the next manager action explicit. The goal is not a perfect document; it is a short record that helps the next conversation start with context.
EvalSuite keeps review evidence connected to meetings, action items, scorecard context, manager notes, and review-safe packets while leaving final review decisions with the manager.
Keep the source, situation, behavior, impact, competency or expectation, and manager decision. Avoid unsupported labels or surprise feedback with no prior context.
Before drafting a review, a manager filters the strongest examples, checks the source context, maps them to expectations, and decides what belongs in final language.
The visible output should be concrete enough to inspect.
This page links to related acquisition pages and canonical docs instead of duplicating support content.
EvalSuite adds the durable layer: capture, follow-through, history, and review-ready context.