Project Tracking, Performance Measurement and Control

Introduction

Project tracking and control convert a project plan into a disciplined management system. Planning establishes what should happen, when, at what cost, and to what quality standard. Tracking establishes what is actually happening. Control compares actual performance with the approved baseline, explains deviations, forecasts consequences, and authorizes corrective or preventive action.

In contemporary projects, tracking is not merely the collection of status information. It is an integrated capability involving data architecture, performance measurement, governance, risk and issue management, change control, forecasting, communication, and managerial judgment. Poor tracking produces either false confidence or excessive administrative effort. Effective control provides timely, decision-relevant information while preserving accountability and avoiding uncontrolled changes to scope, schedule, cost, or quality.

This chapter focuses on reporting systems and dashboards; milestone, dependency, risk, issue, and change tracking; earned value management (EVM); earned schedule (ES); trend analysis; forecasting; variance thresholds; and corrective-action processes.

Learning Objectives

By the end of this chapter, a learner should be able to:

1. Design a reporting system that connects project data with management decisions.
2. Distinguish baselines, actuals, forecasts, milestones, dependencies, risks, issues, and changes.
3. Construct and interpret earned value measures and earned schedule measures.
4. Use trend analysis, thresholds, and forecasts to identify emerging performance problems.
5. Design a corrective-action and escalation process that is proportionate and auditable.
6. Evaluate the limitations, ethical implications, and governance requirements of project dashboards.

1. The Control Logic of a Project

Project control follows a recurring logic:

baseline → collect evidence → compare → diagnose → forecast → decide → act → remeasure

The baseline is the approved reference for scope, schedule, cost, and sometimes quality or benefits. It is not an immutable prediction. It is a controlled commitment against which performance is assessed. Approved changes revise the baseline through formal configuration or change-control procedures; informal rebaselining conceals poor performance and destroys comparability.

A useful control system distinguishes four states:

• Plan: the approved work, sequence, budget, dates, quality criteria, and assumptions.
• Actual: verified work performed, expenditure incurred, resources used, and events occurring.
• Forecast: the best current estimate of future outcomes.
• Decision: an authorized response to a deviation, risk, issue, or change.

Tracking should operate at several levels. Work-package teams need detailed operational information, project managers need integrated schedule and cost information, sponsors need exceptions and decisions, and governance bodies need trends, exposure, and compliance evidence. A single dashboard cannot serve all audiences equally well.

Control Account and Work Breakdown Structures

Measurement begins with a credible work breakdown structure (WBS). Deliverables are decomposed into work packages, and work packages are assigned budgets, responsibility, acceptance criteria, and schedule logic. A control account is a management-control point, often combining a responsible manager, defined scope, planned schedule, and authorized budget. The control account allows performance to be measured without requiring executives to inspect every activity.

The quality of tracking depends on traceability:

deliverable → work package → activity → resource/cost → evidence of completion → forecast

If this chain is weak, a sophisticated dashboard may simply display unreliable data more attractively.

2. Designing a Project Reporting System

A reporting system is a designed information process, not just a collection of templates. Its architecture should answer five questions:

1. What decisions must be made?
2. What evidence is needed for those decisions?
3. Who owns and validates the data?
4. How frequently must information be refreshed?
5. What action follows each material exception?

Information Requirements

A practical reporting specification defines the metric, purpose, source, owner, frequency, threshold, audience, and response. For example, “schedule performance” is insufficiently precise unless the organization defines whether it means milestone adherence, critical-path float, percentage of activities complete, earned schedule, or a combination.

Data Governance

A reporting system requires common definitions and controls. The data dictionary should define terms such as “complete,” “started,” “forecast finish,” “approved change,” and “open issue.” Data ownership should be explicit: the scheduler owns schedule integrity, the cost controller validates actual cost, work-package managers provide status evidence, and the project manager integrates the information.

Important controls include versioned baselines, date-stamped status cut-offs, approval records, automated validation rules, role-based access, and an audit trail. A status report that mixes data dates or uses unverified self-reported completion can generate materially misleading conclusions.

