Using Messages in an HR Complaint or Workplace Grievance

What messages can show

A useful message record answers a narrow question: what happened, when, between whom, and what followed? A direct message might record a supervisor’s instruction. A group chat may show that coworkers saw a remark. A later message may show that you reported it, asked for an adjustment, or corrected an inaccurate account. A series can show frequency and escalation more clearly than one screenshot.

Messages rarely tell the whole story. Tone can be ambiguous. A reaction emoji may mean different things to different people. A call, meeting, deleted post, or prior exchange may explain a sharp reply. Treat messages as records that support your account, not as a substitute for your account.

HR and workplace investigators commonly need to identify the allegation, relevant policy, people involved, witnesses, dates, and available records. They may compare the messages with calendars, access logs, emails, schedules, performance records, or interviews. Help them by connecting each message to an event rather than sending an unexplained archive.

Show a pattern without losing context

For repeated conduct, make a chronology first. Give every event a stable number. Write a neutral one-sentence description, then link the supporting message pages. Include uneventful gaps when they matter. For example, a timeline might show a complaint on 4 March, a rota change on 6 March, a follow-up on 11 March, and a performance warning on 20 March. It should not state that the sequence proves a motive. State the sequence and explain why you believe it matters.

Include enough messages before and after a selected passage to make its meaning fair. Preserve replies and quoted messages. Identify edits, reactions, attachment names, and missing media if the source shows them. Do not crop out your own unhelpful words. A candid record is more useful than a polished record that creates obvious questions.

Distinguish three categories in your notes:

1. what you personally saw, heard, sent, or received;
2. what a document records; and
3. what another person told you.

Use factual language. “At 10:14, Lee wrote…” is stronger drafting than “Lee was obviously plotting.” If a date is estimated, say so. If a display name was added by you, preserve the underlying handle and explain the label.

Preserve before you organize

Keep the original conversation in the app and retain the device where reasonably possible. Do not delete, edit, unsend, or annotate the source. Save attachments in their original form. Record the platform, account, conversation title, participants, date range, time zone, and how you collected the copy. If disappearing messages are enabled, document that promptly and ask the appropriate record owner to preserve material.

Screenshots are quick and may show familiar interface details, but they can omit the sender, year, preceding exchange, or attachment. Use overlapping screenshots if that is the only available method. A structured export can make a long thread easier to search and print. Keep both where practical, because the screenshot shows the display while an export can show continuity.

Text Exporter is coming soon for iPhone. It will process locally and create a PDF with a cover page, page numbers, and a SHA-256 manifest. Those features can help organize what the app received; they do not establish that the conversation was genuine before import or decide what an investigator accepts. The free incident log runs in the browser without uploading its contents.

Personal devices, work devices, and company accounts

The device and the account are separate questions. A personal phone may contain a company-controlled Teams or Slack account. A company phone may contain limited personal exchanges. Employers may retain, administer, monitor, suspend, or delete company accounts according to law and policy. Do not assume a work-device message is private or that you can access the account after leave, suspension, or dismissal.

Read the employer’s acceptable-use, monitoring, confidentiality, records, investigation, and bring-your-own-device policies. Preserve only material you are entitled to access. Do not bypass controls, guess another person’s password, use a colleague’s session, or install an unauthorized export tool.

Do not forward confidential company data merely because it may be relevant. Messages may include customer records, privileged legal advice, trade secrets, security details, health information, or unrelated employee data. Ask HR, your union, or an adviser how to preserve and identify the material without taking an unauthorized copy. A written preservation request can name the channel, custodians, and date range without reproducing its contents.

On a personal device, isolate a working copy from family photos and unrelated chats. Avoid broad cloud sharing links. If HR requests the device itself, ask what it needs, how review will be limited, who will see it, and when it will be returned. Consider advice before granting unrestricted access.

Writing the complaint and timeline

