How to Publish Business Hours: Holidays, Appointments, Overnight Work and Timezones
Publish hours for the service customers can really use, attach them to the right location and keep dated exceptions up to date. When visiting hours, response hours and appointment availability differ, show them separately.
An online form can accept a request at any time while the business reviews it only during staffed hours. A restaurant can have different kitchen and collection periods. A mobile provider can accept appointments without operating a walk-in shop.
Accurate hours let a customer understand those differences before they travel, call or wait for a reply.
Decide what the schedule means
Write one sentence defining each published schedule. Examples might be when the shop receives customers, when the office answers enquiries or when a specific service is available.
Do not merge different meanings into one broad window. A business that is open for collection in the evening may not offer its full daytime service then.
| Schedule | What it describes | What it should not imply |
|---|---|---|
| Customer visiting hours | When customers can use the represented premises | All services are available throughout that period |
| Enquiry response hours | When the team normally handles requests | Immediate booking or emergency attendance |
| Appointment availability | When agreed appointments can occur | Walk-in access or every slot being free |
| Service-specific hours | A defined operation such as collection | The entire business operates identically |
| Emergency/on-call arrangement | The actual supported urgent response model | Guaranteed attendance unless promised |
Google provides main hours, split periods and other hour treatments depending on the operation. Its guidance also supports separate special and service-related hours where applicable. Use the fields appropriate to the business type rather than forcing every schedule into main hours. Google's hours guidance
Build one branch-level hours record
Keep the recurring weekly schedule, local timezone, exceptional dates and the person who confirms it. Store separate records for branches that differ.
| Field | Example meaning |
|---|---|
| Location/service | The branch or activity the schedule represents |
| Local timezone | A named IANA timezone for the actual location |
| Weekly periods | One or more open intervals on each relevant weekday |
| Dated exceptions | Closed or changed hours on specific local dates |
| Appointment wording | How customers obtain a confirmed slot |
| Response expectation | When a received request should be reviewed |
| Confirmed by/date | Actual owner check and next review trigger |
A branch record can inherit brand information, but it should not silently inherit another branch's hours.
The owner should be able to explain what an unknown or empty schedule means. Unknown hours and confirmed closure are different states.
Represent split shifts as separate periods
A shop that closes for a break has two intervals, not one continuous open period. A visitor should not arrive during a closure because the profile displays only the first opening and final closing time.
For example, a fictional specialist retailer might receive customers from 09:00 to 13:00 and again from 14:00 to 17:30 on an ordinary weekday. The gap should remain visible in systems that support split periods.
Where a platform cannot represent an important distinction accurately, use its supported alternative or a clear explanatory field. Do not publish a misleading continuous schedule simply to complete the form.
Handle overnight periods at the date boundary
An interval beginning Friday at 22:00 and ending Saturday at 02:00 crosses a local calendar boundary. Check both sides of midnight in the public display.
Record the actual start and end relationship. A closing time earlier than the opening time can represent an overnight interval; it should not be interpreted casually without the platform's supported input method.
Test the customer's questions:
- Is the business open late on Friday?
- Is it still operating early on Saturday?
- Does a Saturday holiday exception affect the part after midnight?
- Are enquiry response hours the same as the overnight service?
These questions expose mistakes that a plain Monday to Sunday text list can hide.
Treat holidays as dated exceptions
Keep regular weekly hours intact and add the relevant local-date exceptions through the supported controls. Google describes Special hours as a way to represent brief changes such as holidays without replacing the normal schedule. Google's Special hours guidance
Create an exception register before the busy period:
| Date | Location/service | Actual availability | Owner | Public check |
|---|---|---|---|---|
| Relevant local holiday/date | Correct branch or service | Closed or explicit changed intervals | Named confirmer | Observed result/date |
Do not assume every country, branch or customer market shares the same holiday calendar. An international business may need different exceptions for different operations.
Also check the website, recorded phone message, appointment confirmation and any automatic reply. A correct map profile does not repair an email that promises a response from an unstaffed office.
Describe appointment-only work clearly
Establish whether the business receives customers only by appointment, visits customers at agreed times or has a mixture of walk-in and booked service.
A useful instruction explains how to request an appointment and when it becomes confirmed. A request form or email exchange should not imply an accepted slot before the business has agreed it.
Check the platform's rules for your business type, including any advice to leave out standard main hours. The public information should reflect the real arrangement, not a 09:00 to 17:00 schedule copied from an office template.
For a fictional instrument repair studio, visiting arrangements might require an agreed drop-off time. The website can explain the process while the profile uses the appropriate supported hours treatment. It should not invite unannounced visits if the workshop cannot receive them.
Use a timezone name when the audience is international
A recurring schedule belongs to the branch's local civil time. A customer's appointment also needs enough date/time context to avoid ambiguity.
IANA's timezone database records the history and changes of local time, including daylight-saving rules. A named zone such as Europe/London carries different information from a permanently fixed UTC offset. IANA timezone information
For international communication, state the date and relevant timezone. Use a calendar invitation or another clear agreed representation where appropriate. A message saying "tomorrow at ten" can mean two different moments to the sender and the recipient.
Avoid assuming a whole country has one timezone. Confirm the branch location, and ask the website or booking supplier how daylight-saving changes and repeated/missing local times are handled.
Do not confuse open, available and responsive
A shop can be open while a particular service is unavailable. A provider can be available by appointment while the office is closed to walk-ins. A mailbox can accept requests while no one is responding.
Use those distinctions in the customer explanation. If the business publishes a response target, identify whether it uses working hours or elapsed time and whether it applies to every channel.
A realistic response promise is more useful than an automatic assurance the team regularly misses. Link the schedule to the enquiry follow-up process so reminders and acknowledgements use the same operating facts.
Worked public check: three schedules in one business
The case is fictional. A small furniture maker has a workshop team, an appointment showroom and an email inbox.
The workshop operates during ordinary production hours, but customers cannot visit the production area freely. The showroom accepts agreed appointments, including some times outside production hours. Email is reviewed during a defined staffed window.
The owner writes three distinct internal definitions. Public pages explain appointments and response expectations rather than turning the broadest of the three schedules into a 24-hour availability claim.
Before a holiday closure, the owner updates relevant profile exceptions, website wording, appointment confirmations and the email acknowledgement. A public recheck finds that an old contact page still displays walk-in hours; that page is corrected as a separate task.
A repeatable hours audit
Check the next ordinary opening, a split-period gap, an overnight boundary if applicable, the next exception date and an out-of-hours enquiry. Use the customer view on each important platform.
Record what the customer sees and who must correct any difference. Review after staffing changes, new service arrangements and holiday decisions, not just when a platform prompts you.
The hours record is working when the business can explain what each published time means and customers can make a sensible decision from it.