Dashboard Design Principles

A dashboard should support action rather than display every available measure. Effective dashboards generally contain:

• a concise overall status and explanation;
• milestone and critical-path information;
• cost and schedule performance indicators;
• top risks and issues with owners and due dates;
• approved and pending changes;
• trend charts and forecast dates;
• decisions required from the audience.

Traffic-light indicators are useful for rapid scanning but can oversimplify uncertainty. A red, amber, or green status should have a documented rule. For example, amber might mean that a forecast milestone is within five working days of its tolerance boundary, whereas red might mean that the boundary has been exceeded or a recovery decision is overdue. Colors should never replace explanatory text.

3. Tracking Milestones, Dependencies, Risks, Issues and Changes

Milestones

A milestone is a significant event with zero duration, such as design approval, contract award, prototype acceptance, or operational handover. Milestones should have an objective completion condition and an accountable owner. “Design substantially complete” is weak unless the project defines the documents, reviews, tests, and approvals required.

Milestone tracking should record baseline date, current forecast date, actual date, variance, confidence, predecessor conditions, and consequences of slippage. A milestone may be on time while its supporting work is unhealthy; therefore milestone status should be interpreted alongside leading indicators such as unresolved defects, remaining effort, and critical-path float.

Dependencies and Criticality

Dependencies express logical relationships between activities or deliverables. Common relationships include finish-to-start, start-to-start, finish-to-finish, and start-to-finish, although finish-to-start should not be used automatically when a more accurate relationship exists. External dependencies—such as regulatory approval, supplier delivery, or customer data—require particular attention because the project team may not control them.

The critical path is the sequence of activities that determines the earliest project completion under the modeled logic and constraints. In a simple activity-on-node network, total float for activity i can be expressed as:

where ES and EF are early start and early finish, and LS and LF are late start and late finish. Float is measured in time units and assumes a valid network, defined calendars, and a specified completion objective. Negative float indicates that the schedule cannot meet a required date without changing logic, resources, scope, or constraints. In resource-constrained schedules, criticality can also arise from resource availability and not only from logical path length.

Risks and Issues

A risk is an uncertain event or condition that may affect objectives; an issue is a problem that has already occurred or requires immediate management. Treating an issue as a risk delays action, while treating every possibility as an issue overwhelms the team.

A risk register should include cause, event, effect, probability, impact, proximity, owner, response strategy, trigger, residual exposure, and status. Qualitative risk scoring may use a probability-impact matrix, but ordinal scores should not be interpreted as precise probabilities or monetary values unless the scale has been carefully calibrated.

For quantitatively assessed risks, expected monetary value (EMV) is commonly calculated as:

where p_j is the probability of scenario j and I_j is its monetary impact, with costs conventionally represented as negative values and benefits as positive values. EMV is an expectation across scenarios, not a prediction of the exact outcome. It is most useful when scenarios are reasonably defined and probabilities and impacts are decision-relevant. It should not be used to hide highly variable or catastrophic outcomes behind an average.

An issue log should identify description, date raised, impact, priority, owner, target resolution date, dependencies, decision required, and closure evidence. Risks and issues should be connected to schedule activities, cost accounts, deliverables, or decisions wherever possible.

Change Tracking

Change control protects the integrity of the approved baseline while allowing justified adaptation. A change request should describe the requested alteration, rationale, impact on scope, schedule, cost, quality, risk, resources, contracts, and benefits, along with options and recommendation.

A change-control board or delegated authority should distinguish:

• correction of an error within approved scope;
• clarification that does not alter the baseline;
• approved change to the baseline;
• emergency change requiring expedited authorization;
• unauthorized scope growth.

Once approved, the change must be incorporated into relevant plans, budgets, schedules, requirements, contracts, and communication. Closing the change request without updating affected baselines creates “phantom performance”: the project appears late or over budget because the approved work was never represented in the plan.

4. Earned Value Management

Earned value management integrates scope, schedule, and cost through a time-phased performance measurement baseline. The three fundamental measures are:

