Estimated reading time : 4 min · Published
Define hours for each service
Separate venue opening, telephone reception, delivery and appointments. Online booking at any time does not imply continuous reception. Show breaks as two distinct time ranges; explain access conditions without making visitors guess what is open.
For each location, record the time zone, validity period and person who confirms the hours. A period crossing midnight should be understood from the starting day into the next day. Ask someone unfamiliar with the organization to review that example.
Fictional teaching case using Europe/Paris rules consulted on 23 October 2026: on 25 October 2026, 02:30 can identify two instants. With offset +02:00 it corresponds to 00:30Z; with +01:00, to 01:30Z. They are 3 600 seconds apart. Europe/Paris identifies a set of rules, not a fixed year-round offset. A local clock time alone therefore cannot always identify an appointment or an opening boundary.
The IANA database changes with decisions about zones and daylight saving. For a recurring rule, retain local time and zone; for a confirmed exception, also identify unambiguous boundaries and dates. In the same 25 October example, 01:30 to 03:30 in Europe/Paris lasts three elapsed hours despite the two-hour difference between displayed clock values. Test both occurrences of 02:30 and the interval end. This calculation proves neither actual reception nor slot availability; those remain for the responsible person to confirm.
Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.
| Local time · Europe/Paris | Instant or duration | What can be concluded |
|---|---|---|
| 2026-10-25 02:30 +02:00 | 2026-10-25T00:30:00Z | First occurrence of 02:30 |
| 2026-10-25 02:30 +01:00 | 2026-10-25T01:30:00Z | Second occurrence of 02:30, one hour later |
| 2026-10-25 01:30 +02:00 → 03:30 +01:00 | 10 800 s | Three elapsed hours for this dated interval |
| 02:30 without an offset | Ambiguous instant | Specify the occurrence before confirmation |
Treat exceptions as dated data
Record full dates, affected services and expected reopening. Fictional example: reception closes for two days while the telephone operates on the first morning; publish separate exceptions. A public holiday alone does not establish opening status. Have each period confirmed by its owner and replace “tomorrow” with a date that remains clear when shared.
Schema.org distinguishes normal hours from dated exceptions through specialOpeningHoursSpecification. Google Business Profile also supports special hours. The website, structured data and platforms should describe the same verified situation, without blindly copying an old calendar.
Fictional exercise: reception closes on 15 November 2026 while the phone line remains open from 09:00 to 12:00. The next day, reception opens from 14:00 to 18:00. Record an exception for each service and date; a general “closed” banner does not describe all three situations.
Test expiry too: after 16 November the exception must stop obscuring the approved regular timetable. A place’s special opening hours override its general hours for the relevant period; they do not establish booking availability or telephone coverage.
Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.
| Service and date | Approved information | Expected check |
|---|---|---|
| Reception · 2026-11-15 | Closed all day | The page does not invite a visit on that date. |
| Telephone · 2026-11-15 | 09:00–12:00 | The phone line remains distinct from closed reception. |
| Reception · 2026-11-16 | 14:00–18:00 | The following day does not inherit the closure. |
| After 2026-11-16 | Approved regular timetable resumes | The old alert disappears without inventing hours. |
- Schema.org · specialOpeningHoursSpecification
Schema.org describes overriding regular opening hours with exceptions; the dates and services here are fictional. Source consulted on 22 October 2026.
Synchronize and check published versions
Keep one reference for opening hours and translate its explanations. Fictional example: an evening runs from Friday at 8 pm to Saturday at 1 am; name both days and check the display before midnight, after midnight and after closing. Define when the notice expires so regular hours become clear again without an outdated exception.
Test a normal day, a break, a closure and reopening. Check location pages, contacts, booking links and mobile versions. When a time remains uncertain, offer a confirmation contact instead of calculating an ‘open’ status from incomplete data.
Reference documents
- Schema.org : specialOpeningHoursSpecification · Source consulted
- Google Business Profile
- IANA : Time Zone Database · Source consulted
- IANA tzdb 2026e : Europe · Source consulted
Content updated on
