Earned value management is not a complicated idea. You compare what you planned to spend, what you have actually earned by installing work, and what it actually cost you. The math is three numbers. The reason it fails on dirt jobs has nothing to do with the math and everything to do with where the numbers come from.
The problem: your earned value is only as honest as Friday afternoon
Here is how it usually goes. The crew works Monday through Thursday. Quantities live in a foreman's head, a bent notebook, and a couple of text messages. Hours get written down Friday morning from memory. Somebody in the office keys it all into a spreadsheet the following week, backs into a percent complete, and hands the PM a number.
By the time that number exists, it describes a job site that no longer exists. The crew has already moved 400 feet down the line. If the number says you are underwater on the storm run, you cannot go back and fix the storm run. You can only decide what to do about the next one, with a week less runway than you should have had.
The specific failures show up in a predictable pattern:
- Percent complete gets estimated, not measured. Somebody eyeballs "about 60 percent" on a pay item instead of counting the 1,840 linear feet that are actually in the ground.
- Hours land on the wrong cost code. A crew spends half a day on unclassified excavation and half on pipe bedding, and all eight hours get coded to whichever one the foreman remembers.
- Cost shows up last. Invoices, equipment time, and material tickets arrive weeks after the work, so actual cost is always the stalest number in the model.
- The variance gets explained away. When the data is soft, every bad index turns into an argument about whether the data is right instead of a decision about the job.
If it isn't captured when the work happens, it doesn't exist. Earned value built on reconstructed data is a story about the job, not a measurement of it.
How PM Axsus handles it at the point of installation
PM Axsus is built the other direction. Instead of asking the office to assemble earned value out of leftovers, it captures the three inputs at the moment they are created, in the field, by the people who created them.
Earned value comes from installed quantity. When a crew installs pipe, places structure, or moves a lift of embankment, that quantity is logged against the pay item and cost code on site. Earned value is the budgeted rate multiplied by the quantity actually in the ground. Nobody estimates a percentage.
Actual cost starts with the clock. Time is captured with GPS-tagged clock in and clock out tied to the project and the work being performed, with the daily hazard acknowledgment built into the same moment. Equipment assignments and material deliveries are logged against the job as they happen rather than reconciled later.
Planned value comes from your own schedule and budget. The baseline is whatever you bid and scheduled. PM Axsus does not need a different way of estimating; it needs the field side to report against the structure you already use.
Because all three inputs live in the same system, they stay comparable. That is the entire trick. Most contractors have all this data somewhere; they just have it in four places that never line up in time.
What the office sees
CPI, live
Earned value divided by actual cost, refreshed as field records land, by project and by cost code.
SPI, live
Earned value against planned value, so slipping items surface while there is still schedule left to protect.
The record behind the number
Every index traces back to the field entries that produced it, with timestamps and the person who logged it.
Axsus Intelligence OS
The AI layer reads the same verified field record and surfaces where cost, schedule, and production are diverging.
The practical result is that the conversation changes. Instead of the Monday meeting being about whether the numbers are right, it is about which crew needs to move, which item needs a rate change, and which quantity needs to be billed this cycle. That is a week you get back on every job.
Where this fits with the rest of the platform
Earned value is the output. It only works because the inputs are disciplined. If you are evaluating this, start with the capture layers that feed it: quantity tracking, time tracking, and production tracking. If you want the underlying method first, our plain-English guide to earned value in construction walks the math with dirt quantities.