Built by an excavation contractor who got tired of guessing

Excavation is a volume business with a documentation problem. You move dirt all day, you know roughly how you did, and then you spend the evening trying to turn that into numbers that somebody in an office can bill and cost against. The gap between those two activities is where the margin goes.

The day, as it actually runs

The crew is on site before seven. The excavator is running by 7:15 because daylight is money and the trench box has to move before the plumbers show up at ten. Somewhere in there a testing tech shows up, shoots density on last night's backfill, and leaves. A truck delivers pipe to the wrong end of the job. The inspector wants to see bedding on the run that is already half covered. A machine throws a hydraulic line at 2pm.

Every one of those events is a data event. Every one of them affects cost, schedule, or compliance. And every one of them is currently recorded, if at all, as a text message, a note in a notebook, or a thing somebody intends to remember.

Then the foreman goes home and is expected to produce: a timecard, a quantity count, a daily report, and a compaction record. From memory. After a ten-hour day. This is the actual constraint, and any tool that ignores it fails.

What hurts most

• Yards are a guess until the survey. You know you had a good week. You do not know whether you are ahead or behind on the item until somebody shoots it.
• Compaction paperwork is the recurring emergency. The tests passed. Proving they passed, at a specific station and lift, two weeks later, is the fire drill.
• Hours land on the wrong code. A day split between mass excavation, trench, and haul gets coded to one thing, so all three items are costed wrong.
• Equipment cost is invisible. Machine hours are the second biggest number on a dirt job and the one least likely to be tracked against the item that consumed them.
• Nobody knows the real production rate. You bid 900 yards a day. Whether you got it is a conversation, not a number.

How the platform fits an excavation operation

PM Axsus is built around the assumption that the field is the source of truth and the office is downstream. Crews clock in with GPS tagging tied to the project and the work being performed, with the daily hazard acknowledgment handled in the same step. Quantities are logged against pay items as material moves. Compaction and pressure test records are captured at the trench with photos, signatures, and timestamps, and can be delivered to inspectors as branded PDFs. Equipment lives in a registry with assignments and maintenance, so a machine's time is attributable to a job rather than absorbed into overhead.

Because all of that shares one project record, the office side is a view rather than a re-entry. Earned value, production rates, and cost-to-date are computed from the same field entries that produced the compliance documentation. The Axsus Intelligence OS layer reads that verified record and surfaces where cost, schedule, and production are diverging.

What changes in the first month

1. Payroll week gets quieter. Fewer disputes because hours were captured at the gate rather than reconstructed on Friday.
2. Compaction stops being a fire drill. The record exists before the trench is backfilled, so the inspector request is a lookup instead of a search.
3. The Monday meeting changes subject. Instead of arguing about whether the numbers are right, you argue about which crew moves where, which is the argument worth having.

Honest about scope

This is a field capture and earned value platform, not a takeoff package and not an accounting system. It sits between the machine and the ledger. If your problem is that your estimate is wrong, this will tell you that faster than anything else you own, but it will not write the estimate. Bring a real job to a demo and check the fit against your own pay items.

Start with production tracking, compaction tracking, and time tracking, or read earned value for dirt work for the method applied to yardage.