Treadstone Associates
Case File · Trade Service Operations

A restoration firm cuts its first-response time

Anonymised, illustrative composite. An Alberta water- and fire-damage restoration firm found that the clock it was actually being judged on — call to first mitigation work — had a mandatory safety step buried inside it, and the fix was to move that step earlier without skipping it.

Treadstone Associates · Updated 2026

At a glance

  • • Alberta water and fire damage restoration firm, one dispatch crew on rotating call.
  • • Elapsed time tracked was call-to-mitigation-start, not call-to-arrival — the two are not the same clock.
  • • Alberta’s OHS Code requires a work-site hazard assessment before work begins, and repeated whenever the work process changes.
  • • The assessment used to start from a blank page on arrival; it now starts from a draft built during the drive.
  • • Call-to-mitigation-start fell from an average 56 minutes to 40 — the exact 16 minutes the on-site assessment used to add.

The situation

A restoration firm operating out of a mid-size Alberta city ran one rotating on-call crew for water, fire and mould emergencies — the calls insurers and property managers dial first because speed decides how much damage spreads before mitigation starts. The firm had always measured itself on how fast a truck showed up. What it had not measured, until a slow month prompted a closer look at its own dispatch logs, was how much time passed after the truck showed up before anyone actually started work.

The problem

Alberta’s OHS Code does not let a crew start mitigation work cold. Under Part 2 of the Code, an employer “must assess a work site and identify existing and potential hazards before work begins,” and must repeat that assessment “when a new work process is introduced” or a work process changes — which a fresh water-damage call, with its own electrical exposure, structural risk and contamination class, effectively is every single time. The technician had always done this on arrival, walking the site cold and writing it up from scratch before touching anything.

That was never wasted time — it was the law working as intended. But it was also, structurally, dead time sitting on the front of every job, because nothing about the assessment actually required the technician to start it only after arriving.

The numbers

The firm pulled six weeks of dispatch logs. Average drive time from call acceptance to arrival on site was 34 minutes, and that leg was not going to change — it is bounded by geography, not process. What varied was what happened next: technicians spent an average of 22 minutes on arrival walking the site, identifying hazards (standing water depth, panel exposure, structural sag, containment needs for suspected mould) and writing up the assessment before mitigation work could begin.

Call-to-mitigation-start, added together: 34 minutes of drive plus 22 minutes of on-site assessment equals 56 minutes, on average, from the phone ringing to the first pump switching on.

The rule that decided it

The firm built a structured intake script for its dispatcher: damage type, source, affected rooms, any visible electrical exposure, and any prior mitigation attempted by the occupant. That intake auto-drafts a preliminary hazard assessment specific to the damage type while the technician is still driving, instead of after they park.

It does not replace the on-site step, because Alberta’s OHS Code requires the employer to “involve affected workers in the hazard assessment” under s.8(1) — a draft written by a dispatcher from a phone call is not a completed assessment. The technician still walks the site on arrival and confirms, corrects or adds to the draft against what is actually there before starting work. What changed is that confirming a draft takes minutes; building one from a blank page took considerably longer.

The outcome

On-site assessment time fell from 22 minutes to 6 — the time it now takes a technician to walk the site against a draft already in hand and correct anything the intake call did not anticipate. Drive time did not change, because nothing about this touches the drive. Call-to-mitigation-start fell from 56 minutes to 40: 34 minutes of drive plus 6 minutes of confirmation, exactly the 16 minutes removed from the assessment step and nowhere else.

For the adjacent question of which jobs can be priced without a truck roll at all, see how one service company drew that line from customer photos. For the sector-wide pattern this sits inside, see how AI is showing up in restoration contracting.

What it would have cost otherwise

Had the firm left the assessment where it was, on-site-only, it would have kept losing the same 16 minutes on every call indefinitely — not a one-time cost, a permanent tax on the metric the firm is actually judged on. On a firm fielding several emergency calls a week, that adds up to hours of standing water and active fire damage spreading each month that a faster start would have contained. None of that shows up as a missed deadline; it shows up as a slightly worse damage report on jobs nobody flagged as unusual.

The tell

The signal is a mandatory compliance step sitting entirely inside the clock a customer or insurer actually cares about, with nothing about the rule itself requiring it to sit there. Alberta’s hazard assessment has to happen “before work begins” and has to involve the worker doing the work — it does not say the worker has to start writing it from nothing after they park the truck. Look for the same pattern anywhere a statutory or safety step is bundled into a response clock by habit rather than by requirement, and ask whether drafting it earlier, then confirming it on site, still satisfies the rule.

Takeaways

  • • Measure the clock your customer actually cares about, not the clock that is easiest to log — call-to-arrival and call-to-work-start are different numbers.
  • • Alberta OHS Code s.7 requires a hazard assessment before work begins and s.8(1) requires the worker be involved — drafting it earlier does not violate either requirement as long as the on-site confirmation step stays intact.
  • • A compliance step is often only slow because of when it starts, not because of what it requires.
  • • The same audit works on any statutory step embedded in a response clock: insurance verification, intake forms, site notifications — check what the rule actually requires before assuming the timing is fixed.

See where AI pays off first in your business.

A 30-minute call is enough to tell you whether AI pays for itself here.