HAWKEYE SYSTEMS
Field Operations KPIs: What to Track and How to Measure It
Field operations KPIs for construction and utility teams: which to track across schedule, labor, safety, documentation and billing, with formulas and target-setting tips.
Plan a walkthroughThe field operations KPIs worth tracking are the ones that follow a job from assignment to invoice: schedule adherence, labor utilization, safety incident rate, rework, completion-to-invoice time and invoice correction rate. Pick one or two per stage, define each in writing, and capture the underlying data in the field as the work happens. A KPI is only as good as the record behind it, which is why the best field KPI programs start with how crews document work, not with the dashboard.
This guide is for construction managers, project supervisors, safety officers and billing specialists. It shows what each KPI measures, how to calculate it, what data it needs, and where the numbers mislead.
Hefieldops
Connect Field Records to Better KPIs
Hefieldops connects field activity with office management, helping teams document site work for efficient review and billing.
TL;DR
- Choose KPIs by stage of the job: plan and schedule, labor and equipment, safety and quality, documentation and billing. Four to eight KPIs beat thirty.
- Safety rate KPIs use a standard OSHA formula: cases × 200,000 ÷ hours worked. Use the same hours source for every project so rates compare.
- Billing KPIs, such as completion-to-invoice time and invoice correction rate, expose cash lag that schedule KPIs never show.
- Bad inputs ruin good KPIs. Capture time, location, photos and approvals at the moment of work, not from memory at the end of the week.
- Set targets from your own baseline first, and read every number alongside its context before drawing conclusions about a crew.
Table of Contents
- What field operations KPIs actually measure
- Choose KPIs by goal, not by popularity
- KPIs for schedule, crews and site visibility
- Safety KPIs and how to calculate them
- Quality and rework KPIs
- Documentation and billing KPIs
- How to keep field KPI data accurate
- Set targets and read the numbers without fooling yourself
- A starter KPI set by role
- Our perspective: one record from field to invoice
- See your KPIs in one place
- FAQ
- Sources
What field operations KPIs actually measure
A field operations KPI is a number that tells you whether work in the field is on plan, safe, correct and billable. It is different from a general business metric because it comes from site activity: hours on a task, a ticket signed, an incident logged, a photo attached.
Top-ranking generic lists focus on field service metrics such as first-time fix rate, travel time and customer satisfaction. Those fit a dispatch business. Construction, utilities and similar field-heavy operations need a wider set, because the money and the risk sit in different places: labor burden, equipment time, incident rates and the gap between finished work and an approved invoice.
A useful test for any KPI: can you name the decision it changes? If a number moves and nobody would act differently, drop it.
Choose KPIs by goal, not by popularity
Start from the question you are trying to answer, then pick the measure.
Goal | Question | Candidate KPIs
Stay on schedule | Is work happening when and where planned? | Schedule adherence, planned vs. actual crew hours, task completion rate
Control labor cost | Are paid hours turning into productive work? | Labor utilization, productivity by task, overtime share
Work safely | Are people getting hurt, and are we ready for the work? | TRIR, DART, near-miss reports, training compliance
Deliver quality | Is work right the first time? | Rework rate, punch-list items per area, inspection pass rate
Get paid | How fast and how cleanly does field work become revenue? | Completion-to-invoice time, invoice correction rate, unbilled completed work
Pick a small set per goal. Most teams do well with one leading measure (something you can still change, like training compliance) and one lagging measure (an outcome, like incident rate) for each goal they care about.
KPIs for schedule, crews and site visibility
These tell a construction manager or supervisor whether crews and remote sites are productive and on plan.
Schedule adherence. Share of planned tasks started and finished within the planned window. Formula: tasks completed on time ÷ tasks scheduled. It needs a task-level plan, not just a project end date.
Planned vs. actual crew hours. Compare hours budgeted per task with hours logged. The variance points to estimating problems, access delays or unplanned work. It needs time entries tied to a task or cost code, not just a daily total.
Labor utilization. Productive hours ÷ paid hours. The hard part is defining “productive” once, in writing: waiting for materials, travel between sites and rework should each have a category so the ratio means something. Our guide to labor productivity tracking in construction walks through that setup.
Equipment utilization. Hours an asset works ÷ hours it sits on the job. Idle rented equipment is a cost that rarely shows up on a crew report.
Site activity and visibility. For remote or unattended sites, track how often a site is verified and how long a reported issue takes to be seen and acted on. Mobile surveillance gives the office a live view of a site, which turns “we think the crew is on it” into a record. See how construction site surveillance supports project managers with camera roles and billing proof.
The same logic applies in other trades. If you want a worked example of defining and improving productivity in one field, this piece on technician productivity measurement shows how a trade breaks the idea down.
Safety KPIs and how to calculate them
Safety officers work with a few standard rates. They are standard because OSHA defines the formula, which lets you compare projects, years and, with care, other firms.
Total recordable incident rate (TRIR). OSHA’s formula is the number of injuries and illnesses × 200,000 ÷ employee hours worked. The 200,000 figure stands for 100 employees working 40 hours a week for 50 weeks, so the result reads as cases per 100 full-time workers per year.
Worked example: 4 recordable cases over 520,000 hours worked gives 4 × 200,000 ÷ 520,000 = 1.54.
DART rate. Days away, restricted or transferred cases use the same 200,000 base. Count only cases that resulted in days away from work or job restriction or transfer, then apply the formula. It shows severity better than TRIR alone.
Lost-time injury frequency rate (LTIFR). Common outside the US, it uses a base of 1,000,000 hours instead of 200,000. Use it only if you report to international clients, and label the base on every chart.
Leading indicators. Near-miss reports per 100,000 hours, safety observations completed, and the share of crew members with current required training. Rates like TRIR need a lot of hours before they stabilize, so a small contractor can swing wildly on a single case. OSHA notes that combining several years of counts and hours reduces that effect on a small establishment.
For context, the Bureau of Labor Statistics reported that the total recordable case rate for private industry in 2025 was 2.3 cases per 100 full-time equivalent workers. BLS publishes industry-level tables each year, so compare your rate with your own industry’s table rather than the all-industry number.
Data you need: accurate hours worked (including subcontractors if you report them), a consistent definition of what is recordable, and incident records tied to date and site. Training status is the easiest leading indicator to track if it lives in the same system as scheduling. Our guide to training compliance tracking for field crews lists what to record.
Quality and rework KPIs
Rework is work done twice, and the cost shows up as labor and materials with no matching revenue.
- Rework rate: hours spent on corrective work ÷ total hours on the scope. This only works if crews can log corrective hours separately from original work.
- Punch-list items per area or unit: counts items found at closeout. Trend it by crew, trade or phase.
- Inspection pass rate: inspections passed on first attempt ÷ inspections held.
- Daily record completeness: share of daily work records submitted with required fields filled. It is a quality KPI for the data itself, and it quietly drives everything downstream. For a field list that holds up in review, see 11 daily fields for WIP reporting.
Track quality KPIs by cause where you can: design change, material issue, workmanship, access. A rework rate without a cause tells you there is a problem but not who can fix it.
Documentation and billing KPIs
Billing specialists live downstream of everything the field does. A late or incomplete record delays revenue even when the work itself was flawless. These four KPIs show where the delay starts.
Completion-to-invoice cycle time. Days or hours from work completed to invoice issued. Report the median and a high percentile, such as the 95th, not only the average: the slowest jobs often carry the most revenue risk, and an average hides them.
Invoice correction rate. Invoices needing correction or credit ÷ invoices issued. A rising rate usually points to a workflow problem, such as missing ticket data, rather than to careless people.
Unbilled completed work. Count and dollar value of finished work with no invoice at the end of each billing cycle. Tickets missing a signature, PO number or photo are the usual cause.
Dispute or rejection rate by job type. Time-and-materials work and change orders tend to be challenged more than lump-sum progress billing. Split the rate by job type so you know where to tighten documentation. Our guide to time and materials billing steps covers the field steps that prevent rejected pay applications.
Data you need: work-completed timestamps, signed field tickets, labor and equipment hours by job, and invoice dates. When these are captured in the field and flow straight to billing, the KPIs calculate themselves. When they come from paper or texts, someone rebuilds them each week.
How to keep field KPI data accurate
Most bad KPIs come from bad inputs. Four habits fix most of it.
- Capture at the moment of work. Hours, quantities, photos and sign-offs recorded at the site beat anything reconstructed on Friday. A move off paper helps here; see how to move field crews to digital work orders.
- Standardize the definitions. Write down what counts as productive time, a recordable case, a completed task and a billable ticket. Put the definitions where crews and the office both see them.
- Verify presence and time. Location-based clock-in and photo records reduce disputes about who was where. Payroll errors compound through labor burden, so the cost of a bad hour is more than its base wage. Our piece on construction labor tracking to stop payroll errors goes deeper.
- Close the loop with the crew. If foremen never see the numbers or their effect, entries get sloppy. Show crews the KPI they influence and what changed because of it.
Set targets and read the numbers without fooling yourself
Start with your own baseline. Run a KPI for one or two billing cycles before you set a target. Industry benchmarks give context, but your mix of work, region and crews decides what is realistic.
Set a direction and a threshold. “Invoice correction rate trending down, and investigate any month above our trigger level” is more useful than a single number nobody can explain.
Watch for these traps:
- Averages hiding the tail. A good median with a long tail of slow jobs still costs cash.
- Comparing unlike jobs. Trenching and finish work have different productivity. Compare like with like.
- Real-time numbers without context. A crew showing low utilization in the morning may be waiting on a delivery. Read live views as prompts for a question, not a verdict.
- Gaming. If a KPI becomes a target with consequences, people optimize the number. Pair it with a balancing measure: schedule speed with rework, or hours logged with quality.
- Too many KPIs. Each one needs an owner and a review rhythm. If nobody reviews it weekly or monthly, remove it.
A practical rhythm: review leading indicators and live site data daily or weekly at the supervisor level, safety and quality monthly, and billing KPIs at each billing cycle close.
A starter KPI set by role
Role | Starter KPIs | Review rhythm
Construction manager | Schedule adherence, planned vs. actual hours, site verification | Weekly
Project supervisor | Labor utilization, daily record completeness, rework rate | Daily to weekly
Safety officer | TRIR, DART, near-miss reports, training compliance | Monthly, with weekly leading indicators
Billing specialist | Completion-to-invoice time, invoice correction rate, unbilled completed work | Each billing cycle
Our perspective: one record from field to invoice
We build Hawkeye Field Ops around a simple idea: KPIs are a by-product of a good record, not a separate reporting project. When crew assignments, labor and equipment hours, field tickets, daily work records and site surveillance live in one connected, audit-ready record, each handoff from assignment through billing is clear and traceable.
That is why we pair configurable workflows with workforce readiness tracking. Training status sits next to the schedule, so a safety officer sees readiness before the crew is dispatched. Daily records and tickets feed the preparation of billing and payroll documents, so billing specialists work from captured data instead of chasing it.
Our advice: choose fewer KPIs, define them once, and capture the data where the work happens. The dashboard then takes care of itself.
Client
See your KPIs in one place
If your KPIs depend on spreadsheets and rebuilt reports, Hawkeye Field Ops connects crew scheduling, job planning, labor and equipment tracking, field ticketing and daily work records, with automated preparation of billing and payroll documents. Hawkeye Security adds mobile surveillance for remote site monitoring, and Hawkeye Workforce Readiness tracks workforce learning and readiness. A product walkthrough is the usual way to see how it fits your jobs.
For construction teams, start with the construction overview or the page on billing readiness.
FAQ
How many field operations KPIs should we track?
Four to eight is a workable range for most teams, with at least one for each stage you care about: schedule, labor, safety, quality and billing. Each KPI needs an owner and a review rhythm. If a number is not reviewed, remove it.
What is the difference between a leading and a lagging KPI?
A lagging KPI reports an outcome after the fact, such as TRIR or invoice correction rate. A leading KPI measures something you can still change, such as training compliance, near-miss reports or daily record completeness. Use both so you can act early and confirm results.
How do you calculate TRIR?
Multiply the number of recordable injuries and illnesses by 200,000, then divide by total hours worked by employees in the same period. The 200,000 base equals the yearly hours of 100 full-time workers. Four cases over 520,000 hours gives 1.54.
Which KPIs matter most to billing specialists?
Completion-to-invoice time, invoice correction rate, unbilled completed work and dispute rate by job type. Together they show how quickly and cleanly field work becomes an invoice. Missing signatures, PO numbers or photos on field tickets are the most common causes of delay.
Can we monitor field KPIs in real time?
Yes, for data captured digitally at the site, such as time entries, tickets and site views. Treat live numbers as prompts to ask a question, since a low reading can have a simple cause like a late delivery. Use period-end figures for targets and reviews.
Sources
Recommended
START WITH YOUR WORKFLOW
See your operations in action.
Walk through the handoffs that slow your team down—and see where a connected record can help.