ArticleLast reviewed June 21, 2026

Earned Value & Cost Control in Field Service Projects

How project-based field service businesses use earned value management to track job cost vs. schedule — and protect margins on large contracts.

For project-based field service businesses, the most expensive moment is finding out a job lost money after the work is done. Earned value management (EVM) moves that discovery to week two, when there’s still time to do something about it.

EVM tracks three numbers against each job: what you planned to spend by now, what the completed work is actually worth, and what you’ve spent. When those diverge past a threshold, you have a variance — and a decision to make about scope, billing, or labor.

Key Takeaways

  • EVM gives project-based field service operators real-time cost vs. progress visibility, not just end-of-job summaries.
  • FSM software captures the labor hours, materials, and milestone completions that make EVM possible without manual timesheet aggregation.
  • Cost Performance Index (CPI) and Schedule Performance Index (SPI) are the two ratios worth tracking — both below 1.0 means a job is over budget and behind schedule.
  • Accurate job-level cost data supports profitable billing and provides a documented record if a contract dispute arises.

What Earned Value Management Actually Measures

EVM is a project accounting method that started in government contracting and has become standard in construction. The core idea applies directly to any field service business running multi-visit, contract-based work.

The Three Core Inputs

Every EVM calculation starts with three values:

  • Planned Value (PV) — the budgeted cost of work scheduled to be complete at this point in the job. If you planned to spend $15,000 by week four, PV is $15,000.
  • Earned Value (EV) — the budgeted cost of work actually completed. If 60% of scope is done and the total budget is $25,000, EV is $15,000.
  • Actual Cost (AC) — what you’ve really spent so far. If you’ve invoiced $18,000 in labor and materials to reach 60% done, AC is $18,000.

When AC is higher than EV, you’re over budget for the progress made. When EV is lower than PV, you’re behind schedule. A job where AC is $18,000 and EV is $15,000 is spending faster than it’s earning — and you need to know that in week two, not when you’re writing the final invoice.

CPI and SPI: The Two Ratios That Matter

Two derived metrics turn those three numbers into actionable signals:

  • Cost Performance Index (CPI) = EV ÷ AC. A CPI of 0.83 (15,000 ÷ 18,000) means you’re getting 83 cents of completed work for every dollar spent. Below 1.0 is a cost overrun.
  • Schedule Performance Index (SPI) = EV ÷ PV. An SPI of 1.0 means work is proceeding exactly as planned. Below 1.0 means the job is running behind the schedule you priced.

These ratios let you distinguish a job that’s expensive but on-time from one that’s late and over budget — which have different root causes and different fixes.

Why Project-Based Field Service Needs This

Single-visit repair calls don’t need EVM. One technician, one work order, one invoice — the job is either profitable or it isn’t, and you know at close.

Multi-visit project work is a different situation. Commercial HVAC installation, large preventative maintenance agreements, construction subcontracting, electrical retrofits — these jobs run weeks or months, involve multiple technicians, consume tracked materials, and often carry partial billing milestones. Without cost-vs-progress tracking, you can be 70% of the way through the budget while only 50% through the scope and not know it until you’re past the point where anything can be done.

The field service businesses where I see EVM most clearly needed:

  • Commercial HVAC contractors running equipment installation projects with separate material and labor phases
  • Construction trades — electrical, plumbing, mechanical — working under subcontracts with defined scope and completion milestones
  • Facilities maintenance firms holding multi-site service agreements where labor and parts consumption varies by location
  • Equipment dealers managing large installation or commissioning projects alongside recurring service

For businesses in enterprise field service management territory — 50+ technicians, multiple project types running simultaneously — EVM becomes a profitability management discipline rather than a nice-to-have.

How FSM Software Makes EVM Practical

EVM requires three data inputs: scheduled scope, completed scope, and actual cost. The reason most small field service operators haven’t used it is that gathering those inputs used to require manual timesheet reconciliation and spreadsheet gymnastics at month end.

