Parking host booking changes: prevent avoidable cancellations
The best way for a host to handle a booking change is to prevent surprises before accepting the reservation. A calendar that looks open but depends on a neighbour, a work shift, or a moveable car creates pressure for both sides. Open only the windows you can actually keep.
Review the conflict before acting
When your plan changes, check the confirmed booking, time window, access method, and current terms in the app. Do not silently move the driver to another bay, ask them to stay on a public road, or assume that a longer stay is harmless. Another reservation may follow, and the driver chose the space based on the details shown.
Contact the driver as soon as you know there is a problem and use the documented booking or support route for the next step. Keep the message factual: what changed, which booking is affected, and what action is available. Avoid promising a refund, payout, or exception that you cannot authorize. Current cancellation and payment terms take priority over a casual message.
Fix the underlying listing
After the immediate issue is resolved, record why it happened. Was the calendar too broad? Did a gate close earlier than expected? Was the access instruction missing a second step? Update the availability calendar, listing description, or access photos instead of relying on memory.
If you need to pause a space, remove future windows before accepting more bookings and tell support when the listing state does not match reality. The first-booking guide covers arrival preparation; the host payout guide explains why completed-booking status and payout status should not be guessed from a conversation.
Reliable hosts are not those who never encounter a change. They are the ones who communicate early, follow the current process, and make the next booking less likely to repeat the same problem. Use the public host page when your calendar is dependable again.