Multi-Outlet Service Calendars: Record Exceptions Clearly

Scope the exception before anyone changes a listing

Name the outlets, the service and channel the hours apply to, the timezone and the exact date or dates. Hours here are customer-service hours only: the times customers can be served in that service. Staff working hours and last-order times are separate and are not assumed to match.

Write the baseline as a reference to the current regular hours, then the proposed temporary hours or a closure for each outlet. Record the approver, their authority and the approval date, the effective-from and effective-through dates, and the date regular hours return under the approved plan. Link the operational arrangements by reference and name an owner for each.

State what each endpoint means. If service runs past midnight, record both calendar dates rather than a single range that silently crosses into the next day. The form makes no assumption about public holidays, legal requirements or permission to trade; authority and operating controls come from your existing qualified, responsible process.

Separate planned, approved, submitted and visible

Four different facts tend to collapse into one. Planned hours are what someone proposed. Approved hours are what the authority agreed. A submitted message is what was sent to a channel. Visible hours are what a person actually saw on that channel, at a recorded time, with evidence. Keep a field for each.

Check publication per outlet and per customer-facing channel. In this example that means the website, the business listing and the door sign at each outlet: nine rows for three outlets. Do not collapse them into one status per outlet. An outlet whose website is correct but whose door sign is not has one outstanding channel, and that channel must stay visible.

For each channel row, record the planned entry, what was submitted and when, the hours actually observed, the observation timestamp and an evidence reference kept in your own records. An observation without a timestamp cannot show it was current, and a submission without an observation shows only that someone tried. Give each row an owning role and a due time early enough to inform customers before the previously advertised service begins. A later opening time is not a reason to leave the old opening time visible until then.

Customer communications are record fields. The form sends nothing, publishes nothing and connects to no platform; people make changes through the channels themselves and record what they observed.

Worked example: CAL-024 for 9 November 2026

In this fictional case, North, South and East normally serve dine-in customers from 08:00 to 20:00 IST (UTC+05:30), under regular-hours reference REG-03. A one-day exception for 9 November 2026 is approved: North serves 10:00 to 18:00, South is closed, and East is explicitly confirmed unchanged at 08:00 to 20:00. Regular hours return on 10 November 2026 under the approved plan. Each outlet below summarises three separate channel rows in the worksheet.

Reading CAL-024 as of 8 November, 17:00

Eight of the nine channel rows show the approved hours for 9 November. The North door sign still shows the regular 08:00 to 20:00 and needs a dated exception notice. Its owner is the North manager, with a fictional deadline of 20:00 on 8 November, ahead of the previously advertised 08:00 start on 9 November.

The overall case therefore stays Open. Approval alone is not success, and a mostly correct set of channels is not a reconciled one. The North door sign needs its own verified update. Even after every exception notice is correct, the later expiry review remains open; close the overall case only after that review and all other outstanding actions have evidence.

East matters too. Unchanged hours still need checking: East's three channels were each explicitly verified for 9 November, so the record shows that rather than assuming nothing needed doing. These records are entirely fictional and describe no real platform change.

Expiry, later changes and unplanned closures

Plan an expiry review. On 10 November, check that each channel shows regular hours again and that dated notices have been removed. Until that check is done and recorded, it is pending, not complete. Do not assume one channel's temporary hours lapse on their own because another channel's do. The expiry review has its own owner and due date, and its result is recorded per channel, just like the exception itself.

If the approved exception changes later, create a revision with its own approval and keep the original beside it. Recheck every affected channel against the revised hours, and record new observations rather than editing the old ones.

If an outlet has to close unexpectedly, the responsible person acts under the existing process. Afterwards, record the actual change and the communications that were made. Do not rewrite the schedule as if the closure had always been planned.

Where the principle comes from

Google's Business Profile help page on special hours describes setting temporary, date-specific hours that sit apart from regular hours, and points to separate handling for hours that apply only to particular services. Only those two ideas are used here: date-specific exceptions are distinct from regular hours, and service-specific hours need a clearly stated scope. Its day-count limits, interface steps, spreadsheet format and other channel behaviour are not adopted, and nothing here assumes that any other channel removes temporary hours automatically. CAL-024 and its workflow are original.