Use when a bank holiday or a shutdown is coming and the hours must be right everywhere a customer looks.
You are rolling out closure hours across every surface a customer might check. You cannot edit anything yourself.
Business: {{BUSINESS_NAME}}
Exact closure dates and any reduced hours: {{CLOSURE_DATES}}
Normal opening hours: {{NORMAL_HOURS}}
Everywhere hours or a status appear: {{SURFACES}}
What happens to urgent enquiries while we are shut: {{COVER_ARRANGEMENT}}
Produce:
1. A rollout table: Surface from {{SURFACES}}, What to set, When to set it, When to revert to {{NORMAL_HOURS}}, Owner, How to confirm it shows correctly to a member of the public.
2. The wording for each surface: a profile note under 100 characters, a site banner under 25 words, a voicemail script under 45 words that states the reopening date, an email auto reply under 60 words, and a notice for the door.
3. A revert plan with the date each item goes back to {{NORMAL_HOURS}}.
4. Where {{COVER_ARRANGEMENT}} must be stated and where it must not, so nobody promises cover we do not have.
Rules:
- Use only the dates in {{CLOSURE_DATES}}. Where a date is ambiguous, write [CONFIRM DATE] rather than picking one.
- Do not state a response time that {{COVER_ARRANGEMENT}} does not support.
- Name {{BUSINESS_NAME}} once per notice at most, and cut the apologies and the seasonal preamble.
- No em dashes and no exclamation marks.
Replace each placeholder with your own detail. The more specific you are, the less the model invents.
When should I use this rather than just editing the profile hours?
When hours live in more places than the profile. Editing that alone leaves the site banner, the voicemail, the auto reply and the door notice saying something else. Run it a fortnight ahead, since same day edits often do not show before people have already set off to find you closed.
What do I need to confirm first?
Exact {{CLOSURE_DATES}} including any reduced hours, the normal hours to revert to, every surface where hours or a status appear, and what {{COVER_ARRANGEMENT}} genuinely exists. Ambiguous dates come back as [CONFIRM DATE] rather than a guess, which is worth more than it sounds two days before a shutdown.
What comes back?
A rollout table with set and revert dates per surface and how to confirm each shows correctly to the public, wording for each notice at its own length from a 100 character profile note to a door sign, a revert plan, and where cover must and must not be stated. Diarise the revert column.
What is the mistake?
Treating the closure as the job and forgetting the revert. Hours left wrong in January cost more than the shutdown itself did. Check every surface signed out, on a phone, as a member of the public sees it, and do not let the voicemail promise a response your cover arrangement cannot deliver.