Ready-to-paste ChatGPT prompts for HR Managers who need performance review drafts finished today. Each prompt takes 30 seconds to customise and produces a polished document 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 Review Drafts
You are an HR manager writing a year-end performance review.
Employee: {employee_name} Role: {job_title}, {tenure} at the company Rating: {rating: exceeds / meets / below expectations} Wins this year: {three_to_five_wins_in_bullets} Growth areas: {two_to_three_struggles} Tone: {direct / supportive / formal} Promotion consideration: {yes / no / not_yet}
Write a 350 to 450 word performance review using the SBI model (Situation, Behaviour, Impact). Open with recognition that names a specific win. Address growth areas in the middle, framed as development not failure. Close with two forward-looking goals tied to the role.
When to use it: You have 15 annual reviews due this week and need consistent, professional drafts that hit all your company’s review criteria.
Pro tip: If the employee is promotion-ready, mention specific leadership behaviours you’ve observed. If not, frame growth areas as “expanding your impact in [specific area]” rather than listing deficits.
You are writing a performance review for an underperforming employee who needs clear improvement expectations.
Employee: {employee_name} Role: {job_title} Time in role: {tenure} Specific performance gaps: {three_concrete_examples} Previous feedback given: {yes_or_no} Company rating system: {rating_scale} Your rating: {specific_rating} Support available: {training_or_resources}
Write a 400 to 500 word review that is direct but constructive. Use the STAR format for examples. Include a 90-day improvement plan with measurable outcomes. Maintain a professional tone that documents concerns while showing commitment to the employee’s success.
When to use it: You’re documenting performance issues that need to be on record, but you want to give the employee a genuine chance to improve.
Pro tip: Always include what support you’re providing. It strengthens your documentation if the situation escalates and shows good faith to the employee.
You are writing a glowing review for a high performer being considered for promotion.
Employee: {employee_name} Current role: {job_title} Target promotion: {new_role_or_level} Standout achievements: {four_to_five_specific_wins} Leadership examples: {two_to_three_instances} Peer feedback theme: {common_praise_point} Salary impact: {revenue_or_cost_savings}
Write a 300 to 400 word review that builds a strong promotion case. Lead with quantified impact. Include specific examples of leadership potential. Address any skill gaps as “areas for growth in the new role” rather than current weaknesses. End with a clear promotion recommendation.
When to use it: You’re advocating for someone’s promotion and need to present a compelling case to senior leadership or the promotion committee.
Pro tip: Include peer feedback or cross-functional praise. It shows the employee’s impact beyond your direct observation and strengthens the promotion argument.
You are writing a mid-year check-in review focused on goal progress and course correction.
Employee: {employee_name} Role: {job_title} Goals set in January: {three_to_four_original_goals} Current progress: {brief_status_on_each} Unexpected challenges: {two_to_three_obstacles} New priorities: {any_shifted_focus_areas} Support needed: {resources_or_help_required}
Write a 250 to 350 word mid-year review using the GROW model (Goal, Reality, Options, Way forward). Acknowledge progress made. Address obstacles without blame. Adjust goals if business needs have shifted. End with clear actions for the next six months.
When to use it: It’s mid-year review season and you need to recalibrate goals based on business changes or unexpected challenges your team has faced.
Pro tip: If goals need significant adjustment, explain the business context that drove the change. It prevents the employee from feeling like they failed at the original objectives.
You are writing a review for a remote employee whose performance is hard to evaluate through traditional metrics.
Employee: {employee_name} Role: {job_title} Location: {remote_location} Time zone difference: {hours_difference} Project contributions: {three_to_four_specific_deliverables} Communication style: {strength_or_area_for_growth} Team collaboration: {specific_examples} Self-management: {observed_behaviours}
Write a 350 to 450 word review that evaluates remote work effectiveness. Focus on output quality and team impact rather than hours worked. Address communication and collaboration specifically. Include feedback on their remote work setup and self-management. Provide clear expectations for remote work success.
When to use it: You’re reviewing remote employees and need to assess performance based on outcomes and collaboration rather than physical presence.
Pro tip: Mention specific examples of proactive communication or problem-solving that you wouldn’t have seen with in-office employees. It shows you’re evaluating fairly across work arrangements.
Difficult Conversation Scripts
You need to deliver a performance improvement plan during a face-to-face review meeting.
Employee: {employee_name} Role: {job_title} Main performance issue: {specific_problem} Business impact: {how_it_affects_work} Previous discussions: {dates_and_topics} Improvement timeline: {30_60_or_90_days} Success metrics: {measurable_outcomes} Support provided: {training_resources_mentoring}
Write a 200 to 300 word script for delivering this PIP. Start with care and context. Be specific about the problem and its impact. Explain the timeline and support clearly. End by asking for their commitment and questions. Use a firm but supportive tone throughout.
When to use it: You’re about to have the hardest conversation of your month and need to deliver clear expectations while maintaining the relationship.
Pro tip: Pause after explaining the improvement timeline and ask “What questions do you have so far?” It ensures they understand before you move to next steps.
You are having a review conversation with an employee who consistently misses deadlines.
Employee: {employee_name} Recent missed deadlines: {three_specific_examples_with_dates} Impact on team: {specific_consequences} Their usual explanation: {common_excuse_pattern} Workload assessment: {realistic_or_overwhelming} Time management observation: {what_you_see} Available support: {tools_or_training}
Write a 250 to 350 word conversation script using the SBI model. Address the pattern, not individual incidents. Ask about root causes before offering solutions. Set clear expectations for deadline communication. End with specific next steps and check-in schedule.
When to use it: You’re tired of the same deadline excuses and need to have a direct conversation that actually changes behaviour.
Pro tip: Ask “Walk me through how you plan your week” before offering time management solutions. You might discover process issues, not skill issues.
You need to address an employee who received complaints about their attitude or interpersonal behaviour.
Employee: {employee_name} Complaint source: {peer_customer_or_manager} Specific behaviour described: {two_to_three_examples} Impact on others: {team_morale_or_relationships} Their likely perspective: {how_they_might_see_it} Desired behaviour: {specific_alternative_actions} Follow-up plan: {how_you_will_monitor}
Write a 300 to 400 word script for this sensitive conversation. Start by stating the issue without naming sources if possible. Use specific behavioural examples, not personality judgements. Ask for their perspective before explaining impact. Agree on specific behaviour changes and follow-up timing.
When to use it: You’ve received complaints about someone’s attitude or behaviour and need to address it without creating defensiveness or drama.
Pro tip: Use “I’ve observed” or “It’s been brought to my attention” rather than “People are saying.” It keeps the focus on behaviour, not gossip.
You are discussing a failed project or major mistake during a performance review.
Employee: {employee_name} Project or situation: {what_went_wrong} Timeline: {when_it_happened} Impact: {cost_delay_or_other_consequences} Their role: {specific_responsibility} Contributing factors: {team_process_or_system_issues} Lessons identified: {what_they_learned} Prevention steps: {how_to_avoid_repeat}
Write a 250 to 350 word review section that addresses the failure constructively. Acknowledge the impact without dwelling on it. Focus on lessons learned and prevention rather than blame. Ask what support they need to handle similar challenges. End with confidence in their ability to apply lessons learned.
When to use it: A major mistake happened months ago, and you need to address it in the formal review without rehashing old drama.
Pro tip: If they’ve already implemented changes based on the failure, lead with those improvements. It shows growth and prevents the conversation from feeling punitive.
You need to explain why someone didn’t get the promotion they expected.
Employee: {employee_name} Position they wanted: {specific_role} Who got it: {internal_external_or_no_one} Their strengths: {two_to_three_positives} Gap areas: {specific_skills_or_experience_missing} Development needed: {concrete_improvement_areas} Timeline for growth: {realistic_timeframe} Next opportunity: {when_similar_role_might_open}
Write a 200 to 300 word script for this conversation. Start with appreciation for their interest and effort. Be specific about why they weren’t selected without comparing them to others. Focus on development opportunities. End with encouragement and concrete next steps for growth.
When to use it: Someone applied for a promotion, didn’t get it, and now you need to keep them motivated while being honest about what they need to develop.
Pro tip: Offer to connect them with someone who has the skills they need to develop. It shows investment in their growth beyond just identifying gaps.
Team-Wide Performance Communications
You need to address declining team performance metrics in a team meeting.
Team: {team_name_or_department} Declining metrics: {specific_numbers_or_kpis} Time period: {how_long_this_has_been_happening} Potential causes: {workload_process_or_external_factors} Individual vs system issues: {your_assessment} Support available: {resources_or_changes_you_can_make} Improvement timeline: {realistic_timeframe}
Write a 300 to 400 word team meeting script. Present the data without blame. Ask for their input on causes before sharing your assessment. Discuss solutions collaboratively. Set clear expectations for improvement while offering support. End with next steps and follow-up plan.
When to use it: Your team’s numbers are down, leadership is asking questions, and you need to address it without destroying morale.
Pro tip: Bring specific examples of when the team performed well under similar conditions. It reminds everyone that good performance is achievable.
You are announcing a reorganisation or role changes that affect performance expectations.
Team: {affected_group} Change type: {restructure_new_process_or_role_shifts} Effective date: {when_changes_start} New expectations: {three_to_four_key_changes} Impact on reviews: {how_performance_evaluation_changes} Support during transition: {training_or_resources} Timeline for adjustment: {reasonable_learning_period}
Write a 250 to 350 word announcement that explains changes clearly. Address how it affects their performance evaluation and career development. Acknowledge the adjustment period needed. Provide specific support and training available. End with open door for questions and concerns.
When to use it: Major organisational changes are happening and your team needs to understand how their job expectations and evaluation criteria are shifting.
Pro tip: Schedule one-on-ones within two weeks of this announcement. Group questions will emerge, but individual concerns need private conversation.
You need to reset team expectations after a period of low standards or accountability.
Team: {team_name} Standards that slipped: {specific_areas_of_decline} Timeline: {how_long_this_has_been_happening} Business impact: {consequences_they_might_not_see} New expectations: {four_to_five_clear_standards} Implementation date: {when_new_standards_start} Support provided: {training_tools_or_resources}
Write a 300 to 400 word team meeting script that resets standards without attacking past performance. Explain the business need for higher standards. Be specific about new expectations. Provide clear support for meeting them. Address questions about fairness or feasibility directly.
When to use it: Standards have gotten sloppy over time, and you need to raise the bar without making the team feel like they’ve been doing everything wrong.
Pro tip: Give a specific start date for new standards, ideally 2-3 weeks out. It shows you’re serious while giving time for adjustment.
You are communicating new performance tracking or monitoring tools to your team.
Tool or system: {specific_software_or_process} What it tracks: {metrics_or_behaviours_monitored} Frequency: {daily_weekly_or_monthly} Purpose: {coaching_evaluation_or_compliance} Data access: {who_sees_what_information} Implementation timeline: {rollout_schedule} Training provided: {how_they_will_learn_the_system}
Write a 200 to 300 word communication explaining the new tracking system. Address privacy concerns upfront. Explain how the data will be used constructively. Emphasise coaching and development over punishment. Provide clear training timeline and support resources.
When to use it: You’re implementing new performance monitoring technology and need to introduce it without making the team feel micromanaged.
Pro tip: Share an example of how the data helped you coach someone successfully (with permission). It demonstrates positive intent rather than surveillance.
You need to address team performance during busy season or high-pressure period.
Current situation: {specific_busy_period_or_pressure} Duration: {how_long_it_will_last} Performance expectations: {what_cannot_slip} Temporary adjustments: {what_you_are_flexible_on} Support available: {overtime_resources_or_help} Communication schedule: {how_often_you_will_check_in} Recovery plan: {how_you_will_handle_post_busy_period}
Write a 250 to 350 word team communication that acknowledges the pressure while maintaining standards. Be clear about non-negotiable expectations. Offer specific support and flexibility where possible. Set realistic check-in schedule. Address how you’ll support recovery after the busy period ends.
When to use it: Your team is entering crunch time, and you need to maintain performance standards while showing you understand the increased pressure.
Pro tip: Identify one specific thing you’re temporarily relaxing (meeting frequency, reporting detail, etc.) to show you’re genuinely adjusting expectations, not just adding pressure.
Goal-Setting and Development Planning
You are creating development goals for a high-potential employee ready for stretch assignments.
Employee: {employee_name} Current role: {job_title} Strengths to leverage: {three_key_strengths} Growth areas: {two_skills_to_develop} Career interest: {direction_they_want_to_go} Available stretch opportunities: {specific_projects_or_assignments} Timeline: {6_months_or_1_year} Success metrics: {how_you_will_measure_growth}
Write a 300 to 400 word development plan using the SMART goal framework. Create 2-3 specific development goals that stretch their abilities. Include concrete assignments or projects. Set measurable outcomes and clear timelines. Address how this connects to their career aspirations.
When to use it: You have a star performer who’s ready for bigger challenges, and you need to create a development plan that keeps them engaged and growing.
Pro tip: Include at least one cross-functional project or assignment. High performers often need broader perspective, not just deeper expertise in their current area.
You need to set performance improvement goals for someone who is meeting basic expectations but not excelling.
Employee: {employee_name} Current performance level: {meets_basic_requirements} Areas for improvement: {two_to_three_specific_skills_or_behaviours} Business need: {why_higher_performance_matters} Available support: {training_mentoring_or_resources} Measurement approach: {how_you_will_track_progress} Review timeline: {30_60_or_90_day_check_ins} Success definition: {what_exceeds_expectations_looks_like}
Write a 250 to 350 word goal-setting document that moves someone from adequate to strong performance. Focus on 1-2 key areas rather than everything. Provide specific behavioural indicators of success. Include support and resources. Set realistic but challenging timelines.
When to use it: Someone is doing fine but not great, and you want to help them level up without making them feel like they’re failing.
Pro tip: Frame goals around business impact rather than personal improvement. “Increase client retention” feels more meaningful than “improve communication skills.”
You are setting goals for a new employee at the end of their probationary period.
Employee: {employee_name} Role: {job_title} Start date: {when_they_started} Onboarding progress: {what_they_have_mastered} Areas still developing: {two_to_three_skills_to_strengthen} Team integration: {how_well_they_fit_in} First year priorities: {three_to_four_key_objectives} Success metrics: {how_you_will_measure_progress}
Write a 300 to 400 word goal document for their first full year. Acknowledge successful onboarding elements. Set realistic learning and performance goals. Include relationship-building objectives. Create quarterly milestones for the first year. Address both technical and cultural success factors.
When to use it: Someone has successfully completed their probationary period, and you’re setting them up for success in their first full year.
Pro tip: Include one goal about building internal relationships or contributing to team culture. New employees often focus only on task completion and miss the relationship side.
You need to create goals for someone transitioning to a new role or increased responsibilities.
Employee: {employee_name} Previous role: {old_position} New role: {new_position_or_added_responsibilities} Transition timeline: {how_long_for_full_transition} Skills to transfer: {what_they_bring_from_before} New skills needed: {three_to_four_capabilities_to_develop} Success in 90 days: {early_wins_needed} Success in 1 year: {full_performance_expectations}
Write a 350 to 450 word transition goal plan with 30-60-90 day milestones. Acknowledge their existing strengths. Set realistic learning goals for new responsibilities. Include relationship-building with new stakeholders. Create success metrics that account for learning curve.
When to use it: Someone got promoted or took on significantly new responsibilities, and you need to set them up for success while being realistic about the learning curve.
Pro tip: Set different expectations for managing former peers versus completely new responsibilities. Role transition challenges vary significantly based on relationship dynamics.
You are setting goals for a veteran employee who has become comfortable and needs re-energizing.
Employee: {employee_name} Tenure: {years_with_company} Current performance: {consistent_but_not_growing} Past strengths: {what_they_used_to_excel_at} Potential energy areas: {two_to_three_things_that_might_motivate_them} Available challenges: {new_projects_or_responsibilities} Skills they could mentor: {expertise_to_share_with_others} Career refresh options: {lateral_moves_or_special_assignments}
Write a 300 to 400 word goal-setting approach that re-engages a long-term employee. Connect goals to their expertise and experience. Include opportunities to mentor or lead others. Offer variety and new challenges. Address both performance improvement and job satisfaction.
When to use it: You have a long-term employee who’s coasting, and you want to re-engage them rather than manage them out.
Pro tip: Ask them what energized them most in past roles before proposing new challenges. Veterans often know what motivates them but haven’t been asked recently.
Frequently Asked Questions
How do I modify these prompts for different performance rating systems?
Replace the rating variables with your company’s specific scale (1-5, exceeds/meets/below, A-B-C, etc.). The prompt structure works with any rating system as long as you’re specific about what each rating means.
Can I use these prompts for 360-degree reviews or peer feedback?
Yes, but modify the perspective. Change “You are an HR manager” to “You are providing peer feedback” and adjust the variables to focus on collaboration, teamwork, and cross-functional impact rather than direct management observations.
What if my company requires specific competency frameworks like leadership behaviours?
Add your framework to the constraints section. For example: “Use our company’s five leadership competencies: Vision, Execution, People Development, Innovation, and Results” and include variables for rating each competency area.
Want every prompt for HR Managers in one pack?
200+ prompts for HR Managers organised by use case. Ready to paste. The full collection.