Schedule Updates Versus Schedule Revisions

Introduction
Within the CMAA Time Management domain, few distinctions are tested as consistently as the difference between a schedule update and a schedule revision. Both involve changing the project schedule file, both are usually submitted by the contractor, and both are reviewed by the Construction Manager (CM). Yet they serve completely different purposes, follow different approval paths, and have very different implications for delay analysis, claims, and the integrity of the baseline. Candidates who blur these two concepts tend to miss questions that are otherwise straightforward. This guide explains what each term means, why the distinction matters, how the process works in practice, and how to recognize the correct answer on exam day.

Why This Distinction Is Important
The CMAA Standards of Practice treat the approved baseline schedule as the contractual yardstick for measuring time performance. Every month, the project team needs to answer two separate questions: Where are we? and Has the plan changed? The first question is answered by an update; the second is answered by a revision. If the two are mixed together without documentation, several problems arise:
1. The baseline loses its value as a reference point, making it impossible to perform a credible delay analysis or time impact analysis (TIA) later.
2. Logic changes can be used, intentionally or not, to mask slippage. A contractor who is falling behind can change relationships, shorten future durations, or add constraints so that the projected completion date still appears on time. This is often called a hidden or buried revision.
3. Float ownership and concurrent delay arguments become contested because no one can establish what the plan actually was at a given point in time.
4. Owner approval requirements are bypassed. Updates typically require review and acceptance of progress data; revisions typically require formal review, justification, and approval because they alter the plan the owner relied upon.
The CM protects the owner by insisting that progress reporting and plan changes be kept separate, transparent, and documented. That protective role is exactly what the exam is probing.

What Is a Schedule Update?
A schedule update is the periodic (usually monthly, sometimes biweekly) process of recording actual progress against the current schedule. The update moves the data date (status date) forward and records:
- Actual start and actual finish dates for activities
- Percent complete or remaining duration for in-progress activities
- Actual resource usage or cost, if the schedule is resource or cost loaded
- Recalculation of the remaining network based on that progress
Critically, an update does not change the plan for future work. The logic, original durations of unstarted activities, calendars, constraints, and activity scope remain as they were. The update simply tells the team how the plan is performing. The baseline remains untouched; the update is compared to it to reveal variances, float consumption, and critical path shifts caused by actual performance.
Think of an update as a status photograph. It describes reality as of the data date and recalculates the forecast, but it does not alter the intended route to completion.

What Is a Schedule Revision?
A schedule revision is a deliberate change to the plan itself. Revisions alter how the remaining work will be executed and typically include one or more of the following:
- Adding or deleting activities (for example, to reflect a change order adding scope)
- Changing logic relationships, lags, or sequencing
- Changing durations of future (unstarted) activities
- Changing calendars, resource assignments, or crew sizes
- Adding, removing, or modifying constraints
- Incorporating an approved time extension
- Developing a recovery schedule to regain lost time
Because a revision changes the commitment the owner is relying upon, it must be identified, justified in writing, reviewed by the CM, and approved according to the contract. Once approved, a revision may become the new current schedule or, in significant cases, a revised baseline (re-baseline). Even then, the original baseline is retained for historical and forensic purposes.
Think of a revision as redrawing the route map. The destination may be the same, but the path, timing, or resources to get there have changed.

Side-by-Side Comparison
Purpose: Update = report progress and status. Revision = change the plan.
Trigger: Update = passage of the reporting period. Revision = change order, delay event, owner directive, means and methods change, recovery requirement, or correction of planning errors.
What changes: Update = actual dates, percent complete, remaining durations, data date. Revision = logic, durations of future work, activities, calendars, constraints, resources, scope.
Effect on baseline: Update = none; baseline is the comparison point. Revision = may lead to a revised baseline if approved, but original baseline is preserved.
Approval: Update = CM review and acceptance of accuracy. Revision = formal justification, CM review, and owner approval per contract.
Documentation: Update = narrative report explaining progress, variances, and critical path. Revision = written description of each change and reason for it, often with a fragnet or TIA.

