Cost Estimates Through the Project Lifecycle

How Estimates Evolve Through the Project Lifecycle

Cost estimates are not static. They evolve as projects progress through the Queensland Project Framework phases, with each estimate reflecting increasing levels of design maturity, reduced uncertainty, and refined scope understanding.

The accuracy and detail of cost estimates improve progressively as projects move from strategic planning through to implementation. Early estimates are necessarily broad and include larger contingencies to reflect uncertainty. As design develops and risks are understood, estimates become more precise and contingencies reduce.

This progression is deliberate and valuable. Early estimates inform investment prioritisation and strategic planning without requiring expensive detailed design. Later estimates support procurement and project controls with the precision necessary for contractor selection and cost management.

Critical Concept: Each project phase has specific decision-making requirements, and estimates must be fit-for-purpose for those decisions. A strategic planning estimate suitable for 10-year programming would be inappropriate for tendering, just as a detailed tender estimate would be wasteful during early concept development. Understanding what each estimate phase must achieve is fundamental to effective project cost management.

The Five Project Lifecycle Phases

The Queensland Project Framework defines five key phases through which infrastructure projects progress:

Strategic/Detailed Planning: Investment prioritisation and program development
Concept: Business case development and options analysis
Development: Detailed design and tender preparation
Implementation: Construction delivery and contract management
Finalisation: Project completion and lessons learned

Each phase requires specific types of cost estimates with defined accuracy expectations, methodologies, and governance requirements.

Strategic/Detailed Planning Phase

Estimates in this phase guide early-stage prioritisation and inform the 10-year Transport Infrastructure Project Prioritisation System (TIPPS).

Purpose and Context

Strategic planning estimates support high-level investment decisions before significant resources are committed to project development. These estimates help determine:

Which potential projects warrant further investigation
Approximate funding requirements for long-term capital programs
Comparative costs of strategic alternatives
Order-of-magnitude benefits versus costs

Estimating Approach

Strategic planning estimates are typically developed using global estimating methods:

Composite rates: High-level unit rates applied to key project parameters (e.g., $/lane-km for road projects, $/station for rail)
Historical rates: Costs from similar completed projects adjusted for scope differences, location, and escalation
Benchmark data: Industry-standard cost ranges for project types and scales
Parametric models: Statistical relationships between project characteristics and costs

These methods are appropriate given the limited design information available at this stage. They provide sufficient accuracy for strategic decisions without requiring detailed quantity take-offs or design development.

Work Breakdown Structure Level

Strategic planning estimates are typically structured at:

WBS Level 2 (major cost categories) as the primary breakdown
Selected Level 3 items for supporting detail where significant cost impacts are anticipated

This level of detail is sufficient for strategic comparison and programming without excessive effort on projects that may not proceed beyond planning stages.

Expected Accuracy and Contingency

Due to limited design information and high uncertainty:

Expected accuracy range: typically -30% to +50% or broader
Contingency allowances: 30-50% of base estimate to reflect uncertainty
Estimates presented as ranges rather than point values where appropriate

Key Deliverable

Strategic planning estimates feed into long-term capital works programs like TIPPS, where they inform investment prioritisation across multiple competing projects. The estimate must be defensible and documented, but does not require the rigour of business case estimates.

Concept Phase

The Concept Phase produces the most critical estimates in the project lifecycle: those that support investment decisions and establish the project budget envelope.

Concept phase estimates are used for high-stakes decision-making, including government budget approvals and public commitments. Consequently, they require significantly greater rigour than strategic planning estimates.

Project Proposal / SASR Estimates

The first formal estimate in the Concept Phase supports the Strategic Assessment of Service Requirement (SASR) and Project Proposal:

Purpose: Secure approval to proceed with business case development
Scope definition: Preliminary scope based on identified service needs
Method: Refined global estimates or preliminary unit rate estimates
Accuracy: Typically -20% to +30%
WBS detail: Levels 1-2 with selected Level 3 items

Options Analysis / Preliminary Evaluation Estimates

As the business case develops, multiple options are evaluated and compared:

Purpose: Enable objective comparison of alternative solutions
Requirement: Consistent estimating methodology across all options for fair comparison
Method: Combination of unit rates and first principles for differentiating elements
Accuracy: Sufficient to distinguish meaningful cost differences between options
Documentation: Clear identification of cost drivers and differentiators between options

Comparative accuracy is more important than absolute accuracy at this stage. Estimates must use consistent assumptions and methods so that cost differences between options are meaningful.

Business Case Estimates - The Critical Milestone