The monetary unit is a budget unit, such as dollars or euros. EV is not the market value of the output and is not necessarily equal to AC.

Variances and Performance Indices

Schedule variance (SV) and cost variance (CV) are expressed in monetary units. A positive SV means more budgeted work has been accomplished than planned by the status date; a negative SV means less has been accomplished. A positive CV means the earned budget value exceeds actual cost. SPI and CPI are dimensionless ratios: values above 1.00 are favorable, values below 1.00 are unfavorable, and 1.00 indicates parity. These interpretations assume consistent measurement rules and a valid baseline. EVM schedule variance is expressed in money and eventually tends toward zero when all planned work is complete, so it should not be treated as calendar delay without additional analysis.

Worked Example: EVM

Suppose a project has a budget at completion of 1,000,000 currency units. At the status date, PV is 420,000, EV is 360,000, and AC is 400,000.

The project has accomplished 60,000 currency units less budgeted work than planned and has spent 40,000 more than the budgeted value of work accomplished. An SPI of approximately 0.857 and CPI of 0.900 indicate unfavorable schedule and cost efficiency. Management must investigate causes rather than conclude automatically that the project will finish exactly 14.3% late or 11.1% over budget.

Forecasting Cost

The estimate at completion (EAC) is the forecast total cost. The appropriate formula depends on the reason for past variance and assumptions about future performance.

If current cost efficiency is expected to continue:

If the remaining work will be performed according to the original budget, while past cost variance is considered atypical:

A combined schedule-and-cost efficiency assumption is sometimes used:

where BAC is budget at completion. These are forecasting models, not universal truths. They assume that the selected efficiency relationship is meaningful, that EV and AC are measured consistently, and that no major structural change invalidates the baseline. A bottom-up estimate of remaining work is preferable when conditions have changed materially.

The estimate to complete is:

The variance at completion is:

A positive VAC indicates a forecast underrun; a negative VAC indicates a forecast overrun.

For the example, if current CPI continues:

Thus the forecast overrun is approximately 111,111 currency units, subject to the stated assumption.

5. Earned Schedule and Time-Based Forecasting

Earned schedule addresses a limitation of monetary schedule variance by expressing schedule performance in time. Let AT be the actual time elapsed at the status date. Earned schedule, ES, is the time on the performance measurement baseline at which the current EV would have been planned. In other words, locate EV on the cumulative PV curve and read the corresponding planned time.

A time-based schedule variance is:

and the earned schedule index is:

Positive SV(t) indicates time ahead of the baseline position; negative SV(t) indicates time behind it. SPI(t) below 1.00 indicates unfavorable time efficiency. ES is obtained from the baseline curve, often by interpolation between status periods. It requires a time-phased baseline and reasonably measurable EV. Like all indicators, it does not replace critical-path analysis, resource analysis, or milestone review.

A simple duration forecast based on current time efficiency is:

This is an assumption-based forecast. It should be compared with schedule-network forecasts, remaining-duration estimates, and known constraints.

6. Trend Analysis, Forecasting and Thresholds

A single status point can be noisy. Trend analysis examines performance across successive data dates. Useful displays include cumulative PV-EV-AC curves, CPI and SPI(t) trend lines, milestone slippage charts, risk exposure over time, defect arrival and closure rates, and forecast completion dates.

Managers should distinguish:

• lagging indicators, which show results after performance occurs, such as cost variance;
• leading indicators, which signal future outcomes, such as declining float, overdue design decisions, rising rework, or unresolved interface dependencies.

A trend is not automatically a cause. Repeated adverse CPI may result from under-budgeting, premature cost recognition, incorrect EV methods, supplier pricing, or genuine inefficiency. Diagnosis requires triangulation with qualitative evidence.

Threshold Design

Thresholds should be established before results are known where possible. A threshold may be absolute, relative, trend-based, or risk-based. Examples include:

