Test the Assumptions Before the Field Does

Abstract

Major capital projects are commonly approved, funded, bid, awarded, and mobilized through a sequence of governance events that can create a false sense of readiness. An approved business case is not proof that the construction plan is executable. A competitive EPC bid is not proof that the price can support the field sequence. Notice to proceed is not proof that work packages, materials, craft, supervision, interfaces, and turnover planning are ready to support productive field work.

The distinction matters because project performance is often determined before the first major field milestone is missed. The project begins carrying assumptions that have not been tested: about scope maturity, labor availability, productivity, material timing, construction sequence, supervision capacity, contract alignment, commissioning interfaces, and the organization’s ability to respond when conditions change.

This paper sets out a decision framework for testing those assumptions before the field tests them at full cost. It draws on construction-readiness research, Front-End Loading and staged-decision concepts, and established project-management practice. It then applies a practical Torvane lens: identify the assumption carrying the decision, establish the evidence that must support it, observe the field conditions that can invalidate it, define the threshold that requires action, and preserve credible options while they still exist.

The question is not whether the project has been approved. The question is whether the evidence supports the next commitment.

The approval trap

Every major project has formal moments of commitment:

• A sponsor approves the business case.
• An owner authorizes capital.
• An investment committee approves funding.
• A lender reaches financial close.
• An EPC contractor submits a price.
• An owner selects and awards a contractor.
• Long-lead equipment is released.
• Notice to proceed is issued.
• Early works begin.
• Craft mobilizes.
• A recovery plan is authorized.
• The organization declares mechanical completion.
• Turnover begins.
• Start-up is scheduled.

Each moment is important. None, by itself, proves that the work can be delivered as planned.

A project may be technically authorized while its scope remains unstable. It may be commercially awarded while its schedule relies on untested productivity. It may have a procurement plan but lack materials at the work face. It may have craft forecasts but insufficient qualified supervision. It may have a recovery schedule that depends on adding labor to conditions already constrained by congestion, work-package immaturity, access, logistics, or unavailable materials.

This is not an argument against governance. It is an argument for a different standard of governance.

A credible approval process should not ask only:

Has the required package been prepared?

It should ask:

What assumptions are carrying this decision, what evidence supports them, what field conditions could disprove them, and what will we do if they do not hold?

That is the difference between administrative approval and execution readiness.

What established research says

Construction readiness is not a feeling

The Construction Industry Institute defines construction readiness as the activities and procedures that should be substantially complete before construction begins in order to start and sustain operations productively. CII’s Construction Readiness Assessment work identifies 228 readiness factors across 15 categories, treating readiness as a measurable, multi-dimensional condition rather than a subjective project-team judgment. The factors span the project team, planning, procurement, and materials-management conditions that shape whether work can productively begin and continue.

Source: Construction Industry Institute — Construction Readiness Assessment for Productivity Improvement

That distinction is essential.

A project can be “ready” in the sense that it has passed an internal milestone, issued a notice, or loaded a schedule. It may still be not ready in the construction sense: unable to sustain productive work without predictable disruption, rework, congestion, waiting, out-of-sequence activity, or unmanaged interfaces.

Construction readiness research has also emphasized that a checklist alone is insufficient. The purpose is not to create a score for its own sake. The purpose is to identify gaps before those gaps are converted into field losses.

Front-end work is intended to create decision quality

Independent Project Analysis describes Front-End Loading as the early planning work that improves capital-project safety, cost, and schedule performance. In a mature stage-gated approach, each phase is intended to progressively define the project, test risk, establish execution and contracting strategies, and support a decision about whether to proceed to the next commitment.

Source: Independent Project Analysis — What Is Front-End Loading (FEL) in Project Management?

The underlying logic is straightforward:

The point of Front-End Loading is not paperwork. It is to convert untested assumptions into evidence before capital and commitments become difficult to reverse.

MIT’s project-management curriculum likewise treats planning, organizing, execution, monitoring, and control as integrated elements of project performance. Planning establishes objectives, alternatives, resources, responsibilities, and methods; control requires defining the factors to be measured, generating reliable performance information, considering corrective options, and replanning when necessary.

Source: MIT xPRO — Project Management: Leading Organizations to Success

That last point matters: a credible project system must be designed not only to follow a plan but also to recognize when the plan no longer represents reality.

The Assumption Test

Every major commitment rests on a set of assumptions. Some are low consequence. Others determine whether the project can perform at all.

Torvane calls the disciplined examination of these critical assumptions the Assumption Test.

The Assumption Test is not a replacement for the owner’s governance process, the EPC’s execution plan, project controls, lender monitoring, or contractor reporting. It is an independent way to determine whether the evidence supports the commitment those systems are asking leadership to make.

Five assumptions that deserve scrutiny

