The 25 Best AI Prompts for Writing Performance Reviews

Performance reviews are the writing task most people put off until the night before they are due, which is exactly when they are worst at writing them. The standard failure modes are familiar: vague generalities that could apply to anyone, backhanded compliments dressed up as feedback, and strings of corporate synonyms for "did fine" that communicate nothing useful. AI is genuinely helpful here, but only if you feed it specific observations. "Write me a review for Sarah" produces slop. "Here are four things Sarah did this quarter, help me turn them into a review" produces something worth reading. The prompts below assume you will do the observing. They help you with the harder part: turning observations into something honest that the other person can actually use.

Below are 25 prompts I use during review season and throughout the year when feedback needs to be written well. Raw notes, quarterly highlights, 1:1 summaries, and half drafted review language all go into {{clipboard}}. Pick the ones that fit the kind of review you are writing and keep them a keystroke away so you are not starting from a blank text box at midnight.

---

Download Free for macOS

Self reviews

1. Turn raw highlights into a self review

I need to write my self review and I have a pile of raw notes about the quarter or year. Help me turn them into a clean, specific self review without making myself sound either arrogant or falsely humble.

Here are my notes:

{{clipboard}}

Produce a self review with:

1. A short summary of the period that leads with impact, not activity.
2. Three specific accomplishments, each with the outcome and my contribution stated clearly.
3. Two areas where I grew or stretched myself, with concrete examples.
4. One challenge I faced and how I handled it, including what I would do differently.
5. Two goals for the next period that are specific and measurable.
6. A short close about what I need from my manager to do my best work next period.

Voice: confident and direct, not boastful. First person. No corporate language. Do not pad items that do not deserve space.

2. Find the strongest accomplishments in a year of work

I have a rough list of everything I did this year and I cannot decide which ones to lead with in my self review.

Here is the list:

{{clipboard}}

Produce:

1. A ranking of the accomplishments from most impactful to least.
2. For each top accomplishment, the one sentence framing I should use, emphasizing outcome over activity.
3. A note on any accomplishment that sounds impressive in the list but will not hold up under scrutiny.
4. Any pattern across multiple accomplishments that suggests a theme I should use as the narrative spine.
5. Any accomplishment I should cut because it is too small or tangential.
6. A gap: what kind of accomplishment is missing that I should either search my memory for or note as an area of growth.

3. Write a self review when the year did not go well

I had a tough year and I need to write a self review that is honest without being a resignation letter.

Here is the context:

{{clipboard}}

Produce:

1. A framing that acknowledges the difficulty without spin.
2. The specific things I did that were still valuable, even in a hard year.
3. What I learned about myself, my work, or the environment.
4. What I would do differently, stated concretely not abstractly.
5. A forward looking plan that is grounded in the reality of the year.
6. A close that is honest but not defeatist.

Do not pretend the year was great. Do not apologize for things outside my control. Aim for clarity and ownership.

Manager reviews of direct reports

4. Draft a full performance review for a direct report

I need to draft a full performance review for someone on my team. I have notes from the year and I want a review that is specific, fair, and useful to them.

Here is my report's role and the notes I have:

{{clipboard}}

Produce a review with:

1. A summary paragraph that captures how the year went overall.
2. Three to five specific strengths, each with an observable example.
3. Two to three areas for development, each with an observable example and a concrete suggestion.
4. A note on their trajectory: growing, steady, or concerning.
5. Specific goals for the next period.
6. A short close that acknowledges their contributions without being generic.

Do not use "exceeds expectations" style language without a specific example behind it. Every rating or adjective needs an observation to back it up.

5. Write a review for a high performer who is coasting

I have a direct report who is clearly talented but has been coasting. I need to write a review that acknowledges the talent while being direct about the coasting.

Here is the context:

{{clipboard}}

Produce:

1. An opening that names the talent and the track record.
2. A direct but respectful statement about the coasting, with specific observations.
3. The impact of the coasting on the team and the business.
4. A question about what is going on underneath the behavior (disengagement, boredom, burnout, other).
5. A clear expectation for what the next period should look like.
6. A note on the conversation I should have alongside the written review.

