How to track contradictions across a message history
People say things that contradict what they said before. Sometimes it's forgetfulness. Sometimes plans change. But when contradictions form a pattern - when stated positions shift repeatedly, when accounts of events change depending on the audience or the argument - the pattern itself carries information. Tracking contradictions methodically turns scattered observations into a clear record.
What counts as a contradiction
Not every inconsistency is meaningful. People update their opinions, change their minds, and revise plans. That's normal communication.
A contradiction worth tracking is one where someone states something as fact, and that stated fact conflicts with a previous stated fact - without acknowledgment that anything changed. "I never said that" when you have a message showing they did say it. "I was home all evening" when earlier messages place them somewhere else. "I told you about this weeks ago" when the message history shows no prior mention.
The distinction matters: changing a position openly ("I thought about it and I've changed my mind") is not a contradiction. Asserting a different version of events as though the previous version never existed - that's the pattern to track.
Setting up a contradiction log
A simple spreadsheet or text document works for this. You don't need specialized software. Four columns cover the essentials:
- Date of statement A - when the original claim was made
- Statement A - the original claim, quoted directly
- Date of statement B - when the contradicting claim was made
- Statement B - the contradicting claim, quoted directly
Quote messages exactly. Don't paraphrase or summarize. The value of a contradiction log is precision - it shows the actual words used, not your interpretation of them. If you're working from screenshots, include the file reference so you can pull up the original message.
An optional fifth column for context can note what was happening at the time - what prompted the conversation, who else was involved, what the stakes were. This helps when reviewing the log later, especially if weeks or months have passed.
Finding contradictions in long message histories
Scrolling through months of messages looking for contradictions is impractical. A more targeted approach works better.
Start with specific claims. If someone makes a factual assertion today that feels inconsistent with something you remember them saying before, search your message history for the earlier statement. Most messaging platforms have search functions. Use keywords from the claim - names, places, dates, distinctive phrases.
Track recurring topics. Contradictions cluster around certain subjects - plans, commitments, accounts of events, statements about other people. If a topic comes up repeatedly and the story shifts each time, that topic deserves closer review.
Pay attention to high-stakes moments. Contradictions during arguments, when justifying decisions, or when explaining absences tend to carry more weight than contradictions about low-stakes preferences. If someone's account of an important event changes significantly from one telling to the next, that's worth documenting.
Patterns matter more than individual instances
A single contradiction, on its own, doesn't tell you much. People misremember. People round up or round down. People tell slightly different versions of the same story depending on context.
But contradictions that form a pattern tell you something specific. If someone's account of events consistently changes in ways that serve their position in an argument, that's different from random inconsistency. If commitments are made and then denied with "I never said I'd do that," and this happens repeatedly, the repetition is the data point - not any individual instance.
When reviewing your contradiction log, look for:
- Frequency - how often contradictions occur relative to the volume of communication
- Direction - do the contradictions consistently benefit one person or position?
- Escalation - are the contradictions getting more significant over time?
- Response to evidence - when presented with the earlier statement, does the person acknowledge the discrepancy or redirect?
These pattern-level observations are more useful than any individual "gotcha." They describe a communication dynamic rather than a single moment.
Keeping the record clean
The purpose of a contradiction log is clarity, not ammunition. A few principles keep it useful.
Document, don't editorialize. Record what was said and when. Leave out your feelings about it, your theories about why, and your conclusions about what it means. Those belong in a separate space - a journal, a conversation with a therapist, a discussion with a trusted person. The log itself stays factual.
Include your own statements when relevant. If you're tracking a conversation, your side of it is part of the record. Context requires it. Selectively omitting your own messages creates a distorted picture.
Update, don't overwrite. If new information clarifies an apparent contradiction - if you find a message you'd missed that fills in a gap - add the update rather than deleting the original entry. The record should show your understanding as it developed, not a curated version of events.
A well-maintained contradiction log gives you something your memory can't: a fixed, searchable, precise record of what was said and when. It doesn't tell you what to make of the contradictions. That part is yours.