Assumption Debt in Projects: the Hidden Liability Leaders Miss
Major projects rarely fail because one person wrote “assume” in a spreadsheet. They fail when dozens or hundreds of reasonable assumptions survive long enough to become invisible.
A plot plan assumes tie-in access during a short shutdown. An estimate assumes normal ground conditions because the geotechnical campaign is incomplete. A procurement schedule assumes long-lead equipment will receive vendor data on time. A commissioning plan assumes utilities will be available before mechanical completion. Each assumption may be sensible when made. The problem starts when the project keeps building on them without proving, retiring, or openly carrying them.
That is assumption debt.
Like technical debt in software, assumption debt is the accumulated project liability created when unverified assumptions are used as if they were confirmed facts. It grows quietly during concept development, estimating, FEED, tendering, EPC execution, construction, commissioning, and handover. By the time it shows up, it often looks like a cost overrun, a schedule slip, a contract dispute, a safety concern, or an operational readiness problem.
In capital-intensive sectors, this is not administrative housekeeping. It is commercial risk, technical risk, and leadership risk.
How Assumption Debt Builds Across The Project Lifecycle
Assumptions are not the enemy. Projects need them. They allow teams to estimate, plan, contract, and move forward before every detail is known.
The issue is that assumptions have a shelf life. If they remain untested past the point where decisions depend on them, they become debt. The project has borrowed certainty from the future.
Concept Development Creates The First Layer
Early studies often carry broad assumptions about scope, site conditions, permitting, interfaces, technology selection, execution strategy, market capacity, logistics, and stakeholder approvals. At this stage, assumptions help compare options.
A mining project may assume a haul road can follow an existing corridor. A marine facility may assume dredging volumes based on limited bathymetric data. A transmission project may assume access to land corridors based on early desktop review. An oil and gas brownfield concept may assume existing utility capacity is available because as-built records show sufficient nameplate capacity.
These assumptions are acceptable only if the project records them clearly and treats them as open questions. Trouble starts when concept assumptions flow into the business case, then into the funding request, then into the target budget, while each presentation softens their uncertainty.
Front-end planning bodies such as the Construction Industry Institute have long emphasized the value of scope definition and front-end loading. AACE International cost estimate classification guidance also links estimate accuracy to project definition maturity and requires a clear basis of estimate. The practical message is simple: the less mature the definition, the more visible the assumptions need to be.
Estimating Turns Assumptions Into Money
Estimates are full of assumptions. Productivity rates, escalation, logistics, labor availability, weather allowances, contractor markups, contingency, design growth, temporary works, tie-in hours, commissioning support, and vendor data timing all require judgment.
A shutdown estimate might assume 24-hour access to equipment once the plant is handed over. A refinery revamp may assume scaffold quantities based on typical ratios. A metro project may assume night work permits are available. A utility-scale solar project may assume standard trenching productivity across the site.
These inputs often become embedded in estimate line items, indirect cost models, risk allowances, and schedule-derived costs. If the estimate basis is thin, reviewers may challenge totals but miss the buried assumptions driving them.
A good basis of estimate should not read like a defensive note written after the number was agreed. It should state what is known, what is assumed, what is excluded, what remains unresolved, and what evidence would change the estimate.
Feed Gives Assumptions Technical Authority
FEED can turn assumptions into drawings, datasheets, execution plans, and procurement packages. That gives them credibility.
A process design may assume feed composition ranges that later prove too narrow. A civil design may assume bearing capacity from preliminary investigation. A brownfield layout may assume underground services are in the locations shown on old drawings. A construction methodology may assume crane pads can be installed without relocating live services.
Once these assumptions appear in design deliverables, downstream teams may treat them as confirmed engineering inputs. Procurement may place orders. Contractors may price work. Planners may sequence activities. Change control may later struggle to separate real scope change from correction of an unverified assumption.
This is where assumption debt becomes expensive. The project has now spent money and committed schedule logic around something still waiting for evidence.
Contracting Can Transfer Assumptions Without Making Them Disappear
Contracts often appear to solve assumption problems by allocating risk. They do not eliminate the uncertainty. They only decide who pays, who proves, and who suffers when the assumption fails.
A tender package may state that access roads are “available,” while the site team knows two permits remain open. A client may include legacy drawings “for information,” while contractors rely on them to price a brownfield scope. A contractor may assume free issue equipment arrives by a required date, while the procurement plan depends on vendor data not yet approved.
RICS, ICE, and government infrastructure guidance frequently stress clarity of scope, risk allocation, and information quality in procurement. The commercial point is straightforward: ambiguous assumptions invite claims, inflated pricing, strained relationships, and defensive behavior.
When assumptions sit outside the contract baseline, they return later as arguments about reliance, entitlement, delay, disruption, and fitness for purpose.
Procurement And Construction Harden Assumptions Into Physical Commitments
Procurement has little patience for uncertainty. Long-lead items need purchase orders. Fabrication needs dimensions. Logistics need routes. Vendors need approved documents.
If the project assumes vendor data will arrive in six weeks but the design cannot progress without it, the schedule logic is already exposed. If imported modules assume unconfirmed port-handling capacity, the logistics plan carries hidden risk. If materials are ordered before late design reviews close, quality and rework exposure grows.
Construction then tests assumptions brutally.
Ground conditions differ. Underground services are not where expected. Temporary works take longer. Permits restrict working hours. Local labor productivity does not match the estimate. Interface areas are congested. Weather windows close. Brownfield isolation plans become more complex once operations review them in detail.
None of these outcomes is unusual. What makes them damaging is treating assumptions as settled inputs.
Commissioning And Handover Expose What Execution Concealed
Commissioning is where assumption debt often matures all at once.
A project may assume construction completion packages are clean enough to support systemization. It may assume vendor representatives are available. It may assume energization permits, utilities, control system configuration, spares, operating procedures, training, and maintenance master data will be ready when needed.
On industrial projects, commissioning problems are rarely confined to one discipline. A late instrument loop affects functional testing. Missing vendor documentation affects regulatory acceptance. Incomplete punch clearance affects mechanical completion. Poor preservation affects equipment reliability. Unresolved operating assumptions affect safe start-up.
Process safety guidance from organizations such as IOGP and the Energy Institute strongly emphasizes readiness, barriers, management of change, and disciplined handover. These themes matter because operations inherit the consequences of project assumptions. If unresolved assumptions are passed into handover as “to be managed by operations,” the debt has not been retired. It has changed owner.
Why Normal Governance Often Misses Assumption Debt
Most large projects have governance. They have stage gates, risk registers, cost reports, schedules, action trackers, dashboards, assurance reviews, and change control boards. Yet assumption debt still grows inside them.
That does not mean governance is useless. It means governance often looks in the wrong places.
Risk Registers Do Not Always Capture Assumed Certainty
A risk register tends to capture uncertain events. “Ground conditions may differ from survey data” fits that model. But many assumptions are not written as events. They are written as planning inputs.
The schedule assumes permit approval by a date. The estimate assumes a productivity norm. The contract assumes access. The design assumes data accuracy. The commissioning plan assumes systems will be complete in sequence.
Because these items appear as inputs rather than threats, they may not enter the risk register. Even when they do, the risk description may be too broad to drive validation. A risk owner may monitor the issue, while no one owns the underlying assumption.
ISO 31000 frames risk as the effect of uncertainty on objectives. That definition is broad enough to include assumptions, but many project processes still treat assumptions as background information, not active risk sources.
Project Controls Can Report Precision Without Proving Accuracy
A cost report can be arithmetically correct and still rest on weak assumptions. A Level 4 schedule can show logic, float, and critical path, while the underlying durations depend on unproven access, productivity, and approvals.
Earned value, progress measurement, and milestone tracking can reveal variance after it starts. They are less effective at exposing the assumptions that make the baseline fragile.
This is especially true when the baseline has been politically hardened. Once teams approve a sanction estimate, contract date, or public opening milestone, they may hesitate to challenge the assumptions behind it. Reporting then focuses on performance against the baseline, not whether the baseline still represents reality.
Stage Gates Can Reward Confidence Over Evidence
Stage-gate processes are meant to prevent immature projects from moving forward. They can also create pressure to present a clean story.
At investment approval, teams may summarize assumptions in appendices while highlighting NPV, schedule, contingency, and delivery confidence. At tender approval, unresolved items may be described as manageable clarifications. At handover readiness reviews, teams may reframe open assumptions as operational actions.
Experienced reviewers know this pattern. The slide deck gets sharper, while the evidence remains thin.
Good assurance asks, “What would have to be true for this plan to work?” Better assurance asks, “Which of those things have we proved, and which are we still assuming?”
Commercial Incentives Can Bury Uncertainty
Assumption debt also grows because different parties benefit from temporary clarity.
Clients want budget confidence. Contractors want a priceable scope. Designers want frozen inputs. Vendors want approved data. Sponsors want a sanction case. Lenders and public stakeholders want dates and commitments.
None of these motives are improper. Together, they can encourage unresolved uncertainty to be packaged as manageable detail.
This is common in EPC and infrastructure programs. A contractor may accept assumptions to win work, then recover through variations. A client may push assumptions into the contractor’s risk allocation, then face pricing premiums or disputes. A joint venture may defer uncomfortable validation because it threatens the approved business case.
The debt does not disappear. It accrues interest through contingency drawdowns, claims preparation, management time, rework, resequencing, and lost trust.
Assumptions Are Not Facts, Constraints, Risks, Dependencies, Or Decisions
One reason assumption debt survives is poor language. Teams use “assumption” as a catch-all for anything uncertain, inconvenient, inherited, or undecided.
That weakens management discipline. These terms are different and should be treated differently.
Term | What it means in practice | How it should be managed |
Assumption | A statement accepted as true for planning until verified or replaced | Record it, assign an owner, define evidence, set a validation deadline |
Fact | A verified condition supported by reliable evidence | Reference the evidence and protect it through configuration control |
Constraint | A fixed limitation the project must work within | Build it into scope, schedule, cost, contracts, and approvals |
Risk | Uncertainty that may affect objectives | Assess probability and impact, define response actions, monitor exposure |
Dependency | Something the project needs from another party, system, package, or event | Track the interface, owner, due date, acceptance criteria, and fallback |
Decision | A choice made by authorized people based on available information | Record the rationale, authority, consequences, and change process |
A simple test helps. If someone says, “We are assuming this,” ask what would make that statement no longer an assumption.
If the answer is a survey, permit, vendor submission, signed agreement, constructability review, test result, operations acceptance, or board decision, then the project needs a validation plan. If the answer is “nothing, that is just how we are proceeding,” then it may be a decision and should be governed as one.
This distinction matters under pressure. Calling something an assumption can make it sound temporary and harmless. Calling it an unresolved design input, unvalidated access condition, or unconfirmed operating requirement makes the exposure harder to ignore.
The Consequences Are Wider Than Cost And Schedule
Cost and schedule impacts get attention because they are visible. Assumption debt is more dangerous because it can affect the whole project system.
Cost Growth And Contingency Erosion
Unverified assumptions create underestimated quantities, missed indirects, duplicated work, late procurement, acceleration, standby, and rework. They also reduce contingency's usefulnesspackage unresolved uncertainty because the project spends it on items that were knowable but not validated.
AACE International guidance separates estimate basis, assumptions, exclusions, and contingency because each serves a different purpose. Contingency should address expected uncertainty within the defined scope. It should not become a quiet fund for unresolved assumptions that no one wanted to test.
Schedule Fragility And False Float
Schedules often depend on assumed access, approvals, design release dates, crew productivity, inspection availability, third-party interfaces, and commissioning sequence. When those assumptions fail, float disappears quickly.
A shutdown project may assume all materials are kitted before the outage. If late discovery work adds scope, the repair plan changes during the event, not before it. A rail project may assume utility diversions finish before civil works start. If one utility provider slips, the headline critical path may change overnight.
The schedule did not suddenly become risky. It was already risky. The assumption simply matured.
Technical Integrity And Quality Exposure
Engineering decisions depend on input quality. If assumptions about loads, corrosion conditions, process composition, seismic data, soil behavior, ambient temperatures, or operating modes are wrong, the design may require late change.
Quality teams also suffer. Inspection and test plans may assume vendor hold points, material certificates, weld procedures, calibration records, and preservation records are complete. When they are not, the project faces concession requests, reinspection, repair, or delayed acceptance.
In high-risk industries, technical integrity is not a paperwork preference. It protects people, assets, the environment, and the license to operate.
Safety And Process Safety Impacts
Assumption debt can undermine safety when execution plans rely on unverified isolation, access, SIMOPS conditions, lifting studies, temporary works, ground stability, or hazardous area classifications.
A brownfield contractor may assume an area is gas-free because it was cleared in a previous shutdown. A lifting plan may assume ground bearing capacity based on a general site standard. A marine operation may assume weather windows from seasonal averages without confirming the vessel spread's operational limits.
Safety systems are designed to be conservative, but project pressure can normalize assumed conditions. That is a dangerous drift. The Energy Institute, IOGP, and other process safety bodies repeatedly emphasize managing changes, verifying safeguards, and confirming readiness before operations. Assumptions that bypass those disciplines deserve senior attention.
Contract Disputes And Damaged Relationships
Many disputes are assumption disputes with legal language added later.
Who assumed the drawings were accurate? Who assumed access was unrestricted? Who assumed permits were included? Who assumed design development was normal rather than change? Who assumed the client’s data was reliable? Who assumed the contractor carried the productivity risk?
Clear contracts reduce ambiguity, but they cannot compensate for poor assumption management. If the tender basis is unclear, the parties may spend more effort reconstructing intent than solving the project problem.
Operational Readiness Gaps
Projects often declare success at mechanical completion or handover, while operations judge success by safe, reliable performance.
Assumption debt appears in operations when training is incomplete, spares are missing, procedures do not match the installed plant, maintainability issues remain unresolved, safety-critical elements lack verified records, or digital asset data is not fit for the maintenance system.
Handover is not a storage location for unresolved assumptions. It is the point where the project must prove what the asset is, how it should be operated, and what remains open by formal agreement.
The Controls That Make Assumptions Visible
Assumption management does not need to become a bureaucratic industry. It needs to be disciplined enough that leaders can see which parts of the plan still depend on unproven statements.
Build An Assumption Register That People Actually Use
An assumption register should be more than a list attached to the project management plan. It should connect to the estimate, schedule, risk register, interface register, procurement plan, contract basis, and handover plan.
For each material assumption, capture:
The assumption statement in plain language
The decision, deliverable, or baseline element that depends on it
The owner accountable for validation
The required evidence
The validation deadline
The consequence if it proves false
The route for escalation
The status, such as open, validated, retired, converted to risk, or converted to decision
This aligns with the intent across PMI and APM project guidance, where assumptions and constraints support planning, governance, and change control. The specific form matters less than the discipline of ownership and evidence.
Assign Ownership To People Who Can Act
A weak assumption register lists functions as owners. “Engineering,” “commercial,” “construction,” or “operations” does not validate anything. A named owner should have enough authority, access, and technical understanding to close the item or escalate it.
The owner doesn't have to generate all the evidence personally. They do need to make sure the project gets it.
For example, an assumption about underground services in a brownfield area may need input from operations, records management, ground-penetrating radar, trial pits, and permit authorities. One person should still own the validation path.
Set Validation Deadlines Before The Assumption Affects Commitment
The useful deadline is not “before construction.” That is often too late.
Set deadlines tied to decisions:
Before estimate freeze
Before tender issue
Before bid return
Before contract award
Before purchase order
Before fabrication release
Before workface release
Before energization
Before handover acceptance
Resolve an assumption about module transport route capacity before locking module dimensions and shipping plans. Resolve an assumption about plant shutdown duration before freezing the shutdown worklist and resource plan. Resolve an assumption about asset data requirements before specifying vendor documentation packages.
Define Evidence Before People Argue About Confidence
“Confirmed” is a dangerous word when no one defines what confirmation means.
Evidence may include approved drawings, signed permits, completed surveys, vendor guarantees, test results, operations acceptance, legal agreements, inspection records, constructability sign-off, or verified field measurements.
Make the evidence requirement explicit. That prevents optimistic closure.
A schedule assumption about third-party approval is not validated by “positive discussions.” Validate it with approval, or with a formal agreement that changes how the project will proceed without it.
Escalate Assumptions That Threaten The Baseline
If unresolved assumptions affect cost, schedule, safety, quality, or contractual commitments, they belong in baseline discussions. Leaders should not allow teams to hold a baseline steady while its foundations weaken.
Baseline management should distinguish between:
A validated change in project scope
A correction of an invalid assumption
A risk event that has occurred
A deferred decision now reaching its deadline
A dependency failure outside the project’s direct control
This distinction affects entitlement, contingency use, management reserve, sponsor communication, and commercial strategy. It also helps stop the casual conversion of poor assumptions into “change” after the fact.
Weak Signals That Assumptions Are Becoming Embedded
Assumption debt rarely announces itself. It sends signals. Senior leaders should learn to spot them before the project claims surprise.
Listen for phrases that sound harmless but avoid evidence:
“That is standard.”
“We allowed for that.”
“The contractor owns it.”
“Operations are aware.”
“It is included somewhere.”
“We will confirm after award.”
“The schedule assumes approval.”
“The old drawings should be close.”
“We have priced a typical solution.”
“Commissioning will pick that up.”
None of these phrases is automatically wrong. Each is a prompt for inquiry.
Other weak signals include repeated deferral of survey work, large exclusions in contractor bids, risk items with no validation action, contingency drawdown before physical work starts, vendor data delays treated as normal progress noise, and interface registers that track dates but not evidence.
A mature team does not treat these signals as bad news. It treats them as early warnings.
Questions Senior Leaders Should Ask
Project directors, sponsors, and senior leaders do not need to inspect every assumption. They need to create pressure for truth.
The best questions are specific enough to drive behavior change.
What top assumptions support the current cost and schedule baseline?
If the team cannot answer quickly, the baseline may be carrying hidden debt.
Which assumptions must be validated before the next major commitment?
Tie the discussion to tender issue, contract award, procurement release, construction start, energization, or handover.
What evidence will close each assumption?
Avoid accepting confidence, experience, or “no objection” as evidence when formal proof is needed.
Which assumptions have passed their validation deadline?
A late assumption is not a note. It is an unmanaged exposure.
Which assumptions are being carried because the answer may be commercially uncomfortable?
This question often reveals the real issue.
Which assumptions have been converted into risks, decisions, contract qualifications, or baseline changes?
Open assumptions need a destination. They should not live indefinitely.
What would we stop doing if this assumption proved false tomorrow?
If the answer is “a lot,” it deserves senior attention today.
Practical Actions That Reduce Assumption Debt
The cure for assumption debt is not a larger spreadsheet. It is a stronger habit of validation.
Start early. During concept and FEED, make assumptions visible in the basis of design, basis of estimate, schedule basis, execution plan, and risk process. Do not wait for EPC execution to discover that the business case depended on weak inputs.
Connect registers. An assumption that affects a procurement package should appear in procurement readiness. If it affects handover, it should appear in completions and operational readiness planning. One that affects contract price should appear in tender clarifications and commercial risk review.
Review assumptions at decision points. Do not hold generic assumption reviews. Run them before commitments, where they matter.
Retire assumptions properly. If the evidence confirms the statement, close it and reference the evidence. If evidence disproves it, trigger change, risk response, redesign, or commercial action. If it cannot be validated in time, make the uncertainty explicit in the baseline and governance record.
Avoid false closure. “Accepted by the team” is not the same as validated. “No further comments” is not the same as approved. “Included in contingency” is not the same as managed.
Use independent challenge where stakes are high. External assurance, peer reviews, constructability reviews, value studies, readiness reviews, and technical authority checks can all expose assumptions that delivery teams have normalized. This aligns with good practice across PMI, APM, ISO, AACE, CII, ICE, RICS, and sector-specific guidance, without turning assumption management into a separate universe.
Most of all, make it safe to surface uncertainty. Teams hide assumptions when leaders punish ambiguity but reward confidence. On major projects, early uncertainty is not failure. Late discovery is.
Assumption debt is a hidden project liability because it disguises uncertainty as progress. It lets teams approve budgets, sign contracts, release designs, place orders, mobilize crews, and declare readiness on foundations that may not hold. Leaders should treat material assumptions as temporary credit, not free capital. Identify them, assign owners, demand evidence, set deadlines, escalate the overdue ones, and adjust the baseline when reality changes. Projects that do this don't run slower. They are less surprised.