The detailed questions differ by sector and delivery model. The following five assumptions, however, commonly determine whether a major project can proceed productively.

1. The scope is mature enough to release work

The assumption is often expressed as: “The design is sufficiently complete.”

The field question is different:

Can the work be released, sequenced, installed, inspected, completed, and turned over without creating predictable rework or out-of-sequence loss?

Evidence should include:

• Design and drawing-release status by construction priority.
• Work-package readiness, not merely overall document percentages.
• Open technical decisions that affect installation sequence.
• Constructability input tied to the actual construction path.
• Interfaces between disciplines, contractors, modules, equipment, systems, and areas.
• The relationship between design maturity and the near-term work-front plan.

A mature overall design percentage can conceal an immature critical work package. A schedule can show planned work without proving that the work has an executable release path.

2. Materials will support the field sequence

The assumption is often expressed as: “Procurement is under control.”

The field question is:

Will the right material, in the right condition, be available at the work face when the planned crew needs it?

Evidence should include:

• Vendor commitments and actual manufacturing or shipment status.
• Material-receipt forecasts tied to work-package dates.
• Identification of long-lead, scarce, damaged, incomplete, or nonconforming items.
• Site storage, preservation, staging, kitting, and issuance readiness.
• Material-interface risk between owner-furnished, EPC-furnished, and subcontractor-furnished items.
• A constraint log that distinguishes an expected date from an executable release date.

Material readiness is not the same as purchase-order placement. A purchase order may establish commercial intent; it does not establish work-face availability.

3. The labor plan reflects the labor market

The assumption is often expressed as: “The headcount curve is achievable.”

The field question is:

Can the project recruit, retain, deploy, supervise, and productively use the craft workforce the schedule assumes?

A craft forecast does not answer whether qualified people are actually available in the relevant geography, at the relevant pay structure, during the relevant peak period, and under the relevant work conditions.

Evidence should include:

• Local and regional craft-market conditions.
• Competing-project demand and timing.
• Wage, travel, per diem, housing, and transportation conditions.
• Actual recruitment and retention performance.
• Craft mix, not just total headcount.
• Productivity assumptions under expected weather, access, congestion, shift, and logistics conditions.
• Supervision depth and span of control at peak craft loading.

A project does not recover simply because it adds people. When work fronts, materials, access, supervision, and sequence are constrained, more people can intensify congestion and lower productivity.

4. The schedule represents a construction path

The assumption is often expressed as: “The schedule is logic-linked and has a critical path.”

The field question is:

Does the schedule represent the sequence through which work can actually be released, staffed, installed, completed, and handed over?

A credible schedule must be connected to more than activity relationships. It must reflect the delivery system:

• Work-package release and construction sequence.
• Material availability.
• Craft availability by discipline and work area.
• Temporary facilities, access, lifts, laydown, logistics, and work-face conditions.
• Interfaces between civil, structural, mechanical, electrical, instrumentation, vendor, and commissioning activities.
• The relationship between construction completion, system completion, turnover, and start-up.

The schedule should be used to expose assumptions, not to conceal them under an increasingly detailed activity network.

5. Completion and turnover have been planned early enough

The assumption is often expressed as: “Commissioning will take care of that later.”

The field question is:

Has the project established how installed work will become complete, documented, handed over, tested, and ready for an operating organization?

CII notes that system-completion and precommissioning activities commonly begin while construction is still materially underway. The transition from construction to commissioning therefore requires an early and deliberate plan—not a late-stage handoff.

Source: Construction Industry Institute — Planning Construction Activity to Support the Startup Process

The International Atomic Energy Agency makes the same point in nuclear-project guidance: commissioning preparation must begin well before construction nears completion, including planning for documentation transfer, testing, acceptance criteria, organizational preparation, and the eventual transition to operations.

Source: International Atomic Energy Agency — Project Management in Nuclear Power Plant Construction: Guidelines and Experience

The principle applies across sectors. Construction complete is not the same as ready to turn over. Mechanical completion is not the same as operational readiness. A punch list is not a turnover strategy.

Decision points are not reporting milestones

A major project has many milestones. Not all are decision points.

A milestone records that an event is expected or has occurred:

The distinction is material.

A project that treats every milestone as an automatic continuation point can preserve momentum while silently consuming its remaining options. A project with genuine decision points identifies what must be true, who must review the evidence, what threshold triggers action, and what alternatives remain.

The purpose is not to make a project indecisive. The purpose is to make decisions explicit while they can still influence the outcome.

What leadership should request

Senior decision-makers do not need every project detail. They need the evidence that tells them whether the next commitment is supported.

Before sanction, EPC award, notice to proceed, full mobilization, major acceleration, recovery funding, turnover, or start-up, leadership should request answers to the following questions.

1. What assumptions are carrying this decision?

