Baselines, Progress Measurement, and Project Control

Introduction

Construction projects are controlled against an approved plan, not against an informal expectation. The approved plan establishes what work is to be performed, when it is planned, how much it is expected to cost, and what contractual or technical conditions govern completion. During execution, actual performance is compared with that plan. The resulting information supports decisions about resources, sequencing, procurement, productivity, payment, risk, and corrective action.

Project control is therefore more than updating a bar chart. It is a disciplined cycle of establishing a baseline, collecting reliable field data, measuring progress, analysing variances, forecasting outcomes, and implementing agreed actions. Poor control may arise from an unrealistic baseline, inconsistent progress rules, late data, double counting, or failure to distinguish a revised plan from an approved change.

This chapter examines baseline management, schedule updating, physical progress, earned value management (EVM), earned schedule, forecasting, and corrective action in construction projects.

Learning Objectives

After studying this chapter, the reader should be able to:

1. Explain the purpose and components of a project baseline.
2. Establish and govern schedule, cost, and scope baselines.
3. Update a schedule using actual starts, actual finishes, remaining duration, and a data date.
4. Select suitable methods for measuring physical progress.
5. Calculate and interpret planned value, earned value, actual cost, variances, and performance indices.
6. Apply earned schedule concepts and forecast completion.
7. Diagnose causes of variance and recommend proportionate corrective action.
8. Recognise the limitations, ethical requirements, and digital implications of project control.

1. The Baseline as a Management Commitment

A baseline is an approved reference model against which actual performance is measured. It normally includes:

• a scope baseline: approved drawings, specifications, work breakdown structure (WBS), and scope statement;
• a schedule baseline: activities, logic, calendars, durations, milestones, constraints, and planned dates;
• a cost baseline: time-phased budget distributed across the work;
• a resource baseline: planned labour, plant, materials, and productivity assumptions; and
• control procedures: data dates, update frequency, progress rules, change control, and reporting responsibilities.

The baseline is not necessarily a prediction that will remain unchanged. It is the authorised plan at a defined point in time. A forecast may change frequently, but the baseline should change only through formal approval. If the baseline is altered whenever performance deteriorates, the project can appear successful while the original commitment is being concealed.

The schedule baseline should be traceable to the scope baseline and cost baseline. For example, a concrete-frame activity should have a defined quantity or deliverable, a planned duration, resource assumptions, a budget, and logical relationships to preceding and succeeding work. This integration makes it possible to answer not only “Are we late?” but also “What work is late, why is it late, and what will be the cost and completion consequence?”

1.1 Baseline quality

Before approval, the baseline should be tested for:

• completeness of scope and interfaces;
• realistic activity durations and calendars;
• logical continuity and absence of unexplained open ends;
• reasonable relationships between quantities, resources, cost, and time;
• identifiable milestones and acceptance criteria;
• alignment with contract requirements and approved changes; and
• a documented basis of estimate and schedule assumptions.

A baseline that is mathematically consistent but physically impossible is not a good baseline. For example, a programme may contain no negative float yet still require more labour than the site can accommodate or show excavation before access and permits are available.

2. Schedule Updating and the Data Date

A schedule update records the current status of the project as of a specified data date, sometimes called the status date. Information after that date should not be mixed into the update unless the reporting procedure explicitly permits it. A data date creates a common time boundary for comparing planned and actual conditions.

For each activity, the scheduler may record:

• actual start date;
• actual finish date;
• percentage or quantity complete;
• remaining duration;
• remaining quantity or effort;
• actual resources or costs, where available;
• revised logic or constraints approved through change control; and
• evidence supporting the status.

2.1 Status rules for activities

An activity not started retains its forecast start and finish, subject to logic and any approved changes. An activity in progress has an actual start, a status date, and a remaining duration or remaining quantity. An activity complete has an actual finish and should satisfy the project’s definition of completion. A reported percentage alone is inadequate unless the basis of measurement is defined.

For an activity in progress, the original duration should not be confused with remaining duration. If an activity was planned for 10 working days, has worked for 6 days, and requires 5 further working days, its forecast total duration is 11 working days. The correct update is not to force the original 10-day duration to remain unchanged.

