Capital project recovery needs a usable baseline

Preserve the record before resetting the plan

Separate the original baseline, the current forecast and the record of authorised changes. The baseline describes the reference against which management agreed to track delivery. The forecast describes the sequence now expected under stated assumptions. A change record explains a decision affecting that comparison. Replacing the baseline with the forecast can conceal the difference that management needs to understand.

Preserve each source schedule with its scope, status cut-off, version and authorising instruction where available. Identify the work-package definitions, calendars and dependencies used to construct it. Retain the accompanying narrative and assumptions, not merely a picture of milestone dates. A schedule image may show the intended sequence without exposing the conditions on which that sequence depends.

Establish a common work-package register before comparing versions. Link each package to its defined output, responsible delivery role and receiving operation. Record where a package has been split, merged or renamed so that its history remains traceable. A change in reporting structure should not make unfinished work disappear or make the same work appear as an additional package.

Where the historical record is incomplete, label any reconstructed reference as a reconstruction and identify its sources and limitations. Keep inferred relationships separate from contemporaneous instructions. Do not backdate a management decision or present a newly assembled sequence as the plan previously in force. Questions about contractual significance or responsibility for delay belong with directly appointed qualified providers, not the person reconciling schedule files.

When management adopts a revised control baseline, preserve the bridge from the earlier reference. Record the scope carried forward, authorised changes, unresolved differences and assumptions behind the revision. State when subsequent reporting begins using it and retain the earlier comparison. The reset should establish a usable reference for future decisions without suggesting that previous departures have been explained, accepted by other parties or reversed.

Reconcile reported progress with supporting evidence

Define the event behind each progress label. Fabrication finished, dispatched, received, installed and accepted describe different states. Identify which state the work package tracks and what source can substantiate it. Preserve the distinction between the contractor's reported status, records supplied to management and the receiving role's confirmation. A status inherited from another package should retain its original meaning.

Consider an illustrative scenario in which a supplier marks an equipment package complete because fabrication has finished. The project report carries that status into the installation package, although dispatch records, site receipt and receiving-team acceptance have not been located. The discrepancy concerns what complete means and what evidence exists. Missing records alone do not establish whether the later activities occurred.

Trace the package through the available source references. Identify the equipment or delivery concerned, the event recorded, the reporting cut-off and the custodian able to explain it. Separate an event's occurrence from the later entry of its record. If a source covers only part of the package, preserve that boundary rather than extending its status across the whole reported output. Carry package revisions into the evidence map as well. A record supporting an earlier configuration should not silently support its replacement; ask the responsible specialist to identify what remains applicable.

Give discrepancies an owner and a defined next action. A missing receipt reference requires retrieval or an explanation from the receiving operation; a question about technical completion requires the assigned qualified specialist. Operational coordination can connect records and follow outstanding actions. It should not determine engineering adequacy, infer acceptance from physical presence or substitute a project-status label for a required specialist determination.

Carry remaining work into the forecast explicitly. Identify incomplete activities, unresolved evidence and any corrective work reported by the responsible provider as distinct entries. Record who can establish their status and what subsequent activity depends on them. When a headline progress label changes, retain the source and reason. The correction may improve reporting accuracy without representing additional work completed on the project.

Expose the dependencies behind the forecast

Start from a delivery event management needs to decide about and trace its prerequisites backwards. Identify the design information, access, procurement, resources, specialist determinations and management instructions required before the receiving activity can proceed. Replace a broad dependency such as site readiness with the specific input and receiving role. Each connection needs a condition that its owner can demonstrate or explain.

Distinguish an intended date from a supported dependency. A supplier's proposed dispatch date may rely on documents that remain outstanding or a production slot that has not been established. Preserve the supplier's statement and the conditions attached to it. Do not convert an indicative date into an unconditional input merely because the scheduling system requires a value.

Ask the schedule owner to explain the relationships driving the forecast. Record activities held by imposed dates, dependencies changed since the previous version and remaining durations supplied by delivery owners. Where work is already underway, check that the model still represents the prerequisites and unfinished activities reported by those owners. Treat an unexplained change in logic as a question, not automatic evidence of acceleration.

Examine shared constraints across work packages. Different activities may depend on the same access window, specialist team or supplier input. Link those demands to a common constraint record so that separate package forecasts do not each assume unrestricted availability. Record whose allocation decision is needed and the activities it affects. Management should see the contention before accepting apparently compatible package dates.

Keep uncertainty visible without inventing probabilities or durations. For a risk, record the uncertain event, exposed activity, available evidence and response owner. Distinguish it from a dependency already known to be missing. Where the relevant owners supply alternative assumptions, keep the resulting sequences separate and identify what would determine which applies. A schedule model is a conditional representation of the work, not a prediction that those conditions will occur.

Compare recovery options before choosing activity

Define the constraint the proposed recovery action is meant to address. Bringing forward an activity matters only if the resulting output becomes usable by the work that follows. Identify the receiving dependency and the evidence needed to show that it can take advantage of the change. More activity on the site or in a supplier's facility is not itself evidence of an improved delivery sequence.

