Ramadan 2027 service desk playbook: the day shrinks, the SLA doesn't

Ramadan 1448 is expected to begin on Monday 8 February 2027 (Umm al-Qura calendar), and for four weeks most private-sector desks in the GCC lose working hours by law, for some or all of their staff, while their SLA promises stay exactly as written. Demand moves too: in some sectors the busy hours shift to after iftar, and the month ends in a two-day window for Eid that nobody can date until the moon is sighted.

Do this in November or December, not the week before. Here is what moves, what must not, and the three free tools that do the arithmetic.

Ramadan working hours by GCC country: what the law reduces

My practitioner reading of each country's private-sector labour law, not legal advice: the ministry text governs, and public-sector hours are set separately by each government, not by the labour law.

Confirm each rule with the ministry before you rely on it.

Where the reduction is written for Muslim workers, ask HR which schedule your non-Muslim staff are on before you build the rota. And the law sets a ceiling, not your hours: your HR circular sets those, and the SLA calendar copies the circular.

The SLA clock

A business-hours SLA counts only the hours on the schedule. Shorten the schedule and every business-hours target takes longer in calendar time. That is correct, and it surprises the business every year.

Set the Ramadan dates and hours in your ITSM tool's schedule and in the GCC business hours calendar you check it with, and keep them identical, or the SLA report and your own check will disagree in March.

On the Saudi Sunday–Thursday preset with the calendar's default Ramadan hours of 09:00–15:00:

• An 8-hour P3 logged Monday 15:30 is due Tuesday 14:30 on normal hours and Wednesday 11:00 on Ramadan hours, because the clock does not start until Tuesday 09:00.
• A four-hour P1 logged at the same time is due Monday 19:30 either way. P1 runs 24 × 7 by default and then ignores Ramadan hours, weekends and holidays.
• The week drops from 45 counted hours to 30. An 8-hour P3 fits inside one normal day; on six-hour days it always spills into the next.

To replay a real incident in the SLA clock, set the Ramadan dates in the calendar first, then choose "My saved calendar".

Two rules. P1 stays on 24 × 7; the discipline in A P1 outage isn't a technical event. It's a trust event. applies at 20:00 on a Ramadan evening as much as at 02:00. Business-hours targets stretch in calendar time, and that is fine, provided the business hears it from you before the first target breaches, not from a report afterwards.

Send this the week before, with your own hours and days in the brackets:

From Monday 8 February (expected, subject to the moon sighting) the service desk runs Ramadan hours of [09:00–15:00], [Sunday to Thursday]. P1 incidents are unchanged: 24 × 7, [via the hotline]. P2–P4 targets count in the shorter hours, so an incident or request logged after [15:00] starts the next working morning. Eid Al Fitr is expected on Tuesday 9 or Wednesday 10 March; the SLA calendar will carry the holiday once announced. We will confirm every date on the day of the announcement.

The rota

The legal day is shorter. Demand is not. In retail, the stores' busy hours move to after iftar, and so do their incidents; a desk that closes at 15:00 leaves tills and store systems without first-line cover when it matters most. That is what I have seen on desks I have run, not a statistic.

Expect shrinkage to rise: prayer times inside a shorter day, breaks for fasting staff and leave clustered around Eid all take paid time off the queue. The staffing calculator puts it plainly: "30% to 35% is common. If you need 10 agents taking contacts and shrinkage is 30%, you need to roster 15." Re-run it on what you actually saw last Ramadan:

• Take the peak hour from last Ramadan's data, not the annual average. With no data, use this year's peak and label it an estimate.
• Enter contacts in the peak hour, handle time, service level target and shrinkage. The roster is agents on queue divided by (1 − shrinkage), rounded up.
• Watch occupancy: "Above about 85% to 90% for long periods, people burn out, quality drops and absence rises, which pushes shrinkage up."
• The day planner uses fixed arrival shapes and has no Ramadan profile. Size the peak hour, then place it where your data says it falls.

If the peak is in the evening, the usual answer is a split shift: a morning team on the legal hours and a smaller team after iftar. Both must fit the ceilings in the table, so ask HR first. And the SLA calendar applies one Ramadan range per day and cannot split it, so decide whether the evening is cover (the queue is watched, the clock is not running) or counted SLA time (a 24 × 7 clock for that priority). Do not let the rota promise hours the SLA document doesn't.

Eid at the end

Eid Al Fitr 1448 is expected on Tuesday 9 March 2027 if Ramadan runs 29 days, or Wednesday 10 March if it runs 30 (Umm al-Qura calendar). Each country announces separately and may differ by a day. Plan both days.

• Name the Eid cover now. P1 on-call does not stop for Eid; write the names in while people can still swap.
• Take the holiday length from your country's announcement; it can differ by country and, in some countries, between the public and private sector.
• Undated holidays count as working time: the calendar's Eid Al Fitr row ships with a blank date on purpose, so until you enter it the clock runs through Eid. Date it in both places on the day of the announcement; if it overlaps the Ramadan range, the holiday wins.

The checklist

1. Confirm with HR which Ramadan hours apply, and to whom, in each country.
2. Enter the expected dates and hours in the ITSM tool schedule and the business calendar, identically.
3. Keep P1 on 24 × 7 and check which other priorities belong there.
4. Replay last Ramadan's worst breach in the SLA clock, with last year's Ramadan dates in the calendar.
5. Re-run the staffing calculator on last Ramadan's real peak hour with the shrinkage you actually saw.
6. Decide whether the evening is cover or counted SLA time, and write it into the SLA document.
7. Send the announcement the week before, every date marked expected, and a one-line update on the evening of Sunday 7 February (expected) once the start is confirmed.
8. Name Eid cover and P1 on-call for both possible Eid days.
9. Date the Eid holiday in both places on the day it is announced.

Start with the GCC business hours calendar: pick your preset, enter the expected dates, and read the sentence it writes for the board paper. It runs in your browser, and nothing is sent to ITSM Compass.