They have met the child. They have not met the Tuesday 3:15, the other household's door, or the rule about who may be in the lot. You have years of context. They have a Saturday. If you dump the archive, they will remember the fight and miss the 3:15. If you tell them nothing, they will stand in the wrong door.
Send the map. Ask for one thing. Leave the archive.
Current logistics, as if they arrived this week
Write it for a cold reader, because they are one:
- which days the child is at your house
- pickup times and doors — school lot versus field entrance
- who else might be there (the other parent, a grandparent, a sitter)
- the one rule that will embarrass everyone if they break it (no extra adult in the lot; the booster; the early Wednesday)
- your phone, and when not to call the other household
Names they will hear, spelled the way those people publish them. Not the word you use for the other parent on your own list. That nickname is private and stays off this package.
The history of how the schedule got this way is almost never required to stand in the right door. If a sentence exists to recruit them as a witness, cut it.
One ask they can own, not a verdict on the other house
You might need a decision: "Can you hold Friday the 12th so I can take the late shift?" You might need an FYI: "Saturday 9 is a drop-off at the field; you do not need to come." Pick one shape. A briefing that is both a dump and a test of loyalty will get you a careful paragraph and no Friday.
They were not there when the order was written. A fair ask is something they can do. "Tell me if a Saturday trip that week is too much" is fair. "Agree that the other parent is impossible" is not an ask you put in writing.
A sufficient reply is "I can do the 12th" or "I cannot; take the sitter." One line.
They may not be a contact yet — email still works
Writing to someone who is not on RelayLink is ordinary email and a link. They need no account to read or reply. If they already have an account, invite them as a contact before a send will go through. Do not treat that invite as a loyalty test. It is a consent step for two accounts, nothing else.
You approve the send. The session has the whole history. The package does not. You can send a briefing to yourself first if you are handing the same map to another assistant of your own — that path sends no email — and then send the cleaned page to them.
A reply is how you know they have it. A fetched link is not a read. You will not see whether they are ready. That is still a conversation, and it does not belong in a longer briefing.
When the calendar is sitting in a session and you can feel the archive rising, connect your assistant and send the pickup map and one ask, instead of the whole story.