In the illustrative equipment scenario, separate fabrication completion from the unresolved dispatch and receiving conditions. Compare the proposed actions against those conditions rather than treating additional fabrication effort as a general remedy. An earlier shipment might merely transfer waiting into storage if the receiving location cannot accept it. Record that as a scenario consequence to establish, not an assumed outcome.

Prepare an option record covering the proposed sequence, necessary inputs, affected packages, temporary arrangements and unresolved questions. Keep an option dependent on additional resources separate from one that changes the order of work. Ask directly appointed qualified providers to determine engineering, safety and contractual implications within their remit. The operational comparison organises their inputs without making technical choices on their behalf.

Use a common comparison boundary. Include work displaced into another package, continuing support, access requirements and any temporary receiving arrangements. Record management-cost inputs supplied by the authorised client function with their source and exclusions. A proposal should not appear preferable because its supporting work is omitted or assigned elsewhere without an owner. Keep any proposed completion effect tied to the assumptions producing it. Retain the current forecast as an explicit comparison option. Otherwise, a proposed recovery sequence can appear to offer an improvement merely because it is being compared with an obsolete plan rather than the operation management now faces.

Present management with the action each option would require and the conditions preventing execution. Identify commitments that cannot simply be reversed, pending work needing protection and circumstances that would trigger reconsideration. Separate selection for further preparation from authority to instruct live work. The output is a conditional recovery choice and its decision record, not permission to bypass specialist requirements or a guarantee that the project will finish earlier.

Connect changes to management authority

Give each proposed change a stable reference connecting its cause, affected scope, schedule consequences and management-cost inputs. Distinguish a proposal, an authorised instruction, implementation and observed effect. Link the relevant records without treating these states as interchangeable. A contractor including an activity in its latest forecast does not, by itself, establish that client management authorised the corresponding scope or commitment.

Identify who can decide the change and who must receive the resulting instruction. Record the boundary of delegated authority and any unresolved dependency on directly appointed qualified providers. Keep programme coordination separate from client decisions, signatures and payments. A coordinator may assemble the options and track the instruction without directing reserved technical work or making a commercial commitment for the client.

Align the reporting cut-off across scope, schedule and management-cost records, or state where their periods differ. Preserve links from each changed package to the financial information supplied by the authorised client function. Ask that function to explain how commitments, recorded expenditure and expected remaining work relate in its forecast. Do not combine overlapping amounts or apply accounting treatment through an operational change register.

Track implementation through the receiving teams. Identify which schedule, work instruction and provider record should reflect the authorised change, together with the evidence that the instruction reached its intended recipient. Acknowledgement establishes receipt, not execution or agreement with every implication. If records conflict, retain the discrepancy and return the unresolved question to the role with authority over it.

Keep decisions made under urgent conditions traceable under the client's established authority arrangements. Record the instruction actually given, its scope, source and continuing limitations without inventing a retrospective authorisation. Where work is reported outside the recorded authority, preserve the facts and escalate the question. Do not rewrite the change history or infer a contractual obligation merely to make the scope and cost reports agree.

Test whether the revised control cycle is working

Use the next reporting cycle to examine whether the preceding decisions reached the operation. Start with an action that was expected to remove a dependency and trace its instruction, execution evidence and receiving-party response. Keep its original reference and expected condition visible. Moving the due date or changing the owner should not erase the action's history or count as progress.

Return to the equipment scenario after the dispatch records have been supplied. Establish whether that resolved the specific blocker, whether the receiving operation could take the package and whether another prerequisite still prevents installation. The evidence may support closure of the document action while the installation dependency remains open. Keep those conclusions separate rather than carrying the completed action's status into every linked package.

Compare successive forecasts with their assumptions and source changes attached. Identify whether a date moved because work occurred, a duration changed, a dependency was removed or the model was corrected. An unchanged completion date also needs explanation when its prerequisites deteriorate. Ask the schedule owner to show the revised sequence rather than allowing a fixed reporting target to conceal unresolved work.

Close actions against the condition stated when they were assigned. Preserve any remaining limitations and reopen the item when later evidence contradicts its closure basis. A revised procedure or supplied document may address a reporting gap without demonstrating changed delivery. Group recurring failures for a management decision about ownership, sequencing or unavailable inputs, rather than issuing the same unexecutable instruction again.

Hand over the baseline history, current forecast, change register, risk record and unresolved decision queue with their source references. Ask the receiving owner to trace a selected package from reported status to the evidence and authority behind its next action. The deliverable is a usable control record with stated inputs and limitations, not a declaration of engineering adequacy, verified financial recovery or assured completion.

Where this connects to a mandate

Capital project controls and recovery connects a delayed capital programme to cost, schedule, risk and decision records with stated inputs and limitations. Mericad provides non-regulated analytical and project-management support; client management decides, signs, pays and operates. Directly appointed qualified providers retain technical determinations and reserved professional conclusions; a project-status record is neither engineering certification nor a completion guarantee.