Production-rate math is useful only when the assumptions are visible. Truck hauling and fence installation both reduce to quantity, resource, rate, duration, and cost prompts, but measured cycle times, crew history, product instructions, permits, safety plans, route controls, and qualified review still control real work.
The companion Productivity Rate Calculator centralizes the local arithmetic for truck cycle time, match factor, payload, fence crew-days, gate hours, cure lag, and cost prompts. It also keeps source warnings and residual gaps visible so the output does not read like a final bid or dispatch plan.
1. Prompt, Not Approval
A production screen can organize the estimate, but it cannot verify the job. Use the rows as local prompts for review, then reconcile them with current source data, measured production, company cost records, project documents, permits, and safety controls.
The biggest failure mode is treating a clean number as an approved answer. A match factor, LF-per-crew-day rate, cost per BCY, cure lag, or truck count is only as good as the source data and field assumptions behind it.
2. Hauling Cycle Prompts
The hauling model screens load time, haul time, dump time, return time, and spot/wait time. It then applies an efficiency prompt and reports local loose and bank cubic yards per hour, tons per hour, loads per day, and unit cost.
For review, replace defaults with measured cycle records whenever possible. Check haul-road grade, traffic, dump rules, weather, route permits, bridge/axle limits, payload tickets, and truck standby cost before changing fleet size.
truck cycle = load + haul + dump + return + spot/wait
match factor = truck count x load time / truck cycle
Productivity Rate Calculator
Truck hauling cycle time with match factor and bottleneck verdict, plus fencing crew-day rate by type, soil, terrain, and post method. Two estimating modes on one shared engine.
3. Payload and Quantity Basis
The app screens truck payload as the lesser of heaped loose-volume capacity and weight-derived loose volume. It also converts between bank and loose cubic yards with the selected local swell/load-factor row.
Those rows need project verification. Material moisture, density, swell, shrink, compaction, scale tickets, survey quantities, pay-item basis, truck body, legal payload, axle/bridge limits, and route permits can all change the usable result.
4. Fencing Crew-Day Prompts
The fencing model screens local LF-per-crew-day, post counts, line-item crew hours, walk and drive gate hours, labor days, cure lag, optional material placeholders, and cost per linear foot.
Base rates, soil modifiers, terrain modifiers, post-method factors, gate hours, crew-size scaling, and material placeholders are planning rows. Reconcile them with licensed estimating data, company production records, product instructions, crew composition, site access, utility conflicts, weather, permits, and safety controls.
5. Tune Local Rates
Tracked production is better than a generic row, but it still needs context. For fencing, save a company LF-per-crew-day prompt only after documenting actual quantity, crew size, hours, weather, access, tooling, supervision, and product differences. For hauling, document load, haul, dump, return, and spot/wait segments along with route and payload constraints.
Saved values are device-local prompts. They do not replace current data, contract review, safety review, or qualified estimator/superintendent review.
6. Source Boundaries
Use the public source pointers as boundary context, not as row validation. Caterpillar site-performance context does not validate local handbook rows. RSMeans/Gordian is a commercial estimating-data source, and no licensed line items are reproduced. AFA education context does not validate LF-per-crew-day rates. ATRI cost context does not validate local truck hourly cost. FHWA and OSHA pointers support earthwork and safety boundaries, not project approval.