FSM software solves this by capturing the underlying data automatically.

Labor Tracking

When technicians clock in and out against specific work orders in an FSM platform, labor hours accumulate at the job level in real time. No end-of-week timesheet submissions, no guessing how many hours were spent on which phase. ServiceTitan and Simpro both track time against jobs in this way, generating labor cost data that feeds directly into job costing without manual aggregation.

That labor data is the Actual Cost input in EVM. When you know what each visit cost and can compare it to the milestone it completed, the EV and AC columns fill themselves in.

Materials and Inventory

Parts pulled from a truck or warehouse, materials ordered against a job, subcontractor invoices tied to a work order — these are the material cost inputs that most project overruns hide in. FSM platforms with integrated inventory management track parts consumption at the job level.

Buildops is built specifically for commercial contractors and captures materials against jobs in a way that makes the Actual Cost calculation accurate. When a technician pulls a part, it hits the job record — not a general parts expense category.

Milestone and Progress Tracking

Work order completions, phase sign-offs, inspection checkpoints — these are the completed scope markers that determine Earned Value. An FSM platform that tracks job phases lets you define what “60% complete” means concretely: phase 1 closed, rough-in complete, inspection passed.

Project-built platforms like Simpro and BuildOps support multi-phase job structures where each phase carries its own work orders, time entries, and completion status. That structure is what makes progress-tracking meaningful rather than subjective. Lighter platforms aimed at single-visit work — Jobber, for instance — handle multiple visits and milestone-based progress invoicing, but not true phase-level project structures, so they fit project EVM less well.

Building a Baseline: The Starting Point

EVM only works against a budget baseline — a document that says what each phase of work should cost and when it should be complete. Without that, there’s nothing to compare actual performance against.

In field service, the baseline is usually the estimate or proposal. A commercial HVAC install might be broken into phases: site survey, equipment procurement, rough-in, installation, startup and commissioning, final inspection. Each phase has a labor budget, a materials budget, and a scheduled completion date.

That document — built in the FSM platform or imported into it — becomes the Planned Value schedule. Every week, you compare where the job should be (PV) against where it is (EV) and what it cost to get there (AC).

Review your methodology for job cost analysis against this baseline structure if you’re setting up for the first time.

Handling Change Orders

Change orders are the most common source of EVM baseline confusion. When scope changes mid-project, the original baseline becomes invalid as a comparison point unless it’s updated to reflect the change.

FSM platforms that handle change orders formally — requiring documented approval before additional work begins, and updating the job budget when approved — keep the baseline current. This matters both for internal cost tracking and for the documentation trail if a client later disputes what was authorized.

Using EVM Data for Accurate Billing

The connection between EVM and billing is direct: Earned Value is the billable amount you’ve legitimately earned at any point in the project. If a contract allows for progress billing, EV tells you what you’ve earned, and AC tells you what you’ve spent — the gap is your current margin position.

Field service businesses that bill on completion milestones benefit from EVM because it validates that each milestone’s billing amount reflects the work actually done. A client who receives a 40% completion invoice can be shown exactly what was completed, at what cost, against what was planned — which reduces billing disputes before they start.

For percentage-of-completion billing — common in longer commercial projects — EVM provides the defensible completion percentage rather than a subjective estimate. You’re not billing 40% because it feels like you’re 40% done; you’re billing 40% because $X of the $Y total scope has been formally completed and documented.

EVM Data in Contract Documentation

When a project-based field service contract goes sideways — scope disputes, delay claims, payment withheld — the difference between a defensible position and a losing one often comes down to documentation.

EVM, maintained throughout the job in an FSM platform, produces exactly the kind of documentation that matters in those situations:

  • Baseline schedule and budget — what was agreed to
  • Earned value progress log — what was completed, when
  • Actual cost record — what was spent, on what
  • Variance records — where the job deviated from plan, and when it was flagged
  • Change order log — what scope changes were authorized