• milestone forecast slippage exceeding ten working days;
• CPI below 0.95 for two consecutive reporting periods;
• negative float on a contractual completion milestone;
• a risk exposure exceeding delegated authority;
• an issue unresolved beyond its agreed due date;
• a forecast cost exceeding the approved budget contingency.

Thresholds must account for measurement noise, materiality, project phase, uncertainty, and decision capacity. Too many thresholds produce alert fatigue; thresholds that are too wide create late escalation. Each threshold should specify owner, response time, escalation route, and required evidence.

7. Corrective Action and Control Decisions

Corrective action is action to bring expected future performance into alignment with the approved objective. Preventive action reduces the probability of future deviation. A disciplined process is:

1. Detect: identify a variance, trend, trigger, or exception.
2. Validate: confirm data date, definitions, baseline, and evidence.
3. Diagnose: analyze root causes, interactions, and consequences.
4. Develop options: consider schedule recovery, resequencing, resources, scope clarification, procurement action, technical redesign, or risk response.
5. Evaluate: assess cost, benefit, quality, safety, contractual, ethical, and downstream effects.
6. Authorize: obtain the appropriate decision under delegated authority.
7. Implement: assign owner, due date, resources, and success criteria.
8. Monitor: test whether the action produced the intended effect.
9. Close and learn: document outcome and update lessons learned.

Common schedule recovery techniques include fast tracking, which overlaps activities normally performed sequentially, and crashing, which adds resources or cost to shorten duration. Both can increase risk, rework, coordination burden, or quality problems. Scope reduction is not a legitimate recovery technique unless formally approved and consistent with the project’s purpose.

Root-cause analysis may use the five whys, cause-and-effect diagrams, fault trees, or systems analysis. A corrective action should address a causal mechanism, not merely the visible symptom. “Work harder” is not a sufficient action unless it identifies capacity, method, or constraint changes.

8. Case Study: Digital Claims Transformation

The following is an illustrative fictional case.

Background

An insurance company is implementing a digital claims platform over twelve months. The approved budget at completion is 8 million currency units. The project includes software configuration, data migration, integration with payment systems, cybersecurity testing, user training, and operational deployment.

Problem

At month six, the dashboard reports green overall status because 58% of activities are marked complete. However, the contractual pilot milestone is forecast four weeks late. The project has PV of 4.2 million, EV of 3.6 million, and AC of 4.0 million. Two integration dependencies are overdue, the data-migration risk has increased, and three change requests are awaiting decision.

Analysis

The performance measures are:

The dashboard’s activity-completion percentage is misleading because it treats small completed tasks as equivalent to high-value integration work. The project team validates the EV method and confirms that critical integration work has low earned value despite substantial effort. Network analysis shows that the overdue dependencies lie on the path to the pilot milestone. The data-migration risk has a high impact and a response trigger based on failed data-quality tests, but ownership is unclear.

Approach and Solution

The steering committee requires four actions. First, the team establishes a control-account-level dashboard showing EV, milestone forecasts, critical-path float, and dependency status. Second, the integration manager becomes the accountable owner for both external dependencies, with escalation dates and supplier commitments. Third, the data-migration risk is converted into a structured response plan involving a test migration, data cleansing capacity, and a go/no-go criterion. Fourth, the pending changes are assessed for their effect on the pilot; one is rejected, one is deferred, and one is approved with an explicit budget and schedule adjustment.

The team develops two recovery options. Fast tracking would overlap integration testing and configuration review, but the quality lead identifies unacceptable defect risk. Crashing by adding specialized integration resources is more expensive but preserves test independence. The committee approves a limited, time-bound resource increase and authorizes a revised baseline for the approved change.

Outcome

After two reporting cycles, integration dependency closure improves, the pilot forecast recovers from four weeks late to ten working days late, and CPI stabilizes at 0.96. The project does not return to the original date immediately, but management now has a transparent recovery plan and an explicit decision about the remaining delay. The dashboard changes from a completion-count view to an evidence-based control view.

Learning Points

