What should a restaurant do with prepaid reservation deposits when a storm forces an unexpected closure?

Write the closure rule before you ever need it

The single most useful thing you can do about storm closures is decide the rule on a quiet afternoon, in writing, when nobody is stressed. The rule that holds up is simple: if the guest cancels late or does not show, your normal deposit terms apply, and if the restaurant cancels for any reason at all, every deposit is returned in full, automatically, with no request required from the guest. Do not carve out weather as a special case where you keep the money. A deposit exists to protect the table from an empty seat you cannot refill. When you are the one closing the doors, that reasoning disappears entirely. Related: Making Deposits Guest Friendly

Put that sentence in the same place your guests already read the deposit terms: the booking page, the confirmation message, and the reminder. It costs you nothing on a normal week and it earns real trust on the one night it matters. It also settles staff arguments in advance. When a manager is deciding at four in the afternoon whether to close, the last thing they need is an open question about whether the restaurant is going to keep forty deposits from people who were told to stay off the roads. The answer should already be printed on your own website. Related: Which Bookings Need a Deposit

Keep reading: Why No Shows Hurt Restaurants So Much, How a Deposit Changes Behavior, Making Deposits Guest Friendly. See how HoldTabl helps you no-show deposit collection for restaurant reservations.

Run the refunds the same night, in one pass

Treat the refund batch as part of closing the restaurant, not as paperwork for the next open day. Pull the reservation list for every affected service, including the following morning if the closure might extend, and work through it in one sitting. How you release the money depends on how you collected it. An uncaptured authorization on a card can usually be voided outright, which drops off the guest's statement faster and cleaner than a refund of a settled charge. A deposit you already captured has to be refunded through your processor, and the guest will typically see it back within a few business days rather than instantly. Both are fine. What matters is that you initiate them all at once and can prove you did. Related: How a Deposit Changes Behavior

Keep a short record of the batch: date, service, number of reservations, total refunded, and who processed it. This takes ten minutes and it pays for itself the first time a guest calls two weeks later saying the money never arrived. Usually it did arrive, and the answer is a date and an amount rather than a shrug. If a refund genuinely fails, usually because the card was closed or replaced, flag it immediately and reach out rather than waiting for the guest to notice. A short call offering to send the money another way turns a small operational failure into a story the guest tells kindly.

Tell guests before they get in the car

Speed matters more than polish. A rough message that reaches a family before they put coats on beats a beautifully written one that arrives after they have driven across town. Text is the channel that actually gets read in this situation, so if you have mobile numbers from the booking flow, use them first, then follow with email, then post the same words to your social accounts and voicemail greeting so anyone checking finds the same information. Contact every reservation on the list, not just the large parties, and do it in one sweep rather than a trickle as staff find spare moments.

Say four things and nothing else: that you are closed, for which services, that their deposit is being returned in full without any action on their part, and roughly when they should expect to see it. Then offer a way to rebook. Resist the urge to explain the decision at length or apologize three times. Guests are almost always understanding about weather, and a message that reads as calm and organized does more for your reputation than one that sounds anxious. Have this message drafted and saved as a template so the person doing it at five in the evening is editing two details rather than composing from scratch.

Offer rebooking as a choice, never as a substitute for the refund

It is tempting to convert closure refunds into future credit and protect the cash. Do not make that swap without asking. Money the guest paid for a dinner you cancelled belongs back on their card, and a policy that quietly turns it into store credit is the kind of thing people remember and post about. The version that works is a genuine choice: the refund is already on its way, and if they would rather roll the deposit onto a new date, you will hold their preferred slot and apply it there. Framed that way, a meaningful share of guests will simply rebook, because they wanted the dinner and not the money. Related: Handling Deposits Fairly

Give the rebooking offer a little weight so it is worth taking. Priority on the first weekend you reopen, the same table if you can, a note in the reservation so the host greets them knowing what happened. Track which closure guests actually came back, because that number tells you whether your recovery message works and whether closures are quietly costing you more than one service. If you offer credit rather than an immediate refund, keep it optional, keep any expiry generous, and make sure your team can look it up instantly when the guest arrives. A credit nobody can find at the host stand is worse than no credit at all.