# Revise a construction delivery plan

Adopt [construction basis](construction-basis.md). Produce a connected update from the caller's identified accepted baseline, data date, progress evidence, design changes, material commitments and remaining resource calendars. Inputs include requested scenarios, the decision to support, and selected Measurement, Progress, Stock, Pricing, Valuation and Scheduling contracts. The caller identifies whether a design revision, commercial change and revised execution plan are accepted or merely proposed; none implies the others.

Fulfill [document reconciliation](document-reconciliation.md) for the selected revision and [progress forecast](progress-forecast.md) to establish the supported completed and remaining state. Forward the Progress contract to that role. Apply the Measurement contract through [quantity takeoff](quantity-takeoff.md) for changed scope; preserve gross physical history, including removed or rejected work, separately from accepted work retained in the revision. Update the [scope package](scope-package.md) with unchanged interfaces and any selected Acceptance contract. Resolve or retain material conflicts before presenting an unconditional revised plan.

Fulfill [material balance](material-balance.md) with that actual state and the selected Stock policy; its dated residual coverage and proposed purchases become inputs to [cost estimate](cost-estimate.md) and [construction schedule](construction-schedule.md). Apply Pricing to cost, Scheduling to resources, and Valuation through [change valuation](change-valuation.md) to the identified comparator. Estimate cost at completion from actual cost plus remaining cost, eliminating overlap with commitments; separately show the amount still unpaid where requested. Forward cost consequences of calendars, idle reservations, overtime or an extra crew into the estimate. Derive site-duration charges from the same completion event the schedule reports.

If the caller selects a Recovery worker, invoke it with the reconciled remaining work, material dates, resource calendars, immutable actual history and permitted measures. It must produce its concrete candidate resource/schedule/cost basis. Use that basis in a separate schedule and estimate instance; shared scope and acceptance requirements remain binding. A different worker can propose a materially different permitted recovery without changing the accepted baseline. Do not present its output as adopted capacity or an approved change. If time impact is requested, fulfill [time impact](time-impact.md) with the identified comparator and explicit local Impact policy.

Return a usable revision package: source-to-scope reconciliation; physical and accepted progress; materials; cost-at-completion and incremental bridge; feasible remaining schedules; alternatives and their decision consequences. Trace each important change across these roles, retaining source and binding origins. Explain changes caused by scope, productivity, commitment constraints and calendar effects rather than hiding them in one variance. Partial or blocked roles remain visible. Future updates require a named owner and an actual invocation arrangement; this contract does not create a monitoring service.