Low-key dinner
One good restaurant, two to four people, no fuss. The risk is leaving the booking too late and ending up somewhere that was available because nobody wanted to go there.
Moments · Birthday planner
The restaurant you wanted is full. The backup was somewhere that was just available. It becomes a fine night, not a good one. The fix is not grand planning — it is having a clear plan seven days out, not the night before.
What gets planned
Restaurant type, area, vibe, budget band, dietary requirements.
When to arrive, how long each stop takes, when to call it.
Area, transport options, how far people are travelling from.
Whether a bar, walk, or activity after dinner adds to the night or kills it.
Small: a specific wine, a table note, a walk somewhere with meaning. The plan can include this without it being precious.
If the restaurant falls through or the weather changes the mood — what does the alternate look like.
The planning journey
Lock the main booking. Birthdays fail when the restaurant you wanted was full and you ended up somewhere that was just available. Seven days is the minimum. More is better for groups or popular rooms.
Check the weather if anything is outdoors or depends on walking between stops. Confirm headcount. Handle any dietary requirements you have not already passed on.
Final clear plan. What time does everyone arrive, where are you meeting, who is handling what. Nothing to figure out on the night.
Example emails
A sample for a made-up Moment, “Sam’s birthday”, written by the same code as the real reminders. They go a week, three days and one day before by default, and you can change the days when you save.
Subject Sam’s birthday: one week check-in
7 days out · One week check-in
This Moment is one week away. This is the right time to check the main piece: booking, timing, who is coming, transport and whether the plan still fits the person.
What should this feel like?
Subject Sam’s birthday: weather, timing and backup
3 days out · Final check
This Moment is three days away. This is the useful final-check window: weather, transport, booking details and any small thing that would be annoying to fix on the day.
Anything changed before I move this toward the final checklist?
Subject Sam’s birthday: day-before checklist
1 day out · Day-before checklist
This Moment is tomorrow. Keep it simple now. Check the details that make the day feel easy instead of rushed.
Want the final checklist with timing, booking, transport and backup?
Example situations
One good restaurant, two to four people, no fuss. The risk is leaving the booking too late and ending up somewhere that was available because nobody wanted to go there.
Harder than it sounds because the expectation is higher and the input is lower. What does the plan need to feel like? That is the first question to answer.
More people means more constraints. Dietary needs, transport, budget spread, and the energy of a group that may not know each other that well. One solid booking and a loose second stop.
PlanSorted can plan this too: food, drinks, timing, prep order, what to buy and when. A dinner party or backyard birthday still needs a clear plan.
The compressed version. One good bar or restaurant that handles a 7pm start, close to the city or the person's suburb, that does not require military coordination.
Set the date, tell us the vibe and who it is for. Get a draft plan with timing, venue direction, transport and a backup — then refine it as the day gets closer.
Related