The Operational Intelligence Review

Insight

Without a fixed cadence for reviewing the work-in-progress book, stalled files and ageing claims only surface once an insurer or customer escalates — by which point the cash and goodwill cost is already locked in.

Realistic first step

Put a recurring, calendared monthly WIP review on the owner's or ops manager's diary — claims aged past 30/60/90 days, plus crew utilisation — with a written action list produced every time, not just a conversation.

Insight

A gap this size between assessment and mitigation starting almost always means the file is waiting on something outside the crew's control — insurer sign-off, scope approval, or materials — but without stage-by-stage tracking it just reads as "running late."

Realistic first step

Timestamp assessment-complete and works-start on every job, even in a shared spreadsheet, so stalled files surface automatically instead of only being noticed once the customer or insurer chases.

Insight

Running above 100% capacity as the normal state — not just during a storm event — means every emergency callout gets absorbed by pulling a crew off an already-scheduled job, quietly delaying several other files at once.

Realistic first step

Build a simple weekly capacity view — crew-hours available vs. allocated — reviewed before the week locks in, with an explicit plan for how after-hours or CAT callouts get covered, rather than ad hoc reshuffling.

Insight

Jobs that fall through the after-hours-to-day-team handoff without a named owner tend to be the ones that stall longest — no one is explicitly accountable for pushing them to the next stage.

Realistic first step

Make "named job manager assigned" a mandatory field the moment any job is logged, including after-hours emergency calls, and give someone standing responsibility for a daily unassigned-jobs check.

Insight

A gap this size on an insurer-approved job usually traces back to scope creep that was never captured as a variation — extra work done to keep the customer happy but never resubmitted for approval or billed.

Realistic first step

Require any work beyond the approved scope to be logged and submitted as a variation before it starts — or within 24 hours for emergency work — and reconcile actual cost against approved scope at job close, not just at invoicing.

Insight

A follow-up with no reply and no scheduled next contact is a file that's gone quiet — and in insurance work, silence from the business is one of the biggest drivers of customer complaints and cancelled jobs.

Realistic first step

Make every outbound insurer or adjuster follow-up automatically create a next-check-in date (e.g. 3 business days) logged against the job, so silence gets flagged for action instead of being discovered when the customer complains.

Insight

The KPIs left untracked are rarely the unimportant ones — they're usually the ones hardest to pull from disconnected systems, which means the business is managing blind on exactly the numbers most likely to catch a margin or capacity problem early.

Realistic first step

Pick three or four currently-missing leading indicators — claim ageing buckets, crew utilisation, average assessment-to-works time — and put them on one manual, one-page monthly report before investing in a system to automate it.

Insight

When these three systems don't talk to each other, the same job data gets typed in at least twice — every re-key is a chance for error, and the delay between systems is exactly where margin visibility breaks down.

Realistic first step

Map exactly where data is re-keyed between the three systems today and fix the highest-friction handoff first — usually approved scope into invoicing — with even a manual export/import routine before considering a full platform change.

Insight

When invoicing depends on someone remembering to compile a report, completed jobs sit in limbo between "finished on site" and "billed" — unpaid working capital with no operational reason to be stuck there.

Realistic first step

Start with one automation: a job status change to "complete" (or the final sign-off/photo upload) automatically generating a draft invoice for review, rather than trying to automate the whole workflow at once.

Insight

In restoration, volume rarely climbs gradually — one storm event can double the job book overnight — so if scoping and admin are already maxed out under normal conditions, there's no slack left to absorb a surge without response times and insurer trust suffering first.

Realistic first step

Identify the one or two roles that would break first in a volume surge — usually scoping/estimating and admin — and pre-arrange a scaling plan for those specifically before storm season starts, not during it.