Do not sugar coat. Do not be harsh. The goal is to wake them up, not punish them.

6. Write a review for someone who is struggling

I have a direct report who is struggling and I need to write a review that is clear about the performance issues without being cruel or hopeless.

Here is the context:

{{clipboard}}

Produce:

1. An opening that acknowledges the effort, not just the outcome.
2. Specific examples of where they are falling short, stated observably.
3. The gap between current performance and the expected level.
4. The specific changes needed and the timeline.
5. The support I am committing to provide.
6. A statement about what happens if things do not change, without being threatening.
7. A close that is clear about the seriousness without destroying their motivation.

Do not hide the seriousness. Do not make it personal. Stay grounded in behavior and outcomes.

Peer reviews and 360 feedback

7. Write a peer review that is honest and kind

I have to write a peer review for a colleague and I want it to be honest and useful, not just positive noise.

Here is what I have to say:

{{clipboard}}

Produce:

1. A strengths section with two or three specific things, each backed by a moment or behavior I observed.
2. A growth section with one or two honest development areas, framed as observations not accusations.
3. A note on how they collaborate with me specifically (their peer interactions).
4. A recommendation on where they could have the biggest impact going forward.
5. A tone check: is this review something the person would be glad to receive, even the hard parts?

No "great teammate, would recommend" platitudes. No backhanded compliments. Honest and warm.

8. Summarize 360 feedback into themes

I have a bunch of 360 feedback for someone and I need to synthesize it into themes I can share.

Here is the feedback:

{{clipboard}}

Produce:

1. Three consistent themes on strengths, each supported by multiple specific comments.
2. Two consistent themes on development, each supported by multiple specific comments.
3. One outlier comment that stood out but might not be a pattern.
4. Any contradiction between respondents: one said X, another said not X.
5. The tone of the feedback overall: enthusiastic, cautious, mixed.
6. The one theme I should lead the conversation with, and why.

Do not anonymize details so much that the feedback loses its specificity. Preserve the texture while protecting identity.

9. Write a peer review for someone I disagree with

I have to write a peer review for a colleague I have had real disagreements with. I want to be fair and avoid letting the disagreements color the review.

Here is the context:

{{clipboard}}

Produce:

1. A strengths section that is genuine, not performative. Find at least two things I can honestly acknowledge.
2. A development section that names the disagreements in neutral terms, grounded in behavior not personality.
3. A note on what I would find useful from them going forward.
4. A self check: have I let bias creep into the review? Where?
5. A flag for any line that sounds passive aggressive and should be rewritten.
6. A tone check: could a neutral reader tell that we have had conflict?

Be self aware. The goal is to give them feedback that is fair, not feedback that wins the argument.

Handling difficult feedback

10. Turn vague feedback into specific observations

I have vague feedback from myself or someone else and I need to turn it into specific observations before it goes into a review.

Here is the vague feedback:

{{clipboard}}

Produce:

1. A specific observation that the vague feedback is probably gesturing at.
2. Two or three concrete moments that would make the observation land.
3. A rewrite of the vague feedback in specific behavioral terms.
4. A note on what information I would need to sharpen it further.
5. A flag if the vague feedback is not actually actionable and should be reconsidered.

Vague feedback is worse than no feedback. Do not pass it on without sharpening it.

11. Soften direct feedback without losing the point

I have direct feedback that is accurate but too harsh for the written review. Help me soften the wording without losing the substance.

Here is the feedback:

{{clipboard}}

Produce:

1. A rewrite that preserves the point but changes the tone.
2. Three specific phrases that were too harsh, with their replacements.
3. A framing that puts the feedback in context of the person's growth, not their failure.
4. A question I could add that invites their perspective rather than delivering a verdict.
5. A note on whether the feedback should be in the written review at all, or delivered in conversation.
6. A warning if the softening goes too far and the feedback loses its clarity.

The goal is clarity with care, not softness that hides the issue.

12. Deliver feedback about a pattern instead of an incident

I have multiple specific incidents that add up to a pattern. I want to deliver the feedback as a pattern, not as a list of complaints.

Here are the incidents:

