Prompts for Performance Management and Employee Relations

4 ready-to-use ChatGPT prompts for performance management and employee relations. Fill in the bracketed fields, paste into ChatGPT, and go.

HR & Recruiting · 4 prompts

01

Write a Performance Improvement Plan That's Specific Enough to Actually Work

Write a performance improvement plan with specific, measurable expectations and support, structured to give the employee a real chance rather than serving only as termination documentation.

You’ll needemployee role and tenurespecific performance gapsprior feedback already giventimeline for the PIPsupport the manager can offer
Prompt
You are an HR partner helping a manager write a performance improvement plan.

Write the PIP using the context below.

Context:
- Employee role and tenure: [employee]
- Specific performance gaps: [gaps]
- Prior feedback already given: [prior feedback]
- Timeline for the PIP: [timeline]
- Support the manager can realistically offer: [support]

Instructions:
1. Write each expectation as specific and measurable — a vague expectation like "improve communication" gives the employee no real way to know if they're succeeding.
2. Reference the prior feedback already given, so the PIP doesn't read as the first time these issues were raised.
3. Include concrete support the manager will provide (check-ins, resources, mentoring) since a PIP with expectations but no support structure reads as documentation for termination rather than a genuine improvement path.
4. Set a realistic timeline given the nature of the gaps — some skills genuinely take longer to build than a 30-day window allows.
5. Note check-in cadence and what happens at each checkpoint, so the process has visible structure rather than a single pass/fail moment at the end.

Output format:
- Specific, measurable expectations
- Reference to prior feedback
- Manager support commitments
- Timeline with check-in cadence
- What happens at each checkpoint

Missing information policy:
Ask up to 2 concise questions only if the performance gaps or timeline are unclear.

Quality bar:
- Expectations are specific and measurable.
- Includes real manager support, not just expectations.
- Realistic timeline for the nature of the gaps.
02

Prepare a Manager for a Termination Conversation

Prepare a manager for a termination conversation with clear talking points, compliance guardrails, and guidance on staying brief under emotional pressure.

You’ll needemployee role and tenurereason for terminationdocumentation already in placelogistics (final pay, benefits, equipment return)manager's concerns going in
Prompt
You are an HR partner preparing a manager for a termination conversation.

Prepare the manager using the context below.

Context:
- Employee role and tenure: [employee]
- Reason for termination: [reason]
- Documentation already in place: [documentation]
- Logistics to cover (final pay, benefits, equipment): [logistics]
- Manager's specific concerns going in: [concerns]

Instructions:
1. Keep the core message short and clear — a long, meandering explanation under emotional pressure tends to introduce inconsistencies or invite negotiation that a termination conversation shouldn't have.
2. Prepare language grounded in the documented reason, avoiding new justifications introduced in the moment that aren't backed by the existing record.
3. Cover required logistics clearly (final pay, benefits continuation, equipment return, access removal timing) so nothing is left ambiguous.
4. Prepare the manager for likely emotional reactions (shock, anger, requests to reconsider) with guidance to stay calm and not improvise new commitments on the spot.
5. Note what should NOT be said (speculation about the decision process, comparisons to other employees, anything that could be read as discriminatory).

Output format:
- Core message (short, documentation-grounded)
- Logistics to cover
- Guidance for handling emotional reactions
- Language and topics to avoid

Missing information policy:
Ask up to 2 concise questions only if the reason or documentation is unclear.

Quality bar:
- Core message is short and grounded in documentation.
- Logistics covered clearly.
- Explicit guidance on what not to say.
03

Review a Manager's Written Feedback for Consistency and Fairness Across Their Team

Review a set of a manager's written performance feedback across their team for language pattern inconsistencies that might reflect bias rather than genuine performance differences.

You’ll needset of performance feedback across team membersteam contextknown performance differencesreview cycle
Prompt
You are an HR partner reviewing performance feedback for consistency.

Review the feedback set below.

Context:
- Set of performance feedback across team members: [feedback set]
- Team context: [team]
- Known genuine performance differences: [performance differences]
- Review cycle: [cycle]

Instructions:
1. Look for language pattern differences that don't track with the stated performance differences — for example, similar accomplishments described with more assertive language for some employees and softer language for others.
2. Flag feedback that focuses on personality or style ("abrasive," "not a team player") for some employees but not others with comparable behavior, since this pattern often correlates with bias.
3. Check whether feedback specificity is consistent — vague feedback concentrated on certain employees while others get detailed, example-backed feedback is itself a signal worth flagging.
4. Note this is a pattern check, not a determination of intentional bias, and frame findings for a constructive conversation with the manager.
5. Recommend specific language changes where patterns are flagged.

Output format:
- Language pattern findings across the team
- Specificity consistency check
- Framing note for a constructive manager conversation
- Recommended language changes

Missing information policy:
Ask up to 2 concise questions only if the feedback set or performance differences are unclear.

Quality bar:
- Flags patterns, not assumed intent.
- Framed constructively, not accusatory.
- Includes specific recommended language changes.
04

Navigate a Complaint About Peer Conflict Without Prejudging Either Side

Work through how to investigate and respond to a peer conflict complaint fairly, gathering facts from both sides before forming a conclusion.

You’ll needcomplaint as reportedrelationship and history between the partiesteam contextany prior related incidentsurgency level
Prompt
You are an HR partner handling a peer conflict complaint.

Work through the situation using the context below.

Context:
- Complaint as reported: [complaint]
- Relationship and history between the parties: [relationship]
- Team context: [team]
- Any prior related incidents: [prior incidents]
- Urgency level: [urgency]

Instructions:
1. Plan to hear both sides before forming any conclusion, even if the initial complaint sounds clear-cut — a one-sided account is rarely the complete picture.
2. Separate what's directly reported (specific incidents, quotes, dates) from interpretation or characterization, since the investigation should focus on verifiable facts first.
3. Note if there's a power or seniority imbalance between the parties that could affect how comfortable either side is being candid, and adjust the process accordingly.
4. Recommend appropriate confidentiality boundaries during the process so the investigation doesn't become team-wide gossip before it's resolved.
5. Outline possible outcomes ranging from informal coaching to formal action, without prejudging which applies before the facts are gathered.

Output format:
- Fact-gathering plan (both sides)
- Facts vs interpretation separation
- Power-imbalance considerations
- Confidentiality approach
- Possible outcome range (not prejudged)

Missing information policy:
Ask up to 2 concise questions only if the complaint or relationship context is unclear.

Quality bar:
- Plans to hear both sides before concluding.
- Separates facts from interpretation.
- Doesn't prejudge the outcome.