Missed handover note template

EVENT ID:
RECORDED AT (date, time, timezone):
EXPECTED: date / time / place / person / source of arrangement
OBSERVED: arrival / people present / what happened / departure
CONTACT ATTEMPTS: time / channel / exact message or result
CHILD IMPACT: practical, observable effect only
EVIDENCE: ID / filename / what it supports / limitation
INTERPRETATION (optional and clearly marked):
NEXT ACTION:
LINKED FOLLOW-UP IDS:

Complete the expected arrangement first

Identify the date, local time, place, responsible adult, direction of the handover, and source of the plan. If a later message changed it, keep the original and revised terms.

Use observations in the factual field

Write arrival, waiting, departure, people seen, and contact attempts as a sequence. Do not use labels such as irresponsible, manipulative, or always. Those are conclusions, not recordable events.

Label evidence by its limited purpose

Give files stable IDs. State that a message shows what was sent, a call log shows an attempted call, or a receipt supports presence near a location. Avoid saying one file proves more than it can.

Describe impact without recruiting the child

Record changed travel, meals, school, activities, care, or medication. Do not interrogate a child or infer their beliefs. Quote spontaneous words only when genuinely needed and keep context.

Preserve the next step

Record follow-up messages, note, proposed make-up time, and whether it was accepted or completed. Each belongs on its own timestamp so the timeline remains readable.

Review a completed no-show example line by line

In the fictional example below, Expected identifies the agreed 18:00 library handover and points to PLAN-014. Observed gives arrival, absence, waiting, and departure times without claiming why the event happened. Contact records the channel and result of each attempt.

Evidence identifies the complete message thread, call log, and parking receipt while limiting what each file establishes. Follow-up points to the note received the next morning. A reader can so reconstruct the event without treating a later note as something known at 18:00.

Use unknown, disputed, and corrected accurately

Write unknown when you do not know a motive, location, delivery status, or reason. Use disputed when another person challenges a fact or the meaning of an agreement, then link their exact response. Use corrected when you discover that your own date, time, amount, or description was wrong. State the old value, the corrected value, the time of correction, and the source. These labels are more informative than silently filling a gap or polishing an earlier entry after the event.

Fit the note into an organized chronology

Assign one stable event ID and link every related record to it. The original schedule, the handover note, the later note, a proposed replacement period, and the completed or declined follow-up. Keep each development on its own date. In a monthly summary, count the planned and completed handovers and cite the relevant event IDs.

The summary should help someone locate the detailed rows. It should not replace those rows or turn a single event into a claim about a general pattern.