The working question
Which unverified condition would invalidate this recovery option?
Keep the current forecast visible
A recovery proposal often arrives as a new finish date. Before accepting it as a plan, ask what changed in the work, resources, access, sequence, or decision timing. A shorter bar on a schedule is the result of an assumption. The team needs to understand and test that assumption before relying on the date.
Preserve the current forecast and the authorized comparison milestone. Model alternatives as named scenarios rather than overwriting the baseline. Record the reporting cutoff, the evidence available at that cutoff, and the person responsible for validating each enabling condition. An optimistic scenario is not an approved commitment.
The schedule-health guide examines bounded input checks. This article addresses a later management decision: how to compare recovery options once a delay or adverse forecast has been identified. A clean input file alone does not make a proposed recovery feasible.
Give every option an assumption record
Define the changed mechanism
Carry forward the current specifications, design decisions, owner-reviewed requirements, and submittal dispositions before changing the sequence. Ask the general contractor to confirm that the proposed recovery uses the current requirements and includes the required design and owner reviews, tests, and inspections. Identify a proposed substitution or changed requirement explicitly and follow the contract’s review and change process; deleting a review activity is not a recovery measure.
State whether the proposal shortens an activity, overlaps work, changes scope, or removes a constraint. Identify the activities and interfaces affected. “Add manpower” is incomplete without the required skill, workface capacity, supervision, and evidence supporting a different production rate. Extra people do not automatically create proportional time savings.
Separate enabling conditions from actions
An action might be to request another crew. The enabling condition is that the appropriate crew can actually work in the available area when needed, with the required support. Record the evidence that would establish that condition and the latest useful decision date. If the evidence is unavailable, keep the option conditional.
Let the entity controlling each enabling condition make the commitment: the trade partner confirms crew capacity, the manufacturer or its supplier confirms production, and the assigned reviewer confirms review availability. The general contractor coordinates and tests those commitments together; it cannot confirm another entity’s capacity by shortening a schedule bar. Retain the confirming party, scope, date, conditions, evidence, and current document revision. Until confirmed, the recovery date remains the contractor’s planning scenario, subject to required professional reviews and authorization.
For each option, identify the current specification and drawing revision, affected submittal and review disposition, and the professional responsible for confirming any technical assumption. If specifications are not available, retain the documented planning basis and route the gap for clarification rather than assuming a requirement can be omitted. Reuse an existing valid decision; reopen it only when a changed condition requires clarification or an authorized revision.
Compare cost on an explicit basis
Show the incremental cost assumed for each alternative and what it excludes. Distinguish a planning allowance from a supplier quotation or an approved change. Check whether supervision, access, remobilization, inspection, or rework risk changes as well. An option should not appear free merely because its secondary costs have not been estimated.
Check procurement funding alongside the promised dates. Required submittal approval and release conditions may allow an order to proceed, with eligible stored materials included in monthly billing under the contract. Record the required approvals, protection and payment evidence, and any remaining transport obligation. Paying for offsite material does not validate a recovery date or establish that the item is ready at the workface.
Recalculate the actual network
Review affected calendars, relationships, resources, and downstream work in the native schedule. Examine whether the controlling path moves. Local activity savings may be absorbed by another constraint before they reach the project milestone. Do not add savings from two alternatives without testing their combined logic and shared requirements.
Worked example: three scenarios, no promised recovery
Fictional teaching example · elapsed calendar-day model
A fictional interior sequence begins November 9, 2026. Its current model allows six days for preparatory installation, four for finishes, and two for review and return. In this simplified chain, all work is sequential, durations are elapsed calendar-day offsets, and finish is start plus duration. Twelve days gives November 21. The comparison target is November 19, so the current model is two days late.
| Scenario | Model | Finish | Against target |
|---|---|---|---|
| Current sequence | 6 + 4 + 2 = 12 days | November 21 | 2 days late |
| Additional-crew hypothesis | 4 + 4 + 2 = 10 days | November 19 | Matches target |
| Area-overlap hypothesis | 6 + 4 + 2 − 3 = 9 days | November 18 | 1 day earlier |
The crew hypothesis assumes the first activity can be reduced from six days to four. Its incremental labor allowance is eighty hours at $65 per hour, or $5,200. The rate is an invented planning input; the allowance excludes all other effects. The duration and added hours are separate hypotheses, not a demonstrated productivity relationship.
The overlap hypothesis assumes three days of finishes can occur in independently released areas while preparatory work continues elsewhere. It carries an invented $1,800 coordination allowance. Area boundaries, access, compatible work methods, review availability, and downstream effects remain unverified. The arithmetic does not authorize concurrent work.
The worked record leaves both alternatives conditional. It does not combine their savings or select a winner. The reporting cutoff is October 26; evidence is requested by November 2 so the team can reassess the proposed November 9 start. The example provides no probability of completion and no actual project outcome.
Use the option record
The blank CSV has one empty row. The worked file contains the current sequence and two alternatives under the same scenario group. Record the revision, cutoff, start, target, individual durations, proposed overlap, modeled duration, modeled finish, and variance. Positive variance means later than the target; negative means earlier. These are manually reviewed values, not formulas in the file.
Complete the requirement-document and revision fields, design and owner review roles, required review reference, actual disposition and evidence reference, and contractor currentness check. Use the unresolved-requirement field to identify a gap and its next action. These entries carry the existing project basis into the record; filling them does not grant review approval or authorize a change.
Record the entity controlling the milestone, its scope, confirmation status and date, evidence and conditions, and the contractor’s separate forecast and coordination action. Check that the confirmation still covers the current revision. Unconfirmed values remain planning estimates.
Use a stable option identifier and separate fields for the enabling condition, evidence required, responsible role, decision deadline, status, cost basis, and exclusions. Keep the original forecast row as the comparison. Multiple scenario rows are alternatives; their durations and costs must not be summed as a single plan.
The CSV does not calculate the critical path, verify resource capacity, detect unsafe overlap, or validate working calendars. Use the actual planning system and qualified reviewers for those questions. If a duration or cost cannot be supported, leave it unknown and describe the evidence needed instead of inserting a reassuring estimate.
After an option is authorized through the project’s normal process, retain the approval reference and update the operational plan. At the next reporting cutoff, compare observed production with the assumption. If the assumption fails, preserve that result and revise the forecast; do not keep reporting the original recovery date as though the enabling condition had occurred.
Companion tool · Version 1.1
Recovery option and assumption record
A blank record and a separate fictional worked CSV. The files contain plain data, with no formulas, macros, automated checks, or account connection. Read the article before adapting the fields.
Download blank CSVAsk what would change the decision
Before recommending an option, identify the most consequential unresolved condition and the evidence that could disprove it. Check competing demands on crews, work areas, reviewers, and materials. Confirm whether an apparent local gain survives the complete schedule calculation and whether its incremental cost is affordable and authorized.
A disciplined comparison can conclude that none of the options is ready. That is useful when it names the missing evidence and the next decision date. Both fictional recovery options remain subject to the current specified work and required reviews, inspections, and testing; their shorter durations do not waive those obligations. The record supports transparent planning; it does not establish delay entitlement, certify the schedule, or guarantee that additional spending will recover time.
Release edition · 2026-10-21 · Companion file version 1.1-review. All scenarios, durations, costs, and dates are invented.
Sources, method & limitations
The explanation, field structure, and fictional scenario are original teaching material. The cited primary guidance provides context; it does not endorse this resource or make its records an official approval process.
- GAO Schedule Assessment Guide, GAO-16-89G (2015)
Background on integrated schedules, dependencies, baseline comparisons, and the connection between time and cost. The date examples and review records here are original teaching devices, not a GAO assessment. - GAO Cost Estimating and Assessment Guide, GAO-20-195G (2020)
Background on defining estimate scope, documenting assumptions, and updating estimates with actual information. The examples do not reproduce a government cost model. - Caltrans Construction Manual, section 5-1: Project Records and Reports (November 2024)
Background on retaining organized project records. These CSV fields and examples are independently authored, not copied Caltrans forms or a mandated filing structure. - AIA Contract Documents: what is a submittal in construction?
Background on required submittals and their review against project requirements. The project’s own contract determines the responsible roles and procedures; a submittal disposition does not itself replace a required contract modification. - AIA Contract Documents: payment for materials stored offsite
Explains A201–2017 section 9.3.2 as one contractual approach: advance owner approval for offsite storage and payment, an agreed location, protection of the owner’s interest, and applicable insurance and transport arrangements. The executed project contract governs eligibility. - AIA Contract Documents: payment applications and stored-material reconciliation
Describes required payment support and moving stored value to completed work as incorporation occurs without charging for the same material twice. Use the project’s actual payment rules and applicable waiver requirements.
Apply the actual project requirements and obtain the relevant professional review. This guide does not establish contractual entitlement, certify technical performance, or replace authorized acceptance. No actual client record or project outcome is represented by the fictional examples.
Release edition · October 21, 2026. Source notes identify the references used in preparation. Report an error or review our correction policy.