How the Process Works in Practice
Step 1 - Contractor submission. The contractor submits the updated schedule file, a narrative report, and typically a list of all changes made since the prior submission. Many specifications require a schedule comparison report that flags every added activity, deleted activity, logic change, duration change, and constraint change.
Step 2 - CM review of progress data. The CM verifies that actual dates and percent complete are accurate by comparing them to daily reports, inspection records, photographs, and site observations. Inflated progress is a common problem the CM must catch.
Step 3 - CM screening for undisclosed revisions. The CM compares the new update to the previous one. If future logic or durations changed without being disclosed and justified, the CM rejects or conditionally accepts the update and requires the contractor to either restore the prior logic or submit a formal revision request.
Step 4 - Evaluation of disclosed revisions. For each proposed revision, the CM evaluates whether it is reasonable, whether it is tied to an entitlement (such as an approved change order or excusable delay), whether it shifts risk or float improperly, and whether it affects the contract completion date. Time extension requests are typically analyzed using a time impact analysis with a fragnet inserted into the schedule current at the time of the event.
Step 5 - Recommendation and approval. The CM recommends acceptance, rejection, or conditional acceptance to the owner. The CM does not direct the contractor on means and methods, and the contractor retains ownership of its schedule; the CM reviews, evaluates, and advises.
Step 6 - Recovery schedules. When progress falls behind by more than a contractual threshold, the CM typically requires a recovery schedule. This is a revision because it changes the plan for remaining work, and it must demonstrate a credible path back to the contract milestones.
Step 7 - Record keeping. Every update and every approved revision is archived with its data date and narrative. This creates the contemporaneous record needed for forensic schedule analysis if a claim arises.

Common Pitfalls the CM Must Watch For
- Logic changes slipped into a monthly update to preserve an on-time projected finish
- Shortening durations of future activities without added resources or justification
- Adding hard constraints (mandatory finish dates) that artificially suppress negative float
- Out-of-sequence progress that invalidates the logic and is never corrected through a proper revision
- Treating an owner-caused delay as if it required only an update rather than a formal time extension revision
- Replacing the baseline with each new update, destroying the reference for variance analysis

Exam Tips: Answering Questions on Schedule Updates Versus Schedule Revisions
Tip 1 - Scan for vocabulary cues. Words like actual start, actual finish, percent complete, remaining duration, status date, data date, progress signal an update. Words like logic, sequence, re-sequence, added activities, change order, recovery, time extension, constraint, future durations, means and methods signal a revision.
Tip 2 - Ask what changed. If only the past (completed and in-progress work) changed, it is an update. If the plan for the future changed, it is a revision, regardless of what the contractor calls it.
Tip 3 - The baseline is never altered by an update. Any answer stating that the monthly update replaces or modifies the baseline is almost always wrong. The baseline is the fixed reference; revisions may create a revised baseline only through formal approval.
Tip 4 - Follow the approval path. Revisions require written justification and owner approval through the CM. Updates require verification of accuracy. If a question asks what the CM should do upon finding undisclosed logic changes in an update, the best answer involves identifying the changes, requesting justification, and requiring a formal revision submittal, not quietly accepting the update.
Tip 5 - Remember the CM's role. The CM reviews, analyzes, and recommends. The contractor prepares and owns the schedule. Answers that have the CM revising the contractor's logic or dictating means and methods are typically distractors.
Tip 6 - Recovery schedules are revisions. If a scenario describes a contractor falling behind and being required to show how it will regain time, the correct classification is a revision, and it should demonstrate added resources, re-sequencing, or other credible measures.
Tip 7 - Change orders and delays lead to revisions, not just updates. New scope or an excusable delay must be incorporated through a fragnet and time impact analysis, resulting in a revised schedule, not simply recorded as progress.
Tip 8 - Choose the most protective, documented answer. CMAA questions reward transparency, contemporaneous documentation, separation of progress from plan changes, and preservation of the owner's ability to analyze delays. When two answers seem plausible, pick the one that preserves the baseline and requires written justification and approval.
Tip 9 - Watch for mixed scenarios. Some questions describe a single submittal that contains both actual progress and logic changes. The correct response recognizes that it is both an update and a revision, and that the revision portion must be separately identified and approved.

Summary
A schedule update records where the project actually stands; a schedule revision changes where the project plans to go. Updates move the data date and record actuals without touching the baseline or future logic. Revisions alter logic, durations, activities, resources, or constraints and require justification and formal approval. The CM's job is to verify the accuracy of updates, detect undisclosed revisions, evaluate proposed revisions against entitlement and reasonableness, and preserve the baseline so that delays can be analyzed credibly. Master this distinction and the related CM responsibilities, and you will be well prepared for this portion of the CCM Time Management domain.