Skip to content

Instrument 04 · the self-audit

Score your own
leak chain.

Seven questions, one per leak, from the call that rings out to the week the whole company routes through your phone. Answer honestly and the scorecard tells you which leak to attack first, and why. No email, no sales call, and it prints on one page.

About 15 minutes

7 leaks · scored 0 to 3

Your answers stay in your browser

Printable scorecard

The 7-leak self-audit

Self-audit · your answers stay in your browser

01The missed call · Fast fixWhen a call rings out during a job, what happens to it?
02The slow estimate · Medium fixA crew measures a job Tuesday morning. When does the customer see the bid?
03The dead follow-up · Fast fixAn estimate went out ten days ago and the customer went quiet. Who chases it?
04The paper handoff · Deep rebuildHow does a finished job travel from the crew to the office?
05The Sunday re-entry · Medium fixHow do the week's job numbers get into your accounting software?
06The aging receivable · Fast fixAn invoice hits day 31 unpaid. What happens that week?
07The owner as the integration · Deep rebuildIf you stopped answering your phone for a week, how much of the operation would stall?

This link is scored but never ranked for direct attack: it drains as the others close.

Your chain

0 of 7 answered

01020304050607INK DENSITY = SEVERITY0 SEALED · 3 OPEN LEAK

Answer all seven and the chain inks itself: each link colored by your answer, the fix order ranked by what bleeds most among what closes fastest.

How the fix order is ranked

severity = your answer, 0 (sealed) to 3 (open leak)
fix difficulty = our field judgment: 1 fast fix, 2 medium, 3 deep rebuild
priority = severity x (4 - fix difficulty)

In plain terms: attack what bleeds most among what closes fastest. Ties go to the leak earlier in the chain, because upstream leaks feed downstream ones. Leak 07 is scored but never ranked: the owner-as-integration problem drains as the other six close. This is advice from how we sequence real projects, not a diagnosis of yours.

Prints one page · nothing is sent anywhere

Why we give the audit away.

Because the audit is the easy part. Knowing the estimate goes out slow is not the same as rebuilding the handoff that slows it, and a scorecard cannot migrate your data or train your dispatcher. The blueprint maps all seven in week one. This scorecard is yours either way.

Book an operations review

Put a dollar figure on leak 01.

If the missed call came back leaking, the two-minute calculator prices it from your real call volume, with every assumption shown and sourced. The other six leaks do not fit three input fields, which is exactly why the scorecard asks about habits instead of numbers.

Run the missed-call calculator

Scored high on the whole chain? See the system that closes it, or read the adoption playbook first: how to make any new system survive its first month, free like this one.