This isn’t about preparing for disputes — it’s a byproduct of running good job costing. The documentation exists because it’s operationally useful; its value in a contract dispute is secondary.

A client who disputes that work was complete at billing point can be shown the EV calculation. A client who claims overcharging can be shown the AC breakdown by phase. Neither conversation requires a lawyer if the records are clean.

Connecting to Profitability Analysis

EVM also feeds the profitability-per-job analysis that helps field service businesses understand which work types, clients, and contract structures are actually profitable — and which are absorbing overhead without returning margin.

A commercial HVAC contractor who tracks EVM across 20 jobs over a year can see whether installation projects consistently run over budget, whether certain equipment types generate more rework, and whether particular contract structures (fixed-price vs. time-and-materials) perform better under their cost structure.

Simpro’s job costing reports are designed for this kind of cross-job analysis. Fieldboss integrates this directly with Dynamics 365 financials. The FSM comparison that matters for project-heavy businesses isn’t which platform has the best scheduling UI — it’s which platform’s job costing data is reliable enough to inform pricing decisions.

See the FSM software comparisons for how these platforms handle project cost tracking differently.

Setting Up EVM in Practice

For a field service business that hasn’t tracked cost vs. progress before, the practical starting point is simpler than the formal EVM literature suggests.

Step 1: Define phases for your typical project. Start with your most common project type — say, a commercial HVAC install — and break it into 4–6 phases with a budget for each.

Step 2: Build the budget into your job record. Whether in your FSM platform or in a linked spreadsheet, document what each phase should cost in labor and materials.

Step 3: Track actuals against the job. Ensure technicians are clocking time against the right job and phase, and that materials are being recorded at the job level rather than expensed generally.

Step 4: Compare at each phase completion. When a phase closes, compare EV (budgeted phase cost) against AC (what you actually spent). A phase-by-phase review catches overruns before they compound.

Step 5: Update the baseline when scope changes. If a client changes scope, update the job budget formally before the work happens — not after, when the variance looks unexplained.

For businesses in the glossary sense of what cost performance index and schedule performance index mean, these concepts become day-to-day operational language once EVM is running.

Frequently Asked Questions

What is earned value management in plain terms for a field service business?

EVM compares what you planned to spend by now against what you’ve actually spent and what that spending got you. If you’re halfway through a job but have used 70% of the budget, EVM flags that before you finish — giving you time to adjust scope, billing, or labor allocation rather than discovering the loss at invoice time.

Which field service businesses benefit most from EVM?

EVM is most useful for project-based work: commercial HVAC installation, electrical and plumbing contracting, large preventative maintenance agreements, and construction trades. Businesses that dispatch one technician for a single-visit repair usually don’t need it — but any job that spans multiple visits and involves tracked materials and subcontractors benefits from cost-vs-progress monitoring.

How does FSM software support earned value tracking?

FSM platforms like ServiceTitan, Simpro, and Buildops capture the raw data EVM needs: technician time per job, materials pulled from inventory, milestone completions, and change orders. That data flows into job costing reports automatically rather than requiring manual timesheet reconciliation at month end.

Can EVM data help if a client disputes a contract?

Yes. A documented record of what was completed, when, and at what cost is far more defensible than a verbal account. Planned value baselines and earned value progress logs show exactly where the job stood at any point in time — useful if a client claims work was incomplete, work was unauthorized, or billing doesn’t match progress.

What is the difference between CPI and SPI in field service EVM?

Cost Performance Index (CPI) shows whether you’re spending more or less than planned for the work completed — a CPI below 1.0 means you’re over budget. Schedule Performance Index (SPI) shows whether you’re ahead or behind the planned pace — below 1.0 means the job is running late. Tracking both lets you distinguish a job that’s expensive-but-on-time from one that’s behind and over budget.

