Start with a reproducible failure
A time without a zone can mean different things to organisers and visitors. A website needs to distinguish a fixed instant from a recurring local time.
Use a small controlled test to separate a symptom from its cause. Record the starting state, affected URL and observed outcome so that another person can repeat the check.
Collect evidence before changing anything
Choose an ordinary day and dates around spring and autumn transitions. Compare source data, stored instant and display in two zones. A local hour can be missing or repeated; the system needs an explicit decision.
Fictional example: A recurring webinar should start at nine in the organiser’s zone. A fixed UTC offset makes the next session display an hour incorrectly after the transition.
| Check | Expected outcome |
|---|---|
| Starting condition | The same local start time has the wrong relationship to that date’s zone. |
| Implementation | Choose an ordinary day and dates around spring and autumn transitions. Compare source data, stored instant and display in two zones. A local hour can be missing or repeated; the system needs an explicit decision. |
| Verification | Ordinary dates and transition cases agree across the page and calendar export. |
Fix the cause and repeat the test
Use the date’s actual zone rules and define how ambiguous local times are selected. Formatting changes or translated month names do not repair the time model.
Repeat the same test after the change and add a nearby case that already worked. One successful case establishes that task in those conditions; it does not certify the whole website.
What the test establishes
Ordinary dates and transition cases agree across the page and calendar export.