Most job-costing failures get pinned on the execution team. The project manager. The superintendent. The foreman. From that assumption, the response is predictable: tighten the SOPs, apply accountability pressure to the field, run the numbers harder.
The problem is that the assumption is often wrong. By the time the execution team touches a project, two other parties have already built the entire framework inside which that team operates. The estimators who priced the work and the finance team that structured the schedule of values and assigned the product codes got there first. If either of those frameworks is off, the execution team is executing against a broken map — and no amount of field accountability fixes a broken map.
The SOP that actually improves job costing does not start with accountability. It starts much further upstream, with an honest accounting of where failures can originate.
Three Sources, Not One
Three parties have fingerprints on every construction job-costing outcome. Each contributes a distinct document to the project’s cost structure, and a failure can originate in any one of the three.
| Party | Their Document | What it controls |
|---|---|---|
| Preconstruction | The Estimate | Scope definition, quantities, labor hours, unit costs, contingencies. This is the original cost model against which everything else is measured. |
| Finance | Schedule of Values + Codes | How the estimate gets translated into a billing and tracking structure. Product or service codes determine how field-reported costs are categorized and whether they map to billable line items. |
| Execution | Job Financials | Actual hours, materials, and subcontractor costs reported against the codes they’ve been given. The execution team works inside the framework the other two parties built. |
The finance team’s role is where the diagnosis most commonly goes wrong. Estimators structure the scope, but the finance team translates that scope into a schedule of values and assigns the codes the field will use for reporting. If those codes are not intuitive to the person in the field who is responsible for job costing, costs land in the wrong buckets. That produces reporting that looks like an execution failure but is a structural one. The person who entered the wrong code may not have been wrong — they may have made a reasonable interpretation of an ambiguous code that the finance team never field-tested.
“Before the execution team ever touches a project, the entire framework for that project is already built. Accountability pressure on the wrong party doesn’t fix the framework.”
There is also immense complexity in how construction divisions structure schedules of values — line items that span long time periods, grouped tasks that make progress difficult to measure mid-project, billing structures that depend on a specific interpretation of what constitutes substantial completion. The point is not to resolve all of that complexity here, but to establish that the SOV structure is a source of job-costing failure independent of anything the field team does. That source must be named and examined for any review to be meaningful.
The Enhanced Post-Mortem
A standard post-mortem reviews the project financials. The Enhanced Post-Mortem goes further: it sets three documents side by side — the original estimate, the schedule of values with its coding, and the actual job financial performance — and examines the comparison. The comparison is what makes intelligent diagnosis possible. Questions that cannot surface from reviewing any single document become obvious when all three are in the same room.
Each of these questions requires all three documents to ask. Without the estimate, you cannot know whether the SOV reflects what was priced. Without the SOV, you cannot know whether the field had the right framework to report against. Without the actuals, you cannot know where the gap landed. The comparison is the diagnostic tool.
The Review Meeting
Once the comparison has been run and the failure points are documented, the responsible parties — preconstruction, finance, and execution — meet together. The structure of the meeting matters as much as the data: all three parties are questioned, and that expectation is built into the agenda from the start. The agenda itself names the interrogation as a normal part of the review, not a special circumstance.
An owner or a neutral senior leader leads the questioning. The meeting follows a standard discipline: review the comparative data first, then discuss. The three documents are in front of every participant before the meeting begins. From there, the questioning works through each identified failure point and assigns it to a source.
This structure does something that few company cultures manage: it names finance as an accountable party in a construction review. Finance teams that structure reporting frameworks often do so without meaningful input from field supervisors, and they are rarely questioned about it. A common dynamic is that the estimators and the execution team carry a chronic tension about whose failure any given cost problem is — and that tension persists partly because the third party that built the tracking framework is never in the room. Putting all three in the room, with the expectation that all three may be found responsible, changes the dynamic.
The goal of the meeting is not to assign blame. It is to find the true source of each failure so the right party can improve the right thing. A professor who gives an exam does not do so to fail the students — the exam is the mechanism by which gaps are found and closed. The Enhanced Post-Mortem meeting works the same way.
What Makes This SOP Self-Improving
A standard post-mortem is a one-time event. The Enhanced Post-Mortem becomes a self-improving system through six structural conditions that distinguish it from a project debrief.
Companies that run this process consistently find that their estimating gets tighter, their SOV structures become more intuitive to field teams, and their actual job financials start moving toward the estimate rather than away from it. That trajectory is not incidental. It is the result of a structure that examines the right things, questions all three responsible parties, and repeats until the gap closes.
The last thing a company wants is to spend years applying accountability pressure to the execution team for failures that started in the estimating or finance framework. The Enhanced Post-Mortem is the structure that prevents that.
Build the Financial Controls Your Construction Division Needs
GCG works with landscape and construction operators on job costing discipline, SOV structure, and the operational controls that protect margin. Start with the free Business Health Assessment.
Take the Free Assessment