You open your email on Monday and the site manager has forwarded three spreadsheets, a PDF estimate, and a screenshot of a WhatsApp thread. By Tuesday the admin team is reconciling two different versions of the same job, and by Friday someone’s staying late to chase missing permits.
This is ops debt in action. It accumulates quietly until it becomes a drag on delivery, margins, and scale. The goal of the ops-debt audit is simple: spend 90 minutes with the right people and a single worksheet to expose where your ops are bleeding, and leave with a prioritized list of fixes you can prototype in weeks, not quarters.
what the 90-minute audit actually does
This is not a maturity assessment. It’s an extraction exercise. The worksheet forces you to answer three questions for each repeatable process: what is the process, where are the handoffs, and how much time or money does the friction cost? The output is a ranked list of opportunities that are visible, measurable, and actionable.
What you get in 90 minutes:
- a process map for 5–8 high-frequency workflows
- a quantified estimate of rework or duplicative work for each workflow
- a prioritized short list of fixes that can be prototyped quickly
Why 90 minutes. Short, focused audits avoid analysis paralysis. The aim is exposure not perfection. You want to find the biggest leaks fast, then narrow them with a prototype and real data.
the 90-minute agenda and worksheet
Bring two people per process: the person who starts it and the person who finishes it. Timebox the session and use a shared spreadsheet or the printable worksheet.
Agenda (90 minutes):
- 0–10 minutes: scope and rules. Pick 5–8 high-frequency workflows. Define the start and finish for each.
- 10–40 minutes: map processes. For each workflow, list steps, tools, and handoffs. Mark where information is duplicated or re-entered.
- 40–70 minutes: quantify friction. Estimate how much time is lost per instance and frequency per week or month. Convert time to dollars using loaded labor rate if you want a financial view.
- 70–90 minutes: prioritize. Score opportunities by impact versus effort and pick top 2–3 to prototype.
Worksheet fields (one line per process):
- process name
- start trigger and finish condition
- tools involved
- number of handoffs
- re-entry / duplication points (yes/no)
- time lost per instance
- instances per month
- monthly labor cost of friction (time lost x instances x loaded rate)
- quick fix idea
- prototype complexity (low / medium / high)
This is intentionally coarse. A +/-20% estimate is far more useful than no estimate.
a concrete example
A mid-size field services company ran this audit during a 90-minute call with the operations manager and two supervisors. They mapped five processes: job intake, scheduling, materials ordering, site check-in, and invoicing.
Findings:
- scheduling had three separate spreadsheets and a WhatsApp group. Supervisors were double-entering availability into two sheets; time lost was estimated at 12 minutes per job. At 400 jobs per month that’s 4,800 minutes or 80 hours per month.
- materials ordering relied on a paper list from the foreman plus a purchase-order PDF emailed to suppliers. Orders were re-entered by the admin team and averaged 20 minutes of admin time per order. At 150 orders per month that’s 50 hours per month.
Total identified admin rework: 130 hours per month. At a loaded labor rate of $40/hour that’s roughly $5,200 per month. The team prioritized a scheduling prototype that would remove the duplicate entry point and reduce scheduling time by 75 percent.
Result: after an 8-week prototype the team eliminated two spreadsheets and removed the WhatsApp scheduling thread. The savings translated to 60 hours per month freed, plus fewer missed jobs and better data for planning.
This mirrors the kind of rapid impact seen in larger projects. For example, a construction client moved from $5M to $15M revenue and 15 to 40 people after an 8-week mission-control build replaced 20+ spreadsheets with one system. The audit’s role was the same: find the biggest leaks, then prototype a single source of truth.
how to turn the audit into a prototype plan
Once the top opportunities are ranked, the job is to design a minimal prototype that proves the fix. The prototype should do three things: replace the duplicative touchpoints, enforce the critical handoff, and capture one key metric.
Prototype checklist:
- single entry point for the information that is currently duplicated
- a required field or status change that enforces the handoff
- capture of one KPI that shows improvement (for example time to schedule, orders processed per admin hour, or invoice days outstanding)
Keep scope tight. If the prototype requires integration work or changes across multiple teams, break it into smaller slices. The goal is to validate assumptions in weeks, not build a full-system replacement in months.
next steps for the ops leader
Run the 90-minute audit with 2–4 processes this week. Use the worksheet to force numbers, even if they are rough. Prioritize fixes that are low complexity and high impact. Prototype those fixes fast and measure the KPI for 2–4 weeks.
If the prototype proves the hypothesis, turn the validated pattern into a broader mission-control solution. A prototype-first approach reduces buy-in friction and exposes the real cost of ops debt before any big build budget is committed.
If you want a shortcut, Orqestrix runs a prototype-first Discovery that produces a working prototype before any contract is signed. The Discovery compresses the audit, design, and first prototype into a single engagement so you get a tangible solution and real metrics to decide next steps.