A schedule should be recalculated after status is entered. Logic, calendars, constraints, and resource assumptions can move forecast dates. The resulting forecast should be reviewed rather than accepted automatically.

2.2 Progress records and evidence

Reliable updating depends on evidence such as inspection records, delivery tickets, approved test results, timesheets, quantity surveys, photographs, daily reports, and field verification. Photographs can demonstrate location and sequence, but they do not by themselves prove quantity or quality. A completed-looking installation may be incomplete because testing, commissioning, documentation, or inspection remains outstanding.

3. Measuring Physical Progress

Physical progress expresses the amount of objectively completed work. It should be linked to scope and should avoid both optimistic judgement and double counting. Different work types require different rules.

For quantity-based progress, a general physical completion ratio is:

where p is the proportion complete, Q_c is the verified completed quantity, and Q_b is the budget or total quantity. Both quantities must use the same unit and scope definition. If 600 m³ of a planned 1,000 m³ has been accepted, physical progress is 0.60 or 60%.

Earned value is calculated by applying this progress to the budget for the relevant work package, not by multiplying progress by actual cost. If the budget for the work package is $200,000 and physical progress is 60%, earned value is $120,000, provided the progress rule is valid.

Progress measurement should distinguish installed, accepted, and paid quantities. Contract payment may depend on retention, testing, documentation, or other conditions. Consequently, payment progress and technical progress are related but not identical.

4. Earned Value Management

Earned value management integrates scope, schedule, and cost. The three fundamental measures are:

• Planned Value (PV): the authorised budget for work scheduled to be completed by the data date;
• Earned Value (EV): the authorised budget for work actually completed by the data date; and
• Actual Cost (AC): the recorded or accrued cost of the work performed by the data date.

The budget for a work package is often called Budget at Completion (BAC) when referring to the total project or control account budget. Values should be expressed in the same monetary basis and data period. They are not necessarily cash payments: accruals, commitments, and accounting policies must be defined.

4.1 Variances and indices

Schedule variance in value terms is:

Cost variance is:

Schedule Performance Index and Cost Performance Index are:

PV, EV, and AC are monetary-valued measures in the project control currency. SV and CV also have currency units, while SPI and CPI are dimensionless ratios. When SPI or CPI equals 1.00, performance equals the measured plan or cost efficiency. A value below 1.00 indicates less earned value than planned or less value earned per unit of cost, respectively.

These interpretations assume that the baseline is credible, scope is stable or changes are properly incorporated, and PV, EV, and AC are measured consistently. EVM schedule variance is not calendar time. It indicates the value of work completed relative to the value planned, and it becomes zero at completion even if the project finishes late. This limitation is one reason earned schedule is useful.

4.2 Worked example: integrated EVM

An illustrative construction project has a BAC of $2,000,000. At the data date, the time-phased baseline shows PV = $900,000. Verified completed work has a budgeted value of EV = $800,000, and recorded/accrued cost is AC = $1,000,000.

Therefore:

The negative schedule variance indicates that less budgeted work has been completed than planned. The cost variance indicates that the completed work cost more than its budgeted value. The project has earned $0.80 of budgeted value for each dollar of actual cost. These indicators do not identify the cause; field investigation is still required.

5. Forecasting Cost and Time

Forecasting uses current performance information to estimate likely completion outcomes. No single forecast is universally correct; the selected method should reflect the cause of variance and the reliability of current data.

A simple estimate at completion is:

where EAC is Estimate at Completion. This formula assumes that current cost efficiency will continue for the remaining work. An alternative, when past variance is considered unusual and the remaining work is expected to follow the original budget, is:

A combined schedule-and-cost assumption may use:

This should be used cautiously. It assumes that schedule inefficiency will translate into additional cost inefficiency and that the indices are meaningful. It is not a substitute for a bottom-up estimate.

Estimate to Complete is:

Variance at Completion is:

For the worked example, using the continuing-CPI assumption:

Thus, ETC = $1,500,000 and VAC = −$500,000. The result is a forecast, not an inevitable outcome. It should be compared with a detailed estimate of remaining quantities, productivity, commitments, risks, and approved changes.

5.1 Forecasting completion time

