HiveMinded

Co‑parenting calendar: 8 rules that end 'You never told me'

October 1, 2026 · By Matt Pozek, Founder, HiveMinded

We’ve tested a simple way to stop the “you never told me” calendar fights. We call it the Two‑Homes Calendar Pact: eight written agreements both parents sign off on so the shared calendar does the talking. It works on paper or in any app. We spell out who enters what, how far ahead counts as notice, what details are required, how changes happen, and how we confirm.

When both houses follow the same eight rules, we see fewer mix‑ups, faster decisions, and less emotional load. Below are the rules, a filled example, the notice windows, and exactly what to do if one parent won’t use the calendar.

The eight agreements (copy and fill in together)

  1. Scope: We put on the shared calendar any event that affects custody, transport, bedtime, cost, or supervision. Categories: school, medical, extracurriculars, childcare, social/playdates, travel, custody exceptions, parent commitments impacting pickup/drop‑off.
  1. Ownership: Parent A enters school + medical + custody exceptions. Parent B enters extracurriculars + social/playdates + childcare bookings. Each parent adds their own work/transport limits when they affect kids. Known events are entered within 48 hours of receiving info.
  1. What counts as notice: Only events entered on the shared calendar with title, child name, start/end time, location, and driver count as notice. Texts/emails don’t count unless the event is also entered.
  1. Naming rules: Title format is [Child] — [Event]. Prefix who’s driving: D:Mom, D:Dad, or D:Carpool. Include location in the location field, not the title. Use all‑caps NOTE: only for special instructions.
  1. Required details: Every entry has start and end time, address or map link, pickup/return plan, and contact name if not a parent. Add a 15–20 minute travel buffer when needed.
  1. Notice windows by type: School events require 7 days. Medical appointments require 48 hours. Playdates require 24 hours. Late additions follow the “late notice” rule below.
  1. Changes and conflicts: The editor updates the shared entry immediately and adds “Updated [date/time]” in notes. If within the notice window, they also send a short text: “Changed on calendar: [title], [new time].” Priority for conflicts is medical > school > custody order > extracurricular > social. Disagreements pause changes until a call.
  1. Weekly confirmation: Every Sunday by 7:30 pm, both parents review the next two weeks, resolve gaps, and react “OK” (or initial) to the calendar. If no confirmation by Monday 8:00 am, the last confirmed plan stands.

Copy these eight lines into a note or stick them on the fridge. Edit names, times, and categories for your family.

A filled example: the Alvarez Two‑Homes Pact

Here’s an example you can model exactly. The Alvarez kids are Maya (9) and Leo (12). Parents are Dani and Carlos. Two households, alternating weeks, with Wednesday dinners.

  1. Scope (Alvarez): We add to the shared calendar anything that affects time, transport, budget, or supervision: school (conferences, concerts, half‑days), medical (doctor/dentist/therapy), extracurriculars (soccer, band, art), childcare (sitters, aftercare), social (playdates, parties), travel (flights, overnights), custody exceptions (switches, trades), and parent commitments that block pick‑ups.
  1. Ownership (Alvarez):
  1. What counts as notice (Alvarez): Only a shared calendar entry with title, child name, start/end, location, and driver counts. Example: “Maya — Choir Rehearsal | D:Carlos” with the school address and 3:15–4:30 pm. A text that says “Choir next week” does not count.
  1. Naming rules (Alvarez): Title format is [Child] — [Event] | D:[Driver]. Use “NOTE:” in caps only for things like “NOTE: bring recorder” or “NOTE: allergy form due”. Avoid emojis in titles. Use child initials in recurring events: “M: Piano,” “L: Band.”
  1. Required details (Alvarez): Every event includes the exact address in the location field, contact person if not a parent (e.g., “Coach Ramirez, 555‑0102”), and the pickup/return plan in notes (“Pickup by Carlos at 4:30; return to Dani’s”). Add a 20‑minute buffer when crossing town; we enter a separate “Drive: Home to Soccer” block if it crowds the hour.
  1. Notice windows (Alvarez):

Late notice rule: If something lands after the window, the parent adding it keeps the logistics unless the other explicitly accepts on the calendar notes.

  1. Changes and conflicts (Alvarez): If a time moves, the editor updates the event, adds “Updated Tue 4/9 2:15p,” and sends one text: “Changed on calendar: L—Band, now 5:30–6:30.” If a conflict appears, we apply priority: medical beats school beats custody order beats extracurricular beats social. If still unclear, we call for 5 minutes that day and write the decision in the event notes.
  1. Weekly confirmation (Alvarez): Sunday 7:15 pm video call, 15 minutes max, covering the next two weeks. We end by each parent adding “OK—D” or “OK—C” in a single confirmation event titled “Alvarez Weekly OK — [dates].” If someone can’t attend, they send updates by 6:00 pm and must add their “OK” by Monday 8:00 am. Without it, we roll forward last week’s responsibilities.

Sample week entries (the way we actually write them):

That’s a complete, usable pact. Your names, your windows, same bones.

Notice windows that work (in plain words)

Here’s the sample “table in words” many families like. Fill it and post it next to the calendar.

What counts as notice is the event on the shared calendar with all required fields filled. A text that says “FYI—party Saturday” does not count until the event exists on the calendar.

Late notice policy that keeps the peace:

This removes the grey zone that creates most fights. It’s not punitive; it just makes invisible costs visible and voluntary.

Make it stick week to week

Agreement without rhythm falls apart. We anchor the pact to three small routines:

  1. Sunday review, 15 minutes. Open the next two weeks, read titles out loud, fill gaps, then both confirm. If you want a script, we use the one in our guide: The 15‑minute Sunday calendar review that prevents weekday surprises.
  1. Daily glance, 60 seconds. Each parent checks tomorrow before bed. If you see anything missing (driver, address, return plan), fix it then.
  1. Midweek check, 5 minutes. Wednesday night, scan for weekend weather changes, field switches, and birthday party overlaps. If you’re shifting within a notice window, update the calendar and send the one‑line text.

Naming discipline helps:

Conflict script (keep this short and boring):

If one parent won’t use the calendar

We’ve seen this a lot. Two practical paths improve reliability without picking a fight.

Option A: Read‑only link plus a weekly nudge

Option B: Weekly summary message (same time, same format)

If you later move to an app, HiveMinded can run one family calendar both households see, with your custody schedule overlaid and exceptions tracked in the same view. You can still export a read‑only link or print the week for the fridge. Details: https://hiveminded.app

Paper on the fridge or in an app (both work)

Paper setup (fast):

App setup (any calendar):

Ten‑minute start script:

Where this breaks (and the fix)

  1. Vague scope (“we put important stuff on it”).
  1. No clear notice definition.
  1. Duplicates and missing details.
  1. Silent changes.
  1. Custody exceptions lost in threads.

The last step: write it down and post it

That’s the Two‑Homes Calendar Pact: eight agreements, one shared source of truth, no more “you never told me.”

Matt Pozek

Founder, HiveMinded

Matt built HiveMinded after running his own family's calendar, chores and meals out of five apps and a group chat. He writes about the systems that actually survive a school week, using what real families do inside the app — never invented statistics.

Want this to run itself?
HiveMinded puts your family's calendar, chores, meals, and reminders in one shared hub — so the whole hive stays in sync.
Try HiveMinded free

← All articles