How to annotate a message thread without editorializing
There are situations where a raw message thread isn't enough on its own. The conversation references phone calls, in-person events, or prior exchanges on a different platform. Inside jokes or shorthand make the meaning unclear to an outside reader. The context that makes the messages make sense exists only in your head.
Annotation solves this. But there's a line between adding context and inserting opinion, and crossing it undermines the credibility of the entire record. Here's how to stay on the right side.
The core distinction
A factual annotation provides information that helps the reader understand the conversation as it happened. An editorial annotation tells the reader what to think about the conversation.
Factual: "[Context: This message was sent after a phone call in which we discussed the lease renewal. No written record of the call exists.]"
Editorial: "[This is where they started lying about what we agreed to.]"
Factual: "[The 'Tuesday thing' referenced here is a scheduled meeting with our child's teacher on March 12.]"
Editorial: "[Notice how they're deflecting from the actual issue.]"
The factual versions give the reader what they need to follow the conversation. The editorial versions do the reader's thinking for them - and any reader with decision-making authority (a judge, mediator, attorney, therapist) will resent it. They know how to read a conversation. They need context, not conclusions.
When annotations are necessary
Not every message thread needs annotation. If the conversation is self-contained and the meaning is clear to any reader, leave it alone. The messages are their own best evidence.
Annotations become necessary when:
- The conversation references events or discussions that happened outside the thread
- Shorthand, nicknames, or abbreviations would confuse an outside reader
- There's a gap in the thread (deleted messages, a switch to a different platform) that creates a discontinuity
- The thread spans multiple topics and a reader needs guidance on which sections relate to the matter at hand
- Timestamps alone don't convey relevant context (the message was sent from a different time zone, or during an event the reader should know about)
If none of these apply, annotation is unnecessary. Over-annotating a clear conversation makes it harder to read, not easier.
Practical techniques
Bracketed inline notes. The simplest approach. Insert brief context notes directly into the thread, clearly marked with brackets so they're visually distinct from the actual messages.
Format: [Context: brief factual note]
Place the note immediately before the message it relates to. Keep it to one or two sentences. If the context requires more explanation, use a separate document (see below).
A separate context document. For complex situations, create a companion document that provides background for the message thread. Structure it as a brief chronological summary of relevant events, with references to specific messages by date and time.
Example: "On March 3, a phone conversation took place (no written record) in which both parties discussed the division of shared expenses. The text exchange beginning at 4:15pm on March 3 references this call. The term 'the arrangement' used in these messages refers to the expense-sharing plan discussed during the call."
This approach keeps the message thread itself clean and uncluttered while providing all necessary context in a separate, clearly labeled document.
Timeline markers. For long threads that span weeks or months, insert date-range headers that orient the reader. These aren't annotations of specific messages - they're structural guides.
"--- Messages from March 1-7: Discussion about schedule changes ---" "--- Messages from March 8-14: Follow-up after missed pickup on March 8 ---"
Timeline markers help a reader navigate a long record without altering the content.
What to avoid
Characterizing tone. "They were being sarcastic here" or "This was said angrily" are interpretations. You may be right, but tone in text messages is notoriously ambiguous, and your interpretation is exactly that - yours. Let the reader assess tone from the words themselves.
Assigning intent. "They said this to make me feel guilty" or "This was designed to confuse me." You can't know intent with certainty, and claiming to weakens your credibility. If the pattern is there, a competent reader will see it without your help.
Selective emphasis. Bolding, highlighting, or underlining certain messages while leaving others plain is a form of editorializing. It tells the reader where to look and, implicitly, what to think. If you need to direct attention to specific messages, do it in a separate summary: "The messages on March 5 at 2:30pm and 2:47pm are relevant to the scheduling dispute."
Emotional language in annotations. "At this point I was devastated" or "This is when everything fell apart." These are understandable reactions, but they don't belong in annotations. If your emotional state is relevant (for example, in a therapeutic or legal context), include it in a separate personal statement, not embedded in the message record.
Preparing records for a third party
If you're assembling annotated message records for someone else to review - a lawyer, a mediator, a therapist, HR - ask yourself one question before you submit: Could the other person in this conversation read my annotations and say they're factually accurate?
They might disagree with your interpretation of the conversation. They might dispute your version of events. But the annotations themselves - the factual context notes - should be things no reasonable person could call false. "[This message was sent at 3am]" is verifiable. "[This message was sent to intimidate me]" is an interpretation.
Keeping that distinction clear protects the integrity of your records and makes them more useful to whoever is reviewing them.
Receipts provides structured analysis of message threads - surfacing patterns, generating timelines, and adding analytical context without editorializing the content of your conversations.