{{clipboard}}

Produce:

1. The name of the pattern, in one phrase.
2. A paragraph that describes the pattern with two or three incidents as evidence.
3. The likely impact of the pattern on the team or the work.
4. A hypothesis about the underlying cause, stated tentatively.
5. A request for their perspective on the pattern, not a verdict.
6. A specific change I am asking for.

Do not list every incident. Pick the ones that best illustrate the pattern and use them as evidence.

Performance improvement plans

13. Draft a performance improvement plan

I need to draft a PIP for a direct report. I want it to be fair, specific, and genuinely oriented toward improvement, not a paper trail.

Here is the context:

{{clipboard}}

Produce:

1. A clear summary of the performance concerns, grounded in observable behavior.
2. The specific expectations and what meeting them looks like.
3. A timeline: usually 30, 60, or 90 days, with checkpoints.
4. The support the manager and company will provide.
5. The measurement criteria for each expectation.
6. The consequences if the expectations are not met, stated clearly.
7. A close that is honest about the seriousness without foreclosing hope.

Consult with HR before finalizing. Do not skip that step.

14. Evaluate whether a PIP is the right call

I am considering putting someone on a PIP and I want to think it through before I commit. Help me stress test the decision.

Here is the context:

{{clipboard}}

Answer:

1. What specific performance issues are you hoping to correct?
2. Have those issues been communicated clearly before?
3. Is there any ambiguity about what "success" would look like?
4. Is the underlying issue performance, fit, or something else (burnout, personal circumstances, bad management)?
5. What would you hope to see at the end of the PIP period?
6. What is the likelihood, based on the history, that a PIP will actually result in improvement?
7. Is the PIP the first step in a conversation or the last step before termination?

Be direct. If the PIP is really a termination runway, say so and think about whether that is the right path.

Promotion cases

15. Write a promotion case for a direct report

I am writing a promotion case for someone on my team and I need it to be specific, evidence backed, and aligned to the next level's expectations.

Here is the context and the level I am promoting them to:

{{clipboard}}

Produce:

1. A summary of why this person is ready for the next level.
2. Three to five specific examples of them already operating at the next level.
3. How they have grown in the past year, with specific evidence.
4. How their current scope and impact compare to others at the target level.
5. The feedback from peers and stakeholders, if I have it.
6. Any gap at the target level and the plan to close it.
7. A close that is confident without overstating.

Make sure every claim is backed by a specific observation. Committees can smell generality.

16. Make a promotion case stronger before committee review

I have a promotion case draft and I want to make it stronger before the committee reviews it.

Here is my current draft:

{{clipboard}}

Review:

1. Any claim that is not supported by a specific example.
2. Any area where the evidence is thin for the target level.
3. The strongest example in the case and how to make it more prominent.
4. The weakest area and how to shore it up or acknowledge it honestly.
5. Any language that sounds defensive or apologetic (a sign of a weak case).
6. The question the committee is most likely to push back on.
7. A suggested opening paragraph that frames the whole case.

Do not inflate the case. Make it as strong as the evidence allows.

17. Explain why someone was not promoted

I need to tell a direct report they are not getting promoted this cycle. I want to deliver it clearly, with specific reasons and a real path forward.

Here is the context:

{{clipboard}}

Produce:

1. A framing that respects the person and the effort they put in.
2. The specific gaps between current performance and the target level.
3. The one or two things that would most change the outcome next cycle.
4. A realistic timeline for reassessment.
5. A commitment to support from my side.
6. A close that is clear without being discouraging.

Do not lie about the path forward. If the gap is large, say so.

Examples and specific behaviors

18. Turn a vague strength into a specific one

I wrote "strong communicator" in a review and I know it is too vague. Help me make it specific.

Here is what I actually observed:

{{clipboard}}

Produce:

1. A specific observable behavior that backs up "strong communicator."
2. A moment or example I can reference in the review.
3. A rewrite of the line using the specific behavior and example.
4. Two alternative rewrites with different angles.
5. A note on any part of the original claim that is actually not supported and should be cut.

Do not use adjectives that do not have evidence behind them. Strength descriptions should be earnable and verifiable.

