Verified against ChatGPT · 2026-08-08
Turn scattered manager notes into a performance review that would survive the employee pushing back on it
Converts a manager's raw notes and examples from the review period into a structured performance review draft grounded in specific, checkable evidence, flagging any vague or unsupported claim before it goes in front of the employee.
The prompt
Ready to copy — highlighted parts are example details you can swap.
You are helping a manager draft a performance review from their raw notes for the period below. This is a working draft for the manager to review and edit, not a final document — treat it as a first pass that needs to hold up if the employee pushes back on any specific claim in it.
EMPLOYEE ROLE AND REVIEW PERIOD
Product Marketing Manager, H1 2026 review cycle.
MANAGER'S RAW NOTES AND EXAMPLES
Led the launch of the pricing page redesign, conversion went up 12%. Great in cross-functional meetings. Missed the deadline on the competitor battlecard project by two weeks, didn't flag it was slipping until the day it was due. Sometimes seems disengaged in team meetings.
RATING OR LEVEL SYSTEM IN USE
5-point scale: Below Expectations, Partially Meets, Meets, Exceeds, Significantly Exceeds.
AREAS THE MANAGER WANTS TO EMPHASIZE
Wants to be direct about the missed deadline pattern since it's happened twice now, without undoing credit for the pricing page win.
For every strength or growth area you write, trace it back to something specific in the raw notes — a project, a date, a measurable outcome, a direct quote from feedback the manager received about this person. If the raw notes contain a claim that is vague or unsupported ("needs to be more proactive," "great attitude") with no specific example behind it in the notes, do not simply write it into the review as-is — flag it separately and ask the manager for the specific instance that led them to that impression, since an unsupported claim in a written review is both legally exposed and the single most common thing employees push back on successfully. Write growth areas as specific, actionable next steps tied to an actual situation, not as character critiques — "missed the deadline on the Miller account renewal by four days without flagging it in advance" is actionable, "needs better time management" is not. If a rating or level system is given, do not just assign the number — write the narrative in a way that makes the assigned rating obviously consistent with the evidence, so the rating doesn't read as disconnected from the text above it.
WHAT NOT TO DO
Do not use hedging language that undercuts a legitimate concern ("just a small thing, but...") or inflate a genuine strength into vague superlatives ("exceptional in every way") that make the review harder to act on either way.
OUTPUT FORMAT
1. The review draft itself: overall summary, strengths (with evidence), growth areas (with evidence and next steps), and the rating with a one-line justification tying it to the evidence above.
2. A separate "Needs a specific example" list of any claim in the manager's notes you could not ground in a concrete instance.
A note on scope: this is a working draft to support the manager's own judgment, not a substitute for it, and should be reviewed and personalized by the manager before it's shared with the employee.Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Performance-review defensibility, both practically and in any later HR or legal review, rests almost entirely on whether every claim is traceable to a specific, dated, checkable instance rather than a general impression, which is exactly the distinction this prompt forces by requiring every strength and growth area to trace back to something concrete in the raw notes. The explicit instruction to flag rather than silently include vague claims like "needs to be more proactive" targets the most common way reviews go wrong: a manager's genuine but underspecified impression gets written into a formal document, the employee reasonably asks "can you give me an example," and the manager has none ready, which damages trust in the whole review regardless of how accurate the other, well-supported points were — catching this at draft time, before the conversation, is far cheaper than catching it in the room. Rewriting growth areas as specific situations with next steps rather than character critiques matters mechanically because language like "needs better time management" is not actionable — it gives the employee nothing concrete to change — while "flag slipping deadlines earlier, at least a week out" describes an observable behavior they can actually demonstrate improvement on at the next review. Requiring the narrative to make the assigned rating "obviously consistent" with the evidence addresses a specific credibility gap that shows up often in real reviews, where a manager's text reads mostly positive but the number assigned is middling, leaving the employee confused about which one to trust — GPT-5.1 left to draft freely will often produce this exact mismatch because it generates the narrative and the rating somewhat independently unless explicitly told to reconcile them.
What you get back
Strengths: Led the pricing page redesign end-to-end, resulting in a 12% conversion lift — a clear, measurable win this cycle. Growth area: The competitor battlecard project slipped two weeks past deadline, and the delay wasn't flagged until the due date itself; going forward, raise a slipping timeline at least a week out so the team can adjust. Needs a specific example: 'sometimes seems disengaged in team meetings' has no concrete instance in the notes — what specifically happened that gave this impression?
Verified against
ChatGPT GPT-5.1 · 2026-08-08
Changelog
- 2026-08-08 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.
EXPLORE WHAT SCULT BUILDS
