Start with the purpose, not the grievance
A record has three jobs: preserve detail while it is fresh, connect an event to its supporting material, and help a later reader understand sequence. It doesn't need to prove that one parent is good and the other is bad. Before adding an entry, ask: Did this affect the child, parenting time, a decision, an agreement, safety, communication needed for care, or a child-related cost? If not, it may be noise.
This distinction protects the record from becoming a running commentary on personality. A rude message about nothing child-related may feel important tonight and add nothing to a chronology. A short message changing tomorrow's collection time belongs because it changes what should happen next.
The event–interpretation–evidence test
Every difficult event produces at least two stories: what happened and what you think it means. Keep them separate. Event is what a camera, calendar or message thread could show. Interpretation is your conclusion about motive or character. Evidence is the original material that supports the event.
Event: Collection was scheduled for 5:00 pm. The other parent arrived at 5:47 pm.
Interpretation: They were late because they don't respect my time.
Evidence: Parenting-plan calendar, 5:32 pm message saying “running late,” and the 5:47 pm arrival note.
Only the event belongs in the factual narrative. If an interpretation matters, label it as a concern and explain the observable basis. Never present an inference as something you witnessed.
Use one copyable entry format
Consistency makes separate entries comparable. Copy this structure for an exchange, expense, call, school decision or incident. Use “not known” rather than guessing, and preserve the recorded date if you add information later.
EVENT DATE/TIME:
RECORDED ON:
CHILD/CHILDREN:
CATEGORY:
EXPECTED OR AGREED:
WHAT HAPPENED (observable facts):
SOURCE OF KNOWLEDGE (seen / heard / message / record):
PRACTICAL IMPACT ON CHILD OR ARRANGEMENT:
ACTION TAKEN:
EVIDENCE ATTACHED:
FOLLOW-UP NEEDED:
LATER UPDATE (add date; do not overwrite):Write facts a stranger can audit
Specific detail is stronger than forceful language. Replace “always” with dates, “refused” with the request and response, and a diagnosis with an observation. Name the source when you didn't see something yourself.
Emotional: “She deliberately ruined my weekend again and made our son anxious.”
Factual: “The calendar showed collection at 6:00 pm Friday. At 4:18 pm I received a message cancelling the weekend. No alternative time was proposed. At 5:10 pm, L asked twice whether collection was still happening and cried for about five minutes. I replied that plans had changed and did not discuss the reason.”
The rewrite doesn't erase impact. It makes the impact traceable while leaving motive out.
Capture now, complete within 24 hours
When something happens, preserve the fragile item first: take the screenshot with date and surrounding context, save the receipt, note the actual arrival time, or record the exact words spoken. Complete the entry later that day when possible. If you write it days later, say so. The event date and the date recorded are different facts.
A sustainable routine is two minutes after each exchange plus a weekly check for expenses and unanswered child-related requests. One event per entry is easier to filter than a weekly essay. Positive and uneventful entries can also matter: they show the record is a routine, not a file assembled only after conflict.
Turn entries into an organised chronology
A chronology is an index, not a dump of every screenshot. Review monthly and create one-line summaries in date order. Give every attachment a stable reference, such as 2026-03-06-EX01, and cite that reference in the entry. Keep the original file unchanged.
06 Mar 2026 | Exchange | Scheduled 17:00; occurred 17:47 | EX01 message; EX02 arrival note
11 Mar 2026 | Medical | Appointment details sent; acknowledgement received | MED01 email
14 Mar 2026 | Expense | £38 school trip paid; reimbursement requested | FIN01 receipt; FIN02 requestThis mirrors the practical logic of formal court chronologies: short dated entries cross-referenced to the supporting material. A lawyer, mediator or adviser can then decide what is relevant and how it should be used in your jurisdiction.
Use the right branch when the stakes change
- Routine change or expense? Log the event, attach the source and set a follow-up date.
- Repeated pattern? Keep individual entries; add a monthly count or summary without merging the originals.
- Immediate safety or medical risk? Prioritise emergency services, medical care or an appropriate safeguarding professional. Documentation comes after safety.
- Possible breach of an order or need for legal action? Preserve the order, event and communication, then ask a qualified local professional what matters.
- Unsure whether to include it? Apply the purpose test: child, time, decision, safety, necessary communication, agreement or cost.
Should I document every message?
No. Keep messages that change or evidence parenting time, care, decisions, agreements, expenses or safety. Preserve enough surrounding context to avoid changing the meaning.
Can a private journal prove what happened?
A journal is one part of a record. Its usefulness increases when entries are timely, specific and linked to independent material such as original messages, receipts, calendars, school records or witnesses.
Is this the same as preparing court evidence?
No. Daily documentation preserves information. Court forms, disclosure, admissibility and filing rules depend on the jurisdiction and the directions in a particular case. Get local advice before submitting records.
What if I started months after events happened?
Start now. Mark reconstructed entries honestly, identify the records used to rebuild them, and keep new contemporaneous entries separate from recollections.
Sources