Skip to content
Prysm Edge
Book a Free Audit

A maintenance contract is only as valuable as the service level agreement that defines it. A well-written SLA specifies response times, resolution targets, escalation procedures and remedies for non-performance with enough precision that the client has genuine recourse if the provider fails to deliver. A poorly written one uses comforting language to make no meaningful commitments at all.

Here is what a high-quality SLA for building technology maintenance should contain.

Fault Classification and Response Commitments

Service Level Agreements: What to Demand from Your Technology Provider — inline image 1
Expert asset care in practice

Every SLA should define a tiered fault classification system — typically three or four levels — with clear definitions and response time commitments for each. A P1 fault (complete loss of a critical system) should carry a two-to-four hour remote response commitment and a next-business-day on-site commitment. A P4 fault (cosmetic issue with no functional impact) might carry a five-business-day response target. Critically, these should be commitments, not targets — with service credits payable if they are not met.

Resolution vs Response

Many providers commit to response times but not resolution times. “We will respond to your fault within four hours” is a much weaker commitment than “we will resolve your fault within four hours.” Read the SLA carefully: does it specify when an engineer will contact you, or when the fault will be fixed?

Escalation Procedures

Service Level Agreements: What to Demand from Your Technology Provider — inline image 2
Expert asset care in practice

A well-structured SLA includes an escalation matrix: who do you contact if the first-line response is inadequate, how quickly does escalation happen automatically, and at what point does senior management become accountable? The absence of a defined escalation procedure is a significant red flag.

Exclusions and Limitations

Read the exclusions section carefully. Common exclusions that can significantly limit the value of a contract include: faults caused by third-party systems, faults in components not covered by the maintenance schedule, and faults resulting from conditions outside the equipment’s operational specification. Make sure you understand what is and is not covered before signing.

Monthly Insights

Stay Ahead of the Curve

Technical perspectives on BMS, HVAC, energy management, and smart-building technology — delivered monthly. No spam. Unsubscribe anytime.