Start with the outcome you seek, if known: investigation, correction, safety measure, restored duties, training, or another response. Then set out allegations in numbered paragraphs. For each, identify the approximate date, conduct, people, location or channel, and linked evidence. Explain relevant context and impact without exaggeration.

A practical timeline has columns for:

Field	What to enter
Event ID	A stable number such as HR-014
Date and time	Exact, approximate, or a range
People/channel	Names, handles, Slack channel, Teams chat, or phone number
Event	A concise factual description
Record	Message page, email, document, photograph, or witness
Report/response	Who was told and what happened
Follow-up	Later event or unresolved action

Keep the narrative and evidence index separate. This lets an investigator read the issue first and verify each point second. Use consistent file names such as HR-014_Teams_2026-03-04.pdf. Paginate long PDFs. If you redact irrelevant personal information, keep an unredacted preserved copy, visibly mark the working copy, and list what category was removed.

US: internal reports, EEOC deadlines, and retaliation

An internal complaint and an EEOC charge are different processes. EEOC says a charge generally must be filed within 180 calendar days of discrimination. The period generally extends to 300 days where a state or local agency enforces a state or local law prohibiting discrimination on the same basis. Age-discrimination extensions have a different formulation, and federal employees have a separate process with shorter contact deadlines. The safest course is to check the official page and obtain advice early.

EEOC also states that using an internal grievance, union grievance, arbitration, or mediation generally does not extend the EEOC filing deadline. Do not wait for HR’s final report before checking time. Preserve proof of the event date, report date, acknowledgments, meetings, and outcome.

Federal EEO laws prohibit retaliation for protected activity. EEOC describes protected activity as participating in an EEO process or reasonably opposing conduct made unlawful by those laws. That does not make every workplace disagreement protected, and it does not immunize a worker from legitimate discipline. If treatment changes after a report, record facts: shift allocation, access changes, excluded meetings, warnings, comments, decision-makers, and dates. Avoid assigning motive as fact. An adviser can assess the legal connection.

For help, the EEOC provides charge information and LawHelp.org routes people to civil legal aid. A union representative may also explain a collective bargaining deadline or grievance route.

England and Wales: the Acas grievance framework

As of 29 September 2026, Acas’s 2015 Code of Practice remained the operative statutory Code. Acas had published a proposed replacement, but clearly labelled it a consultation draft. The current Code says grievances should be raised in writing without unreasonable delay, stating the nature of the grievance. Employers should hold a meeting without unreasonable delay, allow the employee to explain the grievance and how it might be resolved, communicate a decision in writing, and offer an appeal.

The Code is a framework, not a complete workplace policy. Read the employer’s procedure too. Keep the grievance letter, attachments, meeting invitation, notes, decision, and appeal. If minutes are inaccurate, send a prompt, measured correction. A companion may have a statutory role at a formal grievance meeting in qualifying circumstances; check the current Acas guidance.

Failure to follow the Code does not by itself create a claim. It can be relevant if a matter reaches an employment tribunal. Do not let the grievance timetable obscure tribunal time limits. The UK employment tribunal guide explains Acas early conciliation and current limitation changes.

Acas offers a free helpline. Citizens Advice and a trade union may also help. Where discrimination, dismissal, whistleblowing, safety, immigration status, or professional regulation is involved, timely specialist advice can matter.

Submitting a usable evidence package

Send the smallest package that fairly explains the complaint, unless the procedure asks for more. A sound package contains:

• a short complaint with numbered allegations;
• a chronology;
• an index of message extracts and other records;
• legible, consecutively numbered pages;
• an explanation of collection method and time zone;
• a list of retained originals and known gaps; and
• a request that the employer preserve named company records.

Ask for secure delivery instructions. Confirm receipt in writing. Keep the exact submitted version and any later supplement. If HR asks for more context, provide it rather than silently replacing the first file. This creates a clear record of what each person had at each stage.

The goal is not to overwhelm the investigator. It is to make relevant events easy to find, to preserve what exists, and to be candid about what the messages cannot show.