19.3 Supporting Tenders, Procurement, Audits, Field Verification & Recovery
Key Takeaways
- Field quantity verification must use the same basis as payment — verifying actual placed quantity against a contract that pays theoretical neat-line quantity produces a contractual difference, not an error.
- Buried and covered work must be verified before it is concealed, which makes verification itself a scheduled activity rather than a reporting task.
- Bid analysis requires normalizing scope across bidders, comparing against the owner's independent estimate, and testing unit-rate balance; front-end loading is detected by comparing the rate profile line by line, not the totals.
- An abnormally low bid is a risk finding rather than a saving, usually reflecting scope misunderstanding, error, or a buy-in to be recovered through claims.
- A recovery plan must quantify the gap in dollars and weeks, state the root cause, price each option including the productivity decay of acceleration, assign owners and dates, and end with a specific decision request.
19.3 Supporting Tenders, Procurement, Audits, Field Verification & Recovery
The remaining Domain 2 tasks describe the recurring services a cost engineer provides to other functions: 2.C verify field quantity takeoffs, 2.D support tender/bid process, 2.F support external stakeholder requests (audits, reviews), 2.I review construction plans for cost and schedule implications, 2.O support procurement process, 2.P develop contingency/recovery plans, and 2.Q recommend corrective actions.
1. Verifying Field Quantity Takeoffs (Task 2.C)
Field quantity verification is the physical foundation of both progress measurement and payment. The cost engineer's role is usually to verify, not to perform, the takeoff.
| Verification technique | Best for | Limitation |
|---|---|---|
| Independent re-measure | High-value, disputed quantities | Slow and resource-intensive |
| Sample re-measure with tolerance | Routine monthly quantities | Sampling risk; needs an agreed tolerance |
| Model-based takeoff comparison | Modelled scope (steel, piping, concrete) | Model must match as-built reality |
| Installed-versus-issued reconciliation | Bulk commodities | Does not detect installed-but-wrong |
| Photographic and survey evidence | Buried and covered work | Must be contemporaneous |
Two rules:
- Verify against the same basis as the payment. If the contract pays on theoretical neat-line quantity, verifying against actual placed quantity produces a difference that is contractual, not an error.
- Verify buried work before it is covered. Once concrete is poured or a trench backfilled, verification cost rises by orders of magnitude and evidentiary weight falls. This is a scheduling constraint on the verification activity itself.
2. Supporting Tender and Procurement (Tasks 2.D and 2.O)
The cost engineer's contribution to a tender is the owner's independent estimate and the structured bid comparison.
Bid analysis is not lowest-price selection
| Analysis step | What it reveals |
|---|---|
| Normalize the bids | Bidders exclude different things; the comparison is invalid until scope is aligned |
| Compare against the owner's estimate | A bid far below the estimate signals misunderstanding or a buy-in, not a bargain |
| Compare bid composition | An outlier in one component identifies where a bidder's assumptions differ |
| Test the unit rates for balance | Front-end loading and unbalanced bidding transfer cash-flow risk to the owner |
| Evaluate commercial terms | Payment terms, escalation clauses, and liability caps carry real value |
| Assess total cost of ownership | Operating cost, spares, and life-cycle cost, not award price alone |
Front-end loading deserves specific attention: a bidder inflates early-activity rates (mobilization, excavation) and deflates late ones, so the total matches but the owner over-pays early and holds inadequate retention against unfinished work. Detecting it requires comparing the rate profile against the owner's estimate line by line, not just the totals.
[!IMPORTANT] An abnormally low bid is a risk finding, not a saving. A bid 25% below both the owner's estimate and the next bidder usually reflects a scope misunderstanding, an error, or a deliberate buy-in that will be recovered through claims. The cost engineer's job is to identify the gap and quantify it, so that the award decision is made with the exposure visible.
3. Supporting External Audits and Reviews (Task 2.F)
Audits test whether reported numbers are supported. Preparation is mostly governance work already done — or not done — long before the auditor arrives.
What an audit will ask for, and what must therefore exist:
- The approved baseline and every approved revision, with the change authority for each.
- A reconciliation from the estimate to the budget to current forecast, with each movement attributed.
- Support for actual costs: invoices matched to purchase orders and to receipt or measurement records.
- The accrual basis, showing how period-end accruals were derived and reversed.
- The progress measurement rule for each work package, and evidence it was applied consistently.
- The contingency register, showing drawdowns tied to identified risks.
- Segregation-of-duties evidence on commitment and payment approval.
[!TIP] Answer only what is asked, in writing, from the record. Speculating in an audit interview creates statements that later have to be corrected. The correct posture is to provide the documented basis and to say plainly when something is not documented — which is also what the Canons of Ethics require of objective and complete reporting.
4. Reviewing Construction Plans (Task 2.I)
Reviewing an execution plan for cost and schedule implications means testing whether the plan is physically and commercially achievable.
| Plan element | Cost/schedule question |
|---|---|
| Sequence and phasing | Does it create congestion, trade stacking, or double handling? |
| Manning curve | Is peak manning achievable from the local labour market, and does the peak-to-average ratio imply congestion? |
| Temporary works and site facilities | Are they costed, and does the duration assumption match the schedule? |
| Heavy lift and crane strategy | Is crane time a hidden critical path, and is standby cost accounted for? |
| Shift pattern | Does sustained overtime carry a productivity decay allowance, or only a premium? |
| Weather and seasonal windows | Is the productivity allowance consistent with the season the work now falls in? |
| Logistics and laydown | Is double handling of materials priced? |
| Interface with operations | Are shutdown or tie-in windows fixed, and what does missing one cost? |
5. Contingency and Recovery Plans, and Corrective Action (Tasks 2.P and 2.Q)
A recovery plan is a costed, scheduled, and owned response to an adverse trend. The blueprint asks a cost engineer to develop it — which means it must be quantified, not aspirational.
A defensible recovery plan contains:
- The quantified gap. "Forecast exceeds authorized budget by $6.4M and completion is 7 weeks beyond the contract date." Not "we are behind."
- The root cause, from the variance decomposition of Section 18.3 — rate, efficiency, quantity, scope, or schedule.
- The option set with costs. Each option priced, including its own risk. Typical options: re-sequence, add crew, add shifts, change method, de-scope, accept and re-baseline.
- The net effect of each option. Acceleration usually costs money to save time; de-scoping saves money and time but changes the deliverable. Section 9.1's crashing analysis is the quantitative tool.
- Owner, dates, and measurement. Who does what by when, and which KPI will show whether it worked.
- The decision requested. Recovery plans that end without a specific decision request are not plans.
Corrective action versus recovery
| Corrective action (2.Q) | Recovery plan (2.P) | |
|---|---|---|
| Trigger | A specific variance or trend in one account | Project-level forecast breach |
| Scale | Local, within existing authority | Cross-functional, usually needs approval |
| Typical content | Re-brief a crew, fix a coding error, expedite a delivery, correct a progress rule | Re-sequence, resource, de-scope, re-baseline |
| Approval | Project manager or below | Sponsor or steering committee |
[!WARNING] Acceleration is not free and rarely linear. Adding crew to a congested work face, or extending scheduled overtime, buys time at a cost that rises faster than the time saved — and beyond a point buys no time at all. Every recovery option must be priced with its productivity effect included, or the plan will consume budget without recovering schedule.
Four bids are received. Bidder C's price is 25% below both the owner's independent estimate and the next-lowest bid. How should the cost engineer characterize this in the award recommendation?
A schedule of rates shows a bidder's mobilization and excavation rates roughly 40% above the owner's estimate, while its finishing and commissioning rates are about 35% below, with the bid total matching the estimate closely. What is this pattern, and why does it matter?
A project forecast now exceeds the authorized budget by $6.4 million with completion seven weeks past the contract date. Which recovery plan is defensible?