HR managers with performance reviews due this week. Copy these prompts into ChatGPT, fill in the variables, and get polished drafts in 30 seconds. Each prompt produces a finished piece you can edit lightly and send.
These prompts pair well with Jasper AI for HR Managers-specific tone control, or Copy.ai for fast iteration.
Annual Performance Reviews
You are an HR manager writing a year-end performance review for a high performer being considered for promotion.
Employee: {employee_name} Role: {job_title}, {tenure} at the company Rating: {exceeds_expectations / meets_expectations / below_expectations} Key wins this year: {three_major_accomplishments} Growth areas: {two_development_opportunities} Promotion readiness: {ready / needs_6_months / needs_12_months} Manager tone: {supportive / direct / formal}
Write a 400-500 word performance review using the SBI model (Situation, Behaviour, Impact). Open with specific recognition of their strongest win. Address growth areas as development opportunities, not shortcomings. Close with clear promotion timeline and next steps.
When to use it: When you’re reviewing a top performer and need to balance praise with honest development feedback for promotion consideration.
Pro tip: If promotion isn’t happening this cycle, spend extra words on the specific skills or experiences they need to develop, not vague “leadership potential” language.
You are writing a performance review for an employee who started strong but declined mid-year.
Employee: {employee_name} Position: {job_title} Tenure: {months_in_role} Strong start period: {first_quarter_wins} Performance decline started: {month_when_issues_began} Current challenges: {specific_performance_gaps} Personal factors (if known): {family_issues / health / workload / team_changes} Improvement timeline: {30_days / 60_days / 90_days}
Write a 350-400 word review that acknowledges their early success, addresses the decline without shame, and creates a clear improvement plan. Use a constructive tone that assumes they can turn it around.
When to use it: When an employee’s performance has visibly dropped and you need documentation while keeping the door open for recovery.
Pro tip: Reference specific dates and examples from their strong period to show this isn’t about their capability, it’s about current circumstances.
You are completing a review for a solid contributor who meets expectations but rarely exceeds them.
Employee: {employee_name} Department: {department_name} Years with company: {tenure} Consistent strengths: {three_reliable_skills} Areas where they could stretch: {growth_opportunities} Team impact: {how_they_help_others} Initiative level: {reactive / proactive / mixed} Career aspirations: {wants_promotion / content_in_role / unclear}
Write a 300-350 word review that values their reliability while encouraging growth. Frame it as “good foundation to build on” not “stuck in comfort zone.” Include one specific stretch assignment suggestion.
When to use it: For the steady performers who keep your team running but might need a gentle push toward their next level.
Pro tip: These employees often underestimate their impact on team stability. Call out specific examples of how their consistency enabled others to take risks.
You are writing a performance review for someone whose technical skills are strong but collaboration needs work.
Employee: {employee_name} Technical rating: {excellent / very_good / good} Collaboration challenges: {specific_examples_of_team_friction} Project impact: {how_work_quality_vs_team_dynamics_affected_outcomes} Feedback from peers: {summary_of_360_comments} Previous coaching attempts: {what_youve_tried_already} Receptiveness to feedback: {open / defensive / mixed}
Write a 450-500 word review that leads with technical strengths, then addresses collaboration as essential for career growth. Include specific behavioral changes and a 90-day check-in plan. Tone should be direct but not punitive.
When to use it: When you have a skilled individual contributor whose interpersonal issues are becoming a team problem.
Pro tip: Frame collaboration skills as technical skills that can be learned and measured, not personality traits they’re stuck with.
You are writing a review for a new employee at the end of their first year.
Employee: {employee_name} Start date: {hire_date} Onboarding experience: {smooth / rocky / mixed} Learning curve: {faster_than_expected / as_expected / slower_than_expected} Cultural fit: {excellent / good / concerning} Skill development: {areas_where_theyve_grown} Remaining gaps: {skills_still_developing} Manager support needed: {more / less / about_right}
Write a 300-400 word first-year review that celebrates their integration while setting clear year-two expectations. Include specific learning goals and support commitments from their manager.
When to use it: For first-year anniversary reviews where you want to mark the milestone and set direction for their second year.
Pro tip: New employees often don’t realize how much they’ve grown in their first year. Include a brief “then vs now” comparison to show their progress.
Difficult Conversations
You need to document a formal warning for attendance issues.
Employee: {employee_name} Position: {job_title} Attendance pattern: {specific_dates_and_absences} Previous verbal warnings: {dates_of_prior_conversations} Impact on team: {specific_coverage_issues_or_workload_impacts} Employee’s stated reasons: {their_explanation_for_absences} Accommodation requests: {any_formal_requests_made} Improvement timeline: {30_days / 60_days / 90_days}
Write a formal 250-300 word written warning that documents the pattern, explains business impact, and sets clear expectations. Include specific consequences if attendance doesn’t improve. Professional tone, no emotional language.
When to use it: When verbal coaching hasn’t worked and you need to create formal documentation before escalating further.
Pro tip: Always include the specific business impact of their absences, not just policy violations. It strengthens your documentation if this leads to termination.
You are preparing talking points for a difficult mid-year conversation about performance decline.
Employee: {employee_name} Performance decline areas: {specific_metrics_or_examples} Timeline of decline: {when_issues_started} Previous support offered: {training_coaching_or_resources_provided} Current impact: {how_its_affecting_team_or_projects} Employee’s awareness level: {know_theres_a_problem / seem_surprised / in_denial} Your relationship: {strong / neutral / strained}
Create a conversation script with 5-7 talking points. Start with care, present facts without emotion, ask for their perspective, then collaborate on solutions. Include specific questions to ask them and specific support to offer.
When to use it: When you need structure for a performance conversation that could go sideways without careful handling.
Pro tip: Write down the exact questions you’ll ask them about their perspective. When these conversations get tense, managers often forget to listen.
You need to address a complaint about an employee’s attitude affecting team morale.
Employee: {employee_name} Specific behaviors reported: {what_teammates_have_said} Frequency: {daily / weekly / during_certain_projects} Team members affected: {number_of_people_or_specific_roles} Work quality: {still_good / declining / unaffected} Previous feedback given: {none / informal / formal} Employee’s likely reaction: {defensive / surprised / aware}
Write a 200-250 word conversation opener that addresses behavior impact without attacking character. Focus on specific examples and business impact. Include questions that help them understand the team perspective.
When to use it: When multiple team members have complained about someone’s attitude but you need to address it without revealing who spoke up.
Pro tip: Never say “people are saying” or “the team feels.” Use your own observations and the business impact you’ve witnessed directly.
You are documenting a performance improvement plan for an employee at risk of termination.
Employee: {employee_name} Performance gaps: {specific_measurable_deficiencies} Business impact: {how_gaps_affect_results_or_team} Previous interventions: {coaching_training_or_support_already_tried} Improvement timeline: {30_days / 60_days / 90_days} Success metrics: {specific_measurable_improvements_needed} Support being provided: {additional_training_coaching_or_resources} Review schedule: {weekly / biweekly / monthly_check_ins}
Write a formal 400-500 word Performance Improvement Plan that clearly defines expectations, support, timeline, and consequences. Include specific metrics and review dates. Professional tone that assumes they can succeed but documents the stakes.
When to use it: When informal coaching hasn’t worked and you need formal documentation before considering termination.
Pro tip: Make the success metrics so specific that both you and the employee will know exactly whether they’ve met them. Vague goals create legal problems later.
You need to have a coaching conversation about professional boundaries after an inappropriate comment.
Employee: {employee_name} Incident details: {what_was_said_or_done} Setting: {meeting / email / casual_conversation / public} People present: {who_witnessed_or_was_affected} Employee’s intent: {joking / unaware / repeat_behavior} Company policy: {specific_policy_they_violated} Previous incidents: {none / similar_issues_before / first_time}
Write a 300-350 word coaching conversation that addresses the incident clearly, explains why it’s problematic, and prevents future issues. Assume good intent but be firm about standards. Include specific language about what’s acceptable going forward.
When to use it: When someone crosses a line but it’s not severe enough for formal discipline, and you need to address it before it escalates.
Pro tip: Don’t get drawn into debating their intent or whether others were “really” offended. Focus on professional standards and business impact.
Feedback and Recognition
You are writing an email to recognize an employee who went above and beyond during a crisis.
Employee: {employee_name} Crisis situation: {specific_emergency_or_challenge} Their specific actions: {what_they_did_beyond_normal_duties} Impact: {how_their_actions_helped_company_or_team} Personal cost: {extra_hours_stress_or_sacrifice_they_made} Team members who benefited: {who_else_was_helped} Recognition type: {email_only / copying_leadership / public_announcement}
Write a 150-200 word recognition email that specifically describes their actions and impact. Make it personal and genuine, not generic praise. Include how their example sets the standard for others.
When to use it: Right after a crisis or busy period when someone stepped up significantly and you want to acknowledge it while it’s fresh.
Pro tip: Send this within 48 hours of the action you’re recognizing. Late recognition feels like an afterthought, even if you mean it sincerely.
You are giving feedback to someone who delivered a great presentation to senior leadership.
Employee: {employee_name} Presentation topic: {what_they_presented_on} Audience: {who_was_in_the_room} Specific strengths: {what_they_did_particularly_well} Executive feedback: {what_leaders_said_afterward} Preparation effort: {how_much_work_they_put_in} Career impact: {how_this_visibility_helps_them}
Write a 100-150 word feedback message that celebrates their success and reinforces what they should keep doing. Include the business impact of their strong presentation and how it positions them for future opportunities.
When to use it: After an employee has a visible win with senior leadership and you want to reinforce the behaviors that led to success.
Pro tip: Be specific about which parts of their presentation worked best. They need to know what to repeat in future high-stakes situations.
You need to give constructive feedback on a project that missed the mark but showed effort.
Employee: {employee_name} Project: {what_they_were_working_on} Effort level: {time_and_energy_they_invested} What missed: {specific_gaps_or_problems} What worked: {parts_they_did_well} Learning opportunity: {what_this_teaches_them} Next steps: {how_to_recover_or_improve}
Write a 200-250 word feedback conversation that acknowledges their effort, addresses the gaps honestly, and focuses on learning. Frame it as skill development, not failure. End with specific actions for improvement.
When to use it: When someone tried hard but the result wasn’t what you needed, and you want to maintain their confidence while improving their approach.
Pro tip: Lead with effort recognition before addressing the gaps. People who tried hard need to know you saw that before they can hear criticism.
You are writing feedback for an employee who consistently delivers solid work but rarely speaks up in meetings.
Employee: {employee_name} Work quality: {consistently_good / excellent / reliable} Meeting participation: {silent / occasionally_contributes / only_when_asked} Expertise level: {knows_more_than_they_share / learning / expert} Team impact of silence: {missed_insights / others_dominate / decisions_made_without_input} Career goals: {wants_promotion / content / unclear} Communication style: {shy / thoughtful / prefers_written}
Write a 200-250 word coaching conversation that values their work quality while encouraging more participation. Frame speaking up as sharing expertise, not performing. Include specific tactics for contributing to meetings.
When to use it: When a strong performer is limiting their impact and advancement by staying too quiet in group settings.
Pro tip: Give them specific roles in upcoming meetings, like “I’d like you to share the data findings” or “Can you speak to the technical feasibility?” It’s easier than general encouragement to “speak up more.”
You are recognizing a team player who always helps colleagues but rarely gets public credit.
Employee: {employee_name} How they help others: {specific_ways_they_support_teammates} Recent example: {particular_instance_of_helpfulness} People they’ve helped: {colleagues_who_benefit_from_their_support} Impact on team dynamics: {how_their_attitude_affects_culture} Their own work quality: {whether_helping_others_affects_their_deliverables} Recognition preference: {public / private / peer_nomination}
Write a 150-200 word recognition message that highlights their collaborative spirit and gives them credit for enabling others’ success. Make it clear that you notice and value this contribution.
When to use it: When you realize someone is consistently making others better but flying under the radar because they’re not self-promoting.
Pro tip: Copy their colleagues who have benefited from their help. Team players often underestimate their impact until they see it acknowledged by peers.
Exit and Transition Conversations
You are conducting an exit interview with a high performer who is leaving for a better opportunity.
Employee: {employee_name} Tenure: {time_with_company} New opportunity: {why_theyre_leaving} Relationship with manager: {positive / neutral / strained} Team fit: {loved_team / neutral / conflicts} Company feedback