Vendor SLA for Property Management: Template With the Three Clocks

Open the maintenance contracts in any property portfolio and count how many say the vendor will "respond promptly", "attend as soon as reasonably practicable" or "prioritise emergencies". Then try to work out, from those words, whether the plumber who arrived nine hours after a burst pipe was in breach. You cannot, and neither can the vendor, which is why nothing happens after the ninth hour except an argument.

"Respond promptly" is not a time. A vendor SLA property management teams can enforce needs three clocks, each with a number of hours attached, a rule for when the clock starts, and a rule for when it stops: acknowledge (the vendor confirms it has the job), attend (a qualified person is on site), and restore (the fault is fixed or made safe). Almost every SLA dispute traces back to one of those clocks being missing, or to nobody having agreed when it started.

This post is a vendor SLA property management template. It defines what a vendor SLA is and what it is not, sets out the three clocks, gives a P1 to P4 priority matrix with times by trade, provides an annotated clause set, works a service credit example in dollars, covers the variations by trade, and shows how the clocks are measured from the work order rather than from memory.

Definition

A vendor service level agreement (SLA) in property management is the part of a maintenance or service contract that sets measurable commitments for how quickly and how well a vendor responds to work orders: the time to acknowledge, the time to attend on site, and the time to restore service, each by priority level, together with the exclusions, the reporting, and the consequences (service credits, escalation, termination) when a commitment is missed. RIOO describes the three commitments as the three clocks. An SLA is not a scorecard (which measures the vendor across many dimensions) and not the whole contract (which also covers scope, price, insurance and term).

At a glance

What a vendor SLA is, and what it is not

An SLA is the measurable part of a maintenance service level agreement. The contract says what the vendor will do and for what price; the SLA says how fast, to what standard, with what evidence, and what happens if not. It is a short document, usually a schedule to the main agreement, and its whole value lies in being specific enough to score.

Three things get confused with it. The first is the scorecard, which rates the vendor on quality, cost, compliance and communication as well as speed; the SLA is the input to the speed and reliability lines of the scorecard, not a replacement for it (the vendor scorecard covers the rest). The second is the internal service standard the property promises its residents or tenants ("we respond to emergencies within one hour"); that standard is the property's, and the vendor SLA has to be tighter than it, because the property's clock started before the vendor's. The third is the statutory repair timescale in landlord-tenant law (24 hours for no heat in winter in many US jurisdictions, for example); that is a floor set by law and the SLA has to sit inside it, not restate it.

In the vendor lifecycle, the SLA is written at stage 3 (contract), enforced at stage 5 (dispatch) and reviewed at stage 7. It is also the document that decides whether a termination for cause at stage 8 will hold up, because "the vendor was slow" is an opinion and "the vendor missed the P1 attend clock four times in a quarter" is a record.

The three clocks

Each clock needs four things defined: the event that starts it, the event that stops it, the time allowed, and the evidence that proves the stop event happened. Without all four, the clock cannot be measured, and an unmeasurable clock is not a commitment.

Two rules keep the clocks honest. The clock starts when the work order is issued, not when the vendor opens it; a vendor who does not monitor the portal at weekends has an SLA problem, not an excuse. And the restore clock is satisfied by "made safe" only if the SLA says what made safe means for that trade (a temporary heater in a no-heat call, an isolated circuit for an electrical fault, a locked-off lift) and requires the permanent repair to be scheduled before the clock stops.

For remote diagnosis, the attend clock can be split: a remote attend within one hour for building systems with remote access (BMS, lift controllers, access control), followed by a physical attend if the fault cannot be cleared remotely. That is worth writing in for those trades, because a vendor who can clear a fault from a laptop in forty minutes should not be forced to drive two hours to satisfy a clock.

Priority levels: the P1 to P4 matrix

The priority levels maintenance SLAs use are conventionally four. Each is defined by consequence, not by trade, and then illustrated by trade so that the dispatcher and the vendor classify the same call the same way.

Three notes on using the matrix. The examples column is the part to argue about at contract stage, because the classification of "HVAC failure" (P1 in a July heatwave with vulnerable residents, P2 in April) needs a rule, and the rule usually references outside temperature and the occupant. The times are planning ranges from common practice; a dense urban portfolio with an in-house team can tighten P1 attend to two hours, while a rural portfolio contracting a single trade across a county may need four. And the statutory floor overrides the matrix: where a state or local code sets a repair timescale for a habitability item, that timescale is the restore clock whatever the table says.

