There is a particular kind of message that gets written at 11pm. It is factually correct, it is completely justified, and it does not get you the thing you were asking for.
That is the frustrating part of co-parenting communication. The messages that feel best to write are very often the ones that work least well, and the gap between the two is mostly technique rather than temperament.
You do not need to be guarded or strategic about this. You mostly need a method.
Write it so it can be answered
The test that fixes most messages is simple: could someone reply to this in one line, tonight, without having to defend themselves first?
That is not about being nice. It is about not accidentally asking two questions at once, one of which is "do you accept that you have been unreliable". A message that only contains the actual request gets the actual request answered.
One subject, one ask
The single highest-leverage habit is separating topics. A message that opens with Thursday's pickup, moves to unpaid dental costs, and closes with a general observation about reliability is three conversations in one, and it will be answered on whichever point is easiest to answer.
Split it. Thursday's pickup is one thread. The dental invoice is another. That is why Halven organises messages into subject-based threads rather than one endless scroll — a thread with a subject line stays answerable, and it is still findable next term.
Then make the ask explicit and answerable. "Can you take the Thursday run from week 3" can be answered yes or no. "It would be good if the Thursday thing was sorted" cannot.
Leave the history out
The strongest instinct, and the most expensive one, is to include the pattern. Not just can you collect Mia on Thursday, but can you collect Mia on Thursday, given that I have done the last four.
The second version feels fairer to write. It reliably produces a worse outcome. You have given a yes-or-no question a defence to mount, and the reply will be about the last four Thursdays rather than about this one. The request gets lost.
If the pattern genuinely matters, it is worth raising on its own, separately and calmly, rather than smuggled into a request about Thursday. And if you note handovers as they happen, you will have the actual dates rather than a feeling — which makes that conversation much shorter when you do have it.
Three specific rewrites
Cut the mind-reading. "You obviously don't care about her routine" is a claim about someone's inner life that they will immediately dispute, and now you are arguing about that instead. "She was thirty minutes late to school on Tuesday and Thursday" is just true, and much harder to wave away.
Cut "always" and "never". They are rarely literally true, and one counterexample lets the whole sentence be dismissed. Two specific dates cannot be.
Cut the sarcasm and the rhetorical question. "Any chance you'll be on time this week?" is a dig, and it will be answered like one. Sarcasm is the thing that survives the trip into written text least well of anything.
Put a gap between writing it and sending it
Write the message. Then do not send it.
Most of what people regret is not the content, it is the timing — written in the ten minutes after a bad handover, when everything true feels urgent. The same message written the next morning is usually shorter, usually cleaner, and almost always more effective.
If you cannot wait, at least read it back once. Two questions: what am I actually asking for, and is anything in here going to start a different argument? If the first is unclear, rewrite it. If the answer to the second is yes, cut that part.
This is the one place Halven deliberately steps in before you send. Tone check reads a draft and points out the phrases most likely to be taken the wrong way, and the writing assistant offers a neutral version that keeps every fact and every request you made. It is entirely private — the results are visible only to you, nothing is stored, and your co-parent is never told the tool ran. All they see is the message you chose to send.
When something has actually gone wrong
Sometimes the message is not a request. Sometimes a handover did not happen, or medication did not come back with them, and it needs saying.
Write it as a report rather than a complaint. What happened, when, and what you need next. No adjectives, no theory about why. Something like: Mia was not at the 5pm handover on Friday 18 July. I waited until 5:40. Can you let me know what happened, and whether Sunday is still going ahead?
That is harder to write than the version with feelings in it, and it works far better — because it gives the other person something to answer rather than something to defend against.
Which is the whole point. The goal is not to be right about last Friday. It is for Sunday to go ahead.