Module 3 - Time Management
The baseline schedule is the approved plan against which all later performance is measured. The CM reviews the contractor's proposed baseline before accepting it, and acceptance is not a formality. A CM who accepts a defective baseline has surrendered the measuring stick for the rest of the project.
A baseline review looks for: activity durations that are reasonable for the scope and crew sizes stated; logic that reflects how the work will actually be built rather than a mathematical convenience; no open ends, meaning every activity except the first has a predecessor and every activity except the last has a successor; constraint dates used sparingly and justified; float that has not been artificially sequestered through inflated durations; a critical path that makes physical sense; and resource loading consistent with the contractor's stated plan if the contract requires it.
Schedule updates are typically monthly and are the CM's principal early warning system. In an update, actual start and finish dates are recorded for completed and in-progress work, remaining durations are re-estimated, and the network is recalculated. The critical path can and does shift between updates, which is one reason a single snapshot at the end of a project is a poor basis for delay analysis.
The trap to watch for is the silent baseline revision. A contractor submits an update in which logic has been changed, durations have been shortened, or activities have been deleted, without flagging those changes. The recalculated schedule then shows recovery that has not actually occurred. The CM compares each update against the prior one and requires that any logic or duration change be identified and justified in writing. Software can produce this comparison, but the CM must actually read it.
Every delay question on the exam reduces to two axes, and you should categorize before answering.
The first axis is excusable or non-excusable. An excusable delay is one beyond the contractor's control, entitling the contractor to a time extension. A non-excusable delay is the contractor's own fault, entitling them to nothing and exposing them to liquidated damages.
The second axis is compensable or non-compensable, and it applies only to excusable delays. A compensable delay entitles the contractor to both time and money, and it typically arises from owner-caused events such as late owner-furnished equipment, defective design documents, or owner-directed changes. A non-compensable excusable delay entitles the contractor to time only, and it typically arises from events beyond both parties' control such as unusually severe weather, strikes, or acts of government.
Combining the axes produces three practical outcomes. Owner-caused delay yields time and money. Force majeure yields time only. Contractor-caused delay yields nothing and may trigger liquidated damages.
When an owner-caused delay and a contractor-caused delay overlap in the same period and both independently affect the critical path, the delay is concurrent. The general rule the exam expects is that concurrency yields time but not money. The contractor gets the extension because the owner contributed, but is denied delay damages because the contractor was also at fault. Jurisdictions vary on the details and the analysis can turn on whether the delays are truly concurrent or merely sequential within the same month, but the exam wants the general rule.
Liquidated damages. These are a pre-agreed daily amount the contractor pays for late completion. They must be a reasonable forecast of the owner's actual anticipated loss at the time of contracting, not a penalty. If they function as a penalty, courts may refuse to enforce them. A properly set LD amount protects both parties by making the exposure knowable in advance.
Notice. Nearly every delay claim rises or falls on notice. Contracts impose a short time limit, commonly measured in days or a few weeks from the event, within which the contractor must give written notice of a claimed delay. Missing notice can forfeit an otherwise valid claim. The CM's duty runs both ways here: track notices received, and do not quietly benefit from a contractor's procedural lapse when the CM knows the delay was genuinely owner-caused. The exam rewards the answer that documents contemporaneously and deals honestly.
Classifying a delay is only half the job; proving how much time it actually consumed requires a method, and several are in common use. An as-planned versus as-built comparison lays the original baseline schedule side by side with what actually happened and looks for the difference; it is simple and cheap but weak, because it does not account for the critical path moving over the course of the project, and it tends to overstate or understate impact depending on which single path is compared.
A windows analysis (sometimes called a contemporaneous period analysis) breaks the project into consecutive time periods and updates the schedule at the start of each window, then measures which delays actually drove the critical path during that specific window. Because it uses the schedule as it stood in real time, it correctly captures the critical path shifting between updates, which is why it is generally considered stronger evidence than a single as-planned versus as-built comparison.
A time impact analysis (TIA) inserts a specific delay event, as a fragnet, into the schedule that was current immediately before the event occurred, and calculates the net impact to completion that single event caused. TIAs are typically prepared close to the time of the event itself, which is exactly why contemporaneous notice and documentation (the previous section) make a later TIA far more defensible.
A collapsed as-built analysis starts from the actual as-built schedule and removes, one at a time, the delays attributable to one party, recalculating what completion would have been without them. It is powerful for isolating the effect of specific events after the fact, but it depends heavily on the accuracy and completeness of the as-built record, which is only as good as the contemporaneous documentation behind it.
Why this matters for the exam
A scenario naming a specific delay method is usually testing whether you know its core weakness: as-planned versus as-built ignores a shifting critical path, and any retrospective method is only as strong as the contemporaneous records, notices, and updates that were actually kept at the time.
1. Unusually severe weather that halts work is typically:
2. Late delivery of owner-furnished equipment is typically:
3. Under the general rule, concurrent owner and contractor delay yields:
4. A contractor submits an update showing dramatic recovery, achieved by shortening durations without explanation. The CM should:
5. Liquidated damages are unenforceable if they:
6. An open-ended activity in a baseline schedule, with no successor, is a problem because:
7. A contractor experiences a genuine owner-caused delay but fails to give written notice within the contractual period. The likely result is:
8. The critical path shifting between monthly updates is:
9. Accepting a defective baseline schedule harms the CM's position because:
10. Which delay analysis method is generally considered strongest because it accounts for the critical path shifting between updates?
11. A time impact analysis (TIA) works by:
12. A collapsed as-built analysis is most limited by:
13. Why is a simple as-planned versus as-built comparison considered a weak method on its own?
14. Why does contemporaneous notice and documentation make a later time impact analysis more defensible?
Write three short delay scenarios from your own experience or invention: one owner-caused, one force majeure, one contractor-caused. For each, state the classification on both axes, the entitlement that follows, and the specific notice the contract would require. Then write a fourth scenario in which two of them overlap, and state how you would analyze it.