Every civil contractor has a version of this story. The owner's rep directs a change verbally. The crew does the work because the crew is standing there and the schedule does not wait. Three weeks later the ticket goes in, and now there is a negotiation about hours that nobody wrote down at the time.
The problem: the strongest position is a record you did not keep
Force account and time-and-materials work has a documentation burden completely out of proportion to its dollar value. A $9,000 extra can consume more office hours than a $400,000 pay item, because on the pay item nobody disputes what was installed.
The usual failure modes:
- Verbal direction, no written trigger. The work starts because it has to, and nothing marks the moment it became extra work.
- Hours are not segregated. The crew worked on base scope and extra work the same day, and all the hours went to one code. Now the extra has to be estimated backward.
- Equipment gets forgotten. Labor is remembered because payroll forces it. The excavator, the trench box, and the water truck that were also committed frequently are not.
- Materials are untraceable. Pipe and fittings pulled from the yard for the extra never get separated from job stock.
- No photos of the condition. The differing condition that caused the work is now backfilled, and the only evidence is a description.
- Signatures come late. Daily T&M tickets signed at the time are strong. Tickets assembled weeks later and presented in a batch invite line-item negotiation.
On extra work, you are not paid for what you did. You are paid for what you can show you did, in the form and on the timeline the contract requires.
How PM Axsus handles it at the point of installation
PM Axsus does not negotiate your change orders. What it does is make sure that when the negotiation happens, the underlying record was created contemporaneously by the people doing the work.
The same field-capture layers that run your base scope carry the extra work:
- Hours segregated at the source. Time is captured with GPS-tagged clock in and out against the project and the work being performed, so hours on extra work can be separated at the time rather than allocated from memory later.
- Equipment on the record. Equipment assignments are tracked against the fleet registry, so the machines committed to the extra are documented alongside the labor.
- Materials captured on delivery. Material deliveries are logged with photos when they arrive, and procurement requests are tracked against the project, so material consumed by the extra has a paper trail.
- Conditions photographed before they are covered. Structured field records with attached photos and timestamps establish what the crew actually encountered, at the moment they encountered it.
- Signatures collected in the field. Where your process calls for a signature, it is collected on the record, not chased down later.
None of that is exotic. It is the ordinary discipline of capturing work as it happens, applied to the category of work where sloppy capture is most expensive.
What the office sees
The extra work is visible now
Hours and resources on extra work surface while the ticket can still be presented promptly.
Backup that already exists
Labor, equipment, materials, and photos live on the same project record instead of in four systems.
Unbilled extra work
Extra work in progress is visible as cost before it turns into an unpleasant surprise at month end.
Kept out of base scope
Segregated hours keep extra work from silently distorting the earned value on your base pay items.
That last point is underrated. When extra-work hours get buried in base cost codes, two things break at once: the extra is under-billed, and the base scope looks unprofitable. PMs then go chasing a productivity problem that does not exist. Clean segregation fixes both.
An honest limit
Software does not create entitlement. If your contract requires written authorization before extra work begins and you did not get it, no field app fixes that. What field-first capture gives you is the strongest possible factual record, created at the time, in a consistent form, which is what makes a legitimate claim easy to substantiate and an aggressive one easy to defend against.
Where this fits
T&M documentation is built on time tracking and field capture with photos and signatures, and it protects the accuracy of your earned value model. Contractors working under strict public-agency rules should also read the DOT subcontractor page.