Copyable custody journal entry
ENTRY ID: CJ-[YEAR]-[NUMBER]
EVENT DATE/TIME: [exact or approximate]
RECORDED DATE/TIME:
CHILD: [initial or approved identifier]
CATEGORY: [exchange / parenting time / communication / school / health / expense / other]
LOCATION:
PEOPLE PRESENT:
EXPECTED ARRANGEMENT: [source reference]
EVENT โ DIRECT OBSERVATIONS:
EXACT WORDS: [speaker + quote, only if exact]
INFORMATION FROM SOMEONE ELSE: [source + statement]
OBSERVABLE CHILD-RELATED EFFECT:
ACTION / FOLLOW-UP:
EVIDENCE REFERENCES: [MSG-___ / IMG-___ / REC-___]
LIMITATION OR UNCERTAINTY:
CHRONOLOGY LINE: [date | category | neutral event | evidence IDs]Keep the recorded timestamp separate from the event timestamp. That distinction shows whether the note was contemporaneous or reconstructed later.
Annotated realistic entry: event, interpretation and evidence
Entry CJ-2026-041. Event time: 14 July 2026, scheduled 17:00; actual arrival 17:38. Recorded: 14 July, 18:05. Location: Westgate library entrance. Expected arrangement: parenting plan CAL-01, item 4. Direct observation: I arrived with L at 16:55. Other parent arrived at 17:38. L and I remained inside the library until then. Exact words: other parent said, The train was cancelled. Evidence: MSG-144 is the 17:21 message; IMG-033 is the library clock photo. Limitation: I didn't independently verify the train cancellation. Event is the timing and what the writer directly saw. Interpretation would be They don't respect my time; it doesn't belong in the entry. Evidence is the preserved message and image, neither of which proves motive.
Checklist before saving
- One event, not a week's worth of complaints
- Event time and recorded time both present
- Precision stated when a time is estimated
- Sources distinguished from direct observation
- Quotes exact and attributed
- Child impact observable, not diagnosed
- Original file or message kept with a stable reference
- Contrary or ordinary facts included
- Follow-up stated as an action, not a threat
- Entry linked to one chronology line
A record that includes routine events as well as exceptions is easier to assess than a file built only from adverse moments.
Turn entries into an organized chronology
The journal is the detailed layer; the chronology is the index. Reduce each saved entry to one line without losing its source: 14 Jul 2026 | Exchange | Arrival 17:38 for 17:00 schedule; explanation attributed and unverified | CJ-2026-041; MSG-144; IMG-033. Sort by event date, not upload date. If evidence arrives later, keep its received date and link it back to the original event. Review monthly with transparent counts such as 9 exchanges: 7 on time, 2 late, while retaining the underlying entries. The journal contents guide explains what deserves an entry.
Use local terminology without changing the facts
Labels vary. England and Wales commonly use child arrangements and describe whom a child lives with or spends time with; Canada's federal Divorce Act uses parenting time and decision-making responsibility; California self-help materials use custody and parenting time (visitation). Put the wording from your actual order or agreement in the expected-arrangement field. The observation itself should stay plain enough to survive a change of label. This template is organizational guidance; a local professional can explain evidence, notice and privacy rules.
Should I record positive and routine events?
Yes. Routine entries provide a baseline and reduce selection bias. You don't need a long narrative; a short on-time or resolved entry is enough.
Can I add an entry later?
Yes, but record the true creation date and explain what refreshed your memory. Don't backdate or silently edit the original event record.
Should I name children in an exported journal?
Use the identifiers appropriate for the intended recipient and local privacy rules. Initials can reduce unnecessary exposure in working files, while official filings may require another format.
Sources