Best AI for Human Resources: Can It Draft a Grievance Report?

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for Best AI for Human Resources: Can It Draft a Grievance Report?
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for Best AI for Human Resources: Can It Draft a Grievance Report?

Yes, for structure: AI can turn coded interview notes into an allegation list, an evidence table and a neutral first draft of the report. It must never decide outcomes. Keep names, health details and witness identities out of consumer tools, use a business plan that does not train on your content, and follow the client's own grievance procedure and local law.

The risk in a grievance report is rarely a wrong comma. It is a sentence that sounds certain where the notes were not, a witness who becomes identifiable, or a finding that nobody can trace back to evidence. Used well, AI helps with the dull mechanical work (sorting forty pages of notes by allegation, building a timeline, spotting where two accounts clash). Used badly, it smooths over the very conflicts a fair investigation exists to expose.

Follow me on Instagram@sagnikteaches

Three tiers of material, and what each is allowed to touch

Before any tool opens, sort what you hold into three tiers. The tiers decide where each piece of work happens.

Connect on LinkedInSagnik Bhattacharya
TierWhat it containsWhere it can go
RedNames, job titles that identify one person, health or family details, protected characteristics, employee numbers, contact details, the original signed statementsYour own secure storage only. Never into an AI tool, even a business one, unless the client's contract explicitly allows it
AmberCoded notes: "C" for the complainant, "R" for the respondent, "W1" to "W5" for witnesses, with dates shifted to "Day 1, Day 14" and places generalisedA business-tier assistant with no training on your content, in an account you control, with chat history you delete on closure
GreenThe report template, the client's procedure with the company name removed, your own headings, generic definitionsAny tool you normally use

The practical consequence is that the identity key (who "W3" is) stays in a single spreadsheet that never leaves your own storage. If a tool provider were breached or an account were shared by accident, the notes would not identify anyone by themselves. That is not perfect protection, because small teams can often be recognised from the content alone, which is why the next step matters.

Subscribe on YouTube@sagnikteaches

Coding the notes: a before and after

Coding is the step people skip and the one that matters most. Do it by hand or with find-and-replace in your own word processor, not with an AI tool, because asking the tool to remove names means it has already seen them.

An illustrative extract from a set of interview notes, before coding:

Interview with [first name] (recruiter), 14 March, 10:30.
[First name] said that at the Monday pipeline meeting [team leader]
told her in front of the team that her placements were "a joke".
She says this has happened "at least four times since January".
She was off sick with anxiety for two weeks in February.

After coding:

