Sharing the Load: Tracking for Two Parents

When two-parent households talk about tracking, the conversation is usually framed as a record-keeping problem: who is logging, whether they are logging consistently, whether the record is complete. That framing misses what is actually going wrong.

The real cost is at the boundary between shifts. A handoff requires transferring the state of the day, and if that state only exists in one person's memory, the transfer has to happen by conversation. Conversations require both people to be awake, present, and patient, which at 6am or 11pm they are not.

So the handoff degrades. It becomes a rushed exchange with gaps in it, and the gaps get filled by guessing. The person coming on duty makes decisions with incomplete information, and the person going off duty has to stay half-engaged in case they are needed for a follow-up question. Neither of them is really off, which is the whole point of a shift.

There is a version of the handoff that is worse than inefficient, and most couples find it eventually.

The questions are practical, but they land as an audit. “How much did she take” is a request for information; after four hours alone with a baby who fed badly, it can sound like an assessment of how the shift went. And because the person answering genuinely does not remember, they answer with an estimate, then feel the estimate being weighed.

This is where tracking gets tangled up in something much bigger than data. The record becomes evidence, the questions become a review, and a system meant to help the household starts generating friction inside it. Plenty of people quietly stop logging for exactly this reason: an empty log cannot be used against them.

The way out is not better questions. It is making the information available without anyone having to ask. If the day is readable, nobody is being examined — you are both reading the same page.

There is a second, quieter asymmetry underneath the handoff problem, and it is worth naming because it is usually what the arguments are actually about.

In most households one person becomes the keeper of the state. They are the one who knows when the last feed was, which size diapers are running low, when the appointment is, and what happened on Tuesday. That knowledge is real work, it is continuous, and it is close to invisible, because it produces no observable output. The other person can do an equal number of hours and still not carry it.

You cannot split that load by dividing tasks, because it is not made of tasks. It is made of holding information. It splits when the information stops living in one head and starts living somewhere both people can read — which is the actual argument for a shared log, and it has very little to do with charts.

The practical marker of success is not an even task list. It is that the person coming on duty can find out what they need without asking, and the person going off duty can genuinely stop thinking.

Surprisingly little, as it turns out. The person coming on duty needs roughly five facts, and none of them need explaining.

Once the state transfer is solved, shifts become worth designing properly. A few patterns hold up across a lot of households.

Give each person a genuine block rather than alternating wake-ups. Alternating feels equitable and leaves both people equally wrecked, because nobody gets an unbroken stretch and unbroken stretches are where recovery happens. Long blocks, then swap.

Make off-duty mean off. Different room if the house allows it, phone away, not listening. Being on standby is not rest, and a household where nobody is ever fully off is a household running at half capacity all day.

Own whole domains, not fragments. If one person owns the 8pm-to-2am block completely — feeds, changes, settling, and logging — there is nothing to coordinate mid-shift. Splitting a single feed between two people creates more handoffs, not fewer.

Write down the exceptional things, say nothing about the routine ones. If the routine is readable from the log, the only thing that needs a spoken sentence is what was unusual. That is a very short sentence.

There is a common asymmetry where one person tracks and the other does not, which produces a record with holes exactly where one person's shifts were — the least useful possible shape.

It is nearly always a friction problem rather than a willingness problem. If logging takes twelve taps and requires learning where things live, the person who did not set the app up will not do it, particularly if they are already worried about doing it wrong. Two things fix it, and neither is a conversation about commitment.

The first is that the common case has to be one action, discoverable without instruction. If a bottle is one button on the first screen, anyone can log a bottle. The second is that mistakes have to be cheap. A lot of reluctance is fear of corrupting a record that somebody else clearly cares about, and an undo that lasts long enough to catch a slip removes that fear entirely.

It also helps to say out loud, once, that the log is not a scorecard. Nobody logs willingly into something they suspect will be reviewed.

It is worth being straight about the trade-off here, because it is a real one.

Live sync between two phones requires a server and an account, which means a copy of your child's history sitting on someone else's infrastructure. There is no way to have two phones update each other in real time without one.

The alternative is one phone that lives with the baby — on the arm of the chair, wherever the shift is happening — so the record never exists anywhere but the phone in your hand. It costs you the second screen, and it keeps a minute-by-minute record of your nights off any server.

Both are reasonable. What matters is choosing knowingly: whether sharing is off until you turn it on, what exactly gets uploaded, who can read it, whether joining a shared log merges your own history into it, and how you delete the server copy if you change your mind.