For student housing and multifamily, where the volume is residential and the calls arrive through a resident portal, the matrix is what the dispatcher uses to set the priority on the work order before it reaches the vendor, so the vendor's SLA clock and the resident's expectation are set by the same decision. For commercial and industrial buildings, the tenant's lease often defines its own service standards, and the vendor matrix has to be at least as tight as the tightest lease in the building.

The annotated clause set

The clauses below are drafted as a schedule to a maintenance agreement. Square brackets mark the negotiable values. The notes explain what each element is doing and what happens if it is left out.

1. Scope of services. The Vendor shall provide [reactive repair and maintenance of plumbing systems] at the Properties listed in Appendix A, in response to Work Orders issued by the Manager, and [planned maintenance] in accordance with the schedule in Appendix B.

The SLA applies to work orders within scope. A vendor asked to attend something outside its trade cannot be held to the clocks for it, so the scope has to be exact and the appendix of properties current.

2. Hours of service. P1 Work Orders may be issued at any time and the Vendor shall maintain a 24-hour contact number staffed by a person able to dispatch a technician. P2 to P4 Work Orders are issued during Business Hours, being [08:00 to 18:00, Monday to Friday, excluding public holidays], and the clocks for P2 to P4 run in Business Hours only.

Without this, a P3 issued at 17:55 on Friday has a 1-business-day acknowledge clock that a vendor will read as Saturday and a manager as Monday. Say which.

3. Priority levels and the three clocks. Each Work Order shall carry a Priority (P1 to P4) assigned by the Manager in accordance with the Priority Matrix in Appendix C. For each Priority the Vendor shall meet the Acknowledge Time, the Attend Time and the Restore Time set out in Appendix C. Each Time runs from the Issue Time of the Work Order, being the time the Work Order is issued through the Manager's [portal] or, for P1, the time of the telephone call to the Vendor's 24-hour number.

This is the operative clause. It fixes the start event (issue, not receipt), names the channel, and points to the matrix. The Manager assigns the priority; the vendor may challenge a classification through the escalation clause, but cannot re-classify a P1 to a P2 by itself.

4. Evidence of compliance. The Vendor shall record acknowledgement, arrival on site and completion through the Manager's [portal or mobile application], with the time of each, and shall attach on completion a description of the work, photographs of the fault and the repair, and any parts used. Where the Vendor is unable to record through the portal, it shall notify the Manager's [maintenance coordinator] by telephone at each stage and the Manager's record shall be conclusive.

No evidence, no measurement. This clause makes the vendor's use of the work order system a contractual obligation and settles whose record wins when they differ.

5. Made safe and permanent repair. Where a P1 or P2 fault cannot be permanently repaired within the Restore Time, the Vendor shall make the fault safe within the Attend Time (in the manner described for the relevant trade in Appendix D), shall notify the Manager of the temporary measure, and shall issue a follow-up Work Order for the permanent repair with a date not later than [5 Business Days] after the initial attendance.

Stops the SLA being met by a visit that fixes nothing. Appendix D defines "made safe" per trade, which is where HVAC, plumbing, electrical and lift vendors differ.

6. Exclusions and clock suspension. The clocks are suspended for any period during which the Vendor is unable to attend or complete because of: (a) denial of access by an occupant, recorded at the time; (b) unavailability of a part that is not a Stocked Part under Appendix E, from the time the Vendor notifies the Manager until delivery; (c) severe weather or a declared emergency preventing safe travel; (d) an instruction from the Manager to stand down. The Vendor shall notify the Manager of the suspension event within [1 hour] of its occurring or the suspension does not apply.

Every vendor will ask for these and they are fair. The notification requirement is what stops them becoming an after-the-fact excuse: a suspension not claimed at the time is not a suspension.

7. Reporting. The Vendor shall provide, within [5 Business Days] after each month end, a report of all Work Orders issued in the month with the Priority, Issue Time, Acknowledge Time, Attend Time and Restore Time for each, the clocks met and missed, and any suspension events claimed. Where the Manager's system produces this report, the Manager's report shall be used.

