Maintenance Contractors

Built for mixed
reactive and planned.

Maintenance contracting runs on two parallel tracks: reactive jobs that arrive unpredictably and planned maintenance that must happen on schedule. Managing both simultaneously, with the same team, is the defining operational challenge.

Jerrold handles both in a single view, balancing reactive urgency against PPM commitment, SLA tiers against utilisation, and first-time fix against return visit cost.

J
Jerrold · 09:12

“New P2 reactive at Northgate: 4-hour SLA, logged 40 minutes ago. Marcus is 8 minutes away and not booked until 1pm. I recommend dispatching him now. His 11am PPM moves to Andy, who has a gap with no SLA impact. Utilisation holds at 84%. Confirm?”

18
Engineers
84%
Utilisation
0
SLA risk
91%
FTF rate
The three planning problems

What makes maintenance contracting hard to schedule.

Planning reactive and planned simultaneously

The planning challenge in maintenance contracting is not reactive jobs or planned jobs in isolation. It is both at once. Engineers shift between reactive dispatch and PPM visits in the same day. Most schedulers handle one or the other. Jerrold handles both simultaneously.

First-time fix rate

A failed first-time fix costs roughly 2.5x the original job: return travel, engineer time, customer goodwill. Jerrold pre-loads engineers with site history, asset service records and parts needed before they arrive, giving them the information that drives first-time fix.

SLA management across contract tiers

Different clients carry different SLA obligations: 4-hour response, same-day, next-day. Jerrold knows every contract's SLA structure and dispatches reactive jobs accordingly: not by availability, but by obligation.

What Jerrold does for contractors

Six capabilities that matter most.

1

Reactive and PPM in one scheduler

Jerrold balances reactive urgency against PPM commitment continuously. When a reactive job arrives, he identifies the lowest-impact PPM to move and proposes the switch, with SLA preserved on both.

2

SLA-tier dispatch

Every contract's SLA obligations are encoded. A P1 reactive is dispatched differently from a P3. Jerrold knows the difference and dispatches accordingly, every time.

3

First-time fix intelligence

Jerrold pre-loads site history, asset service records, known issues and parts needed into the engineer's pre-arrival brief. The information that drives first-time fix, before the engineer knocks.

4

PPM frequency compliance

Planned maintenance visit frequencies monitored per contract and site. Jerrold flags gaps before they breach contractual obligations, not after the client notices.

5

Utilisation across both job types

Reactive jobs create unplanned gaps and spikes. Jerrold maintains a live utilisation view across all engineers across all job types, flagging underload and overload simultaneously.

6

Contract margin monitoring

Reactive-heavy contracts erode margin faster than planned ones. Jerrold monitors actual vs estimated per contract and flags the ones drifting the wrong way, with the cause and a modelled fix.

90 sec
Reactive job scheduled
Jerrold recommendation to confirm
91%
First-time fix rate
After Jerrold pre-arrival briefs
84%
Average utilisation
Reactive + PPM combined
Zero
Missed PPM frequencies
Typical result after 90 days

See Jerrold manage reactive and planned simultaneously.

30-minute demo. We demonstrate a reactive P2 arriving mid-morning alongside an active PPM schedule. Jerrold handles both in 90 seconds.