The Business Case estimate is arguably the most important estimate in the entire project lifecycle. It establishes the funding envelope, informs ministerial and cabinet decisions, and becomes the baseline against which project performance is measured.

Mandatory P50 and P90 Confidence Levels: Business case estimates MUST present both P50 (median, 50% confidence) and P90 (90% confidence) values. This explicitly acknowledges uncertainty and ensures decision-makers understand the range of potential outcomes. Funding is typically approved at P90 to provide high confidence of budget sufficiency.

Business Case Estimate Requirements

Estimating method: First principles and unit rates (global estimates not sufficient)
WBS structure: Levels 1-3 mandatory, selected Level 4 for major elements
Risk assessment: Comprehensive risk workshop and quantified risk register
Contingency: Probabilistic analysis (Monte Carlo) to determine P50 and P90
Validation: Independent peer review mandatory
Concurrence review: Required for projects exceeding $25 million
Accuracy expectation: P50 typically -10% to +15%, P90 provides high confidence buffer

Business Case Estimate Components

A comprehensive business case estimate includes:

Base estimate: Most likely cost of all scope elements
Risk allowance: Quantified cost of identified risks
Contingency: Allowance for uncertainty and unknown risks
Escalation: Cost increases over time to project completion
Outturn cost: Total funding requirement in year-of-expenditure dollars

Estimate Component	P50 Treatment	P90 Treatment
Base Estimate	Most likely cost	Most likely cost
Risk Allowance	Median risk cost (50% probability)	High confidence risk cost (90% probability)
Contingency	Moderate allowance for unknowns	Substantial allowance for unknowns
Escalation	Based on Treasury parameters	Based on Treasury parameters
TOTAL (Outturn)	50% confidence total	90% confidence total

Why P90 Matters

The P90 estimate provides 90% confidence that the project can be delivered within budget. This high confidence level is appropriate for government funding decisions because:

Budget overruns have political and reputational consequences
Government funding is typically fixed rather than contingent
Projects compete for limited capital, so budget reliability is critical
Public accountability demands projects be delivered within approved funding

However, P90 should not be viewed as a target or as "free money" to spend. It represents the prudent funding level given uncertainty, and should reduce as risks are retired and design matures.

Cenex Business Case Expertise

Cenex specializes in business case estimates that meet all PCEM requirements. Our probabilistic risk analysis capability ensures robust P50/P90 values, while our CE1 pre-qualification provides confidence that estimates will withstand concurrence review scrutiny. We understand that business case estimates set the project budget envelope and deliver estimates that are defensible, realistic, and approval-ready.

Development Phase

Development phase estimates support detailed design and procurement, with increasing precision as design matures toward construction-ready documentation.

Stage 1 Design (S1D) Estimates

S1D estimates are developed once preliminary design (typically 15-30% design completion) is available:

Purpose and Function

Budget verification: Confirm the project remains within the business case funding envelope
Value engineering: Identify opportunities for cost optimization while meeting project objectives
Scope refinement: Support decisions on scope inclusions and priorities
Risk update: Reassess risks based on design development

Estimating Characteristics

Method: Predominantly first principles with detailed quantity take-offs where design permits
WBS detail: Levels 1-3 comprehensive, expanding Level 4 detail
Accuracy target: -10% to +15% at P50
Contingency: Reducing from business case levels as design matures

S1D estimates often reveal scope elements that were underestimated or not fully considered during business case development. This is a critical reality check before significant design investment continues.

Important: If the S1D estimate significantly exceeds the business case budget, project sponsors must make difficult decisions: seek additional funding, descope the project, or cancel/defer the project. Early identification through S1D estimating is far preferable to discovering budget shortfalls during or after tendering.

Stage 2 Design (S2D) Estimates

S2D estimates accompany detailed design (typically 90-100% complete) immediately prior to tender release:

Purpose and Function

Tender expectation: Establish the expected market price for contract award
Budget confirmation: Final verification before market engagement
Tender evaluation: Provide the baseline for assessing tender submissions
Procurement strategy: Inform decisions on packaging and contract strategy

Estimating Characteristics

Method: Detailed first principles with comprehensive quantity take-offs from final design
WBS detail: Levels 1-4 comprehensive, selected Level 5 for complex elements
Accuracy target: -5% to +10% at P50
Contractor perspective: Estimating from the contractor's perspective, including overheads, profit, and risk pricing
Market conditions: Explicit consideration of current market pricing, availability, and risk appetite

S2D estimates should closely approximate tender prices if design is complete and market conditions are well understood. Significant divergence suggests either estimating issues or market factors requiring investigation.