1. Percent complete is not a substitute for value-based measurement.
2. Milestone status must be connected to dependencies and network logic.
3. Risk ownership and triggers must be operational, not merely recorded.
4. Recovery decisions require comparison of cost, quality, risk, and contractual consequences.
5. Approved changes must update the baseline and preserve an audit trail.

9. Limitations, Ethics and Governance

Performance measurement can create dysfunctional behavior. Teams may accelerate low-value work to improve completion statistics, defer cost recognition, overstate progress, or avoid reporting risks that threaten performance ratings. EVM is especially vulnerable to weak rules for measuring physical progress. Governance should therefore reward accurate information and early escalation rather than only favorable numbers.

Data privacy and cybersecurity are also relevant. Dashboards may contain employee performance data, supplier information, customer information, or commercially sensitive forecasts. Access should follow least-privilege principles, and exported reports should be controlled. Automated status generation must not obscure accountability: a project manager remains responsible for interpreting evidence and making decisions.

AI and advanced analytics can assist with anomaly detection, schedule-risk prediction, natural-language summarization, and pattern recognition across projects. However, models may reproduce historical bias, confuse correlation with causation, or generate confident explanations unsupported by evidence. AI-generated forecasts should be traceable to source data, validated by subject-matter experts, monitored for drift, and clearly identified in governance records. Human approval remains essential for changes affecting safety, compliance, contractual commitments, or material investment.

10. Best-Practice Checklist

A mature project control environment generally:

• uses an approved, time-phased baseline;
• defines completion and EV rules before measurement begins;
• separates actuals, forecasts, and approved changes;
• integrates scope, schedule, cost, risk, issue, quality, and dependency data;
• uses both leading and lagging indicators;
• makes thresholds and escalation paths explicit;
• reports uncertainty rather than hiding it behind colors;
• assigns an owner and due date to every material action;
• validates data at a fixed status cut-off;
• preserves decision and baseline audit trails;
• tests whether corrective actions actually worked; and
• adapts reporting detail to audience and decision need.

Chapter Summary

Project tracking and control are an integrated cycle of baseline comparison, diagnosis, forecasting, decision, action, and remeasurement. Effective reporting systems begin with decision requirements, common definitions, accountable data ownership, and controlled baselines. Milestones require objective acceptance conditions; dependencies require network and external-interface analysis; risks must be distinguished from issues; and changes must be authorized and incorporated into affected plans.

Earned value connects scope, schedule, and cost through PV, EV, and AC. SV and CV express variance in budget units, while SPI and CPI express efficiency ratios. EAC, ETC, and VAC provide forecasts whose validity depends on explicit assumptions. Earned schedule supplements EVM by expressing schedule performance in time, but it should be interpreted with critical-path and resource analysis. Trend analysis combines leading and lagging indicators, while thresholds convert information into escalation rules. Corrective action requires validated data, root-cause analysis, evaluated options, authorization, implementation, and follow-up.

Finally, dashboards are socio-technical governance tools. Their value depends not only on technology but also on truthful reporting, ethical incentives, data protection, human judgment, and organizational willingness to act on adverse information.

Key Terms

Baseline: Approved reference plan used for comparison and control.

Control account: Management control point linking scope, budget, schedule, and responsibility.

Dashboard: Visual reporting interface that presents decision-relevant project information.

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

Earned Schedule (ES): Baseline time position corresponding to the earned value achieved.

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

Issue: A problem or condition that has already occurred and requires management.

Milestone: Significant zero-duration event used to mark achievement or decision.

Planned Value (PV): Budgeted value of work scheduled by a specified status date.

Preventive action: Action intended to reduce the probability of future deviation.

Risk: Uncertain event or condition that may affect objectives.

Schedule Performance Index (SPI): Ratio of EV to PV, indicating schedule efficiency in EVM.

Schedule Performance Index (time) (SPI(t)): Ratio of earned schedule to actual time elapsed.

Threshold: Predefined boundary that triggers review, escalation, or action.

Trend analysis: Examination of performance observations across successive reporting periods.

Variance: Difference between planned, earned, actual, or forecast performance.

