Build a chat and email index before anyone reviews your file

A chat and email index is a list with one row per important thread or message: the date and time, the platform, the participants described by role, the key message in a sentence, why it matters to your timeline, and where the original lives. It lets a reviewer understand hundreds of messages in a few minutes and ask for the ones they need.

Pair the index with screenshots that show dates, senders and the surrounding messages, and do not crop in a way that changes the meaning. Index messages on employer-owned platforms instead of bulk exporting them, and include other people's messages only where they are part of your own conversation and needed to understand it.

Workplace conversations are spread across work email, a team chat tool, a direct message channel, text messages on a personal phone, and sometimes comments inside shared documents. The important line is often a short reply buried under forty messages about something else, or a thumbs-up reaction that someone later says meant 'seen' rather than 'agreed'.

Someone reviewing your situation, such as an employment lawyer at a first consult, a union rep or an HR investigator, usually has limited time. A phone handed across a desk with 'scroll up to February' is hard to work with. A two-page index that says exactly which messages matter, and where to find them, is not.

• An ID you assign, such as C-01 for chats and E-01 for emails, so your timeline can point to it.
• Date and time of the key message, plus the date range of the thread if it ran over several days.
• Platform and location: work email, team chat channel name, direct messages, personal text messages.
• Participants by role, such as 'my manager', 'payroll coordinator', 'two team members', never full names in anything you share widely.
• The key message, quoted briefly or closely paraphrased, with a note on which you used.
• Why it matters: the change, instruction, request or response it records.
• Copy status: screenshot saved, email saved as PDF, or not copied and still on the original platform.

Keep the 'why it matters' column factual. 'Manager asks me to start covering weekend shifts' is useful. 'Manager starts punishing me' is a conclusion a reviewer will want to reach, or not, on their own.

• C-04 | 2026-01-19, 4:52 p.m. | Team chat, direct messages | My manager to me | Quoted: 'Starting next week, please own the month-end reports as well.' | First mention of added duties | Screenshot saved, shows the two messages before and my reply.
• E-11 | 2026-02-03, 9:08 a.m., thread to 2026-02-05 | Work email | Me to payroll coordinator, my manager copied | Paraphrased: I asked why January overtime was missing; payroll replied it needed manager approval | Pay question raised in writing | Not copied; still in work inbox, folder Payroll.
• T-02 | 2026-02-20, 7:41 p.m. | Text message, personal phone | My manager to me | Quoted: 'Can you come in at 6 tomorrow instead of 8?' | Schedule change outside the posted schedule | Screenshot saved with date header visible.

A screenshot is only as useful as the context it carries. Many chat apps show a date header only once per day, and phones often show just a time. If the date is not on screen, scroll until the date divider is visible and capture it, or take two overlapping screenshots and note that they belong together.

• Include the sender's name or role label and the timestamp for every message in frame.
• Capture at least one message before and after the key line so the question being answered is visible.
• Keep labels such as 'edited' or 'deleted message' in view instead of cropping them out.
• Do not draw arrows or highlights on the original image; put your notes in the index or a separate copy.
• Name each file with the ID and date, such as C-04_2026-01-19.png, so it can be matched to the index.
• Note your time zone if participants work in different ones.

Cropping is where meaning gets lost most easily. A reply of 'fine, do it' reads very differently depending on whether the message above it was a request for a day off or a complaint. If a reviewer later sees the full thread and it does not match your crop, it can undermine the rest of your record.

Your record should be about conversations you were part of. Messages between two coworkers that you happened to see on a shared screen, or a group chat you were not a member of, raise privacy concerns and are a poor foundation for your own file. Where a group thread includes personal details about someone else, such as a coworker's health or family situation, leave that out of your screenshot or describe the message in neutral terms.

The Office of the Privacy Commissioner of Canada notes that inappropriate disclosure of personal or confidential information through social media can lead to complaints, grievances and reputational harm, with responsibility that may rest with employees as well as organizations. The safest habit is to capture the minimum needed to show what happened to you.

Work email and team chat tools are usually owned and administered by your employer, may be monitored under workplace policies, and often have retention settings that delete older messages automatically. That makes indexing especially useful: a row recording the date, channel and key line still exists after the message is gone from the platform.

Avoid bulk exports, forwarding whole folders to a personal account, or using admin tools you have access to for your job. Those steps can conflict with policies and agreements, and they sweep in coworkers' and clients' information. If you need full copies, note what exists and ask a qualified employment lawyer how to obtain it properly. Text messages a manager sent to your personal phone are on your device, but the same care about other people's information applies.

1. Write the rough date range your situation covers and list every platform where relevant messages may sit.
2. Search each platform for key words tied to events you already know about: a meeting, a schedule change, a pay issue, a request you made.
3. For each relevant thread, add one index row before you take any screenshot, so nothing is captured without a label.
4. Take screenshots of rows that rely on exact wording, following the context rules above.
5. Mark rows that were not copied and note where the original is stored.
6. Link each row to the timeline entry it supports, and add new timeline entries for events you only found in the messages.
7. Read the index top to bottom and remove anything that is about someone else rather than you.

Should I quote or paraphrase? Quote short lines where the exact wording matters, such as an instruction or a promise. Paraphrase long messages and say that you did, so nobody mistakes your summary for the original.

What about voice notes and calls inside chat apps? Index them like messages, with date, length and participants by role, and write a dated summary of what was said as soon as you can.

Does it matter when I raised a concern in chat? Often the date you first raised something is one of the most useful facts in a file. The US Equal Employment Opportunity Commission, for example, encourages employees to report harassment to management at an early stage, so a clearly dated message where you did that deserves its own row.

How many rows is too many? There is no fixed number, but an index stops helping once a reader cannot scan it in a few minutes. If you have hundreds of rows, group routine messages into one row per week and keep individual rows for the turning points.

In SteadyFile, the records index gives every message or screenshot its own ID, so a dated entry about the January duties change can point straight to C-04 instead of to a camera roll. You can start a private work file in your browser at app.steadyfile.com with no account needed, list people by role rather than by name, and keep threads you have not copied on the gaps and questions list. Your employer has no access to the file. When it is time for a consult, export a chronological PDF where each entry is followed by the messages it relies on; the Complete packet also attaches your screenshots as exhibits.