What Should a Reactive Property Maintenance SLA Cover?

A reactive property maintenance service-level agreement (SLA) should do more than state a single response time. It should explain how faults are reported, how priority is assessed, what “response” means, who controls access and authorisation, how progress is communicated, and what evidence closes a job.

The useful SLA is the one that fits the building, its occupants and the operational impact of a fault. The points below are a planning checklist, not a statement of Invincible’s contractual response times.

Define the service boundary

List the properties, assets and work types included. Confirm exclusions, work that needs specialist assessment, and risks that require an emergency or statutory response outside the general maintenance process.

Distinguish diagnosis, temporary containment, a permanent repair and follow-on works. Attendance does not always mean the issue can be fully resolved on the first visit.

Set priorities by risk and disruption

A priority framework should reflect consequence, not simply who reported a fault first. It may distinguish:

• An immediate threat to people, property or essential operations

• A serious fault causing disruption or escalating damage

• A routine defect that can be safely scheduled

• A planned improvement outside the reactive queue

Use examples relevant to the site or portfolio. Record who may change a priority and how that decision is communicated.

Separate acknowledgement, attendance and completion

“Response time” is ambiguous unless each stage is defined. An SLA can record when a report is acknowledged, reviewed and prioritised; when a suitable person attends; when the immediate risk is contained; and when the permanent repair is completed. A quick acknowledgement should not be mistaken for a completed repair.

Agree access and authorisation

Reactive work may depend on access hours, permits, keys, isolation requirements, spending limits or working around occupants. Name the people who can grant access, authorise costs and approve work outside the initial instruction.

For multi-site portfolios, keep site contacts and access constraints current. Sensitive access details should be shared through an appropriate controlled process, not in a general article or public form.

Specify updates and completion evidence

Agree when progress updates are needed and what the completion record should include. Depending on the work, useful evidence may be:

• Times reported, acknowledged, attended and completed

• Diagnosis, action taken and any temporary measures

• Before-and-after photographs where permitted

• Materials used and follow-on work required

• Remaining safety or access constraints

• Client sign-off or the reason a job remains open

Reporting should make the next decision clear, especially when a permanent repair is still outstanding.

Review outcomes, not just attendance

Useful measures may include first-visit completion, repeat defects, work awaiting approval, temporary repairs still open and recurring faults by property or asset. Reviewing patterns can show which tasks belong in a planned-maintenance programme.

Before agreeing terms, test the proposed priorities, access process and communication steps against realistic site scenarios. The final SLA should reflect the actual service scope and contract.

For help scoping works on an occupied site, explore Invincible’s reactive property maintenance service or discuss your requirements.