The schedule forecast should normally be obtained from a logic-based schedule update using actual dates and remaining durations. A rough EVM-based approximation sometimes used is:

This approximation assumes that the measured SPI represents future time performance and that the index is stable. Because EVM schedule variance is value-based and can be distorted by activity weighting, the approximation should not replace critical-path analysis.

6. Earned Schedule

Earned schedule (ES) translates earned value into time by identifying when the planned-value curve reached the current earned value. If the project has earned $800,000 and the baseline planned to earn that amount at week 18, then ES is 18 weeks, even if the current data date is week 20.

The time-based schedule variance is:

and the earned schedule performance index is:

where AT is actual time elapsed from the baseline start to the data date. ES and AT must use the same time unit and reference origin. A negative SVₜ indicates time behind the baseline; SPIₜ below 1.00 indicates reduced time efficiency.

When ES lies between two baseline time points, linear interpolation may be used if the planned-value curve is treated as approximately linear over that interval. If PV at week 17 is $750,000 and PV at week 18 is $850,000, and EV is $800,000, then:

At week 20, SVₜ = 17.5 − 20 = −2.5 weeks and SPIₜ = 17.5 ÷ 20 = 0.875. Earned schedule is informative for time performance, but it still depends on the quality of the baseline and the assumption that value weights represent meaningful progress.

7. From Variance to Corrective Action

A variance is a signal, not a diagnosis. Effective control follows a structured process:

1. Detect: identify schedule, cost, quantity, quality, safety, or productivity deviation.
2. Validate: confirm the data, measurement rule, accounting treatment, and baseline status.
3. Diagnose: determine whether the cause is design information, access, procurement, labour, equipment, weather, rework, productivity, interface failure, or an approved change.
4. Assess: evaluate effects on critical path, cost, quality, safety, contractual obligations, and risk.
5. Select action: choose a proportionate response with an owner and due date.
6. Implement: execute the action and record decisions.
7. Verify: measure whether the action produced the intended improvement.

Corrective action may include resequencing, releasing design information, adding a second shift, changing work methods, improving material logistics, increasing supervision, accelerating procurement, or negotiating an approved change. Acceleration should not be ordered without considering congestion, safety, quality, fatigue, and cost.

A recovery plan should state the affected activities, proposed logic or resource changes, assumptions, expected gain, additional cost, risks, responsible persons, and verification dates. A revised forecast is not automatically a revised baseline. If the owner approves a scope or time change, the change should be documented, priced where required, and incorporated through controlled baseline revision.

8. Applied Case: Illustrative Hospital Extension

Background

An illustrative 18-month hospital extension has a BAC of $12 million. The approved baseline includes structural works, building services, finishes, testing, and handover. Reporting is monthly, with progress measured through quantities and weighted milestones.

Problem

At month 9, the report shows PV = $6.0 million, EV = $5.1 million, and AC = $6.2 million. The contractor reports that the project is “90% complete” based mainly on the number of activities marked complete, while the commissioning milestone is not yet available.

Analysis

The control team calculates:

The activity-count claim is rejected because activities vary greatly in value and completion of finishes does not establish completion of testing or handover. Field review identifies late mechanical equipment, incomplete design information at plant rooms, and rework caused by coordination errors. The cost report also shows that materials were purchased early, increasing AC without producing equivalent EV.

Approach and solution

The team first validates quantities and separates procurement cost from installed progress. It then updates actual starts, finishes, and remaining durations using a month-9 data date. A logic review confirms that commissioning cannot start until testing and documentation are complete. The recovery plan prioritises design release, equipment delivery, coordinated access, and progressive testing rather than simply adding labour to finishing activities.

The owner approves a change for additional medical-gas outlets. That change is documented separately and incorporated into the baseline only after approval. The original baseline remains available for variance analysis, while the current approved plan becomes the basis for future reporting.

Outcome

The project team reports a credible forecast, identifies the critical commissioning path, and assigns owners to recovery actions. Monthly progress becomes evidence-based. Although the project does not immediately return to the original completion date, management gains visibility of the likely outcome and can make informed decisions about acceleration and stakeholder communication.

Learning points

