“Open” Is a Promise Your Entire Local Stack Has to Keep

The website says the shop closes at six. Maps says seven. The booking tool accepts a 6:30 appointment, and the phone message says holiday hours will be posted online. Every system is technically working. Together they have sent a customer across town to wait outside.

Create an availability record for each location and service with time zone, regular customer-facing hours, appointment rules, service or department hours, seasonal pattern, holiday exceptions, emergency state, effective dates, approver, and last verified time. Distinguish a staffed premises from a phone line, delivery window, or online service.

Google asks businesses to publish regular customer-facing hours and use special hours for holidays or known exceptions. Some business types have specific guidance. “Open 24 hours” should not describe a voicemail box, an unstaffed website, or an emergency number when a customer expects a physical service.

Explain material constraints near the hours: appointments required, last admission, kitchen closing earlier, pickup only, seasonal closure, or departments with different schedules. Structured data should match the visible page and real operation; it is not a place to publish a more attractive version.

Schedule known holidays weeks ahead. Generate one approved change event that updates Business Profile, location page, LocalBusiness markup, booking inventory, call routing, campaign extensions, directory feeds, email signatures where relevant, and the sign on the door. Include an effective time and a rollback.

For weather, staffing, or utility emergencies, give a small on-call group permission to activate a pre-defined temporary state. Record who changed it, where it propagated, what failed, and when normal hours should return. A stale emergency closure can be as damaging as a missed one.

Check the live profile and rendered site, not only the source record. Sample calls, bookings, major directories, and mobile search. Reconcile changes returned by platform updates or user suggestions before accepting them into the authoritative record.

Monitor mismatched hours, failed propagation, stale exceptions, bookings outside staffed periods, calls during closures, and customer reports. The useful service level is the time from an approved operational change to accurate customer-facing availability everywhere that matters.