17.4 Cost System Governance, the Code of Accounts & Preserving Project Controls Data
Key Takeaways
- Blueprint task 1.P (adhere to cost system governance requirements) and task 2.R (preserve critical project controls systems data) make cost-system integrity directly examinable.
- A reported variance is only meaningful when budget, commitment, accrual, and actual were captured against the same code structure, in the same period, under the same policies.
- The WBS answers what scope, the code of accounts answers what kind of cost, the OBS answers who is responsible, and the control account is the WBS-OBS intersection where cost is measured.
- An allowance covers known scope not yet detailed and belongs in the base estimate, while contingency covers identified risk and is held separately — conflating them understates the base and overstates the risk provision.
- Native-format schedules, every baseline revision, contemporaneous daily reports, and quantity records must be preserved through contract audit-rights and retention clauses; a legal hold suspends routine destruction once a dispute is anticipated.
17.4 Cost System Governance, the Code of Accounts & Preserving Project Controls Data
Two blueprint tasks cover the infrastructure that everything else runs on: 1.P adhere to cost system governance requirements and 2.R preserve critical project controls systems data. They look administrative. They are examined because a cost professional who cannot defend the integrity of the cost system cannot defend any number that comes out of it — in an audit, in a claim, or in front of a board.
1. What Cost System Governance Means
Governance is the set of rules that make cost data consistent, traceable, and defensible across the organization and over time.
| Governance element | What it fixes | Consequence when absent |
|---|---|---|
| Standard code of accounts | One structure for capturing cost | Projects cannot be compared or benchmarked |
| Chart of accounts mapping | Project codes tie to the general ledger | Project cost and corporate cost never reconcile |
| Documented cost policies | When to accrue, how to capitalize, how to treat escalation | Each project invents its own accounting |
| Authorization thresholds | Who may commit or approve what value | Uncontrolled commitment |
| Change control procedure | Nothing moves the baseline without approval | Baseline drifts and variance becomes meaningless |
| Segregation of duties | The person estimating is not the sole approver | Fraud and error exposure |
| Period cutoff calendar | All data streams use the same cutoff | Manufactured variances |
| Records retention schedule | Data survives to when it is needed | Claims and audits cannot be defended |
[!IMPORTANT] Governance is what makes a variance explainable. A cost variance is only meaningful if the budget, the commitment, the accrual, and the actual were all captured against the same structure, in the same period, under the same rules. When those conditions fail, the reported variance measures the accounting system, not the project.
2. The Code of Accounts
The code of accounts (COA) is the classification structure for cost. It is distinct from, and must be mapped to, the WBS.
| Structure | Answers | Example |
|---|---|---|
| WBS | What scope? — deliverable-oriented decomposition | 1.3.2 Compressor Building |
| Code of accounts | What kind of cost? — resource/commodity classification | 4200 Structural steel; 6100 Craft labor |
| OBS | Who is responsible? | Mechanical Construction |
| Control account | Intersection of WBS and OBS where cost is measured | 1.3.2 x Mechanical Construction |
A well-formed cost code is a composite of these dimensions, which is what allows the same actual cost to be reported by deliverable, by commodity, and by responsible organization without re-entering it.
Three properties matter for the exam:
- Stability. The COA must not change mid-project. Re-coding history destroys trend continuity, and trend is the basis of forecasting.
- Granularity discipline. Codes finer than the organization can reliably capture produce garbage. If the field cannot distinguish two codes at time entry, the split is fiction.
- Bidirectional mapping. Estimate codes, schedule activity codes, and accounting codes must map to each other. Where the mapping is many-to-many, variance analysis becomes impossible.
3. Capitalization and Cost Treatment
Governance also fixes cost treatment questions that have real financial consequences:
- Capital versus expense. Costs that create or extend an asset are capitalized and depreciated (see Chapter 6); costs of operating are expensed in the period. Misclassification distorts both the project's reported cost and the company's tax position.
- Allowance versus contingency. An allowance covers known scope whose detail is not yet defined and belongs in the base estimate. Contingency covers identified risk and is held separately. Treating an allowance as contingency understates the base estimate and overstates the risk provision.
- Escalation. Whether the baseline is in constant or current dollars must be declared once and applied consistently. Mixing them is a classic estimate error.
- Interest during construction and owner's costs. Governance states whether these are inside the project cost or held corporately.
4. Preserving Project Controls Data (Task 2.R)
Task 2.R sits inside the Interface with Other Disciplines domain because preservation depends on IT, records management, legal, and the contractor — not on the cost engineer alone.
| What must survive | Why | Typical loss mechanism |
|---|---|---|
| Native schedule files, every update | Delay analysis needs the as-planned and each as-updated schedule in native format | Only PDFs archived; logic and calendars lost |
| Baseline and every approved revision | Establishes what was agreed and when it changed | Overwritten in place |
| Estimate files with basis and backup | Defends the estimate and supports change pricing | Estimator leaves, files leave with them |
| Daily reports, timesheets, quantity records | The evidentiary core of any productivity or disruption claim | Contractor retains and later withholds |
| Correspondence, RFIs, change logs | Establishes notice and causation | Lives in individual mailboxes |
| Photographs and survey records | Contemporaneous physical evidence | Never centrally filed |
Preservation rules that the exam expects a cost professional to know:
- Contemporaneous records outweigh reconstructions. A record made at the time carries far more evidentiary weight than an after-the-fact analysis, regardless of how rigorous the analysis is.
- Native format matters. A schedule delivered only as a PDF cannot be re-run; the underlying logic, calendars, and constraints are gone.
- Contract terms must require it. Access to the contractor's cost and schedule records must be secured in the contract — audit rights, record retention obligations, and format requirements. It cannot be negotiated after a dispute starts.
- A legal hold suspends routine destruction. Once a dispute is reasonably anticipated, the normal retention schedule stops applying to relevant records.
[!WARNING] The most expensive governance failure is a missing baseline schedule. Projects routinely archive the final schedule and overwrite everything before it. Without the as-planned schedule and the sequence of updates, every recognised delay analysis method becomes unavailable, and an otherwise valid claim fails on evidence rather than on merit.
Midway through execution, a corporate finance initiative proposes re-coding the project's cost history into a new enterprise chart of accounts, remapping historical actuals to the new structure. What is the principal project controls objection?
An estimate includes $2,400,000 described as covering 'small-bore piping and supports not yet designed, based on historical percentage of major piping.' A reviewer proposes reclassifying this amount as contingency. What is the correct treatment under AACE terminology?
Two years after completion, a contractor files a disruption claim. The owner's project team archived the final as-built schedule as a PDF and overwrote each monthly schedule update in place. Why is this the most damaging records failure, and what contract provision should have prevented it?