The case demonstrates that activity counts can misrepresent progress, procurement expenditure is not automatically earned value, and a schedule update must reflect remaining work. It also illustrates the importance of distinguishing a forecast, a recovery plan, an approved change, and a baseline revision.

9. Governance, Ethics, and Digital Practice

Project controls professionals have a duty to report faithfully. Common unethical practices include backdating actual finishes, claiming progress without evidence, moving activities to hide delay, changing weights after the fact, omitting accruals, and resetting the baseline without approval. Such practices can mislead clients, lenders, subcontractors, regulators, and safety decision-makers.

Governance should define who may approve baselines, who may enter status, how evidence is retained, and how changes are authorised. Audit trails should preserve the original baseline, approved revisions, update history, and source records. Commercial confidentiality and personal data must also be protected.

Digital tools can integrate scheduling, cost systems, quantity records, building information models, field applications, and dashboards. Artificial intelligence may assist with anomaly detection, progress classification from images, forecast risk, and natural-language reporting. However, automated recognition can misclassify installed work, and a model may reproduce biased or incomplete data. Human verification, data provenance, access control, cybersecurity, and clear accountability remain essential. AI should support professional judgement, not replace contractual measurement or engineering acceptance.

10. Best-Practice Control Cycle

A robust monthly control cycle includes:

• freeze and archive the approved baseline;
• establish the data date and reporting calendar;
• collect field quantities and documentary evidence;
• enter actual starts, finishes, remaining durations, and costs;
• recalculate the schedule and review logic and critical path;
• calculate PV, EV, AC, variances, indices, and forecasts;
• investigate material and recurring deviations;
• agree corrective actions with owners and dates;
• record approved changes separately from performance variance; and
• communicate a concise, evidence-based report.

Control thresholds should be established in advance, but thresholds should not become excuses to ignore emerging risks. A small variance on a critical activity may require immediate action, while a larger variance on a non-critical package may have little completion impact.

Challenges and Limitations

Baseline and EVM systems have important limitations. A weak baseline produces precise-looking but unreliable indicators. Subjective progress rules can inflate EV. Level-of-effort activities may earn value merely because time passes. Cost data may lag field production. Inflation, currency changes, approved changes, and accounting adjustments can complicate comparisons. Schedule indices may be distorted by front-loaded or back-loaded budgets. Critical-path forecasts are sensitive to logic quality, calendars, constraints, and out-of-sequence work.

These limitations do not invalidate project control. They require triangulation: combine quantitative indicators with critical-path analysis, physical quantities, field evidence, risk analysis, quality information, and professional review. The most useful control system is not the one with the greatest number of metrics, but the one that supports timely and truthful decisions.

Chapter Summary

A baseline is an approved reference for scope, time, cost, and resources. It must be realistic, traceable, and changed only through authorised change control. Schedule updating requires a defined data date and reliable status information, including actual starts, actual finishes, remaining durations, quantities, and evidence.

Physical progress should be measured using rules appropriate to the work, such as verified quantities, weighted steps, or milestones. Earned value integrates planned value, earned value, and actual cost. Schedule variance and cost variance show value differences, while SPI and CPI show relative performance. Forecasts such as EAC and ETC are conditional estimates and must be interpreted with their assumptions.

Earned schedule expresses progress in time and helps overcome the limitation that traditional EVM schedule variance returns to zero at completion. Variance analysis must lead to diagnosis and corrective action, not merely reporting. Ethical governance, audit trails, controlled changes, and human oversight of digital and AI tools are essential to credible project control.

Key Terms

Baseline: Approved reference plan used for comparison.

Data date: Time boundary as of which status information is reported.

Planned Value (PV): Budgeted value of work scheduled by the data date.

Earned Value (EV): Budgeted value of work actually completed.

Actual Cost (AC): Recorded or accrued cost of completed work.

Budget at Completion (BAC): Total authorised budget for the defined scope.

Schedule Variance (SV): EV minus PV.

Cost Variance (CV): EV minus AC.

Schedule Performance Index (SPI): EV divided by PV.

Cost Performance Index (CPI): EV divided by AC.

Estimate at Completion (EAC): Forecast total cost at project completion.

Estimate to Complete (ETC): Forecast cost required to finish remaining work.

Variance at Completion (VAC): BAC minus EAC.

