The Weekly Metrics Every Field Service Business Should Actually Track.

Are we operating better, worse, or differently than expected? That is the job of a weekly metrics packet.

Most field service businesses do not need a massive BI program to improve their weekly operating rhythm. They need a short, trusted view of demand, production, margin, capacity, quality, and cash. The packet should make the meeting shorter, not longer.

Revenue is not one number in an operating business. Booked work, completed work, billed work, and collected cash all tell different stories. When those stages get mixed together, leaders lose the ability to see where pressure is building.

A good weekly view shows each stage and the movement between them. If booked work is strong but completed work is weak, the issue may be capacity. If completed work is strong but billed work lags, the issue may be administration. If billed work is strong but collections lag, the issue may be customer terms, disputes, or follow-up cadence.

Company-level gross margin is useful, but it is too broad to manage operations. The weekly packet should show margin at the level where decisions are made: job, route, crew, service line, customer class, branch, or territory.

The right unit depends on the business. The test is simple: can someone responsible for the work actually influence the result? If the answer is no, the metric may be useful for finance but weak for operations.

Backlog without capacity is just a pile of promises. Capacity without backlog is just an availability report. The useful view puts them together.

How much work is waiting? How much production capacity is available next week? Where are the constraints: technicians, trucks, materials, weather, subcontractors, permitting, or admin time? This is where reporting starts to support scheduling instead of simply describing the past.

Callbacks, rework, warranty visits, missed appointments, and unresolved tickets are not only customer experience metrics. They are margin metrics. Every return trip consumes capacity that could have produced new revenue.

A weekly packet should show quality issues early enough for managers to act. The goal is not blame. The goal is pattern recognition. Which service line is creating rework? Which crew needs support? Which customer type creates avoidable friction? Which part or process keeps causing repeat visits?

A business can be busy and still feel cash pressure. The weekly packet should include a clean view of open receivables, aging, disputed invoices, unbilled completed work, and large upcoming cash needs.

This does not need to replace accounting reports. It needs to translate accounting status into operating action: what needs to be billed, collected, clarified, escalated, or reserved for.

The packet is not the work. The action list is the work. Each weekly review should end with a short list of decisions, owners, and follow-up dates.

If the same metric appears every week with no decision attached, either the metric is not actionable or the meeting is not using it correctly. Good reporting should focus attention and move work forward.

A useful recurring assignment is to gather the approved exports, check their dates and totals, and prepare a short list of changes that need an owner. Agree on the schedule, where the packet goes, and what to do when a source is missing.

The operations owner confirms the explanation and decides the action. Compare the time saved with the time spent checking and correcting the packet. Keep an accessible manual process for a week when the automation cannot run.