What to include in a communication log and what to leave out
A communication log is only as useful as the decisions you make about what goes in it. Include too little and the log has gaps when you need it most. Include too much and it becomes an overwhelming document that nobody - including you - will want to read through.
The skill isn't in recording everything. It's in recording the right things, in the right way, consistently enough that the log tells a clear story when you review it later.
The purpose drives the content
What belongs in your log depends on what the log is for.
Personal clarity. If you're keeping a log to understand a situation better - to see whether a pattern exists, to ground yourself when your recollection feels unreliable - the bar for inclusion is lower. You can include impressions and observations alongside facts, as long as you keep them clearly separated.
Professional documentation. A workplace communication log (for an HR complaint, a performance dispute, or a project disagreement) needs to be tighter. Stick to facts: what was said, when, by whom, and what actions followed. Leave your emotional responses out of the log itself, or put them in a separate personal section.
Legal preparation. If your log might be reviewed by a lawyer, mediator, or court, factual precision is essential. Direct quotes over paraphrasing. Exact dates over approximations. Observable behavior over your interpretation of intent. A legally useful log reads like a record, not a diary.
Whatever the purpose, clarity and selectivity are always better than volume.
What to include
Direct quotes
When someone says something significant, capture their exact words whenever possible. "You never do anything right" is a record. "They were critical" is a summary that loses the specifics.
If you can't remember the exact words, say so. "They said something like 'this is your fault, as usual'" is more honest than presenting an approximation as a direct quote. Readers of your log - whether that's future-you, a lawyer, or an HR representative - will trust a log that distinguishes between exact quotes and paraphrases.
Date, time, and medium
Every entry needs a timestamp. Date at minimum. Time if you have it. The medium matters too - a text message is a verifiable record, a phone call note is your recollection, and the distinction is worth noting.
Consistent timestamps also let you (or anyone reviewing the log) see frequency and timing patterns. How often does a particular issue come up? Is there a pattern in when certain conversations happen? These questions can only be answered if the dates are there.
Decisions and commitments
If someone agreed to something, promised something, or stated an intention, log it. "Said they would send the revised schedule by Friday" is the kind of entry that matters enormously when Friday comes and goes.
Note whether the commitment was fulfilled. A log that tracks both what was promised and what was delivered is more useful than one that only captures conversations.
Your own statements
Include what you said, not just what the other person said. A one-sided log can look selective, and it also means you lose track of your own communication patterns. Recording your side keeps the log balanced and gives you a fuller picture.
Observable behavior and actions
What someone did is as important as what they said. "Did not respond to three messages over five days" is an observable fact. "Cancelled the meeting 20 minutes before it was scheduled" is an observable fact. These entries don't require interpretation - they record what happened.
What to leave out
Editorializing and interpretation
"They were being manipulative" is an interpretation. "They said 'I guess I'll just handle everything myself, like always' after I asked them to share the workload" is a factual record that lets the reader form their own interpretation.
Keep interpretation out of the log entries themselves. If you want to record your analysis of what you're seeing, create a separate section - "observations" or "notes to self" - so the factual record stays clean.
Speculation about motives
"They did this because they wanted to make me feel guilty" attributes an intent you can't verify. Stick to what was said, what was done, and what resulted. Let the pattern speak for itself. If you record that someone brought up a favor they did for you every time you raised a concern - five times across three months - the pattern is visible without you needing to explain why they did it.
Routine, non-relevant exchanges
Not every interaction belongs in the log. If you're documenting a workplace conflict, the morning "good morning" exchange probably doesn't matter. If you're tracking a custody disagreement, a friendly text about a school event might not be relevant - unless it is, because it shows the contrast between cooperative moments and difficult ones.
Use judgment. Ask yourself: "If I were reading this log for the first time, would this entry add to my understanding of the situation?" If not, leave it out.
Venting
A communication log is not a diary. The urge to write "I can't believe they said that, I'm so frustrated, why does this keep happening" is understandable, but it doesn't belong in the log. Keep a separate journal if you need to process emotions. The log should be something you'd feel comfortable handing to a neutral third party.
Keeping the log sustainable
A communication log you abandon after two weeks is less useful than one you maintain consistently for months. Sustainability matters.
Set a format and stick with it. A simple template for each entry reduces the effort of logging:
Date: [date and time]
Medium: [text / email / phone / in-person]
Participants: [who was involved]
Summary: [what was said and done]
Key quotes: [exact words, if available]
Outcome: [any decisions, commitments, or next steps]
Log promptly. Enter notes as close to the conversation as possible. Even a two-line entry written within an hour is more reliable than a detailed reconstruction written three days later.
Don't backfill extensively. If you decide to start a log and want to include past events, be transparent about it. Note that entries before a certain date are based on memory rather than contemporaneous notes. This is important for credibility.
Review periodically. Reading through your log every few weeks helps you notice patterns and also catch entries that need clarification while the context is still fresh.
A good communication log is specific, factual, consistent, and sustainable. It records what happened in enough detail to be useful, without burying the important entries in noise. The discipline of maintaining one can itself be clarifying - the act of deciding what's worth logging forces you to pay attention to what's actually happening in your conversations.
Receipts applies this same principle to your digital messages - identifying what matters, organizing it clearly, and surfacing patterns that individual exchanges make easy to miss. Whether you're logging by hand or using a tool, the goal is the same: a clear record you can trust.