# UTC vs local time: how recurring classes should be stored

> Store one-off classes as UTC instants and recurring classes as local time plus an IANA zone. Calculate each occurrence using current time-zone rules.

URL: https://halqora.com/blog/utc-vs-local-time-recurring-classes
Last updated: 2026-10-21

Published: 2026-10-21 · By Halqora team

Store one-off classes as UTC instants, but recurring classes as local wall-clock time plus an IANA zone, calculating each occurrence from current time-zone rules. A fixed UTC recurrence shifts the local class hour when that zone changes clocks.

> **Key facts:** - Use a named zone to look up local time rules for each date, as described by the [IANA Time Zone Database](https://iana.org/time-zones).
> - As of 21 October 2026, the UK clock-change rules move clocks forward 1 hour on the last Sunday in March and back 1 hour on the last Sunday in October.
> - As of 21 October 2026, [IANA's release notes](https://data.iana.org/time-zones/tzdb/NEWS) list 5 releases during 2026 through late September, ending with 2026e on 29 September.

> **Definition:** An IANA zone is a named set of local time rules, such as Europe/London, while a UTC offset is the difference from UTC at a particular time.

## What are the ways to store a class time?

A class time can be stored as a UTC instant, a local time with a fixed offset, or a local time with a named zone. The choice depends on what you promised the family: a particular moment or a repeating local hour. Local time without a zone leaves the agreement incomplete when teachers and families live in different places.

For a one-off booking, UTC identifies when everyone should join. Display that instant in each person's zone. For a weekly agreement, preserve the weekday, local hour and zone as the recurring rule.

Before [setting up recurring class schedules](https://halqora.com/blog/recurring-class-schedules), agree whose local time anchors the class. A family's fixed evening hour may require the teacher's local hour to change during the year. Software cannot keep both local hours fixed when their zones change differently.

## Why does fixed UTC break recurring classes?

Fixed UTC breaks a recurring local-time agreement because UTC does not follow the family's clock changes. The recurring class still happens at the saved UTC hour, but the family sees a different local hour. UTC remains useful for each generated occurrence; the mistake is treating a repeating UTC hour as equivalent to a repeating London hour.

**Example:** A rule saved as “17:00Z every Tuesday” gives a London family a 17:00 class in winter. After the UK clock change on 29 March 2026, that fixed UTC rule moves the local class 1 hour later, under the UK rules current as of 21 October 2026.

The family did not request a new timetable. The stored rule preserved a different promise. Keep the local agreement as the source for future occurrences, rather than repairing the series after each clock change.

## Why do fixed offsets break too?

A fixed offset describes a difference from UTC, without describing how a place's rules change over time. UTC+5 and UTC-5 are offsets; they are not substitutes for place-based rules. An offset can suit a place while that offset remains in force, but the stored value cannot respond when daylight saving or a government decision changes the relationship.

As of 21 October 2026, [NIST's explanation of US daylight saving time](https://nist.gov/pml/time-and-frequency-division/popular-links/daylight-saving-time-dst) gives the start as the second Sunday in March and the end as the first Sunday in November, at 02:00 local time. The UK uses different Sundays.

A teacher and family can therefore have a changing time difference even when both observe daylight saving. Ask for each person's IANA zone instead of copying today's offset into the recurring rule.

## How does local time plus an IANA zone work?

Local time plus an IANA zone preserves the meaning of the recurring agreement. For each date, software looks up the zone's applicable rule and calculates the UTC instant. The teacher and academy can then view that instant in their own zones. The recommendation follows from how IANA rules work; it is a storage approach, rather than a quotation from IANA.

**Example:** A 17:00 Europe/London class equals 17:00 UTC in winter and 16:00 UTC during British Summer Time. The arithmetic is 17:00 minus the summer offset of 1 hour = 16:00 UTC. The London hour stays fixed while the UTC hour changes.

Use the same agreement throughout the booking process:

1. Confirm the weekday, local time and named zone with the family.
2. Calculate each occurrence using the rules for its date.
3. Show the resulting class in the teacher's and academy's zones.
4. Recheck affected future occurrences when time-zone data changes.

For developers, keep the recurring rule separate from generated UTC occurrences. Saving converted times alone loses the reason those times were chosen.

## How do the storage approaches compare?

| Approach | What is stored (24-hour time) | Survives DST? | Survives a government rule change? | Example failure |
| --- | --- | --- | --- | --- |
| Fixed UTC time | Example: 17:00Z every Tuesday | Does not preserve the local hour | Does not preserve the local hour | Example: London's local class moves 1 hour after 29 March 2026 |
| Fixed offset | Example: local time with UTC+5 or UTC-5 | No, if the place changes offset | No, if the offset changes | A saved offset differs from the place's new rule |
| Local time + IANA zone | Example: 17:00 Europe/London, recomputed per date | Yes, with current rules | Yes, after updating rules and recalculating | Stale time-zone data can still produce wrong occurrences |
| Local time without a zone | Local hour without a named place | Cannot determine | Cannot determine | Teacher and family interpret the hour in different zones |

The storage comparison is about preserving an agreed local hour, rather than whether an individual timestamp is valid. A UTC occurrence can be correct while a UTC recurrence expresses the wrong agreement. When reviewing [class scheduling software for online schools](https://halqora.com/blog/class-scheduling-software-online-schools), ask how future classes respond to clock changes instead of assuming a time-zone selector answers that question.

## What can government rule changes in 2026 teach you?

Government rule changes mean recurring schedules need maintained time-zone data as well as sensible storage. According to IANA's release notes as of 21 October 2026, changes involving British Columbia, Alberta, the Northwest Territories, Manitoba and Morocco prompted updates during 2026. A named zone gives software a way to apply revised rules, but storing the name does not update the software.

The release notes also describe a temporary modeling workaround for Canada's permanent-time changes because of a limitation in Unicode CLDR 48.1. Different software layers can lag behind a rule change. Check affected future classes after updates reach your scheduling system.

Egypt provides an older warning about short notice. [IANA's Africa commentary](https://data.iana.org/time-zones/tzdb/africa) records a Ramadan suspension in 2014 and canceled planned changes in 2015 and 2016. Treat future Egyptian transition dates as conditional: if the current rule holds.

## How Halqora handles this

Halqora, management software for online academies, stores scheduling rules in each IANA time zone so recurring classes stay correct across daylight-saving changes, with admins viewing calendars in the academy's zone and teachers in their own zone, as described in [Halqora scheduling](https://halqora.com/features/scheduling).

## Sources

- [IANA Time Zone Database overview](https://iana.org/time-zones), checked 21 October 2026
- UK government clock-change rules, checked 21 October 2026
- [IANA time-zone database release notes](https://data.iana.org/time-zones/tzdb/NEWS), checked 21 October 2026
- [NIST daylight saving time explanation](https://nist.gov/pml/time-and-frequency-division/popular-links/daylight-saving-time-dst), checked 21 October 2026
- [IANA Africa time-zone commentary](https://data.iana.org/time-zones/tzdb/africa), checked 21 October 2026

## Questions

### Should I store class times in UTC?

Store a single event as a UTC instant. For a recurring class that should keep the same local time, save the weekday, wall-clock time and IANA zone, then calculate each occurrence in UTC. A fixed UTC recurrence preserves the global time, but the family's local class time moves when the family's zone changes clocks.

### What is an IANA time zone?

An IANA time zone is a named entry in the IANA Time Zone Database, such as Europe/London or Asia/Karachi. The entry records a place's local time rules. Software uses those rules to calculate the UTC offset for a particular date. Future calculations depend on known rules, so software needs updated data when governments announce changes.

### Why do calendar apps sometimes get time zones wrong?

A calendar can show the wrong local time when its time-zone data is old or a recurring event was saved with a fixed offset. According to IANA's release notes as of 21 October 2026, there had been 5 database releases by late September 2026. Software also needs to apply updated rules when calculating future occurrences.

### What happens to scheduled classes when a country changes its rules?

A recurring class stored as local time plus an IANA zone can keep its agreed local hour after a government changes the rules. The scheduling system must receive updated time-zone data and recalculate affected future occurrences. A fixed UTC recurrence or fixed offset does not preserve that local agreement automatically and may need an administrator to correct it.