Estimate for Comparison with Tenders (EFCT)

The EFCT is prepared specifically for tender evaluation and may be a refined version of the S2D estimate:

Key Requirements

Based on the exact scope and specifications in tender documentation
Incorporates latest market intelligence from pre-tender market soundings
Structured to align with tender evaluation criteria and schedule of rates
Provides the reference point for tender evaluation and negotiation
Must remain confidential to avoid influencing tender prices

The EFCT gives the client confidence that tender prices are fair and reasonable. Tenders significantly above or below the EFCT warrant investigation before award.

Agreed Project Delivery Value (APDV)

Once tenders are evaluated and a preferred contractor selected, the APDV is established:

Definition and Purpose

The APDV is the negotiated contract sum plus client-side costs (e.g., project management, independent certification, remaining design). It becomes the formal project budget for delivery.

APDV Components

Contract sum: The awarded construction contract value
Client costs: Project management, supervision, testing, commissioning
Authority contingency: Client-held contingency for variations and risks
Escalation: Remaining escalation to project completion

The APDV is compared to the business case budget to verify the project remains affordable. If APDV exceeds available funding, either additional funding must be secured or scope reduced before contract award.

Development Phase Estimate	Design Maturity	Primary Purpose	Expected Accuracy (P50)
S1D	15-30% design	Budget verification and value engineering	-10% to +15%
S2D	90-100% design	Tender expectation and procurement	-5% to +10%
EFCT	100% tender docs	Tender evaluation and negotiation	-5% to +10%
APDV	100% + contract award	Project delivery budget	Actual contract price

Implementation Phase

During construction, estimating shifts from pre-contract estimates to forecasting and variation assessment to support active cost management and control.

Cost Forecasting and Periodic Updates

Throughout construction, regular cost forecasts are prepared to track expenditure against budget and predict final outturn:

Forecast Components

Committed costs: Contract sum and approved variations
Anticipated costs: Pending variations and known changes
Contingency draw-down: Tracking utilization of contingency allowances
Forecast final outturn: Predicted total cost at project completion

Forecasting Frequency

Cost forecasts are typically updated:

Monthly as part of project reporting and dashboard updates
Quarterly for executive and governance reporting
On-demand when significant changes or risks emerge

Effective forecasting enables proactive cost management, identifies emerging issues early, and supports informed decision-making on scope trade-offs and risk mitigation.

Contract Variation Estimates

When changes to contracted scope occur, variation estimates must be prepared:

Variation Estimating Requirements

Detailed scope definition: Clear description of what has changed from baseline contract
Independent assessment: Client-side estimate before contractor pricing where practical
Schedule of rates: Application of contract rates where applicable
Market rates: Current market rates for new work outside contract scope
Time impacts: Assessment of program delay and associated costs
Documentation: Audit trail supporting variation approval

Variation management is a critical cost control function. Having independent variation estimates ensures the client can negotiate fair pricing and identify unreasonable contractor claims.

Change Management and Contingency Draw-Down

Authority-held contingency is drawn down during implementation for approved scope changes and realized risks:

Contingency Management Principles

Contingency is not "extra budget" but an allowance for uncertainty that should reduce as uncertainty resolves
Draw-down requires formal approval based on demonstrable need
Remaining contingency is forecast against remaining risks and anticipated changes
Depletion of contingency triggers escalation and management response

Implementation Phase Reality

Implementation is where estimates meet reality. Even well-prepared estimates face unexpected site conditions, design clarifications, stakeholder changes, and contractor claims. Effective cost management during implementation requires constant vigilance, robust variation assessment, and transparent forecasting to ensure projects complete within approved budgets.

Finalisation Phase

After construction completion, the finalisation phase captures actual costs, documents lessons learned, and contributes to the knowledge base for future estimates.

Final Cost Documentation

Comprehensive documentation of final project costs provides critical data for future estimating:

Required Documentation

Actual costs: Final contract sum including all variations
Client costs: All project management, design, and ancillary costs
Total project cost: All-in cost for complete project delivery
Cost breakdown: Actual costs by WBS element for benchmarking
Unit rates: Derived actual unit rates for SmartCost database

Post Implementation Review (PIR)

The PIR is a formal review conducted after project completion to assess performance and capture lessons learned:

Cost Estimating Components of PIR

Budget performance: Comparison of final costs to business case, S1D, S2D, and APDV estimates
Variance analysis: Understanding why estimates varied from actual costs
Risk realization: Which risks materialized and at what cost impact
Scope changes: Documenting approved changes and their cost effects
Estimating accuracy: Assessment of estimate quality and areas for improvement

