Cost control actions, reporting to owners and capstone: a monthly cost report

Measurement without action is just bookkeeping. The previous lessons built a system that tells the project team, early and accurately, where the job is heading. This final lesson is about what to do with that knowledge: the corrective actions available when a job is going wrong, how to choose among them, how to report cost to management and to owners on different contract types, and how to close the loop by feeding actual results back into estimating. It ends with a capstone in which you assemble the month 11 cost report for Riverbend Commons from the methods of the whole course.

Corrective actions

When a variance analysis (Lesson 8) identifies a cause, the project team chooses actions to address it. Actions fall into a few broad groups, and the right one depends on whether the cause is still active, whether it lies within the contractor's control, and how much of the work remains.

A few principles help. Act on causes, not symptoms: cutting overtime because labor cost is high will not help if the real cause is late drawings. Act early: the further the work has progressed, the less any action can change the outcome (Lesson 8). Price the action: recovery measures such as acceleration have their own cost (Lesson 10) and should be compared with the cost of doing nothing. And record the decision and its expected effect, so next month's report can show whether it worked.

Reporting to management

Inside the contractor, cost reports go up the line to operations managers and executives, who look across many jobs. They need consistent, comparable information: projected fee against bid fee, change in projected fee since last month, the biggest risks and opportunities, cash position and billing status. A one-page project summary, backed by the full cost report for those who want detail, is the usual format. The most important quality is honesty: a company where project managers fear reporting bad news will learn about losses only when they are too large to hide.

Reporting to owners

What the owner sees depends on the contract. On a lump sum contract the owner sees progress claims, the schedule, change pricing and perhaps a cash flow forecast for its own financing, but not the contractor's costs or fee. On cost-plus, GMP and construction management contracts, the owner usually sees the cost report itself: budget, cost to date, commitments, forecast, contingency use and savings, often monthly and in a format the contract specifies. Open-book reporting raises the stakes for cost control: miscoded costs, unexplained transfers or contingency used without approval can lead to disallowed costs and disputes.

GMP and cost-plus contracts in the United States, such as the AIA A102 and A133 or ConsensusDocs 200-series forms, define which costs are reimbursable, how contingency and allowances may be used and what records the owner may audit; public owners add their own requirements. A contractor working under these forms should set up its cost codes and reports to match the contract's definitions from the start, so that the owner's report is a filtered view of the contractor's own system rather than a separate set of books.

Closing out and feeding back

At the end of the job, the cost record becomes the company's most valuable estimating resource. A close-out review compares final cost with the original budget for each line, records actual quantities, hours and unit rates for self-performed work, notes subcontract buyout results and change history, and captures lessons about methods, suppliers and risks. The results update the historical cost database that estimators use (CON-200 Lesson 1 and CON-300 Lesson 12). Contractors that do this consistently bid more accurately and recognize risky work sooner; those that skip it repeat the same mistakes.

Capstone: the month 11 cost report for Riverbend Commons

It is now the end of month 11. Structure is complete; envelope, mechanical, electrical and interiors are under way. Your task is to assemble the monthly cost report and summary, using the methods of this course. The data are below; the code then carries out the main calculations so that you can check your own work. Work through the steps in order before reading the results.

• Step 1: calculate CV, SV, CPI and SPI.
• Step 2: calculate earned schedule, SV(t), SPI(t) and the earned schedule forecast duration.
• Step 3: calculate the bottom-up EAC, BAC ÷ CPI and the CPI × SPI EAC, and the TCPI the bottom-up EAC requires.
• Step 4: calculate VAC and the projected fee, with and without pending change recovery.
• Step 5: assess the billing position.
• Step 6: write the three-line management summary.

contract, BAC = 16_973_500, 16_236_000
pv = {9: 10_330_000, 10: 11_690_000, 11: 12_830_000}
EV, AC, AT, PD = 11_240_000, 11_520_000, 11, 16
etc_bottom_up = 5_112_000
pend_cost, pend_recovery = 71_000, 64_000
billed, earned_rev = 12_050_000, 11_750_000

# Step 1
CV, SV, CPI, SPI = EV - AC, EV - pv[11], EV / AC, EV / pv[11]
print(f"1) CV {CV:+,}  SV {SV:+,}  CPI {CPI:.3f}  SPI {SPI:.3f}")
# Step 2: EV lies between PV at months 9 and 10
ES = 9 + (EV - pv[9]) / (pv[10] - pv[9])
print(f"2) ES {ES:.2f} months  SV(t) {ES - AT:+.2f}  SPI(t) {ES / AT:.3f}  forecast duration {PD / (ES / AT):.1f} months")
# Step 3
eac_bu = AC + etc_bottom_up
eac_cpi = BAC / CPI
eac_cs = AC + (BAC - EV) / (CPI * SPI)
tcpi = (BAC - EV) / (eac_bu - AC)
print(f"3) EAC bottom-up {eac_bu:,}  BAC/CPI {eac_cpi:,.0f}  CPIxSPI {eac_cs:,.0f}  TCPI {tcpi:.3f}")
# Step 4
vac = BAC - eac_bu
fee_without = contract - eac_bu
fee_with = fee_without + pend_recovery
print(f"4) VAC {vac:+,}  projected fee {fee_without:,} ({fee_without / contract:.1%}); "
      f"with expected change recovery {fee_with:,} ({fee_with / contract:.1%})")
# Step 5
pos = billed - earned_rev
print(f"5) Billing position {pos:+,} ({'overbilled' if pos > 0 else 'underbilled'})")

1) CV -280,000  SV -1,590,000  CPI 0.976  SPI 0.876
2) ES 9.67 months  SV(t) -1.33  SPI(t) 0.879  forecast duration 18.2 months
3) EAC bottom-up 16,632,000  BAC/CPI 16,640,456  CPIxSPI 17,364,790  TCPI 0.977
4) VAC -396,000  projected fee 341,500 (2.0%); with expected change recovery 405,500 (2.4%)
5) Billing position +300,000 (overbilled)

Compare your answers with the results. Cost performance has stabilized since month 8 (CPI 0.976 against 0.969), because the troubled structure is finished and most remaining work is fixed-price subcontracts. Schedule remains the main concern: the project is about 1.3 months behind its baseline on an earned schedule basis, and SPI(t) projects about 18.2 months, longer than the team's month 17 assumption. The bottom-up EAC is almost exactly equal to BAC ÷ CPI and needs a TCPI of 0.977, essentially the CPI achieved to date, so it assumes no unexplained improvement: a realistic, if sobering, forecast. The projected fee is about 2.0 % before expected change recovery, against 4.5 % bid.

The billing position shows Northline about $300,000 overbilled, which helps cash but should be checked: if it comes from claims running ahead of measured progress, the certifier may correct it, and it leaves less contract value for the remaining work. CON-320 explains how this overbilling appears as a liability in the contractor's financial statements.

What makes cost control work

Across the whole course, a few habits separate contractors whose jobs finish close to their forecasts from those that are regularly surprised. They set up a control budget that traces to the estimate. They code costs carefully at the source and accrue at month-end. They measure progress objectively. They forecast from current performance and specific plans, test forecasts against independent formulas, and show ranges. They track changes from first notice and price them promptly. They watch cash as closely as cost. And they act early, record what they did and feed the results back into estimating. None of this needs sophisticated software; it needs discipline and honest reporting.