How to include context without editorializing
Raw message records can be confusing to a third party who wasn't part of the conversation. References to unnamed people, inside shorthand, responses to phone calls that don't appear in the text record - without context, a reviewer has to guess at meaning. But the line between useful context and editorial commentary is one that people cross without realizing it, and crossing it weakens the record.
This is a practical skill, not a personality trait. It can be learned, practiced, and applied to any situation where records need to be shared with someone who wasn't there - a lawyer, mediator, therapist, HR representative, or judge.
What context does
Context answers factual questions that the record itself doesn't address. It fills in the gaps between what was said in writing and what was happening outside the written exchange.
A reviewer looking at a text thread might need to know what event preceded the conversation, what the parties' relationship is, who a nickname refers to, or whether a phone call occurred between two blocks of text messages. Without these facts, the reviewer may misinterpret the tone, sequence, or significance of the messages.
Good context makes the record clearer. Poor context makes the record less trustworthy.
The difference between context and editorializing
Context is factual. Editorializing is interpretive. The distinction is straightforward in principle but tricky in practice because people often interpret while believing they're stating facts.
Factual context: "This message was sent approximately 30 minutes after a phone conversation about the custody schedule."
Editorial: "This message was sent right after a phone call where they were being completely unreasonable about custody."
Factual context: "The 'Sarah' referenced here is my sister. She had been staying with me for two weeks at this point."
Editorial: "They were jealous of my relationship with my sister and were trying to isolate me."
Factual context: "There is a four-hour gap between these messages. During that time, we were in the same house but in different rooms."
Editorial: "They gave me the silent treatment for four hours after this."
In each case, the factual version provides information the reviewer needs. The editorial version tells the reviewer what to think about the information. The factual version lets the record do its job. The editorial version does the job for it - and in doing so, undermines it.
A template for context annotations
When adding context to message records, a consistent format helps. Consider including four categories of information where relevant.
Who. Identify people referenced by name, nickname, or pronoun who might not be recognizable to the reviewer. "J" is my coworker. "The kids" refers to our two children, ages 8 and 11.
When. Note significant timing information that isn't visible in the timestamps. A phone call that preceded the exchange. An event that happened between two blocks of messages. A deadline that was approaching.
Where. Physical context that affects interpretation. Were the parties in the same location? Was one party traveling? Was the conversation happening during a work meeting?
What. Events or circumstances that are referenced but not explained in the messages themselves. A prior agreement, a recent incident, a change in circumstances.
Each annotation should be clearly separated from the messages themselves - set apart visually and labeled as context, not woven into the text as though it were part of the original exchange.
Common editorializing traps
Some editorial language is obvious - words like "manipulative," "controlling," or "unreasonable" clearly reflect interpretation rather than fact. But subtler forms are more common and harder to catch.
Characterizing intent. "They sent this to make me feel guilty" is an interpretation of motive. "This message was sent after I declined the invitation" is a fact.
Assigning emotion. "They were angry when they wrote this" is a guess. "This message was sent in all caps" is an observation.
Using loaded language. "They demanded I come home" vs. "The message reads: 'You need to come home now.'" Let the actual words carry whatever weight they carry.
Implying patterns in annotations. "Once again, they..." or "As usual, they..." are editorial frames. If a pattern exists in the messages, the reviewer will see it. Your job is to present the messages, not narrate the pattern.
When is context not needed
Not every message requires an annotation. If the conversation is self-contained and the meaning is clear from the text, adding context can actually clutter the record. Over-annotating makes it look like you're trying too hard to shape the reader's interpretation.
A useful rule: add context only when a reasonable person unfamiliar with the situation would need additional information to understand what they're reading. If the messages explain themselves, let them.
Why this matters
Third parties - lawyers, mediators, judges, therapists, HR representatives - are trained to be skeptical of narratives. When they see editorialized records, they may discount not just the commentary but the records themselves. When they see well-organized records with clear, factual context, they can focus on the content rather than questioning the presentation.
The discipline of separating fact from interpretation in your annotations is also useful for your own clarity. Writing "this message was sent after I asked for space and was told I was overreacting" forces you to identify the specific facts. Writing "this is a perfect example of how they always invalidate me" keeps you in interpretation mode.
The facts are usually enough. When they're not, that's a signal that the records themselves may not support the conclusion you want to draw - and that's information worth having.