On a job above roughly $30,000, a small estimating miss can outrun the profit you thought you won.
That happened to a landscape materials supplier. The jobs were moving, the team was selling, and the business kept discovering afterward that large projects had paid far less than expected. The problem was buried in labor, materials, rework, communication gaps, and assumptions that survived from the quote to the final invoice.
The fix started with a simple rule: every job above a meaningful dollar threshold gets an after-action review shortly after closeout. The team compares what they expected with what happened, then makes one or two changes before the next bid.
Today I’m going to break down why this happens and how to implement an after-action review to (1) protect your margins and (2) turn a completed job into a better estimating system.
WHY THIS HAPPENS
Underpricing big jobs usually comes from a small group of operational misses. Each one feels manageable by itself. Together, they can consume the margin on a project that looked healthy at the start.
THE ESTIMATE DESCRIBES A PLAN
An estimate captures the way the team expects the work to happen. The job follows the conditions on the ground. Crews take a different sequence, the customer changes direction, materials arrive late, or a scope detail takes twice the expected labor.
The estimate still has value. It becomes useful when the team compares it with reality and updates the assumptions that missed.
SMALL COSTS GET BIG AT SCALE
Mobilization, disposal, equipment rental, travel, rework, and extra supervision can look minor during a sales conversation. On a large job, each one has a way of becoming a real margin problem.
The same thing happens with change orders. A team may recognize extra work but fail to price or document it quickly enough. The job moves forward, and the business absorbs the cost.
SALES AND DELIVERY SEE DIFFERENT PARTS OF THE JOB
Sales wants to win the work. Delivery wants to complete it. Accounting wants to record the result. Each team can do its part while the business loses the connection between the original promise and the final economics.
A forced review gives those teams one conversation about the same job. It surfaces the point where the estimate, the work, and the financial result separated.
THE LESSON DISAPPEARS AFTER CLOSEOUT
Most teams remember a painful job for a few weeks. Then the next similar opportunity arrives, and the estimator rebuilds the quote from memory. The business pays for the same lesson again.
A review only creates value when it changes something the team uses. That could be a production rate, a line item, a scope question, or a change order rule.
THE AFTER-ACTION REVIEW
Keep the meeting short and give it a clear threshold. For the supplier in this example, the review applied to jobs above roughly $30,000. Your threshold should match the point where a pricing miss would meaningfully affect cash or margin. A threshold that catches every job will create busywork. A threshold that is too high will miss useful patterns.
Run the review for 20 to 30 minutes with the estimator and the person closest to delivery, such as the project manager or foreman. Use the same four questions every time.
WHAT DID WE EXPECT?
Pull the original estimate. Write down the assumptions that mattered: labor hours by phase, crew mix, materials, subcontractors, equipment, travel, timeline, and customer responsibilities.
Call out the assumptions that felt fragile when the job was sold. Those are often where the final margin begins to move.
WHAT ACTUALLY HAPPENED?
Pull facts before opinions. Compare estimated labor with actual labor. Compare expected material and subcontractor costs with invoices. Review the timeline, approved and missed change orders, rentals, rework, callbacks, and any work that fell outside the original scope.
This part works best when the team can see the estimate and the actual result side by side. Use this part to create one shared record of the job and identify the process change.
WHERE DID THE GAP COME FROM?
Give the gap a category you can fix. Common categories include scope, production rate, sequencing, procurement, customer constraints, communication, and quality.
“Everyone worked hard” can be true while the production rate was wrong. “The customer changed the scope” can be true while the change order process failed. The category helps the team move from a story about the past to a decision about the next bid.
WHAT CHANGES BEFORE THE NEXT BID?
Choose one change. Two at most. A long list creates the feeling of progress and leaves the estimating process untouched.
The change may be a standard line item for disposal or mobilization. It may be a new production rate, a tighter scope checklist, a required handoff from sales to delivery, or a rule that extra work needs written approval before the crew proceeds.
Put the change where the next estimate gets built. If it lives only in meeting notes, it will disappear.
WHAT TO DO NEXT
Start with the last large job that felt fine operationally but paid poorly. Pull the original estimate, the actual costs, the change orders, and the final margin. Then schedule the review while the people involved still remember what happened.
Use the first meeting to answer the four questions. Keep the conversation factual. When the group identifies the gap, make one process change before the next bid.
Run the same review for three jobs. Look for repeated misses. A single job can contain bad luck. The same miss across three jobs points to a system problem that deserves a permanent fix.
The most useful outputs will usually fit into one of four places:
- a standard line item or cost assumption
- a production rate or labor-hour rule
- a scope and handoff checklist
- a change order approval rule
Review the next estimate against the change before it goes to the customer. That closes the loop between the job you finished and the work you are about to sell.
--
Underpricing big jobs creates a margin problem that shows up after the decision has already been made. The after-action review moves the learning closer to the next decision.
Start with a simple estimating process: a threshold, a short meeting, four questions, and a rule that every review produces a change the team can use.
Pull one completed job this week. Compare the estimate with reality. Fix one assumption before the next bid.
If you want help building a finance rhythm that connects job performance to cash and profit, book a Cash & Profit Diagnostic or see how we work with service businesses.