The monthly report is the input to the service credit calculation and the quarterly review; where the manager's system produces it, the vendor's obligation is to review and dispute within a set period rather than to compile it.

8. Service credits. Where the Vendor misses a clock in a month, the Manager may deduct from the next invoice a Service Credit calculated in accordance with Appendix F, subject to the monthly cap in Appendix F. Service Credits are a price adjustment reflecting the reduced value of the service and are without prejudice to the Manager's other rights, including recovery of the reasonable cost of engaging an alternative contractor where the Vendor fails to attend a P1 Work Order within [twice] the Attend Time.

Two things here. Credits are framed as a price adjustment, not a penalty, which matters in jurisdictions that do not enforce penalty clauses. And the cover-cost limb is what makes the emergency replacement vendor's premium recoverable, which is the number that actually hurts (in the hub's worked example, the premium was $4,900 on a $3,500 job).

9. Escalation. Any missed P1 clock shall be escalated by the Vendor to its [named account manager] and by the Manager to the [regional manager] on the day it occurs. Three missed clocks of any Priority in a month, or one missed P1 Attend Time, shall trigger a review meeting within [10 Business Days] at which the Vendor shall present a remediation plan.

Puts names on the escalation and links the SLA to the review cadence, so that a bad month produces a meeting rather than a mood.

10. Termination trigger. The Manager may terminate this Agreement for cause on [30] days' notice where the Vendor (a) misses the P1 Attend Time on [three] occasions in any rolling [three-month] period, or (b) fails to achieve [90]% of all clocks in any [two] consecutive months, or (c) fails to implement a remediation plan agreed under clause 9 within the time stated in it.

This is the clause that makes termination for cause a matter of record rather than argument. The thresholds are negotiable; their existence is not. How to run the exit itself is in terminating a maintenance vendor.

Service credits: how to size them, with a worked example

Service credits are the mechanism that gives the clocks weight without going to court. They work when they are large enough to be noticed on an invoice and small enough that the vendor accepts them at signing, and they should be structured so that a missed P1 costs more than a missed P3.

The usual design: a percentage of the monthly contract fee per missed clock, graded by priority and by clock, with a monthly cap. For a per-work-order vendor with no monthly fee, the credit is a percentage of the invoice for the work order concerned, with the cap per work order.

Worked example. A multifamily portfolio contracts an HVAC vendor for planned maintenance and reactive repair at a fee of $6,000 a month. The service credit schedule in Appendix F provides 5% of the monthly fee for each missed P1 attend or restore clock, 2% for each missed P2 clock, 1% for each missed P3 or P4 clock, and a cap of 20% of the monthly fee in any month.

Had the July P1 also missed its restore clock, a second 5% would apply and the month's credit would be $960, still under the cap. The credit is deducted from the August invoice, with the July report attached as the calculation.

Two cautions. Credits compensate for a poorer service; they do not compensate the property for the tenant's abatement or the emergency vendor's premium, which is why clause 8 keeps the cover-cost recovery separate. And a vendor that is regularly paying credits is a vendor to replace, not a discount to enjoy; the credits are evidence for the termination trigger, and the scorecard is where the pattern is judged.

Trade-specific variations

The three clocks are the same for every trade. What varies is the P1 definition, what "made safe" means, the stocked-parts list and the hours.

The trade table also shows why a single generic SLA template property maintenance contracts are so often copied from does not work: the elevator entrapment clock, the snow trigger depth and the fire impairment procedure are not variations on a theme, they are different documents that share a structure.

Key facts

