Start with the current arrangement
Gather the schedule you currently use, including any relevant written arrangement, school dates and known exceptions. Do not use a new calendar as a way to introduce an unagreed change. If the underlying dates are unclear, resolve that question through the appropriate process before treating the calendar as settled.
Choose a manageable period to enter first, such as the next month. Check the dates against the source information before adding more. This makes it easier to catch a mistaken week or pickup time before it repeats across a whole term.
Use a consistent event format
For each event, record a clear title, the relevant child, start and end times and any practical context needed. Avoid titles that make sense only to you. “School appointment — 9:30 am” is clearer than “Meeting.”
A fictional entry might read: “Friday school pickup, 3:15 pm; collect at the main gate.” If the school changes its finish time, update the relevant record and communicate the change instead of relying on an old recurring assumption.
Separate confirmed dates from ideas
A proposed holiday or requested swap is not yet a new schedule. Use the appropriate discussion or proposal workflow, and update the calendar after the outcome is clear. A message being opened does not prove agreement.
When a request is declined, leave the current arrangement clear. Keeping a proposal’s context is useful, but several competing entries labelled “pickup” can make the actual plan harder to understand.
Check time zones and daylight saving
An event should represent the intended local time on its actual date. Do not assume the UTC offset is identical all year, or that two places change their clocks on the same day. When entering an event around a clock change, review the displayed time and duration before saving.
If you export an ICS calendar file, check how the receiving calendar displays the event. An exported file is a copy, not necessarily a live subscription. Re-importing copies without checking can create duplicate entries in another calendar.
Add exceptions with context
School holidays, appointments and activity changes may sit alongside the ordinary routine. Label them clearly and check whether they change a handover or simply add an appointment. For school-holiday planning, our existing guide has a separate checklist.
Avoid storing every detail in an event title. Keep supporting notices in the document workspace and the necessary discussion in messages. The calendar should make the date understandable, not become a long transcript.
Check the calendar from both perspectives
Before relying on it, review a sample week: can each participating parent tell what happens, when it happens and which child is involved? Correct unclear entries before adding more complexity. Set a simple habit for checking upcoming dates rather than assuming a notification will always reach someone.
If you have multiple arrangements
Keep each co-parent’s schedule in its own arrangement. Review them yourself to spot overlapping responsibilities, but do not give one co-parent access to another family’s records just to solve a scheduling problem. Share only the availability relevant to the decision.
CoParentOS offers a calendar within each arrangement, alongside its messages and documents. You can start solo, but another parent must join to participate in the shared workspace. The standard trial requires a card and converts to paid billing unless cancelled before it ends.