Earned Value for Construction: Close the Progress–Cost Gap

ISO published the second edition of ISO 21508 in February 2026. Its public abstract covers earned-value management across organizations and sectors, while explicitly excluding guidance on particular methods or tools. It is a management framework, not a software specification. [1]

OlbrichCo’s proposal is to begin with one question: does the work achieved justify the resources consumed, and what does the unfinished scope now require? Before buying a platform, choose a project or package whose scope, budget, progress evidence and costs can be reconciled. Assign a package owner, site verifier, cost reviewer and person authorized to approve changes.

Define whose performance is being measured. An owner’s contracted cost, a contractor’s production cost and a subcontractor’s invoice value are not interchangeable reporting boundaries. Write the included scope, exclusions, cost categories, overhead treatment and reporting currency into a short control note. Agree how records from different parties map to that boundary without pretending that unavailable information is known.

For an Iranian project, ask which site records are actually obtainable and who can check them before the reporting deadline. Use stable package and location identifiers with Persian field descriptions, a named reporting date and one calendar convention. Keep an approved offline capture form where connectivity is unreliable. A sophisticated report should not depend on untraceable messaging screenshots.

DOE describes planned value as the budget assigned to scheduled work, earned value as completed work expressed at its planned cost, and actual cost as the cost of performing that work. Comparing spending with plan without physical progress can mislead. [2]

For each package, document a measurable completion rule and its evidence before the first update. Use verified quantities for genuinely comparable units, or observable milestones with weights justified by the budgeted work they represent. Include design, procurement, installation and testing where they are in scope. Do not assign most of the weight to an easy early milestone merely to improve reported progress.

Distinguish ordered, delivered, installed, inspected and tested states. A delivery may legitimately earn a separately budgeted procurement milestone, but it should not automatically earn the installation and acceptance budget too. Define how rejected work, incomplete tests, rework and cancelled quantities are treated. The site team should know which evidence changes a reported state and who may confirm it.

Keep the measurement rule separate from payment certification. Advance payments, retention releases and commercial settlement require their own contractual treatment; do not convert them directly into physical completion. When the contract’s bill items differ from control packages, retain an explicit mapping. Agree the handling of shared preliminaries so they are neither omitted nor counted in several packages.

NASA’s tutorial measures earned work on the same basis as the plan. It compares earned value with incurred cost from accounting records for cost variance, and with planned value for schedule variance; favourable and unfavourable results both require investigation. [3]

Our illustrative example uses budget units, not Iranian prices or project results. Suppose a package budget is 100, its planned value at the reporting date is 50, verified work earns 40, and incurred cost is 60. The cost variance is 40 minus 60, or minus 20; the schedule variance is 40 minus 50, or minus 10 budget units. Neither figure states days of delay.

Before drawing conclusions, reconcile the period. Ask the responsible cost team to include costs incurred for the measured work that have not yet been invoiced, using approved recognition and estimation policies. Identify provisional amounts and replace them without double-counting when records arrive. Reconcile subcontractor work, labour, plant and materials against the same scope and date; do not mix paid cash with incurred cost.

Hold a short exception review when progress evidence or cost postings are incomplete. Show the affected package, missing record, responsible person and expected correction date. Preserve the issued snapshot and document later corrections. Do not hide uncertain costs in a favourable variance or shift progress into a different period merely because the invoice arrived late.

GAO’s cost-guide overview links reliable estimating to a technical baseline, work breakdown structure, assumptions, data, risk analysis and updates using actual costs. Its stated applications include construction and maintenance projects as well as other capital and non-capital programmes. [4]

Ask each package owner to rebuild the remaining estimate from the actual unfinished scope. Review remaining quantities, crew productivity assumptions, procurement commitments, access restrictions, testing, rework and time-related site costs. Present incurred cost to date plus the estimate to complete as the forecast total, with a stated boundary. Explain differences from the approved budget instead of treating the unspent balance as the remaining forecast.

Where currencies, supplier quotations or price bases differ, record the approved conversion convention, quotation date, validity and uncertainty. Keep the performance baseline identifiable while explaining the basis used for the current forecast. Test project-specific alternatives for unavailable materials, changed sequences or delayed access; do not insert a supposed Iranian inflation rate or exchange rate without a verified, relevant basis.

Keep approved changes, proposed changes and disputed entitlement visible as different statuses. Obtain the necessary authorization before revising the baseline and retain the prior version. Show pending-scope exposure separately and explain whether it is included in each forecast scenario. Repricing the original budget to erase an adverse result removes the comparison that management needs.

GAO’s schedule-guide overview explains that a credible cost estimate must address the cost effects of schedule slippage. It treats an integrated schedule as a model of when activities and major events can finish, not simply a record of expenditure. [5]

Ask the scheduler to review the remaining logic, critical and near-critical work, access, resources, approvals and procurement dates alongside the cost forecast. Check whether a favourable aggregate progress result hides a delayed package needed by several following trades. Do not convert a budget-based schedule variance into a promised completion date; retain the separately reviewed schedule forecast.

For an Iranian site, discuss actual constraints rather than assuming a standard national pattern. A particular supplier’s confirmed delivery, available specialist crew, inspection slot, seasonal working condition or owner access decision may change the remaining sequence. Record the evidence and decision owner. If the team proposes acceleration, review feasibility, additional cost and safety or quality consequences before treating it as the recovery plan.

Connect every material variance to an action that can be checked at the next review. State the cause supported by evidence, expected impact, proposed response, responsible person and due date. Distinguish a correction to bad data from a change to how work will be executed. Neither the report nor an automated recommendation authorizes an unsafe method or a contractual instruction.

Start with one consequential package and two reporting cycles. Before the first close, agree the budget, time-phased plan, earning rules, cost mapping and revision authority. At each close, retain the quantity or milestone evidence, inspection status, cost reconciliation, provisional amounts, remaining estimate and action record. Ask a reviewer outside the package team to reconstruct one reported result from that bundle.

Track the share of reported earned value supported by the agreed evidence, the share of incurred cost still provisional, unresolved scope-mapping exceptions, late corrections and overdue actions. Define denominators and cutoff dates. Compare successive forecasts on a consistent scope basis and explain revisions. These are measures of reporting discipline, not guaranteed savings or proof that the entire project is healthy.

Expand only when the pilot shows that site, cost and schedule teams can sustain the same definitions. A controlled register and reproducible export may be sufficient initially; specify software interoperability, permissions and audit history when more tooling is justified. Do not claim full earned-value-system compliance from this limited pilot or mistake an attractive chart for a reviewed forecast.

The useful outcome is a decision-ready explanation of what was achieved, what it cost and what remains—not one reassuring percentage. Contracts control payment and entitlement; applicable requirements, approved accounting policies, engineering and commercial review, and actual site conditions control implementation. The cover’s balance distinguishes physical work from paperwork as an editorial metaphor, not a valuation method.