The log fields
- **Date & time** of the exchange
- **Channel:** text / email / call / in person / shared app
- **Initiated by:** you or co-parent
- **Topic:** one line — "April school break schedule"
- **Summary:** neutral, two sentences maximum
- **Exact quotes:** only for contested or significant wording, quoted precisely
- **Response needed?** yes/no — and any stated deadline
- **Response received:** date/time, or "none as of [date]"
- **Evidence:** screenshot or email saved? where?
The response-tracking pair is the part most people skip and most professionals value. "Asked about summer schedule Mar 3, no reply as of Mar 17" is a factual, checkable statement — and across twenty entries it documents a pattern no single screenshot can show.
What to log and what to skip
Log exchanges that touch schedule, money, school, health, travel, or agreements — and every request that needs an answer. Skip routine logistics that resolved normally ("running 5 min late" answered with "ok") unless lateness itself is the pattern you're documenting. A log of every trivial message reads as surveillance; a log of substantive exchanges reads as diligence. The difference matters to whoever reviews it.
Keep the summary neutral — the quotes do the talking
Bad: "She refused AGAIN to discuss the school issue and was hostile."
Good: "Raised M's reading report by text 7:14 pm; asked to discuss before parent evening. Reply 9:40 pm: 'not doing this with you.' No further response as of Mar 12."
The second version is stronger precisely because it's colder. When exact words matter, quote them exactly and screenshot the exchange — see text message evidence for how to capture screenshots that hold up.
Where this template runs out of road
A spreadsheet or note handles the fields fine for a while. What it can't do is keep the screenshot with the entry, remind you at handover time, or produce a filtered PDF of six months of communication entries when your attorney asks. That's the job Casewell does — the log above maps one-to-one onto its Communication category, with evidence attached per entry and export built in. In genuinely high-conflict situations, the log doubles as an emotional boundary: the exchange goes in the log, and the log — not your evening — absorbs it.
Should I log every text from my co-parent?
No — log substantive exchanges (schedule, money, school, health, agreements) and any request awaiting a response. Logging routine resolved logistics adds noise without value.
How do I document that my co-parent doesn't respond?
Log the request with date, channel, and topic, then record 'no response as of [date]' and update if one arrives. A series of these entries documents the pattern factually.
Is a communication log admissible in court?
Courts and professionals decide what to accept case by case. What you control is quality: contemporaneous, dated, neutral entries with screenshots preserved make a log easy to take seriously.