How to Keep Track of Everything in a Custody or Family Case

Last updated May 12, 2026.

In short. To keep track of a custody or family-law case, log every relevant event the day it happens with the date, a factual two-to-four-sentence description, who was involved, and any linked evidence — all in one place and tagged by category. Contemporaneous records carry more weight in court than reconstructions, and a consistent log lets you see patterns (eleven late pickups, not just three you remember) that a single-event view will miss.

It's a Tuesday in March. The other parent shows up forty minutes late for the pickup, again. By the time you sit down to make dinner you're annoyed but not surprised, and you forget to write it down. Six months later, in a courtroom, your attorney asks how often this has happened over the past year. You guess. Your guess is probably wrong.

That's the part of a custody case nobody tells you about. The events themselves aren't usually dramatic. The damage is that they pile up across months, get scrambled in memory, and then have to be reconstructed under pressure.

This post is a practical system for tracking what happens in a family-law case so you don't end up guessing when it counts.

Why a clear record matters

Memory under stress is unreliable, and the family-law context is structurally stressful. Decades of research on memory reconstruction, including Elizabeth Loftus's work on eyewitness recall, shows that the act of remembering rewrites the memory itself. Each retelling pulls in details from later events, conversations, and emotions. By the time you're asked about a specific Tuesday in March, your memory of it has been edited dozens of times.

That's not a personal failing. It's how memory works.

The other reason a clear record matters: in family court, the question isn't usually whether one event happened. The question is whether there's a pattern. A single late pickup means nothing. Eleven late pickups over six months, all on the parent's scheduled day, is a pattern a judge will care about. You can only see that pattern if every individual instance was logged at the time, with a date.

A consistent record gives you what memory can't: the actual sequence of events in order, the frequency of recurring issues with real counts, evidence linked to the event it documents, and a document you can hand to an attorney without spending a weekend reconstructing it.

What to track

A useful record is not "everything that happened." It's the right details, captured consistently. Six categories cover most of what comes up:

Dates and times

When something happened matters as much as what happened. Use a consistent format. ISO date (2026-03-17) plus time of day is unambiguous and sorts correctly. Avoid "last Tuesday" or "a few weeks ago" — by the time you reread, neither will mean anything.

What happened (factually)

Two to four sentences. The plain facts of the event, no editorial. A good entry: "Pickup scheduled for 5:00 PM. Other parent arrived at 5:42 PM. No advance notice. Child waited outside with grandparent." A bad entry: "He was late AGAIN and obviously doesn't care about our daughter."

The factual version is more powerful in court precisely because it sounds like someone telling the truth, not someone making a case. Save the editorial for your therapist or your journal.

Who was involved

The other parent. The child. Witnesses (grandparent, teacher, neighbor). Anyone who saw or heard the event. Names matter because they map to potential testimony later.

Communication tied to the event

Screenshots of the text that confirms the late pickup. A voicemail. An email exchange. Each piece of communication should be linked to the event it documents, with the date and the sender clearly identified.

Missed or changed plans

Cancelled visits, last-minute schedule changes, no-shows, refusals to follow the parenting plan. These are the bread and butter of custody modification cases.

Recurring issues with categories

Tag events by category as you go — schedule violations, communication issues, school disruptions, medical decisions, financial issues — and let the tags do the work later. Eleven untagged events look like noise. Eleven events tagged "schedule" tell a story.

The mistakes that break the system

Most parents try to track things. The system usually falls apart somewhere in the first 90 days, for one of these reasons.

Relying on memory

You log the big ones and trust yourself on the rest. Six months later you can name three incidents but the other party's filing references seventeen. Even if you remember accurately, you have no contemporaneous record to back it up.

Notes scattered across five apps

Some in iMessage drafts to yourself. Some in Apple Notes. Some in a Google Doc. Some in your email starred folder. When you need to assemble a timeline, you spend a weekend reconciling four sources and find duplicates and gaps. This is the most common failure mode, and it's why we built Clearhavn the way we did.

Inconsistent format

Some entries have a date. Some don't. Some have screenshots. Some say "see iCloud photo from that day." Some are three paragraphs of context. Some are one line. Inconsistent records are difficult to scan, hard to summarize, and easy for opposing counsel to pick apart.

Evidence floating loose from events

A screenshot saved to camera roll with no event linked to it is worth a fraction of the same screenshot attached to a dated event description. Without context, evidence is just files. With context, it's a record.

What a working system looks like

