These prompts are for HR Managers who need to document, respond to, or escalate grievances accurately and without exposing the organisation to liability. Each one produces a finished piece of writing you can review, lightly edit, and use today.
These prompts pair well with Jasper AI for HR Managers-specific tone control, or Copy.ai for fast iteration.
Acknowledging and Logging a Grievance
You are an HR Manager writing a formal grievance acknowledgement letter.
Employee name: {employee_name} Date grievance was submitted: {submission_date} Method of submission: {submission_method: written / verbal / email / HR portal} Nature of grievance (general category only, no detail in the letter): {grievance_category: harassment / pay dispute / unfair treatment / working conditions / other} Assigned case reference number: {case_reference} Estimated timeframe to respond per company policy: {response_timeframe: e.g. 10 business days} HR contact for questions: {hr_contact_name_and_email}
Write a 150 to 200 word formal acknowledgement letter. Confirm receipt, assign the case reference, state the next step and timeframe, name the HR contact. Tone: professional and neutral. Do not make any admission of wrongdoing or judgement about the grievance at this stage. Close with a statement that the process will be handled confidentially.
When to use it: The moment a grievance lands in your inbox and you need to send an acknowledgement the same day before you have done any investigation.
Pro tip: If the grievance was submitted verbally, add “verbal” in {submission_method} and the AI will word the letter so it functions as the written record of that conversation — saving you from having to draft a separate memo.
You are an HR Manager creating an internal grievance intake log entry.
Employee name: {employee_name} Employee ID: {employee_id} Department: {department} Date received: {date_received} Summary of grievance as stated by employee: {grievance_summary_in_one_to_three_sentences} Alleged party (job title only, no name): {alleged_party_title} Urgency level based on initial review: {urgency: low / medium / high / immediate} Assigned investigator: {investigator_name}
Write a 100 to 150 word internal log entry formatted as a structured case note. Include all variables above. Add a field for “Initial HR assessment” and write two sentences on whether the grievance appears to fall under policy, and whether any interim protective measures are needed based on the urgency level. This entry is internal only. Tone: factual and clinical.
When to use it: Before your first investigative meeting, when you need a clean intake record that holds up during an audit or tribunal disclosure.
Pro tip: If urgency is “immediate” (e.g. a harassment allegation involving physical threat), the AI will flag interim protective measures — but always run those by legal before acting on them regardless of what the output says.
You are an HR Manager writing a grievance triage memo for your CHRO.
Employee name (use initials only): {employee_initials} Grievance category: {grievance_category} Date submitted: {submission_date} Departments involved: {departments_involved} Number of employees potentially affected: {number_affected} Any prior related grievances in the last 12 months: {prior_grievances: yes / no — if yes, briefly describe} Recommended next step: {recommended_action: formal investigation / mediation / manager conversation / legal review}
Write a 200 to 250 word triage memo. Open with a one-sentence summary of the situation. Include a risk assessment paragraph that covers reputational, legal, and operational exposure. Close with your recommended next step and the rationale. Tone: direct, executive-ready. No jargon.
When to use it: Friday afternoon when something escalates and your CHRO needs a written briefing before Monday’s leadership meeting.
Pro tip: Swap {number_affected} for “unknown at this stage” if you haven’t completed your initial scoping — the AI handles that gracefully and notes it as a gap requiring follow-up, which looks more credible than leaving the field blank.
You are an HR Manager writing a grievance acknowledgement for a collective grievance submitted by a group of employees.
Number of employees who signed: {number_of_signatories} Department or team: {team_or_department} Date submitted: {submission_date} Core grievance issue: {core_issue: e.g. shift scheduling changes / pay structure / management conduct} Union or employee rep involved: {union_or_rep: yes — name rep / no} Case reference: {case_reference} First formal meeting date: {first_meeting_date}
Write a 180 to 220 word collective grievance acknowledgement letter addressed to the group. Confirm receipt, reference the case number, name the rep if applicable, and set out the steps of the collective grievance process. State that each signatory’s confidentiality will be protected to the extent possible. Tone: formal, fair, and clear.
When to use it: When more than one employee signs the same grievance form and your standard individual acknowledgement letter would read oddly.
Pro tip: If a union rep is involved, include their name in {union_or_rep} — the AI will adjust the letter’s language to acknowledge their formal role, which avoids any grievance from the rep themselves about being overlooked.
You are an HR Manager writing a short internal email to a line manager notifying them that a grievance has been received involving their team.
Manager name: {manager_name} Your name: {hr_manager_name} Grievance category (no identifying details): {grievance_category} Date HR received it: {receipt_date} Any action the manager must avoid during the investigation (e.g. roster changes, 1:1 meetings with complainant): {restricted_actions} Next step the manager should expect: {next_step: e.g. investigative interview request / no action required yet}
Write a 150 to 180 word internal email. Inform the manager a grievance has been lodged involving their team. Do not name the complainant. Instruct them clearly on what they must not do during the investigation period. State the next step. Tone: firm but collegial. The manager should not feel accused but must feel the instruction is non-negotiable.
When to use it: Within 24 hours of receiving a grievance when the accused or affected manager needs to be kept in the loop without compromising the investigation.
Pro tip: Specify {restricted_actions} precisely — “no 1:1s with the complainant” is far more useful than “act normally”. Vague instructions in this email are the most common source of procedural contamination in grievance cases.
Conducting and Documenting the Investigation
You are an HR Manager writing a formal investigation interview record following a meeting with a grievance complainant.
Complainant name: {complainant_name} Date and time of interview: {interview_datetime} Location: {location: in-person / video / phone} HR Manager present: {hr_manager_name} Support person present: {support_person: name and role, or “none”} Key points raised by complainant (bullet form): {complainant_key_points_in_bullets} Any documents or evidence referenced: {documents_referenced: or “none”} Complainant’s requested outcome: {requested_outcome}
Write a 300 to 400 word formal interview record. Open with the date, attendees, and purpose. Summarise the complainant’s account in the third person. Note any evidence referenced. Record the requested outcome verbatim. Close with a statement that the record was read back to the complainant and {read_back_confirmed: confirmed / not confirmed}. Tone: neutral, factual, no editorial comment.
When to use it: Immediately after your investigation interview while your notes are fresh — paste in your bullet points and get a clean narrative record you can send for sign-off.
Pro tip: Always include a {support_person} value even if it’s “none” — an employment tribunal will want to see that the right to bring a support person was offered and recorded, not just that the interview happened.
You are an HR Manager writing a witness interview summary following an investigation into a workplace grievance.
Witness name: {witness_name} Witness job title: {witness_job_title} Relationship to complainant: {relationship: direct colleague / line manager / indirect colleague / other} Date of interview: {interview_date} Key points the witness raised: {witness_key_points_in_bullets} Any contradictions with complainant’s account: {contradictions: describe briefly, or “none identified”} Credibility observations (factual only): {credibility_notes: e.g. consistent with documentary evidence / unable to confirm key dates}
Write a 250 to 300 word witness summary. Third person throughout. Start with a factual header block: name, title, date, interviewer. Summarise testimony without leading language. If contradictions exist, note them neutrally. Close with a one-sentence credibility assessment that is grounded only in observable facts, not character judgement. Tone: forensic and neutral.
When to use it: When you have spoken to three or more witnesses and need each account documented consistently before you compile your investigation report.
Pro tip: Never write “the witness appeared nervous” or “seemed credible” in {credibility_notes} — these read as character assessments and get challenged at tribunal. Stick to “consistent with CCTV footage dated {date}” or “unable to confirm the time of the incident despite two opportunities”.
You are an HR Manager writing a respondent interview record for an employee named as the subject of a grievance.
Respondent name: {respondent_name} Respondent job title: {respondent_job_title} Interview date: {interview_date} HR Manager conducting: {hr_manager_name} Respondent’s support person: {support_person: name and role, or “none”} Summary of allegations put to respondent: {allegations_summary_in_bullets} Respondent’s response to each allegation: {responses_in_bullets} Any evidence respondent provided or referenced: {respondent_evidence: or “none”}
Write a 300 to 380 word formal respondent interview record. Open with the standard header. Record each allegation followed by the respondent’s reply, clearly separated. Note any evidence they provided. Record whether the respondent was informed of their right to respond in writing within {written_response_deadline: e.g. 5 business days}. Tone: strictly neutral — no language that implies guilt or innocence.
When to use it: After the respondent interview, before you compile findings — having a clean per-allegation structure now makes your investigation report significantly faster to write.
Pro tip: If the respondent denies everything, make sure the prompt output captures that denial specifically per allegation, not as a blanket statement. Blanket denials without per-allegation records create gaps that defence lawyers exploit.
You are an HR Manager writing an investigation findings report for a mid-level workplace grievance.
Case reference: {case_reference} Nature of grievance: {grievance_nature} Complainant (use initials): {complainant_initials} Respondent (use job title only): {respondent_job_title} Investigation dates: {investigation_start_date} to {investigation_end_date} Key findings (bullets): {findings_in_bullets} Evidence reviewed: {evidence_list_in_bullets} Conclusion: {conclusion: grievance upheld / partially upheld / not upheld} Recommended action: {recommended_action}
Write a 450 to 550 word investigation findings report. Use the following structure: Executive Summary (50 words), Background (80 words), Evidence Reviewed (bullet list), Findings (narrative, one paragraph per key finding), Conclusion, Recommended Action. Tone: formal, third person. Cite evidence against each finding. Avoid language that assigns moral fault — use “the evidence supports” or “the evidence does not support”.
When to use it: When you have completed all interviews and evidence review and need to produce the formal written conclusion before a grievance outcome meeting.
Pro tip: Use “partially upheld” in {conclusion} only when you have separate findings that go different ways — the AI will split your findings section accordingly, which prevents the report reading like a muddled compromise.
You are an HR Manager writing a one-page investigation timeline for a complex grievance case involving multiple incidents.
Case reference: {case_reference} Grievance category: {grievance_category} Timeline events (list each incident with date, description, and source): {timeline_events_in_bullets} Date grievance was formally submitted: {formal_submission_date} Date investigation opened: {investigation_open_date} Current date: 2026-07-09 Key gap or disputed date (if any): {disputed_date_or_gap: or “none”}
Write a 200 to 250 word narrative timeline, then present the same information as a clean chronological table with columns: Date | Event | Source. Use past tense throughout. If a disputed date exists, flag it in both the narrative and the table with a note: “date disputed — see witness record [reference]”. This document is for internal use in the investigation file.
When to use it: When an alleged pattern of behaviour spans weeks or months and you need a single document that shows the sequence clearly before your findings meeting.
Pro tip: The table format is what legal teams and employment tribunals actually use when reviewing case files. Getting it right at the documentation stage saves a paralegal 90 minutes of reconstruction work if the case escalates.
Drafting Outcome Letters
You are an HR Manager writing a grievance outcome letter where the grievance has been upheld.
Employee name: {employee_name} Date of outcome meeting: {outcome_meeting_date} Grievance category: {grievance_category} Summary of what was upheld: {upheld_summary_in_one_to_two_sentences} Action being taken as a result: {action_taken: e.g. formal warning issued to respondent / process change / management training} Right of appeal: {appeal_right: yes / no} Appeal deadline: {appeal_deadline: e.g. 10 working days from this letter} Appeal contact: {appeal_contact_name_and_title}
Write a 220 to 280 word formal outcome letter. Confirm the outcome, state what was found, describe the action being taken without disclosing confidential details about the respondent’s outcome. Close with the appeal process. Tone: clear, fair, resolved. Do not be warm — this is a formal document. Do not reference the respondent by name.
When to use it: The day after the outcome meeting, when you have verbal agreement on the decision and need the written confirmation letter ready before end of business.
Pro tip: “Without disclosing confidential details about the respondent’s outcome” is legally important — the AI will naturally want to say what happened to the other person, so specify in your edit pass that the respondent’s specific sanction stays out of the complainant’s letter.
You are an HR Manager writing a grievance outcome letter where the grievance has not been upheld.
Employee name: {employee_name} Date of outcome meeting: {outcome_meeting_date} Grievance category: {grievance_category} Reason the grievance was not upheld (in plain language, without assigning blame): {reason_not_upheld} Any supportive action being offered regardless of outcome: {supportive_action: e.g. mediation offered / additional 1:1 check-ins / none} Right of appeal: {appeal_right: yes