Communication log template for co-parenting — for Canadian parents

How to read this in Canada

Keep the record in layers: what the plan says, the dated event and its source, then what happened next. A fact stops being useful the moment it is written up as a legal conclusion.

Canadian rules can come from federal, provincial or territorial law. Start with the order or plan that applies to you, and keep its exact terms, such as parenting time or decision-making responsibility.

If you need to correct an error, add a dated note rather than editing the original. Keep routine events near the disputed ones so a family lawyer in your province or territory can judge which facts actually matter.

Province-or-territory checklist for a Canadian review

Name the province or territory and the court. Add the law or order tied to the parenting plan. Keep its own terms for parenting time, major decisions, contact, and support. Use local forms and due dates. If two legal areas may be involved, flag that point for a lawyer.

Copyable thread-level communication log

MESSAGES ID: COM-[YEAR]-[NUMBER]
CHILD / TOPIC:
CHANNEL / THREAD REFERENCE:
OPENED DATE/TIME:
REQUEST OR INFORMATION SENT:
RESPONSE NEEDED BY: [date + practical reason]
RESPONSE RECEIVED: [date/time or none as of dated review]
FACTUAL RESPONSE SUMMARY:
EXACT QUOTE: [only if material and exact]
OUTCOME: [agreed / declined / unresolved / information only]
PRACTICAL EFFECT:
ORIGINAL MESSAGE REFERENCES:
FOLLOW-UP:
STATUS / LAST REVIEWED:
TIMELINE LINE:

A deadline belongs in the record only when it came from an order, agreement, institution or genuine practical need. Don't manufacture urgency after the fact.

Annotated example: six messages become one record

COM-2026-029. Topic: school trip consent. Channel: email thread MAIL-077. Opened 2 Sep, 08:16. Request: Parent A forwarded the school's consent form and asked whether Parent B agreed before the school's 5 Sep deadline. Responses: 2 Sep, 19:42, Need to check; 4 Sep, 21:10, Yes, agreed. Outcome: agreed.

Practical effect: form submitted 5 Sep, 08:05. Receipt SCH-031. Status: closed. Annotation: the two incoming messages remain in the original thread. But the timeline needs one line: 2–5 Sep | School messages | Consent requested, received and submitted by deadline | COM-2026-029. MAIL-077. SCH-031. This shows the outcome rather than selecting only the delayed middle response.

Rewrite tone claims as checkable facts

Emotional: She ignored me for days and then sent another rude brush-off. Factual: `Question sent by email 12 Jun, 09:04, asking whether the 18 Jun medical appointment could proceed. Reply received 15 Jun, 18:22: “Do whatever you want.” No answer to the appointment question was included. Follow-up sent 16 Jun, 08:10.

Status: unresolved as of 17 Jun, 12:00. ` The rewrite doesn't praise or excuse the response. It lets dates, the exact quote and the unresolved question carry the meaning.

What belongs in the log

Log schedule, school, health, travel, expenses and agreements when the exchange creates an action, decision, unresolved question or relevant pattern. Routine arrived or thanks messages usually don't need their own entry unless they complete an existing thread or timing itself matters. Keep enough context to prevent quote-mining.

If you screenshot, capture participants, timestamps and nearby messages. Keep a full export separately and use stable references in the log. The messages logs guide explains collection habits. This page is the working form.

Place communication in the chronology

Use the date the issue opened for the main timeline line and include the date range when it spans several days. If the eventual reply materially changes the outcome, update the thread status and add a second dated line rather than moving the first date. Example: 12 Jun | Medical messages opened | Appointment question sent | COM-2026-018.

18 Jun | Medical messages resolved | Agreement received after follow-up | COM-2026-018. This preserves sequence and stops ten screenshots from occupying ten timeline rows when they concern one decision.

A Canadian review note

Copy a co-parenting messages log that turns a message thread into one annotated, evidence-linked timeline entry. Sharing any of it in Canada takes a few more steps.

Keep a review pack short: the current order or plan, a factual timeline and the source files that matter. Say plainly where something is missing.

Ask a family lawyer in your province or territory before you file or share records. Privacy, court, and evidence rules can differ across Canada. One PDF does not make those rules the same.

Name the province or territory. Note whether federal divorce law or another family law applies. Keep the terms used in the order itself.