19. Describe a development area without demoralizing

I need to describe a development area in a way that is honest but motivating. I have the observation but not the right framing.

Here is the observation:

{{clipboard}}

Produce:

1. A statement of the development area in observable terms.
2. The impact, also in observable terms.
3. A reframe that positions this as a growth opportunity without minimizing the issue.
4. A specific behavior change I am asking for.
5. A concrete suggestion on how they might work on it.
6. A note on whether this is the top development area to focus on, or whether there are bigger ones.

Avoid "consider working on" hedging. Direct is respectful.

20. Find the specific examples behind a general impression

I have a general impression of someone's performance but I cannot remember the specific examples. Help me reconstruct them from my notes.

Here are my 1:1 notes, project notes, and any other context:

{{clipboard}}

Produce:

1. The general impression translated into three to five specific behaviors.
2. For each behavior, a moment or example from the notes that supports it.
3. A flag for any impression I cannot back up with evidence from the notes.
4. A suggestion for where to look if I need to fill gaps (recent projects, peer feedback, specific artifacts).
5. A revised review paragraph using only the parts I can back up.

Do not fabricate examples. If I cannot back up an impression, the review should not include it.

Compensation conversations

21. Prepare for a compensation conversation with a direct report

I need to have a compensation conversation with a direct report. I want to be clear, fair, and ready for pushback.

Here is the context:

{{clipboard}}

Produce:

1. The core message: what the decision is and why.
2. The context about the team, the company, or the market that informs the decision.
3. The specific performance factors that went into the decision.
4. How I will deliver the number: before the rationale or after.
5. Likely pushback and my planned responses.
6. What I can and cannot do if they are unhappy.
7. A close that acknowledges their value without dodging the decision.

Do not avoid the number. Do not apologize for a fair decision.

22. Respond to a compensation concern

A direct report raised a concern about their compensation. I need to respond in a way that takes the concern seriously without committing to something I cannot deliver.

Here is the concern:

{{clipboard}}

Produce:

1. An acknowledgment of the concern that does not minimize it.
2. A question that helps me understand what they are actually asking for.
3. A clear statement of what is possible and what is not, with reasoning.
4. A next step: either a follow up conversation, a commitment to check on something, or a firm answer.
5. A close that respects their position whether or not I can meet it.

Do not promise things to get out of the conversation. Do not stonewall.

Tone and delivery

23. Check a review for unintentional harshness

I have a review draft and I want to check for any language that sounds harsher than I intended.

Here is the draft:

{{clipboard}}

Flag:

1. Any sentence that sounds accusatory.
2. Any phrase that blames personality rather than behavior.
3. Any claim stated as absolute when it should be tentative.
4. Any comparison to other team members that would land badly.
5. Any "never" or "always" that is probably not literally true.
6. Any passive aggressive phrase.
7. A rewrite of the three harshest lines.

Do not soften the substance. Soften the delivery when the delivery is the problem.

24. Check a review for unintentional vagueness

I have a review draft and I am worried parts of it are too vague to be useful.

Here is the draft:

{{clipboard}}

Flag:

1. Any statement that could apply to anyone in any role.
2. Any adjective without an example to back it up.
3. Any "areas for improvement" that are not concrete.
4. Any goal that is not measurable.
5. Any praise that is so generic it feels hollow.
6. A rewrite of the three vaguest sections with specific language.

A vague review is worse than a short review. Cut what you cannot make specific.

25. Final pass before submitting a review

I am about to submit this review. Do a final pass on clarity, tone, and fairness.

Here is the review:

{{clipboard}}

Check:

1. Is the summary honest and clear?
2. Are the strengths specific and backed by examples?
3. Are the development areas actionable?
4. Is the tone consistent throughout?
5. Is there any line that contradicts another part of the review?
6. Is there any line that would be embarrassing to have surfaced in a dispute or lawsuit?
7. Is the forward looking section specific and tied to the person, not boilerplate?
8. Does the review treat this person as an individual, or could it apply to anyone on the team?

Give me a list of issues with severity. If the review is ready, say so and point out the one line that is doing the most work.