After a long planning thread, a short summary can prevent a vague maybe from becoming an assumed commitment. Include only the agreed place, date and time, plus one unresolved item. Label proposals as proposals and invite a correction before either person travels.
Separate agreed facts
Read back only what both people have clearly accepted. A suggestion such as โwe could meet earlierโ does not belong in the confirmed part. Keeping the summary small helps the other person spot an error instead of approving a wall of text.
Name the one open point
If the entrance, booking name or travel route still needs confirmation, state it after the agreed details. Say who will check it and by when if that is already decided. Do not hide the uncertainty inside a confident sentence about the whole plan.
Invite a correction
End with a simple request to fix anything wrong. A summary is a coordination tool, not a record you can use later to prove that the other person accepted every suggestion. If there is no clear confirmation, pause the journey rather than treating silence as agreement.
Message examples
Summarise the agreement
Just to check: Friday 22nd, 18:30, the north entrance of the museum. We still need to confirm whether the cafรฉ takes bookingsโhave I got that right?
It distinguishes the settled plan from the one remaining question.
Label a proposal
My suggestion is to meet at 18:00 instead, but that is not confirmed yet. Does the earlier time work for you, or should we keep 18:30?
It prevents a proposed change from becoming a commitment by implication.
Frequently asked questions
How much of the chat should I include?
Only the details needed to act: place, date, time and unresolved logistics. Personal conversation and rejected options do not belong in the summary.
What if they do not confirm the summary?
Set a reasonable point at which you will stop travelling or choose another day, and say that openly. A missing confirmation is a planning fact, not an invitation to guess.
Updated October 25, 2026 ยท By the RIZR team
