→ Articles

2026-08-25

SLAs in Facility Operations & Maintenance Contracts

A Service Level Agreement (SLA) is the part of an O&M contract that turns "good service" from vague promise into binding numbers: within how many hours must a fire-system fault get a response? Within how many days must a routine AC fault be closed? What is the penalty for missing it? For the owner, the SLA is a quality guarantee. For the O&M company, it cuts both ways: a trust-builder that wins contracts — and a source of penalties when it isn't measured and managed properly.

What an FM SLA contains

• Priority classes: emergency, urgent, routine, scheduled — each with its own clocks.
• Response time: from request opened to technician on site or work started.
• Resolution time: from request opened to documented closure.
• Target compliance rates: e.g. "95% of emergency requests responded to within 2 hours".
• Penalties: defined deductions when times or rates are missed.
• Reporting: what the owner receives monthly, and at what detail.

Typical time examples

• Emergency (fire, total power loss, occupied stuck elevator): respond in 30–60 minutes, resolve in 4–8 hours.
• Urgent (AC failure in an occupied hall, water leak): respond in 2–4 hours, resolve in 24–48 hours.
• Routine (lighting, minor works): respond within one business day, resolve in 3–7 days.
• Scheduled (preventive maintenance): per the agreed schedule with 90%+ on-time completion.

Why penalties come as surprises

Because measurement is manual. The request arrives on WhatsApp with no recorded time, the technician closes it verbally, and at month-end a team reconstructs history from memory and chat scroll. The owner calculates it their way, the company has no defensible record, and the penalty is deducted. The equation flips when the SLA clock starts automatically the moment a request is logged, warns the supervisor before a breach, and records every timestamp — reporting turns from argument into a shared record.

How to run SLAs properly

1. Fix priorities in the system: each request class carries its clocks automatically — no on-the-spot judgment.
2. Start clocks automatically: from the moment of logging — with MRFQ, a WhatsApp request is logged instantly.
3. Warn before the deadline: alert the supervisor before response time expires, not after.
4. Document closure with photos and timestamps: the company's protection in any dispute.
5. Review monthly: compliance per contract, site and technician; fix the causes of repeats.

About MRFQ

In MRFQ every contract carries its priorities and clocks; the system starts timers automatically, alerts before breaches, and produces compliance reports per client and site — while technicians close their jobs with photos over WhatsApp, in their own language, no training needed. Arabic-first and PDPL-aligned. Try it free for 14 days at mrfq.sa.

Frequently asked questions

What is an SLA?

The part of a service contract defining binding response and resolution times per priority class, target compliance rates, and penalties for misses.

What is the difference between response time and resolution time?

Response time runs from request opened to work started or technician on site; resolution time runs from opened to fully documented closure.

How do I avoid SLA penalties?

Automatic measurement from the moment a request opens, alerts before deadlines, and photo-and-timestamp closure documentation — which is what MRFQ does automatically.

Do SLAs apply to subcontractors?

Yes — best practice passes the same (or slightly stricter) clocks into subcontracts and tracks them in the same system, so the main contractor doesn't absorb its subcontractors' penalties.

What is a good SLA compliance rate?

Serious contracts typically target 90–98% depending on priority — highest for emergencies — and what matters is measuring from a documented record, not memory.