The system doesn't need to be elaborate. It needs three things:

A chronological log of every relevant event with date, factual description, people involved, category tag, and severity (a 1-5 scale is enough). One entry per event.

A linked evidence layer where photos, screenshots, voicemails, and PDFs sit attached to specific events, not in a separate folder you have to cross-reference.

A scan-friendly view that lets you read the timeline in under five minutes and ask questions of it — how many schedule violations this quarter, what's the trend, which months were worst.

Here's what one entry looks like:

2026-03-17 · 17:42
Category: Schedule violation
Severity: 3 of 5
Pickup scheduled 17:00. Other parent arrived at 17:42, no advance
notice. Child (age 7) waited outside school with grandparent
(M. Smith) for 42 minutes. Grandparent confirms timing.
Evidence: screenshot of text from other parent at 17:38 ("on my
way") · grandparent statement (logged separately).

That entry takes about ninety seconds to write. Six months from now it's still legible, still complete, and still defensible.

I built Clearhavn because the alternative is a weekend

Clearhavn is the system above, made automatic. Every event has the same five fields. Evidence attaches directly to the event it documents. Issue tags surface patterns automatically — when "schedule" passes ten events you see it. A court-ready chronology exports as a PDF in one click on the Pro plan, with attachments included.

If you don't want a tool for this, that's fine. The principles work in a spreadsheet, a Notion doc, or a paper notebook. What matters is that you have one place, that every entry follows the same shape, and that evidence stays attached to its event. The reason I built Clearhavn is that I didn't want to spend the weekend before my own hearing reconstructing eleven months of memory across four apps. Once was enough.

The honest part

This will feel like overhead in week one. You'll skip days. You'll forget to log a pickup until the next morning and feel like the system already failed.

It hasn't. Catch-up entries are still better than no entries. By week four, the logging takes you under a minute per event because you've stopped second-guessing the format. By month three, you have a record that no court filing can manipulate, because you wrote it contemporaneously and dated everything.

There's also a deeper benefit. The act of logging the event factually, without the emotion, helps you carry less of it. Putting the late pickup into the record and closing the laptop is a way of telling your brain this is on paper now, I don't have to keep replaying it. People report sleeping better in month two.

For a fuller pre-hearing prep checklist, see How to prepare to object at your custody hearing and the hearing-prep guide.

Frequently asked questions

How often should I log? Same-day if you can; within 48 hours at the outside. Contemporaneous records are weighted more heavily in court than reconstructions, and your memory's accuracy drops quickly after the event.

What if I'm trying to log events from six months ago? Better to log them late than not at all, but mark them as reconstructed. A note like "logged 2026-09-12, event date approximate" is honest and preserves what you do remember without claiming false precision.

Should I save screenshots, or the original messages? Both if you can. Screenshots preserve context (date, sender, surrounding messages). The original messages on your phone are the primary evidence. The screenshot is what gets attached to your event log so future-you doesn't have to scroll through 4,000 texts to find it.

What if I'm about to send a reply I'll regret? A separate problem worth flagging: every reply you send becomes a future exhibit too. Before firing off a response to a difficult co-parent message, it's worth pausing. We built a free Message Coach that drafts a calm, BIFF-style reply (Brief, Informative, Friendly, Firm) in about 30 seconds. It's communication coaching, not legal advice — but a record full of measured replies reads very differently than one full of escalations.

Do I need to track the good interactions too? Yes. A record that only logs problems looks like advocacy. A record that includes the on-time pickups and the times the two of you managed to figure something out reads as a complete account. It's also more accurate.

What if the other parent finds out I'm logging things? There's nothing to find out. Keeping a record of events involving your own child is something every parent has the right to do. If you're worried about device access, use a tool with a PIN lock or panic-exit. (Clearhavn has both.)

Start with one week

Pick today as day one. Log three things from the past 48 hours, plus anything that happens for the rest of this week. Use ISO dates. Keep entries factual. By Sunday you'll have between five and fifteen entries and the start of a real record.

That's the whole system. You don't need to backfill a year. You just need to start.

---

Ryan Marshall is the founder of Clearhavn, a private case-organization tool for family-law matters. He built Clearhavn after his own family-law case made it clear that the existing tools fell into three buckets: spreadsheets that fall apart at 50 events, iPhone-only apps from a decade ago, or law-firm software priced for firms. This post is informational and is not legal advice. For advice about your specific case, consult a qualified attorney in your jurisdiction.