Production rate is the number your entire business is priced on. Feet of pipe per day. Yards per hour. Structures per crew week. You bid it, you schedule to it, and you live or die by whether you hit it. And on most jobs, nobody actually knows what it is until the job is over.
The problem: the rate is a feeling until the job is finished
Ask a foreman how the crew is running and you will get an honest, useful, entirely qualitative answer. "We're moving." "Rock slowed us down Tuesday." "We're about where we should be." That is real information, and it is not a number you can act on, schedule against, or bid with.
The quantitative answer usually arrives too late to matter:
- Quantities are batched. Installed footage gets tallied at the end of a pay period, so daily variation is invisible.
- Hours are coded loosely. If a day's hours land on a general code instead of the specific work, you cannot divide quantity by labor to get a rate.
- Conditions get lost. The week that ran at half rate because of dewatering looks identical in the numbers to the week that ran at half rate because of a short crew.
- Nothing feeds back into bidding. The next estimate uses the same rate as the last one because there is no clean record of what the crew actually did.
The consequence is that a company can run for years bidding rates it has never verified. When margins compress, that is the difference between a job that makes money and one that does not.
You cannot manage a production rate you only measure once, after the work is over. The rate has to be visible while there is still job left to run.
How PM Axsus handles it at the point of installation
Production rate is a ratio: installed quantity over the labor and equipment hours that produced it. PM Axsus captures both halves in the field, at the same level of detail, tied to the same project and cost code.
The quantity half. As work is installed, the quantity is logged against its pay item and cost code by the crew doing it. Not estimated at the end of the week. Recorded as it goes in.
The hours half. Time is captured with GPS-tagged clock in and clock out tied to the project and the work being performed. Equipment assignments are tracked against the fleet registry, so machine hours are attributable rather than assumed.
When both halves carry the same project and cost-code context, the rate falls out of the data. There is no separate production-reporting exercise, and no one has to reconcile a quantity log against a timesheet that was written from memory three days later.
Why daily resolution matters
A weekly average hides everything useful. A crew that runs 320 feet on Monday, 340 on Tuesday, 90 on Wednesday, and 310 on Thursday averages 265 feet per day, which looks like a mediocre crew. It is actually a good crew with a Wednesday problem. Daily capture lets you find the Wednesday problem. Weekly rollup guarantees you never will.
What the office sees
Who is running what rate
Production compared across crews on comparable work, from records rather than impressions.
Which items are underperforming
Rates by item, so a single bad pay item does not hide inside a healthy job total.
Bid rate vs. actual rate
The comparison that tells you whether the estimate was wrong or the execution was.
Axsus Intelligence OS
The AI layer reads the same verified field record and surfaces divergence between planned and actual production.
The strategic payoff is in the estimating department. After a year of clean production data, your next bid is priced on rates your own crews demonstrated on your own kind of work, in your own ground, rather than on a number that has been copied forward since 2019.
Where this fits
Production tracking is the bridge between quantity tracking and time tracking, and it is a direct input to earned value management. To understand how to build defensible rates from your own history, read production rates and how to track them.