Frequently asked questions

  1. What is earned value management in plain terms for a field service business?

    EVM compares what you planned to spend by now against what you've actually spent and what that spending got you. If you're halfway through a job but have used 70% of the budget, EVM flags that before you finish — giving you time to adjust scope, billing, or labor allocation rather than discovering the loss at invoice time.

  2. Which field service businesses benefit most from EVM?

    EVM is most useful for project-based work: commercial HVAC installation, electrical and plumbing contracting, large preventative maintenance agreements, and construction trades. Businesses that dispatch one technician for a single-visit repair usually don't need it — but any job that spans multiple visits and involves tracked materials and subcontractors benefits from cost-vs-progress monitoring.

  3. How does FSM software support earned value tracking?

    FSM platforms like ServiceTitan, Simpro, and Buildops capture the raw data EVM needs: technician time per job, materials pulled from inventory, milestone completions, and change orders. That data flows into job costing reports automatically rather than requiring manual timesheet reconciliation at month end.

  4. Can EVM data help if a client disputes a contract?

    Yes. A documented record of what was completed, when, and at what cost is far more defensible than a verbal account. Planned value baselines and earned value progress logs show exactly where the job stood at any point in time — useful if a client claims work was incomplete, work was unauthorized, or billing doesn't match progress.

  5. What is the difference between CPI and SPI in field service EVM?

    Cost Performance Index (CPI) shows whether you're spending more or less than planned for the work completed — a CPI below 1.0 means you're over budget. Schedule Performance Index (SPI) shows whether you're ahead or behind the planned pace — below 1.0 means the job is running late. Tracking both lets you distinguish a job that's expensive-but-on-time from one that's behind and over budget.

Trust signal

Fact Checked & Editorial Guidelines

Every post on this site is fact-checked against the policy below before the "Last reviewed" date is updated. If a single item below fails verification, the post does not go live.

  • Every claim traces to a source.

    Pricing, feature lists, integrations, and headquarters are taken from vendor product pages, documentation, or signed contracts — never repeated from secondary blogs. Where a claim is sourced from a single vendor's marketing, it is qualified as such.

  • Vendor relationships are disclosed in-line.

    If a review covers a platform whose vendor has provided trial access, sandbox access, or paid placement on a sister property, that relationship is stated in the review's methodology footer — not buried in a sitewide disclosure page.

  • Pricing is rechecked at every review cycle.

    Vendor pricing changes constantly. The 'Last reviewed' date on each post is the date the price line was last re-verified against the vendor's public pricing page. If you spot a stale price, the contact page accepts corrections.

  • Corrections are logged, not silently rewritten.

    Material factual corrections after publication get a correction note dated and appended to the post. We don't pretend the prior version never said what it said.

Spotted an error? Send a correction via thecontact page — corrections are logged with a dated note on the post.

Trust signal

Editorial Review & Methodology

Reviews and comparisons on this site follow a single documented methodology — the same rubric, applied identically to every platform, on every review cycle.

  • Five-criteria scoring rubric, applied identically to every platform.

    Usability, pricing transparency, feature depth, support quality, and integrations. Each criterion scored 0–10 with documented weighting. The rubric is published on the methodology page and does not change between platforms in the same review.

  • Hands-on testing where vendor trial access permits.

    If a vendor offers trial or sandbox access, the reviewer spins up an account and works through the documented evaluation script before scoring. Where access is enterprise-gated, the access type is disclosed and scoring draws on product documentation, verified buyer reviews, and analyst sources.

  • Editorial independence from commercial relationships.

    No vendor pays for placement, previews scores, or controls the content of a review. Affiliate links, where present, do not change ranking — picks are ordered by score, not by commercial yield. If a conflict of interest exists for a specific review, it is disclosed within that review.

  • Reviews get re-checked, not just re-dated.

    Each 'Last reviewed' update means the rubric was re-applied — pricing, feature inventory, integration list, and any material vendor changes since the prior review. A bare date bump without re-evaluation is not a re-review.

The full rubric, weighting, and review-cycle process is on themethodology page.