Overtime is not an exception, so stop planning it as one
For a lot of shift workers, being held over is a normal part of the month rather than a crisis. But most custody plans treat it as an unforeseeable event, which means every occurrence gets handled from scratch, under time pressure, by two people who are already stressed. The fix is not better communication in the moment. It is deciding the answer once, while nothing is happening.
The reason this matters more than it sounds: a held-over shift is a work problem, but the way it gets handled is what your co-parent experiences. Handled by a standing rule, it reads as the job being the job. Handled by a 6pm phone call asking for a favour, it reads as unreliability — even when the underlying facts are identical.
The four things to decide before the next one
Write these down somewhere you can both see. It takes one conversation and removes most of the recurring friction.
- The notice number. A specific number of hours for anything you know in advance. Pick one you can actually meet on a bad day rather than an aspirational one.
- One named backup. A single person, agreed by both parents, who is allowed to collect. Not a list of possibilities assembled during the callout.
- The default for the handoff. Does the block start late, or move to the next day? Choose a default so nobody is deciding it at short notice.
- Whether time is made up. And if so, within what window. Absorbed is fine. Recovered is fine. Undefined is what causes the resentment.
The threshold that stops the juggling
Add one more line: a point past which you do not attempt to rescue the block. If the overtime runs past a certain hour, the time simply transfers and the plan moves on. Without a cut-off, both parents end up negotiating late at night about whether it is worth moving a sleeping child, which is a conversation that has never gone well for anybody.
| Situation | What happens | Who acts |
|---|---|---|
| Known 12+ hours ahead | Handoff time moves; block still happens | Shift-working parent notifies |
| Known under 12 hours ahead | Named backup collects; block starts late | Backup collects, both parents notified |
| Held over past 8pm | Block transfers to the other parent entirely | No negotiation — the default applies |
| Held over on a handoff day | Next scheduled block extends instead | Agreed in advance, logged after |
Bottom line: Write the backup rule before you need it, not during the callback. Define reasonable notice as a number, name one backup, set a default for the handoff and a cut-off past which the block simply transfers — that turns every held-over shift from a request into a status update.