Morocco’s 2026 Time Change: Permanent UTC+00 for Schedules and Software

Morocco is scheduled to move to permanent UTC+00 on 20 September 2026. The change is recorded in version 2026c of the Internet Assigned Numbers Authority (IANA) Time Zone Database, the data set used by operating systems, programming runtimes, and many calendar services to calculate civil time. For anyone coordinating with Casablanca, the key lesson is simple: replace old assumptions with a current, location-aware conversion before scheduling anything after the transition. IANA’s release summary is the authoritative technical reference for the date.

This is not merely a display-label change. A one-hour rule change can alter the local wall-clock time attached to a meeting, flight, support window, deployment, or automated report. The underlying moment in time may be correct while its local presentation is wrong. That is why teams should make the update a scheduling, communications, and software-maintenance task—not leave it to a last-minute manual calendar edit.

What changes on 20 September 2026

IANA’s 2026c summary states that Morocco moves to permanent UTC+00 on 20 September 2026. UTC is the global reference scale used to express an instant independently of local clock rules. “Permanent UTC+00” therefore means that future scheduling should be calculated from the UTC+00 rule recorded for Morocco, rather than from an inherited expectation that Casablanca will generally be one hour ahead of UTC. IANA explains that its database is updated when political authorities change local offsets, daylight-saving rules, or time-zone boundaries.

The safest practical identifier is Africa/Casablanca, not a bare abbreviation such as “WET” or “GMT.” Abbreviations are ambiguous, can change their meaning in different contexts, and rarely capture a place’s full historical rules. A named IANA zone lets a time-zone-aware application select the right offset for the date being converted.

How the change affects meetings and customer coverage

Start with the meeting’s date. A recurring call that began earlier in the year may cross the rule change while it is still active. Open the calendar series, review the location or time-zone field, and verify that the organiser used Africa/Casablanca rather than a hard-coded offset. Then ask each attendee to view the event in their own calendar. That check matters because two people can see the same instant but have different local-day or local-hour consequences.

Support and operations teams should also inspect service-level windows. If a policy promises replies during Casablanca business hours, a fixed UTC schedule might cease to represent that promise after the transition. Publish windows with both a named local zone and a UTC reference where an international audience needs clarity. TZSync’s time-zone converter can help teams compare a selected Casablanca time against the cities where colleagues or customers are located.

A technical checklist for developers and administrators

The IANA database is commonly bundled by an operating system, language runtime, container base image, or third-party library. That distribution path determines when a change reaches production. IANA notes that end users often receive updates through software and operating-system vendors, so an application can be correct in source code but stale in its deployed environment if the bundled data was not refreshed. Review the current IANA release before relying on an old image or package lock.

1. Inventory the environments that calculate Morocco local time: employee devices, servers, containers, job runners, CRM tools, calendars, and analytics platforms.
2. Confirm each environment’s installed time-zone data version and its vendor’s update path. Apply normal change-control and rollback procedures.
3. Test conversions immediately before and after 20 September using a named Africa/Casablanca value, rather than testing only a current date.
4. Store timestamps as UTC instants in databases and attach the IANA zone only when rendering or collecting local user input.
5. Review recurring jobs that run at a local hour. Decide whether their business requirement is an exact UTC instant or a particular Casablanca wall-clock time.

Do not solve a civil-time update by manually adding or subtracting one hour throughout the codebase. That approach is brittle, difficult to audit, and likely to fail when a user selects a different city or date. Let maintained time-zone data make the rule decision, while your application preserves the intent of the scheduled event.

Travel, bookings, and communications

Travellers should check the local time shown by their carrier, accommodation, and official local notices close to departure. A booked departure or arrival time is normally a local civil-time commitment, while a connection may be in another zone. Keep the original confirmation, avoid converting times by memory, and verify each leg in a current calendar or conversion tool. Automated devices usually update, but not every device receives time-zone data at the same pace.

Communications need one clear owner. An operations lead can send a brief notice that identifies the affected date, uses the full place name “Casablanca, Morocco,” states the selected time zone, and links to the live meeting or booking record. This reduces the risk that a recipient interprets a bare “GMT” label through their own local daylight-saving rules.

Frequently asked questions