You have Wednesday. They have Thursday. The recital is Wednesday at 6:40, their work trip lands Thursday at 4, and the after-school pickup is still written as if none of that were true. The group chat already has fourteen messages about last month's dentist. Opening it again is how a calendar problem becomes a character debate.
Send the week, not the history.
One week, dated, with the conflicts named
Write the calendar as it stands, then write the conflict. Dates, not vibes.
- You have Maya Wednesday; they have her Thursday.
- Recital Wednesday 6:40, doors at 6:20, school is on the other side of town.
- Their flight Thursday lands at 4; usual pickup is 3:15.
That is the situation. It is not "you always do this when I have something." It is three facts that do not fit.
Then ask for one decision: swap Wednesday and Thursday this week, or you take both evenings and they take Saturday morning. Close the list. A third option they invent is fine — that is a counter — but you do not open with an essay.
A briefing keeps the ask at the top and the week underneath. Your assistant can draft it from the mess in the session. You strip the scorekeeping before you approve.
A swap is a yes, a no, or a counter — not a meeting
A call, a text, and a briefing do different jobs. The same-day "I'm at the curb" is a text. The "we need to talk about how we do Tuesdays" is a call, and it is a different ask. The week in front of you is a written decision: one proposal, room to counter, a time you need the answer by.
Name the default if they do not answer. "If I don't hear by noon Thursday I will keep the usual pickup and skip the recital's first fifteen minutes." That is an honest deadline, not a threat. It tells them what the calendar will do if the thread stays quiet.
One follow-up is enough. How to follow up without nagging is the rest of that craft: you restate the ask and the default, you do not add last March.
Keep the private nickname and the venting off the send
You may have a word for them that they have never used. It stays on your list. The package they read uses their name. The draft that opens "Hey [that word], typical…" does not go out.
They reply from the email or the link. A reply is how you know they have it. A fetched link is not a read. You cannot see whether they put it on their calendar. If they already have a RelayLink account, you need an accepted contact. If they do not, the message is email.
When the next conflict shows up in a session — the tournament, the work trip, the teacher conference — connect your assistant and send the week as a briefing instead of feeding the group chat another fourteen messages.