SLA in a Property Management Contract — the Complete Guide for Building Owners

A management contract without an SLA is a promise with no teeth. An SLA — a Service Level Agreement — is the clause that turns "we'll handle it soon" into a measurable commitment with times, metrics and consequences. A building owner who defines an SLA correctly knows exactly what they are getting, and can enforce it. As a building manager who works daily with vendors, tenants and apartment owners, I have seen firsthand what happens when an SLA is worded correctly and when it is not.

What an SLA is and why it is essential in property management

An SLA (Service Level Agreement) is an appendix to the management contract that defines, in numerical and measurable terms, the minimum level of service the company is obligated to provide. Unlike qualitative definitions such as "fast service" or "professional response," the SLA sets numbers — hours, percentages, frequencies — that can be checked after the fact.

In property management in Israel, most management contracts signed between building owners and management companies include no formal SLA at all. This is a mistake we encounter repeatedly in audits: a building owner is dissatisfied, the company claims it provided "reasonable" service, and there is no objective metric to settle the dispute. The SLA solves that gap.

Response times by urgency level — the heart of every SLA

Not every fault is equal. A good SLA defines four urgency levels, and for each one — a response time (until someone acknowledges the request) and a resolution time (until the fault is actually closed).

• Emergency — an immediate safety risk: flooding, a smell of gas, a major electrical failure across the whole building, a stuck elevator with a person inside, a critical safety fault. Response within an hour, 24/7 including weekends and holidays. Resolution time: up to 4 hours.
• Urgent — a significant impairment of the building's function: central HVAC down in summer, a localized water leak, an access-control fault, a power outage on a floor. Response within 4 hours, resolution on the same business day.
• Standard — a fault that does not block function: a burned-out bulb, a dripping faucet, a door that does not close properly, a routine service request. Response within one business day, resolution within 3–5 business days.
• Planned — an improvement, upgrade, painting, installation. Handled by prior arrangement within an agreed time frame.

Clearly defining each level prevents arguments: the moment a fault is classified in advance, it is clear which response time applies to it and what the consequence is if it is missed. A vendor who argues that a "stuck elevator" is a "standard" fault — that is a red flag.

Quality metrics — beyond response speed

Response time is only one part of the SLA. Quality metrics examine performance over time and prevent a situation where the vendor "responds fast" but does not truly resolve. Here are the metrics worth demanding:

• SLA target compliance rate — what percentage of calls were handled within the set time. A reasonable target: 90% and above.
• Repeat rate — does a problem that was closed recur within 30 days? A recurring fault indicates a partial resolution. Target: less than 10% repeat rate.
• On-time statutory inspections — elevator inspections (the occupational safety regulations), fire, generator, electrical installations. These are legally mandated and have a defined schedule.
• Preventive maintenance completion rate — maintenance that was planned in advance and carried out on time. Target: 95%.
• Tenant satisfaction — a short survey (digital is fine) once a quarter.
• Quality of the monthly report — does the report arrive on time, complete, with full SLA data?

SLA for maintenance and faults versus SLA for ongoing services

It is important to distinguish between two fundamentally different types of commitment:

An SLA for maintenance and faults deals with response and resolution times — how fast you react to an event. It is measured event by event, and is based on a service-request system.

An SLA for ongoing services (cleaning, security, landscaping, exterior lighting) deals with a continuous performance level — frequency, quality and consistency. It is measured against a fixed standard and proactive quality control, not only complaint-driven.

A comprehensive contract must include both, with separate metrics. Without such a separation, you get a situation where "fast response to faults" masks poor cleaning or inconsistent security — because there is no metric measuring them. I have seen buildings with excellent response time but corridors that were not cleaned properly for weeks — because there was no SLA for the ongoing service.

Penalties, credits and escalation mechanism

An SLA without consequences is merely a recommendation. The contract must explicitly define what happens when a target is missed.

Common options

• Financial credit — an automatic reduction from the monthly management fee for every material breach.
• Escalation — a call that was not handled on time is automatically raised to a higher tier (a senior manager, the company's owner).
• Right of termination — a recurring breach (for example, more than 3 breaches in 12 months) grants the building owner the right to terminate the contract without penalty.

The right balance

Penalties that are too aggressive push toward shortcuts — a vendor who closes a call on paper to meet the deadline, without solving the problem. A combination is better: a penalty for a significant breach + a positive incentive (a small bonus for above-target performance). This creates a real incentive for quality handling and not just for closing calls.

It is also important to include a proof procedure: not every breach is the vendor's fault — force majeure, a delay by an external vendor the building owner engaged themselves, or unforeseen events. The SLA must define what counts as a "justified exemption" and what does not.

How to ensure the SLA is actually measured

An SLA that is not measured is an SLA that does not exist. Measurement requires three elements:

• A digital service-request system — one that automatically records the time of opening, acknowledgment, and actual closure. The vendor self-reporting on a spreadsheet is not enough.
• Access to the data — the building owner should have access to view all calls and their status in real time, not only in a monthly report.
• A monthly SLA report — a dedicated document that presents all SLA metrics, the compliance rate, and a list of breaches with explanations. See also the guide to the monthly maintenance report.

Ask every management company before signing: "Which system do you use to manage service requests? Can I get view access?" — the answer will reveal a great deal about the transparency you will get.

The common mistake — a generic SLA that cannot be enforced

An SLA written in vague terms ("fast response," "quality service," "handled as soon as possible") has no legal or practical value — because it cannot be measured and therefore cannot be enforced.

The common red flags in Israeli management contracts:

• Response times worded in words ("soon," "reasonable") instead of hours.
• No clear definition of what counts as "emergency" versus "urgent."
• No measurement mechanism — the SLA is written but there is no tool to measure whether it was met.
• No consequence for non-compliance — merely "we'll try to improve."
• An SLA that applies only to working hours, with no defined emergency handling outside those hours.

If a management company objects to committing to concrete numbers — that in itself is important information about the way it works.

The clauses that must be in the contract

Here is a minimum checklist for every SLA in a property management contract:

• A definition of urgency levels (emergency / urgent / standard / planned) with example scenarios for each level.
• Numerical response time and resolution time for each level.
• A definition of hours of operation and emergency handling outside those hours.
• Quality metrics and numerical targets (compliance rate, repeat rate, preventive maintenance).
• A measurement mechanism and an objective data source (a service-request system).
• Building owner access to the data in real time.
• Penalties / credits / escalation for non-compliance.
• A definition of "justified exemption" (force majeure, an external vendor of the owner's).
• The structure of the monthly report and the inclusion of SLA data.
• Contract termination terms due to recurring breaches.

Choosing the right management company starts with the right questions — see how to choose a property management company. At Domera we work with a measurable, transparent SLA and a digital service-request system. Get a quote.