The project team should identify the assumptions explicitly. Avoid generic answers such as “the schedule is aggressive but achievable” or “procurement is being managed.”

Ask for the specific assumptions:

• Which productivity factors are required?
• Which vendor dates are critical?
• Which work packages must release by when?
• What craft mix and supervision ratios are assumed?
• Which interfaces must be resolved?
• Which commercial conditions are required?
• Which turnover milestones are carrying the start-up date?

2. What evidence supports each critical assumption?

The evidence should be current, specific, and tied to the decision. A high-level dashboard is not enough.

Ask whether the evidence is:

• Observed, sampled, and tested—not merely reported.
• Connected to critical work fronts and system priorities.
• Based on actual conditions rather than an earlier plan.
• Reconciled across schedule, procurement, construction, commercial, and commissioning perspectives.
• Clear about uncertainty, gaps, and conditions still requiring action.

3. What conditions could invalidate the plan?

A credible project team should be able to name the conditions that threaten the plan without treating that discussion as disloyalty.

Examples include:

• Design release misses on critical work packages.
• Vendor or material slippage.
• Craft-market pressure.
• Supervision gaps.
• Site access and logistics constraints.
• Unresolved interfaces.
• Changes in labor productivity.
• Owner, contractor, or vendor decision delays.
• Completion documentation behind physical progress.
• Turnover systems not aligned with the construction sequence.

4. What threshold requires a different decision?

A risk register is not enough if it does not identify what triggers action.

Leadership should ask:

What would have to become true for us to stop proceeding on the current path?

Examples of thresholds may include a critical material date slipping beyond the last date that supports the work package; craft recruitment falling below a defined percentage of required capacity; a work-package release date missing the point at which planned sequence can be maintained; or turnover evidence failing to support the next system release.

The precise thresholds are project-specific. The discipline of defining them is not.

5. What options remain if the assumption fails?

A recovery plan should not begin after all options have been exhausted.

The project should identify the credible alternatives before the condition becomes irreversible:

• Proceed with defined monitoring triggers.
• Hold selected work while a critical constraint is resolved.
• Re-sequence work to protect productive fronts.
• Change contracting, procurement, labor, or logistics strategy.
• Revise the estimate, completion date, or completion strategy.
• Conduct an independent diagnostic before authorizing further recovery spending.
• Stop additional commitment to an approach that no longer has a credible delivery basis.

This is not pessimism. It is disciplined preservation of optionality.

Torvane perspective

The most damaging phrase in a major project is often:

We have no choice but to keep going.

Usually, choices existed earlier. They were simply not identified, tested, or escalated while leadership could still use them.

The practical role of an independent assessment is not to second-guess every project decision or to replace the organizations responsible for delivering the work. It is to establish an unvarnished fact base at the moment a consequential decision must be made.

Torvane’s Construction Readiness and Recovery Assessment examines the conditions that determine whether the plan can hold in the field:

• Execution and construction planning.
• Scope definition, work packaging, and sequence.
• Procurement, material readiness, and field constraints.
• Schedule realism and critical interfaces.
• Craft-market exposure, workforce capability, and supervision depth.
• Commercial alignment and responsibility clarity.
• Recovery options where the original plan no longer holds.
• Construction-to-commissioning, turnover, and start-up readiness.

The output is not a generic health score. It is a written readiness determination by critical area, the conditions most likely to affect performance, the thresholds requiring executive attention, and the options available to proceed, hold, re-sequence, re-baseline, change strategy, or recover.

Torvane does not manage construction, direct the work, certify readiness, accept quality, approve payment, or assume responsibility for recovery execution. Those decisions remain with the client and the organizations accountable for the project.

Limits of this analysis

No universal readiness formula can replace project-specific judgment.

The evidence needed to support a decision varies by:

• Delivery model and contract structure.
• Project sector and asset type.
• Brownfield versus greenfield environment.
• Jurisdiction, labor market, and regulatory setting.
• Technology maturity and vendor concentration.
• Module, marine, process-unit, transmission, civil, or nuclear-work interfaces.
• Stage of definition and current project condition.
• The decision being made and the remaining optionality.

This paper addresses construction execution, delivery readiness, turnover interfaces, and executive decision support. It does not address design adequacy, code compliance, safety management, quality acceptance, regulatory approval, legal claims, insurance coverage, credit decisions, underwriting, or construction direction.

Conclusion

A project does not become ready because it has been approved. It becomes ready when the evidence supports the next commitment.

That requires more than a completed governance package, a baseline schedule, an EPC award, or a mobilization date. It requires that the assumptions carrying the decision have been tested against the conditions that will determine actual field performance.

The leadership question is simple:

What must be true for this project to hold—and what will we do if it does not?

That question should be answered before additional capital, time, labor, equipment, and credibility are committed.

Test the assumptions before the field does.