Earned Schedule (ES): Baseline time at which the current EV was planned to occur.

Physical progress: Verified proportion of work completed.

Remaining duration: Forecast time required to complete an in-progress activity.

Critical path: Logic path controlling the calculated completion date.

Corrective action: Action intended to reduce or remove an identified deviation.

Change control: Formal process for evaluating and approving changes.

Level-of-effort activity: Support activity whose value is distributed over time rather than tied directly to a measurable deliverable.

Review Questions

Short Answer Questions

1. What is the difference between a baseline and a forecast?
2. Why is a data date necessary when updating a construction schedule?
3. Define PV, EV, and AC.
4. Why can activity-count completion be a misleading progress measure?
5. State one limitation of traditional EVM schedule variance.

Long Answer Questions

1. Explain the components of an integrated scope, schedule, and cost baseline and describe the checks that should precede approval.
2. Describe a reliable monthly schedule-update process from field data collection through management reporting.
3. Compare quantity-based, milestone, weighted-step, and time-based progress measurement methods.
4. Explain the assumptions and limitations of at least two EAC forecasting formulas.
5. Discuss the ethical and governance responsibilities of a project controls professional.

Analytical / Application Questions

1. A project has PV = $900,000, EV = $800,000, and AC = $1,000,000. Calculate SV, CV, SPI, and CPI, and interpret the results.
2. A work package has a total quantity of 4,000 m² and an approved budget of $320,000. Verified accepted quantity is 2,500 m². Calculate physical progress and EV, assuming uniform budget distribution.
3. A project is behind schedule because design information and equipment deliveries are late. Propose a corrective-action plan that addresses immediate actions, ownership, evidence, risk, and verification.

Multiple Choice Questions with Answers

Question 1

Which statement best describes a project baseline?

A. An informal estimate prepared by the site supervisor

B. An approved reference plan used to measure performance

C. A forecast that must change whenever actual cost changes

D. A list of completed activities only

Correct Answer: B. An approved reference plan used to measure performance

Question 2

A project has PV = $500,000, EV = $450,000, and AC = $400,000. What is the cost variance?

A. −$100,000

B. −$50,000

C. $50,000

D. $100,000

Correct Answer: C. $50,000

Question 3

If EV = $720,000 and PV = $800,000, the SPI is:

A. 0.80

B. 0.90

C. 1.11

D. 1.20

Correct Answer: B. 0.90

Question 4

Which information is essential for an in-progress activity update?

A. Only its original duration

B. Actual start and remaining duration

C. Only its planned finish date

D. Only the number of workers originally planned

Correct Answer: B. Actual start and remaining duration

Question 5

A work package budget is $250,000 and verified physical progress is 40%. Assuming uniform budget distribution, its EV is:

A. $100,000

B. $150,000

C. $210,000

D. $625,000

Correct Answer: A. $100,000

Question 6

Which method is generally most suitable for measuring excavation progress?

A. Counting all project activities equally

B. Verified installed volume

C. Elapsed calendar time only

D. Number of progress meetings held

Correct Answer: B. Verified installed volume

Question 7

If BAC = $1,500,000, EV = $600,000, and CPI = 0.80, using EAC = AC + (BAC − EV) ÷ CPI with AC = $750,000, the EAC is:

A. $1,125,000

B. $1,500,000

C. $1,875,000

D. $2,250,000

Correct Answer: C. $1,875,000

Question 8

Earned schedule primarily improves project control by:

A. Converting all costs into cash payments

B. Expressing earned progress in time units

C. Removing the need for a logic-based schedule

D. Guaranteeing the original completion date

Correct Answer: B. Expressing earned progress in time units

Question 9

Which action is most appropriate when a reported progress percentage lacks supporting evidence?

A. Accept it to avoid conflict

B. Increase the percentage to reflect management optimism

C. Validate the measurement basis and supporting records

D. Reset the baseline immediately

Correct Answer: C. Validate the measurement basis and supporting records

Question 10

An approved scope change should normally be:

A. Hidden within the original variance

B. Documented and incorporated through formal change control

C. Recorded only after project completion

D. Ignored because it affects the baseline

Correct Answer: B. Documented and incorporated through formal change control