Interview with W2 (recruiter on C's team), Day 14, 10:30.
W2 said that at the weekly pipeline meeting R told C in front
of the team that C's placements were "a joke".
W2 says this has happened "at least four times" in the period.
[Health information removed. Held in secure file, ref H-2.]

Notice three decisions. The date moved to a relative day, because a precise date plus a small team identifies people. The health detail was cut from the working copy and logged separately, because the report may not need it at all. And the quotation of the alleged remark stayed, because it is evidence. If a remark itself contains a name or a nickname, replace that too and keep the key.

The Complete Excel Course with AI Integration thumbnail

The Complete Excel Course with AI Integration

From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.

By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner

Buy now

A grievance at a 22-person recruitment agency, step by step

Say a recruitment agency with 22 staff has received a written grievance from a consultant (C) against her team leader (R). She alleges three things: that R criticised her work in front of colleagues, that she was left out of two client calls she would normally join, and that her commission split was changed without explanation. The client (the agency's managing director) has appointed you, an outside HR consultant, to investigate under the company's grievance procedure. You have interviewed C, R and three witnesses. Your notes run to 14 pages.

Step 1: build the allegation list from the grievance letter

Give the assistant the coded grievance and ask for a numbered list of allegations, each as one sentence, with the grievance paragraph it came from. This forces the question "what exactly is being alleged?" before the evidence appears.

You are helping an HR investigator. Below is a coded grievance
letter. Do not infer anything not stated.
1. List each separate allegation as one neutral sentence.
2. For each, give the paragraph number it comes from.
3. List any allegation that is unclear and what clarification
   would be needed. Do not guess.
[paste coded grievance]

A realistic output gives three allegations (A1 public criticism, A2 exclusion from client calls, A3 commission change) and one flagged item: "Paragraph 4 says C was 'treated differently' but does not say how. Clarification needed." That flag is useful. It tells you to go back to C before you finalise the terms of reference. If the tool had quietly folded that sentence into A1, your report would investigate something the complainant never specified.

Step 2: sort every note line under an allegation

Now paste the coded interview notes, one interview at a time, and ask for an evidence matrix. The rule that makes this safe: every line in the output must quote the note and carry its interview and page reference, so you can check it in seconds.

For allegation A1 only, extract every statement in the notes
below that supports, contradicts or is neutral on the allegation.
Output a table: Interview | Note page | Exact quote | Supports /
Contradicts / Neutral | Is it first-hand or hearsay?
Quote the notes word for word. If you cannot find a quote, write
"none found". Do not paraphrase.

Illustrative output for A1, trimmed to two rows:

InterviewPageExact quoteDirectionSource
W25"R told C in front of the team that C's placements were 'a joke'"SupportsFirst-hand
R9"I said the figures were poor, not that she was"Contradicts (partly)First-hand

You then open page 5 and page 9 and confirm each quote exists. Where a quote does not appear word for word, the row goes. In this illustrative case the first pass produced eleven rows for A1 and two failed the check: one paraphrase presented as a quotation, and one line attributed to W3 that actually came from W4. Two bad rows out of eleven, either of which could end up quoted in a finding, is why the check is not optional.

Step 3: ask for the conflicts, not the answer

The most valuable AI pass is the one that sets accounts side by side without choosing between them.

Using only the evidence table, list each point where two
accounts conflict on A1. For each, state the two versions in
neutral wording, who gave each, and what further evidence
(document, message, third person) could resolve it. Do not say
which account is more credible.

A sample result: "Point 1: whether the 'a joke' remark was made at the meeting on Day 9 (C, W2) or was a comment on a spreadsheet (R). Resolving evidence: the meeting calendar entry, any slide or message in the team channel." That list is a to-do list for your next hour. You may still need a second interview with R. The credibility assessment, and the balance-of-probabilities reasoning if the client's procedure uses that standard, stays entirely with you.

Step 4: draft the report sections you will edit

Only now do you ask for prose. Give the template below, the verified evidence table and your own bullet findings, and ask the tool to write sentences that restate your reasoning in plain language. If you have not written the findings, there is nothing safe to ask it to write.

Step 5: build a timeline from the same coded notes

Allegation A2 (exclusion from two client calls) turns on dates, so ask for a timeline rather than a narrative. Paste the coded notes and the coded calendar extract and request one row per dated event, with the source reference and a column for "agreed or disputed".

DayEventSourceStatus
Day 3Client call with Account X, C not on inviteCalendar extract, W4 p3Agreed
Day 3R says C was "too busy that morning"R p10Disputed (C p2: no other bookings)
Day 11Second call, C added 20 minutes beforeW3 p6Disputed on whether R knew

The "Status" column is the useful one. Three rows marked disputed tell you precisely which questions a follow-up interview must settle, and the calendar entries give you something better than anyone's memory. If the tool fills the column with "likely" or "probably", reject the row: status is either what two sources say or it is blank.

When the respondent is the person who hired you

Small agencies sometimes ask an outside consultant to investigate a complaint about the owner. The AI rules do not change, but the confidentiality stakes do, because the person paying you may also be the subject of the notes. Agree in writing who receives the report, keep drafts out of any shared client folder, and do not let the client's own IT account hold the chats. Your independence is the point of the engagement, and a tool setup that routes case material through the respondent's systems undermines it.

A report skeleton you can copy

Most reports that go wrong have the same structural flaw: findings float free of evidence. This skeleton ties each finding to references.

1. Purpose and terms of reference
2. Procedure followed (client's procedure, dates, who was seen)
3. Allegations (A1, A2, A3 as clarified with the complainant)
4. Evidence considered (interviews, documents, with references)
5. For each allegation:
   a. Summary of the complaint's account
   b. Summary of the response
   c. Other evidence
   d. Points of agreement and dispute
   e. Finding, with reasons, using the client's standard
6. Matters outside the terms of reference (noted, not decided)
7. Recommendations for the client to consider
Appendices: interview records, documents list

Section 5e is yours alone. A good test of the whole report: could someone who has never met the parties follow each finding by clicking from the finding to the reference list and then to the interview page? If yes, it will stand up to an appeal.

Where AI quietly distorts an investigation

These are the failures I would watch for, each with how it shows up.

  • Certainty creep. Notes say "W3 thought R was in the room"; the draft says "R was present". Check by searching every definite statement in the draft against the source line. A quick prompt helps: "List every statement in this draft that is stated more firmly than the source quote."
  • Merged witnesses. Two witnesses describe similar events on different days and the draft treats them as one incident. Count incidents in your own timeline before and after the draft.
  • Tone drift. "R was aggressive" is a conclusion. "W2 described R raising his voice" is evidence. Ask for a pass that flags adjectives and replaces them with attributed descriptions.
  • Averaging. A summary of "mixed views" hides that three witnesses saw the event and one heard about it later. Always keep first-hand against hearsay in the table.
  • Invented procedure. If you ask what "usually" happens next, the tool will describe a generic process that may contradict the client's. Paste the client's actual procedure, with the company name removed, and ask it to check your report against that, nothing else.

Choosing an assistant for grievance work

For this job, "best" means safest for amber-tier material, not cleverest. Sorting, quoting and cross-referencing coded notes is well within what any mainstream business assistant can do, so three practical questions decide it faster than a feature list.

QuestionWhy it matters in a grievanceWhat to look for
Does the plan train on your content?Coded notes still describe a real dispute between real colleaguesA business plan whose own pricing or privacy page says no training by default
Where does the case material already live?Moving files into a new system is itself a disclosure to a new processorYour own business account, or the client's existing setup if the client asks for that and the respondent does not control it
Can you delete and show that you did?Case closure needs a clean, recorded endPer-conversation deletion, separate projects per case, and retention settings you can see

One detail on Microsoft's side is worth knowing before you try it. Its Copilot privacy page says some Copilot scenarios restrict the use of generative AI for inferences, judgements or evaluations about an employee's performance, attitude, emotional state or personal characteristics. Expect pushback, then, if you ask Copilot whether a witness seems credible or a respondent seems hostile. That costs you nothing: those are exactly the judgements this process keeps with the investigator. Ask any assistant for the evidence matrix, the conflict list and the reference checks, and it is doing the part of the job it is suited to.

A quick illustration of the difference. Asked "Based on these notes, is R's account believable?", a well-behaved assistant should decline or hedge. Asked "List each point where R's account differs from W2's, with page references", it produces something you can check line by line in ten minutes. If a tool happily answers the first question with a confident verdict, treat that as a reason to tighten your prompts, not as help.

Confidentiality: what to decide before the first prompt

Grievance cases hold the most sensitive material an employer owns. Four decisions belong in writing before you start.

  1. Is any outside processor allowed? Read your engagement letter and the client's policies. Some clients forbid third-party processing of case files altogether. If so, AI use is limited to green-tier work such as templates.
  2. Which plan? Consumer chat accounts may use conversations for model training unless you switch that off in privacy settings, and the switch labels change. Anthropic's pricing page lists no model training on your content by default for Claude Team, and Microsoft's Copilot privacy page says prompts, responses and data accessed through Microsoft Graph are not used to train its foundation models. For ChatGPT Business or any other assistant, find the equivalent statement on the vendor's own privacy page before you rely on it. Claude Team is sold for teams of 2 to 150, so a solo consultant either pays for two seats or uses an individual paid plan with training switched off; check the minimum on any other business plan you consider.
  3. Retention. Delete conversations at case closure, and record that you did. For Claude consumer accounts, Anthropic says chats are kept for up to five years if you allow training and for its standard 30-day period if you do not, so the setting matters. Keep the closing note in the case file.
  4. Who else can see it? Turn off sharing links, check browser extensions, and keep case chats in their own project so nothing leaks into other work through memory features.

Data-protection law gives employees rights over information held about them, including the possibility of a later request for their records. A coded working copy, an identity key and a deletion log make that easier to handle. The redaction tutorial covers the mechanics of removing personal data before sharing documents.

Five further checks, each with an example

A before-and-after of neutral wording

Draft sentence from the tool: "R's behaviour was clearly intimidating and unprofessional." Your edit: "W2 and W4 both said R spoke loudly across the room while C stood at her desk. R accepts he raised his voice but says the room was noisy." The second version gives the reader the evidence and the dispute, and leaves your conclusion to section 5e.

A prompt for that adjective pass: "Underline every adjective or adverb in this draft that describes a person's behaviour, and for each give the interview reference that supports it. If there is none, say 'no source'." In the illustrative case the tool found six such words, four of which had no source at all. Two were then supported by W4's account and stayed, rewritten as attributed description. The other four came out. Running this pass last, after you have edited, catches the phrasing that crept back in during rewrites.

A completeness check against the terms of reference

Ask: "List each allegation in the terms of reference and show whether the draft has a finding for it. Flag any finding about something not in the terms." In the illustrative case it flagged that the draft commented on C's wider workload, which nobody had asked about. That paragraph moved to section 6.

A reference check on the finished draft

Export the final draft and the evidence table and ask for a list of every reference in the draft (for example "W2, p5") that does not match a row in the table. You are looking for typing slips, not insight. This is the type of cross-checking a tool does faster and more reliably than a tired reviewer at 6pm.

A mistake that showed up late

In one illustrative case the coded notes used "W3" for two people because the consultant restarted the numbering on a second interview day. The matrix attributed a damaging remark to the wrong witness. The slip was caught only because the quote check sent the consultant back to page 7. The lesson: write the identity key first, never reuse a code, and read the key against the table before drafting.

A quick sum for the time

With five witnesses and 14 pages of notes, hand-writing the first draft might take about 9 hours. With coding (2 hours), four AI passes (1 hour) and verification and finding-writing (3 hours), the same draft takes about 6 hours. The saving is real but modest, and almost all of it comes from the evidence matrix and the reference checks. Do not expect AI to halve a careful investigation.

Related jobs: planning, bundles and policies

The report is one job. Planning the investigation as a whole, including interview preparation and what to delegate, is in AI in workplace investigations. If the client has an employment lawyer in the loop, grievance bundles and letters for employment lawyers shows what a bundle needs. For the broader consultant workflow, how HR consultants use AI for policies, letters and cases sets the context, and keeping data private when a team uses AI is useful for the safeguards you will agree with a client.

A pre-send checklist for the report

  1. Every allegation in the terms of reference has a finding or a stated reason why not.
  2. Every factual sentence carries a reference to an interview page or document.
  3. Every quotation has been checked against the source, word for word.
  4. First-hand and hearsay evidence are labelled as such.
  5. Findings use the standard in the client's procedure and give reasons in your own words.
  6. No codes, key or health detail leak into the final version unless needed, and names appear only where the client's procedure requires them.
  7. AI conversations are deleted and the deletion is recorded.
  8. The client's own procedure was followed in order, and you have noted any departure and why.

Treat the report as your document, not the tool's. If you could not explain every sentence to the parties' representative without the draft in front of you, rewrite the sentence. The tools in this tutorial are good at sorting, comparing and tidying. Decisions about people stay human, and where the case turns on legal questions, such as whether a process was fair in law, take advice from a qualified employment lawyer.

Grievance report drafting questions

Can I paste witness statements straight into ChatGPT?

Not into a free or personal account. Statements hold names, health details and allegations about identifiable people. Replace names with codes first, use a business plan that does not train on your content, and check your client contract allows any outside processor to see the material at all.

Should the AI recommend whether to uphold a grievance?

No. Ask it to list evidence for and against each allegation and flag conflicts, then write the finding yourself. The reasoning that leads to an outcome is your professional judgement, and you must be able to defend it without reference to what a tool said.

Do I need to tell the client or the witnesses I used AI?

Check your engagement terms and the client's procedure first. A line in the engagement letter naming the tools that will touch case material settles the question up front, and safeguards are easier to agree before the case starts than to explain afterwards. Whether witnesses are told is a matter for the client's procedure and your own professional judgement.

How long should the AI-assisted draft take?

For a case with five witnesses and about 14 pages of notes, expect roughly two hours to code the notes, one hour for the AI passes, and two to three hours of your own checking and finding-writing. Verification is the part you cannot shorten.

Further reads

Sources: Claude pricing page (Team plan, 2 to 150 seats, no training by default); Microsoft Learn, Data, Privacy and Security for Microsoft Copilot (training statement, workplace-harms restriction); Anthropic's consumer terms update and privacy centre (retention). Case details and figures are illustrative.

Want a safe AI step in your investigation process?

On a 1:1 call we'll walk through how you take notes and write reports now, pick the steps where AI is safe to help, and set the confidentiality rules your clients will accept.

Book a 1:1 call with me