Contribution to SmartCost Database

Final project costs are submitted to Queensland's SmartCost database to inform future estimates:

SmartCost Submission Requirements

Structured cost data by PCEM WBS elements
Project characteristics (location, scale, delivery method, etc.)
Unit rates for key elements
Lessons learned and estimating notes
Context information to support future adjustment and application

This data becomes the historical foundation for Step 6 of the PCEM estimating process for future projects. The quality and completeness of SmartCost submissions directly impacts the accuracy of future Queensland infrastructure estimates.

Lessons Learned for Future Estimates

Beyond numerical cost data, finalisation should capture qualitative lessons:

What estimating assumptions proved incorrect and why
Which risks were underestimated or overlooked
What scope elements were consistently under or over estimated
How market conditions or contractor behavior differed from expectations
What estimating methods or data sources proved most reliable

Organizations that systematically capture and apply these lessons progressively improve their estimating capability and reduce the variability between estimates and outcomes.

Closing the Loop: Finalisation completes the project lifecycle by feeding actual performance back into the estimating knowledge base. This continuous improvement cycle is what makes the PCEM framework progressively more accurate and valuable. Projects that skip thorough finalisation deny the industry the learning that benefits future projects.

Summary: Estimating Methods and Detail by Phase

The following table summarizes how estimating approaches evolve through the project lifecycle:

Phase	Primary Estimates	WBS Levels	Estimating Methods	Expected Accuracy (P50)
Strategic/Detailed Planning	TIPPS submissions, strategic options	1-2, selected 3	Global, composite rates, benchmarks	-30% to +50%
Concept - Early	SASR, Project Proposal, Options Analysis	1-2, selected 3	Refined global, preliminary unit rates	-20% to +30%
Concept - Business Case	Business Case (P50 and P90 required)	1-3 mandatory, selected 4	First principles, unit rates, hybrid	-10% to +15%
Development - S1D	Budget verification, value engineering	1-3 comprehensive, expanding 4	First principles, detailed quantities	-10% to +15%
Development - S2D/EFCT	Tender expectation and evaluation	1-4 comprehensive, selected 5	Detailed first principles	-5% to +10%
Development - APDV	Delivery budget	As per contract structure	Actual contract price plus client costs	Contract certainty
Implementation	Forecasts, variations	As required for control	Actual costs plus forecast remaining	Increasing precision over time
Finalisation	Final cost capture	Full project breakdown	Actual costs	100% (actual)

Factors Influencing Estimates Across All Phases

Regardless of project phase, certain factors consistently influence costs and must be explicitly considered in every estimate:

Scope Definition

The completeness and clarity of scope documentation is the single biggest determinant of estimate accuracy. Ambiguous or incomplete scope leads to optimistic estimates and budget overruns.

Project Constraints

Time constraints, staging requirements, traffic management, and working hour restrictions all add cost. These constraints must be identified and quantified in the estimate.

Constructability

Site access, laydown areas, construction methodology, and sequencing significantly impact costs. Estimates must reflect realistic construction approaches, not idealized assumptions.

Construction Program

Overly optimistic programs lead to underestimated preliminaries and time-related costs. Programs must be realistic and validated against similar project experience.

Environmental Issues

Environmental approvals, protected species management, vegetation clearing, sediment control, and rehabilitation all carry costs that must be explicitly estimated, not assumed negligible.

Cultural Heritage

Cultural heritage surveys, management plans, and discovery protocols add costs and program risks. Queensland's Indigenous heritage and historical significance require careful consideration.

Traffic Management

Works in live traffic environments carry substantial traffic management costs. These vary dramatically based on road hierarchy, traffic volumes, and available detours.

Location

Remote locations, restricted sites, and areas with limited contractor and material availability carry location premiums. Queensland's geographic diversity requires location-specific adjustments.

Contract Delivery Method

Design-bid-build, design-construct, managing contractor, alliance, and PPP models have different risk allocations and cost structures. Estimates must align with the intended procurement approach.

Sustainability Requirements

Sustainability targets, recycled materials, emissions reduction, and environmental performance standards add costs. These requirements are increasingly common and must be explicitly costed.

Effective estimators systematically assess each of these factors for every project, documenting assumptions and quantifying cost impacts. Overlooking any factor can lead to significant budget shortfalls.

Need PCEM-Compliant Cost Estimates?

Cenex delivers CE1 pre-qualified, PCEM-compliant cost estimates for Queensland infrastructure projects.

Contact Us Today Call 0429 092 480