T-24 hours
The day before a home dinner is when small uncertainties become expensive: a train delay nobody mentioned, a plus-one that appeared in someone’s head but not in the booking, a host who assumed street parking was obvious. A shared, lightweight cadence keeps everyone oriented without turning the thread into a novel.
Host checklist (send once, bullet form)
- Headcount confirmation — “Still four guests, correct?”
- Arrival window — Not only “7:00” but “doors from 6:45; first course ~7:15.”
- Access — Buzzer code, gate, where shoes go, pets in the home.
- Parking or transit — Links beat memory.
- Dietary recap — One line: “I have your nut-free + no-pork notes locked for tomorrow.”
Tone: Warmth in one sentence, facts in bullets. Guests skim on phones; paragraphs get lost.
Guest responsibilities
- Disclose changes immediately — Late work call, missed connection, new allergy information. The host may still say no to a risky last-minute change; early notice preserves goodwill either way.
- Ask logistics questions before you travel — “Is there a lift?” matters more when you are carrying wine and cake.
- Confirm you read the message — A thumbs-up or “got it, see you at 7” closes the loop.
What to avoid
- Duplicate channels — If the platform thread exists, do not parallel-park the same questions in SMS unless the host invites it.
- Scope creep — The day before is a bad time to negotiate a completely different menu or a surprise performance guest without explicit host consent.
If something breaks
Weather, illness, strikes—name the fact, propose two options (“We can arrive at 7:30 or cancel and release our seats—what works for you?”). Calm options beat anxious walls of text.
Stay in the loop
Pair with booking-holds-explained and cancellations-with-care so expectations around timing and refunds stay aligned.