DEV Community

Hive80-lab
Hive80-lab

Posted on Originally published at hive80-lab.github.io

The Reopen Notice Is a Project, Not a Sentence (It Starts With a Gate, Not an Announcement)

Every closure notice ends the same way: “we'll let you know when we're back.” Then the business comes back, posts “We're back!” into the void, and discovers the reopening has its own failure modes — the card terminal that sat unused for three days and now declines every second payment, the Google profile that still says CLOSED, the autoresponder still apologising for a closure that ended yesterday, and the 41 people whose bookings evaporated and never heard a word.

Here is the reframe: the reopen is a project, not a sentence. It has a gate (verify before you announce), a channel flip (correct the stale information the closure left behind), and a ledger (the customers you still owe). Businesses that treat it as a sentence get “we're back” right and the day after wrong.

1. The gate: seven checks before a single announcement

The rule that prevents every reopen disaster: the notice goes out after the gate passes, not before. Run these in order — fifteen minutes, one person, written down:

  1. People and stock — roster confirmed, inventory that lets you serve. A missing supplier delivery is a limitation to state, not a reason to delay.
  2. The thing that closed you is actually fixed — verified, not promised. “The plumber says it's done” is not a check; running water at full pressure is. Photograph it: that's the operational record.
  3. One customer journey, end to end, done by you. Call the number, place the order, pay by card, take delivery. The payment terminal fails at half of all reopenings because nobody tested it.
  4. The backlog triaged — every order, booking, and message from the closure listed and assigned: honored, rescheduled with a date, refunded, or cancelled with the make-good.
  5. Channels restored — voicemail, autoresponder, banner, pinned post. A half-restored channel tells customers the right hand doesn't know what the left is doing.
  6. Google Business Profile hours correct — checked the evening before, because Maps drives the arrival.
  7. The make-good ledger exists (more below). The reopen notice commits to it — the ledger is what makes that sentence true.

If one check fails, open in a limited state and say so. Don't delay the whole reopen for one line item.

2. The channel flip: the closure list in reverse

On reopen day, your channels aren't informing anyone — they're correcting the stale information the closure left behind:

  1. Google hours — first, before the doors open. A CLOSED pin on an open door is the reopening twin of the OPEN pin on a locked one, and it sends your most ready-to-return customers straight to the competitor.
  2. The door sign — down, or replaced with a clean reopen line. Taped-over signage with pen-scribbled dates reads as improvisation.
  3. Voicemail restored, autoresponder off or rewritten, banner replaced with one reopen line (don't delete it silently — mid-week visitors never saw the closure notice), pinned post swapped.
  4. Scheduled customers, individually — every cancelled booking gets a personal confirmation of its new slot: their name, their time. This is the highest-value hour of the entire reopen.

3. The seven lines every reopen notice contains

  • What is open, and from exactly when (“The Elm Street location reopens Thursday 7am” — not “we're back!”).
  • Hours, including anything temporary, with the date normal hours resume.
  • What is still limited, and until when — or, if nothing is: “no limitations, full service from open.”
  • What changed while you were closed, in one sentence a customer cares about. This is free goodwill: “we're back, and the kitchen has new plumbing” reads as a business that maintains itself.
  • The make-good line: everyone whose booking was moved has been contacted; if we missed you, reply — we'll sort it the same day.
  • The contact channel that will be answered: one channel, named owner, stated response time.
  • The thank-you: one line, not a paragraph. Sincerity scales inversely with length.

4. The make-good ledger

One table, one row per customer you owe: who · what was promised · the new promise (date-bound) · delivered (date). Three rules:

  • Honor the original price. A prepaid service delivered after the reopen at the old price is the cheapest goodwill you'll ever buy.
  • Upgrade, don't discount. The make-good for a missed booking is the next slot plus something, not a percentage off. Discounts reprice the relationship; upgrades reward it.
  • Date-bound or it isn't a promise. “We'll make it up to you” is an apology. “Your replacement slot is Thursday 2pm, confirmed” is a make-good.

Target: every row date-bound within 24 hours of reopening, every row closed within seven days.

5. Worked example — the flooded café

The 9-seat café from the closure notice: burst pipe, closed Tuesday–Thursday.

  • Wed 17:30: plumber signs off (photo logged). Gate checks 1–3 early. The card terminal had dropped into offline mode during the closure — caught, reset, verified with a $1 charge refunded on the spot. This is the failure half of reopenings discover at the register, in front of a queue.
  • Wed 18:00: Google hours flipped and verified, special hours deleted, closure photo removed. Voicemail and autoresponder rewritten. Banner replaced: “We're back — regular hours from Thursday 7am.”
  • Wed 18:20: backlog triage — 41 window bookings rescheduled, 2 preorders refunded, 3 quotes answered. Make-good ledger opened: 46 rows, all date-bound.
  • Thu 05:45: gate formally passed, seven of seven checks, initialed. Door sign replaced, social pin swapped.
  • Thu 06:00–09:00: open at 6am as promised; 41 bookings confirmed individually by 9:00.
  • By Monday: ledger empty. The first Google review after reopening reads: “Flooded kitchen Tuesday, back open Thursday, they called me about my booking before I even thought to ask. This is how you run a place.”

The closure became evidence of competence — because the reopen was verified before it was announced, and the promises had a ledger.

The five traps

  1. Announcing before the gate passes — converts one bad week into two.
  2. Flipping the banner but not Google hours — the banner is the channel you check; Maps is the channel they check.
  3. “We're back!” with no hours, limitations, or make-good — an announcement that forces follow-up questions is one half of readers won't act on.
  4. Treating rescheduled customers as “they'll figure it out” — a broadcast is not a confirmation.
  5. Reopening without saying what changed — the fix story is free; leaving it out is the only waste on this page.

The full version — the three phases of “back” (open, settled, normal), the reopen scorecard, and the copy-paste one-page template — is on the ops notes page: Reopening Notice for Small Businesses. If you landed here planning the closure instead, start with The Temporary Closure Notice Is Two Documents.

Top comments (0)