• A vendor SLA in property management needs three clocks: acknowledge, attend and restore (RIOO's three-clock model), each with a defined start event, stop event, time and evidence.
• All three clocks start when the work order is issued to the vendor, not when the vendor reads it.
• Typical P1 (emergency) times are acknowledge within 15 to 30 minutes, attend within 2 to 4 hours and restore or make safe within 24 hours, on a 24/7 basis; typical P4 (scheduled) times are acknowledge within 1 business day, attend within 10 and restore within 20.
• "Made safe" satisfies a P1 or P2 restore clock only if the SLA defines it for the trade and requires a dated follow-up work order for the permanent repair.
• Service credits are a price adjustment, graded by priority and capped per month; in the worked example a $6,000-a-month HVAC contract with one missed P1 clock and three missed P2 clocks produced a credit of $660 (11%), against a $1,200 (20%) cap.
• Credits do not cover the tenant's abatement or an emergency vendor's premium; the SLA needs a separate cover-cost recovery clause for those.
• Clock suspensions (access denied, parts, weather, stand-down) are fair only when the vendor notifies the event at the time; an unclaimed suspension is not a suspension.
• Lift entrapment, snow clearance and fire impairment need their own clocks and cannot be handled by a generic four-priority matrix.

Measuring against the SLA without a spreadsheet

An SLA that is measured from a spreadsheet the coordinator fills in on Friday is measured from memory, and memory favours whoever is loudest at the review. The clocks have to be measured from the work order itself: the issue time is the record's creation, the acknowledge time is the vendor's acceptance, the attend time is the check-in, the restore time is the completion, and the priority is a field set at issue. When those events are recorded as the work order moves, the SLA report is a filter on the work orders, not a document.

That is also what makes the service credit calculation undisputed. The vendor sees the same record the manager sees, the suspension events are notes on the work order with times, and the monthly report is generated rather than compiled. The disputes that remain are about classification (was it really a P1) and about suspensions (was access really denied), and both are settled by the notes made at the time.

In RIOO on NetSuite, work orders are created, prioritised, assigned to technicians or vendors and monitored to completion in service request and task management, where tenants and residents can submit requests and track their real-time status, and the module's dashboards and performance analytics give the view of maintenance performance across properties. Vendor contracts, communication and documentation are centralised in the same module, and the vendor's invoices come through vendor management and accounts payable against the purchase order, which is where a service credit is applied as a deduction. The SLA schedule itself sits with the contract on the vendor record.

Put the clocks to work.  The ten clauses above are drafted to paste into a schedule; take them to counsel with the priority matrix and Appendices C to F filled in for your trades. To see how work orders, vendor records and invoices sit in one system, book a walkthrough of RIOO's service request and task management. 

Frequently asked questions

Q1. What should a vendor SLA for property management include?
A vendor SLA property management contract can enforce includes scope and hours of service; the priority levels (P1 to P4) with a definition and examples for each; the three clocks (acknowledge, attend, restore) with times per priority and a defined start event; the evidence the vendor must record; what "made safe" means and how the permanent repair is scheduled; the exclusions and clock suspensions with a notification rule; monthly reporting; service credits with a cap; escalation; and the termination trigger.

Q2. What is a reasonable SLA response time for property maintenance?
For a P1 emergency (no heat, no water, active leak, gas, entrapment, building unsecured): acknowledge within 15 to 30 minutes, attend within 2 to 4 hours, restore or make safe within 24 hours, around the clock. For P2 urgent: acknowledge within 1 hour, attend within 8 business hours, restore within 3 business days. For P3 routine: 1, 5 and 10 business days. For P4 scheduled: 1 business day to acknowledge, then as scheduled within 10, restored within 20. Statutory repair timescales override these where they are shorter.

Q3. When does the SLA clock start?
When the work order is issued to the vendor through the agreed channel (the portal, or a phone call for P1), not when the vendor reads or accepts it. The SLA should say so explicitly, name the channel, and make the manager's system record conclusive where the two records differ.

Q4. How do service credits work in a maintenance SLA?
Each missed clock earns a credit expressed as a percentage of the monthly fee (or of the work order invoice for per-job vendors), graded by priority (for example 5% for a missed P1 clock, 2% for P2, 1% for P3 and P4) and capped per month (commonly 15% to 25%). The credit is deducted from the next invoice with the monthly SLA report as the calculation. Credits are a price adjustment; the cost of an emergency replacement vendor is recovered under a separate clause.

Q5. Should the SLA be the same for every trade?
The structure should be the same (three clocks, four priorities, evidence, credits, escalation), but the P1 definition, what "made safe" means, the stocked-parts list and the hours differ by trade. Lift entrapment needs its own, much shorter attend clock; snow clearance is written around trigger depths; fire and life safety restore times may be set by code or the insurer.

Related reading

• Vendor management in property management: the lifecycle guide
• Vendor scorecard for property management: how to measure contractor performance
• Vendor performance review cadence: weekly, monthly, quarterly, annual
• Terminating a maintenance vendor: the off-boarding playbook
• Vendor compliance in property management: why the COI on file is not enough
• NetSuite for facilities management: work orders, PM and vendors