What should HR do with this employee concern?
Support the employee and test the account before making a finding.
The question
You are Harbor’s HR partner. Mira reports that her Friday shift was removed after she raised a safety concern on November 4. The manager says a rota change was planned on November 2. An AI summary calls this proven retaliation. All people and records are invented.
Use an independent fact reviewer. Limit case access to people who need it for support or review. Reprisals for raising a concern are not permitted. Explain the next contact and what can be kept private.
- MiraMy Friday shift changed after I raised the concern. I am worried about my next shift.
- ManagerThe rota change was planned before the report. I can provide the file.
“What should HR do with this employee concern?”
Not saved by this site. Your browser may restore text when you navigate back.
A strong answer, step by step
Open each step in turn. This is one strong answer, not the only one.
Step 1: Acknowledge the concern without deciding it
What would you do here? Open the move you’d make.
Tell Mira the allegation is proved by the timing.
Tempting, but it misses something. Timing alone does not establish what happened or why.
Check support needs and explain the review.
The strong move. This responds without prejudging the account.
Close the concern because the manager disagrees.
Tempting, but it misses something. A conflicting account needs review, not dismissal.
See how a strong candidate says it
“Take the concern seriously, check immediate support needs and explain the independent review. The AI label is not a finding.”
Why it works: An allegation and a conclusion need different evidence.
Step 2: Preserve the records and hear both accounts
What would you do here? Open the move you’d make.
Send the complaint to the whole team for comment.
Tempting, but it misses something. That exposes the employee and can affect later accounts.
Promise that no one else will ever see the concern.
Tempting, but it misses something. The reviewer may need to share relevant facts.
Preserve dated records and agree a limited review plan.
The strong move. This protects the evidence and gives both accounts a fair hearing.
See how a strong candidate says it
“Preserve rota versions and messages. Take separate accounts through the reviewer, limit access and explain who needs the information. Do not promise absolute confidentiality.”
Why it works: A fair review needs relevant records and clear information boundaries.
Step 3: Test the new chronology
The rota file was first created on November 2, but Mira’s shift was edited on November 5. A November 4 message shows that the manager knew a concern had been raised.
What would you do here? Open the move you’d make.
Treat the November 2 file date as complete exoneration.
Tempting, but it misses something. Mira’s shift changed in a later edit.
Review the individual edit and the manager’s explanation.
The strong move. This follows the specific decision that is in dispute.
Treat knowledge of the concern as proof of retaliation.
Tempting, but it misses something. Knowledge and sequence alone do not establish motive.
See how a strong candidate says it
“The earlier file does not settle the individual change. Ask the reviewer to examine the November 5 edit, its reason and the relevant messages. Keep the motive question open.”
Why it works: The new records narrow the question without proving motive.
Step 4: Explain the next step and check support
What would you do here? Open the move you’d make.
Wait silently until every issue is resolved.
Tempting, but it misses something. The employee still needs a clear next step.
Publish the AI summary as the final report.
Tempting, but it misses something. The accounts and records have not been resolved.
Confirm the review owner, next contact and support check.
The strong move. This keeps the process accountable without announcing a finding.
See how a strong candidate says it
“Tell Mira who will contact her next and when, within Harbor’s process. Keep the interim arrangement neutral and ask the reviewer to flag any pressure or further change.”
Why it works: A review still needs follow-through and support while facts are checked.
The answer, in short
- Decision
- Continue an independent fact review with a clear support plan.
- Because
- The new chronology needs explanation; neither initial account settles it.
- What would change it
- Corroborated records and the completed review may support a finding under Harbor’s procedure.
Common traps
- Letting an AI summary decide a disputed concern.
- Promising secrecy that the review cannot keep.
Check your answer
- Did I check immediate support?
- Did I separate the allegation from a finding?
- Did I preserve relevant versions and messages?
- Did I explain the next contact?
Last reviewed Nov 10, 2026