7 Metrics Every Services Firm Partner Should Watch Weekly
The 7 operational metrics that predict services firm health before it shows up in financials. Reviewed weekly, they catch 80% of trouble at 20% of the size.
- Monthly dashboards are too slow for services firms. Weekly is the cadence that catches drift.
- The 7 core metrics: utilization, project health, time capture rate, burn vs plan, days-to-invoice, WIP by client, pipeline-weighted capacity.
- Each metric has a threshold that triggers action — not a number that just gets reported.
- Partner-level review, not just ops-team review. Decisions need to cascade.
- The metrics system is only as good as the data pipeline underneath it.
Services firms are uniquely bad at operational dashboards.
Partner conversations are dominated by anecdote: “I think Project X is behind schedule.” “Someone mentioned utilization seemed off.” “I heard from Jane that Client Y might be unhappy.” By the time anything measurable shows up — on the monthly P&L, in the quarterly pipeline review — the drift is already weeks old.
The fix isn't more reporting. It's the right reporting at the right cadence.
This is our view of the seven operational metrics that separate healthy services firms from struggling ones, the thresholds that actually matter, and why each one belongs on a weekly partner review — not a monthly one.
Why weekly, not monthly
Monthly reporting is built for accounting, not operations.
Accounting reports what already happened. Operations needs to see what's happening right now — before it happens fully. At services firms, the gap between “something is drifting” and “something has drifted” is usually 2–4 weeks. Monthly dashboards are always behind that gap. Weekly dashboards are just in front of it.
The 15-minute weekly review is the single highest-leverage operational meeting a services firm partner can run. Seven numbers, ten minutes of discussion, clear decisions about what to intervene on.
1. Firm-wide utilization (with distribution)
The leading indicator of firm health. Aggregate number plus the distribution across senior, mid, and junior staff.
Threshold: below 65% or above 85% at the aggregate, or a bimodal distribution where half the team is below 65% and half above 85%.
Why weekly: burnout and revenue miss are both predictable from trajectory, not snapshot. See our full piece on utilization and how to calculate true utilization for why this one matters more than most.
2. Project health score (portfolio view)
Every active project, colored red/yellow/green, with a one-sentence reason.
Threshold: any project that moved color in the last week. Any project that's been yellow for 3+ weeks.
Why weekly: scope creep and schedule drift compound fast. A yellow project at week 3 is usually a red project at week 6 if nothing changes. See our scope creep playbook.
3. Time capture rate
What percentage of the firm logged time within 24 hours of the work happening?
Threshold: below 90% is a data quality problem. Below 80% means every other metric on this list is unreliable.
Why weekly: this is the foundation metric. If it's off, nothing else on the dashboard is trustworthy.
4. Actuals vs. planned burn (per project)
For every active project: hours burned this week vs. hours planned, with variance percentage.
Threshold: any project more than 15% over plan for the week, or any project three weeks running 5–10% over.
Why weekly: this is how you catch scope creep before the client notices — or before it blows the project budget.
5. Days-to-invoice (rolling)
Average days between period close and invoice issued, trailing four weeks.
Threshold: anything above 10 days. Target: 7.
Why weekly: this is a working capital metric and a client-experience metric at the same time. Long cycles mean locked cash and disputes. See our piece on compressing the billing cycle.
6. WIP by client (unbilled work in progress)
For each client: hours worked but not yet billed, in dollars.
Threshold: any single client with more than 15–20% of the firm's total WIP, or any WIP growing more than 20% week-over-week.
Why weekly: concentration risk shows up here before it shows up in revenue. And growing WIP on a single client often signals unbilled scope — creep that finance hasn't caught up to yet.
7. Pipeline-weighted capacity
Forward-looking: capacity available in the next eight weeks, weighted against pipeline commitments and likelihood to close.
Threshold: any week forecasted below 70% capacity utilization or above 95%.
Why weekly: this is how you avoid the feast-or-famine cycle that kills services firms. If you see a utilization trough coming in six weeks, you have time to act. If you see it in month-end reporting, you don't.
Each metric has a threshold, not just a number
The single biggest mistake firms make with operational dashboards is reporting numbers without action thresholds.
A number without a threshold becomes wallpaper. Utilization was 74% this week, 76% last week, 78% the week before. The number gets reported, nobody does anything, and a quarter later someone notices the firm is at 84% and burning out.
A threshold creates action. “Utilization above 85% triggers a capacity review.” Now the dashboard does work. It doesn't just report — it prompts.
The seven metrics above each have thresholds built in. The review conversation is always the same shape: are any metrics in threshold territory? If yes, what's the decision?
Partner-level review, not just ops-team review
This dashboard belongs on a partner weekly, not just at an ops-team standup.
Services firm partners often delegate operational review to a COO, a head of ops, or a finance lead. That's fine for execution, but it's the wrong level for the decisions that come out of the dashboard.
Red projects, utilization interventions, client concentration, days-to-invoice issues — all of these require partner-level decisions. The weekly review is the forum where those decisions actually get made.
Fifteen minutes. Seven numbers. Partners in the room.
The system underneath the dashboard
A weekly dashboard is only as good as the data pipeline underneath it.
If time capture is late, utilization is wrong. If project plans aren't current, burn-vs-plan is noise. If the billing system is disconnected from time, days-to-invoice is guesswork.
The firms that actually run the weekly partner review have three things in common:
- Real-time time capture with >90% same-day entry.
- One integrated operational system — time, projects, utilization, billing — instead of four or five disconnected tools.
- Dashboards that auto-refresh, not reports that someone has to compile.
The dashboard is the output. The data pipeline is the foundation. Firms coming off tool sprawl often see this clearly in our PSA migration story from spreadsheet chaos to one operational view.
Without the foundation, the weekly review becomes performative — numbers get reviewed, nothing happens because nobody trusts the data. With the foundation, the weekly review becomes the forcing function for real decisions — the place where drift gets caught and intervention happens.
Octayne's System Intelligence gives services firms a live, decision-ready partner dashboard — all seven metrics auto-refreshed from integrated operational data. Book a demo to see what a weekly partner review looks like with real data underneath it.
See Octayne running on your data
Real-time operational visibility built for professional services firms — time, utilization, projects, billing, all in one place.
Book a demo