The 21-Day Extension Request

1. Out-of-sequence logic (drywall starting before the in-wall inspection). CPM requires a predecessor to finish before its successor starts. An out-of-sequence update creates float that does not exist, moves the apparent critical path, and hides the true consequence of the delay. The prior update must be corrected before the event is analyzed, or the analysis measures the scheduler's editing rather than the project.

2. Duration compression without basis. Cutting remaining drywall from 20 days to 13 days without added crews, overtime, or a change in means and methods is not a schedule update; it is an acceleration assumption inserted silently. It removes exactly 7 days of delay from the analysis. If the contractor intends to accelerate to recover time, that is a deliberate, documented, costed decision submitted separately - not an edit buried in a monthly update.

3. The "finish no later than" constraint. A constraint eliminates negative float by declaration. It does not change the logic, does not shorten the work, and does not create time. Using it to erase 7 days of negative float means the schedule no longer identifies the longest path, which is the one thing a CPM schedule exists to do.

4. No fragnet or time impact analysis. The 21-day request is not tied to a fragment of network inserted at the time of each event with correct logic ties. Instead the contractor re-baselined the whole schedule and read the difference - which lumps owner delay, contractor delay, and schedule edits into one number that cannot be audited.

5. Combining two unrelated events into a single total. The owner-caused mock-up delay and the contractor-caused crane failure have different entitlement rules. Combining them conceals the concurrency and inflates the request.

Start with the dates. Baseline finish October 24; contract completion November 15. The difference is 22 calendar days of contractor-scheduled early finish. That is a buffer in the contractor's own plan, not owner time.

Event 1 - mock-up approval, 9 days, activity float 4 days. The delay consumes the 4 days of float and then pushes its path 5 days past its baseline position. If that path now governs the project finish, the finish moves from October 24 to October 29.

Event 2 - crane gearbox, 12 days on the critical path. Applied to a critical path, it moves the finish by 12 days.

Applied in sequence, respecting the 5-day overlap:

• Mock-up first, then crane: October 24 → October 29 → November 10.
• Crane first, then mock-up: October 24 → November 5, and the mock-up path's 5-day push does not govern because it is now 7 days shorter than the crane-delayed critical path. Finish November 5.

The credible range is November 5 to November 10, not December 6.

Entitlement: the contract completion date is not affected. Even the later figure, November 10, leaves 5 days before November 15. The contractor has consumed roughly 10 to 17 days of its own 22-day buffer, but the contract date has not been breached by either event.

Therefore: 0 days of time extension is supportable on the corrected logic. The 21-day request is overstated by 21 days, and the December 6 finish is a product of the schedule defects, not the events. If the contract contains an owner-owns-all-float clause, the conclusion is the same but the reasoning is cleaner still.

Note separately: the mock-up delay, being owner-caused but not affecting the contract date, generates no time and normally no compensable extended overhead, because no completion date was extended.

Treating the overlap. During the five days when both the late mock-up approval and the crane outage are influencing the work, the project is being delayed by one owner cause and one contractor cause at the same time. The settled rule is that a contractor does not receive an extension for a period in which a concurrent contractor-caused delay would have pushed completion regardless. The periods of the two events that do not overlap are analyzed separately; the overlapping five days are effectively absorbed by the contractor's own delay.

Because the contract date is not impacted at all on these facts, the concurrency analysis is defense in depth: it explains why the request fails even if the arithmetic were more favorable to the contractor.

What the revised submittal must contain:

1. The as-planned schedule agreed at the last baseline, unchanged, with its logic and float.
2. The last accepted update before each event, corrected for out-of-sequence progress and with constraints removed.
3. A fragnet for each event: activities, durations, and logic ties inserted at the point of impact, with the tie to the actual event dates documented.
4. Separate analyses - each event alone, then both together - with the date each one affected and the date each finished affecting.
5. The resource loading and the basis for every duration, so the 13-day drywall claim is either supported by added crews or withdrawn.
6. A narrative identifying the longest path through each window and the float consumed.

Process recommendation: require a monthly window analysis (time-of-occurrence) going forward, and re-baseline by agreement before any extension is negotiated. An extension granted on the current update would be paid for twice - once in time and once in the schedule chaos that follows.