BUS-CONS57-02 · Lesson 7 · 14 clock hours · practice
Schedule Monitoring, Updates, and Earned Value
Objective. Students will update a baseline schedule with progress data, calculate Schedule Variance (SV) and Schedule Performance Index (SPI), and identify activities requiring corrective action.
⚠ Pending professional review
This lesson, its worked examples and its practice questions has not yet been verified by a credentialed professional in the field or by a certification or approval body. It is a study draft and may contain errors. Do not use it as instructions for work on a job site or on live equipment. Always follow your instructor, your supervising professional, and current official references and regulations.
VoTechWorks program approval and accreditation are still in progress. Credentials are issued only by the certifying bodies named in each program, after their own exams.
Why Schedule Monitoring Matters
A baseline schedule is a plan, not a guarantee. Once work begins, conditions change: crews are short, materials arrive late, weather delays a concrete pour, or a subcontractor finishes early. Your job as a construction manager or estimator is to track what actually happened against what was planned and then communicate clearly about the gap. Owners, lenders, and sureties all expect a monthly schedule update that is honest and actionable. CMAA, NCCER, and OSHA standards all recognize that poor schedule control is one of the leading causes of cost overrun and unsafe site conditions—rushed crews cut corners.
Updating the Baseline Schedule
At each status date (often the last day of the month), you collect progress data for every activity: how many days remain, what percentage is complete, and the actual start and finish dates recorded so far. You enter these actuals into the scheduling software without changing the original baseline. The software then calculates a new projected finish for each activity and for the project as a whole.
Key fields you update:
- Actual Start / Actual Finish – dates work began or ended.
- Percent Complete – based on work-in-place, not time elapsed.
- Remaining Duration – your best current estimate of days left.
After updating, compare the Data Date column (current schedule) to the Baseline column. A positive variance means ahead of schedule; a negative variance means behind. Most software displays this automatically in the variance column.
Never alter baseline dates to hide slippage. The baseline is the contract reference point and an auditable document.
Earned Value Analysis for Schedules
Earned Value Management (EVM) gives you a number-based way to measure schedule and cost performance at the same time. Three values drive the analysis:
- BCWP – Budgeted Cost of Work Performed (also called Earned Value, or EV): the budget amount for the work actually completed so far.
- BCWS – Budgeted Cost of Work Scheduled (also called Planned Value, or PV): the budget amount that should have been completed by the status date.
- ACWP – Actual Cost of Work Performed (also called Actual Cost, or AC): what you actually spent to accomplish the work done so far.
Two schedule metrics come from these three numbers:
Schedule Variance (SV) = BCWP − BCWS
- SV > 0: ahead of schedule (earned more than planned)
- SV = 0: exactly on schedule
- SV < 0: behind schedule (earned less than planned)
Schedule Performance Index (SPI) = BCWP ÷ BCWS
- SPI > 1.0: ahead of schedule
- SPI = 1.0: exactly on schedule
- SPI < 1.0: behind schedule
SPI is particularly useful because it scales with the size of the activity. An SPI of 0.80 means you are accomplishing only 80 cents of planned work for every dollar of planned schedule.
Identifying Activities Requiring Corrective Action
Not every behind-schedule activity is equally important. Focus first on critical path activities—those with zero or negative float. A one-day delay on a critical activity delays the entire project by one day. Activities with large negative SV or SPI below roughly 0.90 on the critical path demand immediate corrective action.
Common recovery strategies include:
- Crashing – adding resources (overtime, extra crew) to shorten duration at added cost.
- Fast-tracking – overlapping activities that were originally sequential, which adds coordination risk.
- Scope adjustment – working with the owner to defer non-critical scope.
- Subcontractor remobilization – replacing or supplementing an underperforming sub.
Always document the recovery plan in writing and get owner acknowledgment when the recovery involves additional cost or changed sequencing.
Writing the Schedule Status Narrative
Owners do not read Gantt charts—they read your narrative. A good monthly schedule narrative covers:
1. Overall project status (on schedule, ahead, or behind by how many days).
2. Which specific activities are behind and why.
3. Whether the critical path is impacted.
4. Proposed recovery actions with realistic timelines.
Use specific activity names and dates. Avoid vague language such as "we are working on it." Two clear, factual paragraphs are more useful than a page of generalities.
Safety Note
Schedule pressure is a recognized safety hazard. When a project is behind schedule, site supervision may push crews to work faster, skip pre-task planning, or work additional hours leading to fatigue. OSHA's general duty clause requires employers to maintain a workplace free of recognized hazards regardless of schedule. If a recovery plan involves overtime or compressed work, your status narrative should note that the site safety plan will be reviewed and toolbox talks increased. Never propose a recovery action that implicitly or explicitly trades safety for schedule.
Key terms10
Baseline ScheduleThe original approved schedule frozen at project start; used as the reference for measuring all future progress and variance.
BCWP (Budgeted Cost of Work Performed)The planned (budgeted) value of the work that has actually been completed by the status date; also called Earned Value (EV).
BCWS (Budgeted Cost of Work Scheduled)The planned (budgeted) value of the work that was supposed to be completed by the status date; also called Planned Value (PV).
ACWP (Actual Cost of Work Performed)The real dollars spent to accomplish the work completed so far; also called Actual Cost (AC). Used for cost variance, not schedule variance.
Schedule Variance (SV)BCWP minus BCWS; a negative result means the project has earned less value than planned and is behind schedule.
Schedule Performance Index (SPI)BCWP divided by BCWS; a value below 1.0 means the project is accomplishing less planned work per scheduled dollar than intended.
Critical PathThe longest sequence of dependent activities through the network; any delay to a critical activity delays the project end date by the same amount.
CrashingA schedule recovery technique that adds resources—such as overtime or additional crew—to shorten an activity's duration, typically at increased cost.
Fast-TrackingA schedule compression technique that overlaps activities originally planned in sequence, reducing overall duration but increasing coordination complexity and risk.
Data DateThe status date through which actual progress has been recorded in the schedule; sometimes called the time-now line in scheduling software.
Worked examples4
1. Activity A has BCWP = $12,000 and BCWS = $15,000. Calculate SV and SPI and interpret the results.
- Write the formulas: SV = BCWP − BCWS; SPI = BCWP ÷ BCWS.
- Calculate SV: $12,000 − $15,000 = −$3,000.
- Calculate SPI: $12,000 ÷ $15,000 = 0.80.
- Interpret: SV is negative, so the activity is behind schedule. SPI of 0.80 means only 80% of the planned work has been earned—for every dollar of work planned, only 80 cents has been accomplished.
Answer: SV = −$3,000 (behind schedule); SPI = 0.80 (performing at 80% of planned rate).
2. Activity B has BCWP = $22,500 and BCWS = $20,000. Calculate SV and SPI and interpret the results.
- Write the formulas: SV = BCWP − BCWS; SPI = BCWP ÷ BCWS.
- Calculate SV: $22,500 − $20,000 = +$2,500.
- Calculate SPI: $22,500 ÷ $20,000 = 1.125.
- Interpret: SV is positive, so this activity is ahead of schedule. SPI above 1.0 confirms the team is completing more work than planned for this period.
Answer: SV = +$2,500 (ahead of schedule); SPI = 1.125 (performing at 112.5% of planned rate).
3. Five activities have the following BCWP and BCWS values. Which one presents the greatest schedule risk and why?
- Activity 1: BCWP $8,000, BCWS $8,000
- Activity 2: BCWP $5,000, BCWS $10,000 — CRITICAL PATH
- Activity 3: BCWP $18,000, BCWS $20,000
- Activity 4: BCWP $3,000, BCWS $4,000
- Activity 5: BCWP $25,000, BCWS $22,000
- Calculate SPI for each activity by dividing BCWP by BCWS.
- Activity 1: $8,000 ÷ $8,000 = 1.00 (on schedule).
- Activity 2: $5,000 ÷ $10,000 = 0.50 (critical path, severely behind).
- Activity 3: $18,000 ÷ $20,000 = 0.90 (slightly behind, not on critical path).
- Activity 4: $3,000 ÷ $4,000 = 0.75 (behind, but float available).
- Activity 5: $25,000 ÷ $22,000 = 1.136 (ahead of schedule).
- Identify the highest-risk activity: Activity 2 has an SPI of 0.50 AND is on the critical path, meaning the project end date is directly threatened.
Answer: Activity 2 presents the greatest schedule risk: SPI = 0.50, it is on the critical path, and every day it remains behind delays the project completion date.
4. A project has a total budget (BAC) of $500,000. At the midpoint status date, BCWS = $250,000 and BCWP = $200,000. The project manager proposes crashing two critical activities at an added cost of $15,000 to recover the schedule. Write the SV and SPI, and explain whether crashing is likely warranted.
- Calculate SV: BCWP − BCWS = $200,000 − $250,000 = −$50,000.
- Calculate SPI: BCWP ÷ BCWS = $200,000 ÷ $250,000 = 0.80.
- The project has earned only 80% of what was planned at the halfway point—a $50,000 schedule deficit in earned value terms.
- An SPI of 0.80 on a $500,000 project at midpoint is a significant variance. If the critical path is affected, failure to recover now may result in a much larger delay and potential liquidated damages.
- The $15,000 crashing cost should be weighed against the cost of a late finish (liquidated damages, extended general conditions). If delay penalties exceed $15,000, crashing is warranted.
Answer: SV = −$50,000; SPI = 0.80. Crashing is likely warranted if the projected delay would trigger contractual penalties or extended overhead costs exceeding $15,000.
The math in this lesson1
Learners compute schedule variance BCWP − BCWS and SPI = BCWP ÷ BCWS to judge progress.
A-SSE.1
In class: Students receive a status report with percent-complete data for each activity at the project midpoint; they enter actuals into the software and compare the updated schedule to the baseline using the variance columns. · Students calculate SV (Earned Value minus Planned Value) and SPI (Earned Value divided by Planned Value) for five selected activities by hand using provided BCWP, BCWS, and ACWP data, then verify results in software. · Students write a two-paragraph schedule status narrative suitable for an owner monthly report, identifying which activities are behind schedule, the impact on the critical path, and proposed recovery actions.
Materials: Baseline schedule file from previous lessons, status report data sheet (instructor-prepared), EV formula reference card, scheduling software, report narrative template
Check: SV and SPI calculations checked against answer key (pass: all five calculations correct within rounding); status narrative graded: critical path impact identified correctly and at least one specific recovery action proposed. Pass: both components correct.
Practice check8
Answer each question, then check it. Nothing is recorded; this is your own practice.
Record this lesson on my transcript. Sign in with your key and enrollment email to record lessons (enroll free if you have no key). This page stays open to read and practise.