Communication log template for co-parenting

Copyable thread-level communication log

COMMUNICATION 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:
CHRONOLOGY 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 chronology needs one line: 2–5 Sep | School communication | 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. Preserve 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 communication 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 chronology 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 communication opened | Appointment question sent | COM-2026-018. 18 Jun | Medical communication resolved | Agreement received after follow-up | COM-2026-018. This preserves sequence and stops ten screenshots from occupying ten chronology rows when they concern one decision.