Glossary · Service level agreement (SLA)

SLA (service level agreement): how quickly a contractor has agreed to respond

A service level agreement (SLA) in maintenance sets how quickly a contractor should respond, attend and finish work, usually by priority, trade and site type. SLAs matter most when downtime affects occupiers, customers or regulators. Informal SLAs in email fail because nobody is measuring against the same times.

OpsChase puts SLA policies on work orders, records when times are missed, and starts reminders. Reports show the hit rate by site, trade and contractor.

Why multi-site teams care about SLAs

A single site manager knows when the plumber is late. Across thirty sites, nobody does unless the times are written down and measured the same way. SLAs give area managers, landlords and contractors one shared answer to “how long should this take?” They also turn a vague complaint (“that firm is always slow”) into something you can check by site, trade and contractor.

What a good maintenance SLA covers

  • Respond: how quickly the contractor confirms they have the job.
  • Attend: how quickly someone is on site, usually by priority, such as an urgent make-safe versus a routine repair.
  • Complete: how quickly the work is finished, or a return visit is booked when parts are needed.
  • Proof: what evidence is needed before the job counts as done.
  • Hours: whether the times run in business hours or around the clock, and in which state’s time zone.

Keep the priority list short. Three or four levels that everyone understands beat ten that nobody uses consistently.

Common SLA mistakes

  • Writing SLAs into contracts but never measuring them on the actual jobs.
  • Using one set of times for every site, even where the drive to a regional site makes them impossible.
  • Counting a job as done when the contractor says so, rather than when the proof arrives.
  • Reviewing performance once a year, after the pattern has already cost you.
  • Ignoring after-hours rules, so a four-hour attend time quietly includes a Sunday night.

How SLAs fit contractor tracking

In OpsChase, SLA policies are set by trade and priority. They sit on the work order from the moment it is raised or triaged. When a respond or attend time is missed, tracking starts: the contractor is reminded, and your own team sees the job is late. Business hours, state time zones, after-hours routing and quiet hours are all taken into account. Reports show the hit rate by site, trade and contractor, so a performance review starts with facts.

See tracking until the work is done for how reminders work, and regular contractor for how SLA results sit on each firm’s job history.

On OpsChase: one queue for your team and contractors, each job tracked until the work is done, then photos or sign-off. Book a demo — one site or many.

Are SLAs in OpsChase legally binding?
No. OpsChase tracks the operational times; the legal terms stay in your contracts. Exports support your performance reviews.
Can SLAs differ by state or site?
Yes. Site and region details decide which policy applies, so a regional site can carry attend times a contractor can actually meet.
Do SLAs apply to planned maintenance?
Yes. Planned jobs can miss attend windows just like reactive ones, and the same tracking applies.
What should an urgent attend time be?
It depends on the risk and the site. Agree times with your contractors that they can meet, including at regional sites, then measure them on every job.
What if a contractor keeps missing SLAs?
The reports show it by site and trade, so any conversation with that firm rests on the job history rather than memory.
OpsChaseOpsChase

Start with the part you need today and add the rest when you’re ready. One site or many.

Book a demo