Work Breakdown Structure (WBS): Hierarchical decomposition of project scope into manageable components.

Review Questions

Short Answer Questions

1. Why should a project reporting system distinguish actuals from forecasts?
2. What is the difference between a risk and an issue?
3. What do PV, EV, and AC represent in earned value management?
4. Why is EVM schedule variance not a direct measure of calendar delay?
5. What information should a change request contain?

Long Answer Questions

1. Explain how a project manager can design a reporting system for operational, project, and governance audiences.
2. Discuss the relationship among milestones, dependencies, critical path, and corrective action.
3. Explain the assumptions and limitations of alternative EAC forecasting formulas.
4. Compare leading and lagging indicators in project control, giving appropriate examples.
5. Discuss ethical and governance risks created by poorly designed dashboards and performance incentives.

Analytical / Application Questions

1. A project has PV of 500,000, EV of 450,000, and AC of 480,000. Calculate SV, CV, SPI, and CPI, and interpret the results.
2. A contractual milestone is forecast ten working days late, while CPI is 0.98 and SPI is 0.94. Design a diagnostic and corrective-action plan that considers dependencies, quality, cost, and change control.
3. A project team reports 70% of activities complete, but high-value integration work is unfinished and two external dependencies are overdue. Critically evaluate why the reported percentage may be misleading and propose a dashboard redesign.

Multiple Choice Questions with Answers

Question 1

Which measure represents the budgeted cost of work actually performed?

A. Planned Value

B. Earned Value

C. Actual Cost

D. Budget at Completion

Correct Answer: B. Earned Value

Question 2

A project has EV = 300, PV = 360, and AC = 330. What is the Schedule Performance Index?

A. 0.83

B. 0.91

C. 1.10

D. 1.20

Correct Answer: A. 0.83

Question 3

An SPI of 0.85 generally indicates that the project has accomplished what relative to its planned work?

A. More work than planned

B. Exactly the planned work

C. Less work than planned

D. More work at lower cost

Correct Answer: C. Less work than planned

Question 4

Which statement best distinguishes an issue from a risk?

A. An issue is always financial, while a risk is always technical

B. An issue has occurred or requires immediate management, while a risk is uncertain

C. A risk has occurred, while an issue may occur

D. There is no practical distinction

Correct Answer: B. An issue has occurred or requires immediate management, while a risk is uncertain

Question 5

If BAC is 1,000,000 and CPI is 0.80, which EAC assumption is being applied by BAC ÷ CPI?

A. Past cost efficiency will continue

B. All past variance was atypical

C. The remaining work will cost zero

D. Schedule performance will improve to 1.00

Correct Answer: A. Past cost efficiency will continue

Question 6

Which action best preserves baseline integrity after an approved scope change?

A. Delete the original baseline

B. Ignore the change until project closure

C. Update affected plans and retain an authorized audit trail

D. Record the change only in meeting minutes

Correct Answer: C. Update affected plans and retain an authorized audit trail

Question 7

What is the principal advantage of earned schedule over conventional EVM schedule variance?

A. It eliminates the need for a baseline

B. It expresses schedule performance in time units

C. It measures quality automatically

D. It replaces critical-path analysis

Correct Answer: B. It expresses schedule performance in time units

Question 8

Which is most clearly a leading indicator of future schedule trouble?

A. Final cost at project closure

B. Actual invoice total from a completed activity

C. Declining float and overdue interface decisions

D. Completed project benefits

Correct Answer: C. Declining float and overdue interface decisions

Question 9

What should normally occur immediately after a material variance is detected?

A. Change the baseline without approval

B. Validate the data and diagnose causes

C. Close the project

D. Remove the metric from the dashboard

Correct Answer: B. Validate the data and diagnose causes

Question 10

A corrective action is strongest when it does what?

A. Addresses a verified root cause and has an owner and success criterion

B. Assigns blame without changing the process

C. Reports the variance again without intervention

D. Overlaps all activities regardless of risk

Correct Answer: A. Addresses a verified root cause and has an owner and success criterion