# Co-Parenting Timeline: Example and Blank Record Template

Build a factual co-parenting timeline using dates, events, source references and unresolved details. Adapt a complete schedule-change example.

Use one row per event with a date, a factual description, a source reference and any uncertainty. Keep proposals, final decisions and later amendments separate. Label an unknown date or missing reply instead of filling the gap with an assumption.

A co-parenting timeline puts related events in order so a reader can follow what was proposed, answered and changed. It is a summary with source references, not a substitute for the messages, calendar entries or receipts behind it.

## A completed schedule-change timeline

The following example is fictional. It reconstructs a collection-time discussion without assigning motives to either parent. The source names are illustrative labels you can replace with the identifiers in your own records.

_One issue: collection on 14 November_
| Date | Recorded event | Source | Status or uncertainty |
| --- | --- | --- | --- |
| 2 November | Existing collection is 18:00 at the library | Calendar entry C-01 | Original arrangement |
| 4 November, 09:10 | Parent A asks to move collection to 17:00 | Message M-01 | Proposal |
| 4 November, 12:20 | Parent B offers 17:30 instead | Message M-02 | Alternative proposal |
| 4 November, 13:00 | Parent A agrees to 17:30; other details unchanged | Message M-03 | Recorded agreement |
| 5 November | Calendar shows collection at 17:30 | Calendar entry C-02 | Updated plan; actual collection not established |

## Use a blank row for each new event

Choose a start and end date before collecting entries. Keep the event date separate from the date you wrote your summary. When the source includes a time zone, retain it if records from different locations or systems are being compared.

_Blank timeline fields_
| Field | What to enter |
| --- | --- |
| Date and time | [Recorded event date; time and zone if relevant] |
| Event | [What the source actually shows] |
| Source reference | [Message, request, receipt or calendar identifier] |
| Decision state | [Proposed, answered, completed or unresolved] |
| Uncertainty | [Missing source, unclear date or conflicting detail] |

## Separate facts from interpretation

“A message requesting 17:00 was sent at 09:10” describes a recorded event. “The other parent wanted to disrupt the day” assigns a motive the timestamp cannot prove. If you need to explain your concern, put it in a separate note rather than the factual event column.

Likewise, a calendar entry describes the planned collection. It does not establish the actual arrival time. If an actual event is relevant, identify its own source and distinguish a personal recollection from an app record.

## Include the response and the correction

A timeline that stops at the first proposal can misrepresent the final arrangement. Follow the thread through the answer, any conditions and later amendments. If two sources conflict, cite both and state the discrepancy.

For expenses, keep purchase, approval, reimbursement and receipt confirmation as different events. The [expense ledger example](/en/guides/shared-child-expenses/receipts-and-reimbursements) shows why one payment should not be mistaken for a second purchase.

## Prepare a checkable copy

Order the entries chronologically, check dates against the originals, and retain source files with recognizable names. Note the period covered and the date you prepared the summary. A reader should be able to move from a row to the corresponding source without searching every conversation.

DuoWeek’s calendar, expense records and topic conversations can supply records for your review. Check any export before relying on it, and confirm the recipient’s requested scope. If the aim is a discussion rather than a chronology, organize the result into a [mediation preparation pack](/en/guides/records/mediation-records). For the app workflow, see [Everything you agreed, dated and in one place](/en/features/records).

### What if I do not know the exact date?

Say that the date is unknown or approximate and identify the source of the estimate. Do not present an inferred date as a recorded timestamp.

### Does a timeline prove that a planned handover happened?

No. A plan and an actual event are different facts. State what each source supports and what remains unverified.

- [DuoWeek on the App Store: product description](https://apps.apple.com/us/app/duoweek-co-parenting-calendar/id6802044440)

https://duoweek.com/en/guides/records/co-parenting-timeline
