Everyone says they'll "understand your process before touching tools." Here's what that actually produces — a composite, illustrative Operations Diagnostic, built to the same structure and depth as a real Audit engagement.
Northfield Property Services is a composite, fictional example — a scheduled maintenance and repair business built to show how the diagnostic works, not a real engagement.
34 staff — 22 field technicians, 6 support/dispatch, 4 admin, 2 leadership. Books commercial maintenance and repair jobs for property managers. Grown from 12 to 34 people in under two years.
Job requests via a shared Gmail inbox and phone. Scheduling in a shared Google Sheet. Job notes split across paper dockets, texts, and whatever each technician remembers.
Two days on-site and on calls, shadowing dispatch and a handful of jobs end-to-end. Four gaps came up repeatedly.
New job requests arrive by email, phone, and occasionally a text to whichever technician the client already knows. Roughly 1 in 6 requests only surfaces once a client calls asking why nobody's shown up.
Technician availability and skill-matching lives entirely with the ops manager. When she's out, scheduling either stalls or double-books — happened three times in the last quarter.
Notes on what was done, quoted, or promised live across paper dockets, personal phones, and memory. A repeat job means starting from zero unless the same technician happens to be free.
Job backlog and missed deadlines surface at the monthly review — by then it's a pattern, not an early signal leadership could've acted on.
That's the target Northfield's leadership set. It rules out some fixes before they're even scoped — anything that adds headcount, or that only the ops manager can run, doesn't qualify as a real solution.
The honest answer is usually "mostly yes, with one exception" — not "replace everything" and not "change nothing."
Gmail can be routed and templated into a single structured intake with light configuration. A shared drive, set up properly, is enough to hold job history and a quoting reference — no new platform needed here.
A shared sheet was fine at 12 staff. At 34, with three double-bookings this quarter, it's a structural risk, not a habit to fix. This is the one place the diagnostic recommends a new tool — a lightweight field-service scheduling platform, configured, not built from scratch.
// This is the caveat in practice: the default is configure what you have. A new platform only gets proposed when the assessment shows the current one genuinely can't do the job — and here, it can't.
Look closely at Gaps 02 and 03 above and they're not really scheduling or logging problems — they're knowledge management problems wearing a process costume.
A pricing doc last updated 14 months ago, a running text thread between two senior technicians, and whatever the ops manager remembers from the last exception she approved. New technicians quote differently depending on who trained them. The fix isn't a smarter scheduling tool — it's capturing that logic once, somewhere the whole team actually uses.
This is what actually gets handed over at the end of an Audit. Four fixes, ranked, each tagged by impact and effort.
Route all requests through one structured form/inbox rule, no new platform required.
High impact · Low effortCapture what's currently tribal knowledge into one living reference the whole team can use — the knowledge-management fix behind the process fix.
High impact · Low effortThe one recommended platform change, configured — not custom-built — once the current tool is confirmed as the actual constraint.
Medium impact · Medium effortA simple automated rollup of backlog and jobs at risk of running late, built on top of the tools already in place — the automation layer, applied last.
Medium impact · Low effortA current-state map, the gaps behind it, and a prioritised fix list — process, knowledge, and tooling assessed together, in one bounded engagement.
Takes one item off this list — say, fix 01 or 02 — and builds it end to end, tested with the real team before it's called done.
Embedded, ongoing leadership that works through fixes like these as priorities shift — not a one-off report that sits in a drive.