Scope Osmosis in Capital Projects How Unapproved Work Becomes Baseline
A project rarely loses control of scope in one dramatic moment. More often, it happens through small accommodations.
A superintendent asks for “just one more scaffold tie-in while the crew is up there.” An engineer adds a note to satisfy an operator comment. A commissioning lead accepts a temporary workaround as a future punch item. A client representative says, “Capture that in the minutes,” and the action quietly becomes part of the project’s assumed obligation.
No change request is raised. No commercial position is agreed. No schedule impact is modeled. Yet the work starts to move through the project as if it had always belonged there.
That is scope osmosis: the gradual absorption of work, expectations, obligations, and stakeholder demands into a project without formal approval. It is not the same as dramatic scope creep, where a new facility, system, or major deliverable is visibly added. Scope osmosis is slower and harder to detect. It enters through language, behavior, assumptions, and incomplete governance.
In complex capital projects, this matters because the unofficial scope can be just as real as approved scope. It consumes engineering hours, procurement effort, permits, isolations, access windows, construction labor, commissioning time, management attention, and operational readiness capacity. By the time someone asks, “Who approved this?”, the work may already be embedded in drawings, schedules, test packs, vendor documents, handover dossiers, and stakeholder expectations.
Scope Often Enters Long Before It Looks Like A Change
Traditional change control tends to look for visible events: a revised scope of work, a client instruction, a design change notice, a contract variation, a field change request, or a formal trend. Those mechanisms are necessary. PMI guidance, APM guidance, ISO project management standards, AACE International recommended practices, and construction contract institutions all point in the same direction: projects need defined baselines and disciplined control of changes.
The problem is that many obligations do not arrive wearing a label marked “change.”
They arrive as helpfulness, risk avoidance, relationship management, technical caution, or operational preference. Since each addition appears reasonable in isolation, the project team often accepts it without testing whether it changes the baseline.
Common entry points include:
“While you’re there” requests during brownfield works or shutdowns
Informal client or operator commitments made during site walks
Meeting-minute actions that assign work without commercial qualification
Verbal instructions from client representatives, marine warranty surveyors, regulators, or operations personnel
Technical clarifications that expand the required solution
Vendor assumptions that become embedded in interface documents
Contractor allowances that are treated as commitments
Stakeholder comments that shift from preference to expectation
Punch list items that are not defects, but new work
Handover requirements added late through operations readiness reviews
Safety or access requirements that are valid but not priced, scheduled, or baselined
Consider an EPC package for a compressor station. The contract requires a defined number of instruments, tie-ins, and cable routes based on issued-for-design documentation. During a design review, operations asks for extra local indication “to make maintenance easier.” The engineering team accepts the comment because it appears sensible. The electrical team then adds cable routes. Procurement updates material quantities. Construction updates tray loading. Commissioning adds loop checks. Documentation adds asset tags and maintenance data.
At no stage does anyone believe they have added a major change. Yet the project now owns additional engineering, materials, installation labor, testing, and handover content. If the cost and schedule impact isn't captured early, it becomes difficult to recover later.
The Phrase “While You’re There” Is Rarely Harmless
Brownfield, offshore, utilities, and shutdown environments are especially exposed. Access is expensive. Production outages are limited. Permits, isolations, scaffolds, vessels, cranes, and specialist crews may be available for only a short window.
That creates a strong practical argument for bundling extra work into the same opportunity. The logic is often sound:
The scaffold is already erected.
The area is already gas-free.
The shutdown window is already open.
The vessel is already on hire.
The subsea spread is already mobilized.
The road closure is already in place.
The crane is already rigged.
The issue is not the work itself. The issue is the absence of a decision.
A “while you’re there” request can be good project management if .. It becomes scope osmosis when the team acts first and validates later, or never validates at all.
In offshore work, a small additional bracket, cable pull, valve replacement, or access platform modification can create knock-on effects across engineering checks, lifting plans, hot work controls, material traceability, inspection, certification, and closeout records. In shutdowns, extra work can threaten the critical path because crew loading, permit density, and system reinstatement sequencing are already tight.
Good intent does not remove the need for control.
Why Conventional Change-control Systems Miss Unofficial Scope
Most mature capital projects have change procedures. They define thresholds, approval levels, registers, forms, cost codes, entitlement reviews, and contract notices. Many use trend programs, change management processes, technical query systems, and document-control workflows.
Yet unofficial scope still enters.
That does not mean the procedures are useless. It means the trigger points are often too narrow, too late, or too disconnected from the places where scope is actually created.
Change Systems Rely On People Recognizing A Change
A change-control process only works when someone identifies that a change has occurred or may occur. In practice, many additions are treated as technical detail, not scope.
An engineer may see an added drain point as a design improvement. A field supervisor may view a modified access ladder as workface problem-solving. A commissioning manager may accept added functional tests because they reduce start-up risk. An operations representative may see extra alarms, spares, or maintenance labels as basic readiness.
Each person may be acting responsibly within their discipline. The gap appears because no one tests the request against the approved baseline.
This is where capital projects differ from routine operations. In operations, incremental improvement may be encouraged. In projects, every addition must pass through a control lens because budgets, contracts, schedules, and risk allowances were set against a defined scope.
Meeting Minutes Can Become Accidental Instructions
Meeting minutes are a frequent carrier of unofficial scope.
A typical action might say:
“Contractor to provide revised access platform layout.”
“EPC to include additional flushing points for review.”
“Construction team to support operator request during shutdown.”
“Commissioning to add tests requested by asset team.”
“Vendor to confirm provision of additional spares.”
These actions look administrative, but they can create obligations if they are not qualified. If the minutes are issued, not challenged, and then used as the basis for follow-up, the action gains authority. Weeks later, someone points to the minutes as evidence that the project accepted responsibility.
For experienced teams, the lesson is simple: meeting controls are commercial controls. Minutes should distinguish between agreed scope, actions to evaluate potential change, actions subject to approval, and items rejected or deferred. Silence can become expensive.
Technical Queries Can Expand The Job
Technical queries, requests for information, field change notices, and design clarifications are meant to solve ambiguity. Yet they often alter scope by stealth.
For example, a contractor raises a query on whether an existing pipe support can be reused. Engineering responds that a new support should be installed to meet current design practice. The answer may be technically sound. But has the project confirmed whether current design practice was included in the brownfield retrofit scope? Is the existing support defective? Is replacement required by code, client standard, operational preference, or engineering caution? Who pays for the change?
This distinction matters. ISO guidance on project, quality, and configuration management emphasizes the need to control changes to outputs and baselines. AACE’s total cost management framework also treats scope definition, change control, and cost control as linked disciplines. In plain terms, technical correctness does not replace commercial authorization.
Contractual Notice Periods And Governance Gates May Not Align With Reality
Many contracts require timely notice when a party believes an instruction or event may affect cost or time. Standard forms used in infrastructure and construction, and guidance from institutions such as ICE and RICS, commonly stress the administrative discipline of notices, records, and valuation.
Scope osmosis weakens that discipline because the team may not see an instruction as a change until the notice window has passed. By then, entitlement becomes harder to prove. The project may still have records, but the record trail shows fragmented acceptance rather than a clear instruction and response.
That creates fertile ground for disputes. The client may say the work was included or voluntarily performed. The contractor may say the team was instructed informally. The engineer may say the answer was only a clarification. Operations may say the requirement was always expected.
Everyone may be partly right. That is the problem.
How Scope Osmosis Develops Across The Lifecycle
Scope osmosis does not wait until construction. It starts early and becomes more expensive as the project moves forward. The same unapproved expectation can pass through engineering, procurement, fabrication, installation, commissioning, handover, and operations without ever being properly priced.
Concept And Front-end Definition
The seeds are often planted during concept selection and front-end planning.
At this stage, stakeholders use broad language:
“allow for future expansion”
“consider maintainability”
“make provision for operations”
“ensure adequate access”
“align with existing standards”
“include digital handover requirements”
“support safe start-up”
These phrases may be reasonable, but they need boundaries. Construction Industry Institute research has long emphasized the value of front-end planning and scope definition in project performance. The point is widely accepted across the industry: weak definition creates downstream instability.
For example, “allow for future expansion” could mean spare space in a control cabinet, larger foundations, additional pipe rack capacity, tie-in flanges, future cable tray capacity, or a fully engineered expansion-ready facility. Each option has a different cost and schedule profile.
If the project does not define the boundary, the most demanding interpretation may slowly become the expected one.
Detailed Engineering
Detailed engineering is where preferences become drawings.
Stakeholder comments, design review actions, HAZOP actions, model review notes, constructability comments, and vendor interface comments can all expand scope. Safety studies, including HAZOP and similar reviews, are essential. Guidance from bodies such as the Energy Institute and IOGP supports disciplined risk management in high-hazard industries. Yet project teams must still separate safety-critical requirements from enhancements, preferences, and scope additions.
A HAZOP action might require an additional safeguard. If the safeguard is needed to meet the project’s safety basis, incorporate it and control it. If it reflects a preference for extra convenience or redundancy beyond the agreed basis, the team still needs a decision on scope, cost, and schedule.
That distinction is not about resisting safety. It is about making sure safety decisions are explicit, documented, and properly resourced.
Procurement And Vendor Management
Procurement often absorbs unofficial scope through specifications and vendor documents.
A package engineer may ask a vendor to include extra tests, spare parts, documentation, coatings, tagging, preservation, inspection hold points, or data formats. The vendor may accept some items as technical compliance, price others later, or miss embedded exclusions. Interface requirements may also grow as adjacent packages evolve.
In an EPC environment, these small additions can multiply across dozens of packages. A late requirement for additional material certificates, data books, cybersecurity documentation, lifting accessories, or operating manuals may seem minor until procurement discovers that vendors need more time, cost, and review cycles.
The risk sharpens when the main contract and purchase orders don't align. The EPC contractor may accept an upstream expectation without flowing it down commercially. That traps margin between the client requirement and the supplier agreement.
Construction And Field Execution
Construction exposes every assumption.
A seemingly harmless drawing note becomes an installation work pack. An operations request becomes a field instruction. An access issue becomes a scaffold variation. A design clarification becomes rework. A “temporary” support becomes a permanent modification because the team has no time to reverse it before mechanical completion.
Brownfield work is the classic setting. Existing conditions differ from drawings. Operations have urgent needs. Safety controls require adaptation. Workfronts are constrained. Field teams solve problems quickly because delay is visible. The commercial effect often catches up later.
This is not a criticism of field teams. Good construction supervisors prevent downtime and keep people safe. The governance challenge is to give them fast instruction protocols so they don't have to choose between progress and control.
Commissioning, Handover, And Operational Readiness
Late-stage scope osmosis can be the most painful because the project has little float left.
Commissioning teams may face requests for additional tests, extended run durations, extra performance evidence, revised acceptance criteria, operator training, spare parts cataloging, changes to maintenance strategies, or additional digital asset data. Handover teams may discover that operations expect records and formats not defined in the contract or information requirements.
Operational readiness often creates tension. Asset teams naturally want a complete, usable facility. Projects want to close out obligations. If readiness requirements were not defined early, they may surface as late acceptance conditions.
Examples include:
extra simulation scenarios before start-up
added cause-and-effect testing
new functional test sheets
revised preservation records
additional asset hierarchy coding
extra cybersecurity evidence
new permits or regulatory submissions
expanded training for shift teams
additional spares and consumables
modified maintenance access after walkdowns
Don't dismiss any of these items. Some are necessary for safe and reliable operations. The issue is timing and authorization. Late discovery converts manageable requirements into schedule pressure, claims, and strained relationships.
The Consequences Are Wider Than Cost Growth
Scope osmosis is sometimes treated as a commercial nuisance. That understates the damage. Unofficial scope affects cost, time, quality, safety, contracts, and organizational behavior.
Margin Erosion And Weakened Cost Control
Unapproved work consumes budget before anyone decides whether it should. Engineering hours move from planned deliverables to extra studies. Procurement spends time revising requisitions. Site teams use labor and plant on unpriced work. Project controls may only see the effect as productivity loss, indirect cost growth, or contingency burn.
AACE guidance consistently treats scope definition, estimates, change management, and cost control as interdependent. If scope is moving but the cost system still believes the baseline is stable, forecasts become misleading. The project may report that it is underperforming when part of the “underperformance” is unrecognized work.
This matters commercially because margin erosion often happens before the claim strategy begins. Once the contractor has performed the work, the negotiation changes. The buyer may challenge entitlement, valuation, or causation. The contractor must reconstruct records. The conversation becomes retrospective and defensive.
Schedule Slippage And Hidden Critical Path Effects
Small additions do not always create small delays.
An extra inspection may require a hold point before reinstatement. A late cable can delay loop checks. Added flushing points can affect hydrotest boundaries. Extra documentation can delay acceptance of mechanical completion. A new operations requirement can block handover.
The schedule risk is especially high when unofficial scope enters near path convergence points:
shutdown completion
module sail-away
heavy lift readiness
energization
mechanical completion
pre-commissioning
system handover
start-up approval
performance testing
beneficial use
These milestones depend on many small prerequisites. Scope osmosis adds prerequisites without adding time.
Rework And Technical Inconsistency
When unofficial work enters informally, design integration suffers. One discipline may update its deliverables while another does not. A vendor may revise drawings while site work packs remain unchanged. Construction may implement a field solution that clashes with maintainability, inspection access, or certification needs.
Rework then appears as a technical problem, but the root cause is often governance. The project allowed work to progress without a controlled baseline decision.
Safety And Quality Exposure
A dangerous misconception is that accepting extra work is always the safer option. In some cases, it is. In other cases, poorly controlled extra work increases risk.
Unplanned field work can add simultaneous operations, congested permits, fatigue, lifting interactions, confined space entries, hot work, temporary access, and pressure to complete before a shutdown window closes. Offshore and process safety guidance from regulators, IOGP, and the Energy Institute often stresses the need to manage change, interfaces, and work control in hazardous environments. Informal additions can cut across those controls.
Quality can suffer too. Unplanned work may lack inspection and test plans, material traceability, approved procedures, welding controls, preservation requirements, or documentation. If the team later tries to close the gap, it may need intrusive inspection, retesting, or concession management.
Contractual Disputes And Accountability Gaps
Scope osmosis blurs accountability.
The client may believe the contractor accepted an obligation. The contractor may believe it followed an instruction. The engineer may believe it clarified a technical issue. The operator may believe it raised a requirement early enough. The project manager may believe the change process would capture anything significant.
When the record is unclear, parties argue over intent, authority, notice, and inclusion. Claims become harder to resolve because no single event exists. Instead, a chain of comments, minutes, emails, site conversations, and revised deliverables emerges.
That is expensive even when the amounts are modest. It consumes senior attention, damages trust, slows decisions, and encourages defensive behavior.
How To Identify And Control Unofficial Scope Before It Hardens
The answer is not to reject every request. Capital projects need practical judgment. Conditions change. Safety issues emerge. Stakeholders learn more as the design matures. Operations may identify legitimate requirements. Contractors may uncover incomplete information.
The discipline is to make scope movement visible early enough to decide.
Define Boundaries In Operational Language
A scope statement that lists deliverables is not enough. Teams need boundary definitions that explain what is included, what is excluded, and what assumptions govern interpretation.
For example, instead of saying “provide access for maintenance,” define the standard:
which equipment requires permanent access
what access can be by mobile platform
what inspection activities are included
which maintenance tasks are excluded
which client standards apply
how deviations will be approved
For brownfield work, define the limit of intervention. Does the project replace only disturbed items, bring affected systems to current standards, or upgrade adjacent non-compliant conditions? These are very different obligations.
For offshore or shutdown work, define what can be bundled into access windows and what requires formal screening. Field leaders need this clarity before the job starts.
Use Decision Logs That Separate Agreement From Evaluation
A decision log should not be a graveyard of vague actions. It should record what was decided, who had authority, what baseline was affected, and what remains subject to change control.
Useful entries answer:
What was requested?
Is it within approved scope?
Who has authority to decide?
What cost, schedule, risk, and safety checks are needed?
Is work authorized now, or only evaluation?
What contract notice or communication is required?
What documents must be updated if approved?
The log should be reviewed with project controls, contracts, engineering, construction, commissioning, and client representatives. Scope osmosis thrives when each function keeps its own partial truth.
Establish Instruction Protocols For Site And Technical Teams
Verbal instructions will happen. Site work is dynamic, and not every issue can wait for a weekly governance meeting. The control is to define what happens after a verbal instruction.
A practical protocol might require:
immediate written confirmation
identification of the instruction source
a statement that cost and schedule rights are reserved
a temporary work authorization if urgent
time-bound review by contracts and project controls
linkage to a change, trend, technical query, or risk record
This protects both parties. It allows urgent work to continue while avoiding later arguments about whether the instruction existed.
The same discipline should apply to technical clarifications. If an answer adds work, changes acceptance criteria, or alters assumptions, the response should flag a potential change. Engineers should not be expected to make silent commercial commitments through technical correspondence.
Create Clear Change Triggers
Teams need simple triggers that convert a discussion into a potential change review. These triggers should be visible in engineering, procurement, construction, commissioning, and handover.
Examples include:
Trigger | Why it matters |
More quantity, testing, documentation, or inspection than the baseline | Adds labor, vendor cost, or review time |
New or changed acceptance criteria | Can affect completion and handover |
Work outside defined battery limits | Creates interface and entitlement risk |
Upgrade to current standard in existing facilities | May exceed retrofit scope |
Extra operational readiness deliverables | Can delay start-up or acceptance |
Added safety control that changes design or execution | Needs explicit risk and authorization review |
Stakeholder request entered as a meeting action | May become an implied commitment |
Vendor assumption accepted without review | Can shift cost or responsibility |
The trigger does not mean the answer is “no.” It means the project pauses long enough to decide.
Track Assumptions Like Live Commercial Risks
Assumption logs often start strong and fade. That is a mistake. Assumptions are a main pathway for scope osmosis.
A contractor may assume client-furnished data will be accurate. The client may assume the contractor has included all interface management. Operations may assume the project will provide full maintenance build data. Engineering may assume existing utilities have sufficient capacity. Construction may assume access is available.
Each assumption should have an owner, validation date, impact if wrong, and closure evidence. Review open assumptions at phase gates, estimate updates, procurement awards, readiness reviews, and before shutdown execution.
Tighten Meeting Controls
Meetings are where informal expectations often become accepted work. Good meeting discipline is not bureaucracy. It is scope control.
Use clear labels in minutes:
Approved scope
Potential change under review
Action to estimate only
Action subject to client approval
Contractor reservation of rights
Client position pending review
Deferred to later phase
Rejected or out of scope
Avoid passive actions such as “team to address” or “contractor to incorporate” unless the scope position is clear. Require attendees to challenge minutes quickly when they imply unauthorized work. Treat unchallenged minutes as a serious record, because others will.
Validate Scope At Transition Points
Scope should be checked whenever work moves from one phase to another:
concept to FEED
FEED to EPC
engineering to procurement
procurement to fabrication
fabrication to construction
construction to pre-commissioning
commissioning to handover
handover to operations
At each transition, ask a hard question: “What are we now doing, expecting, or promising that was not in the previous baseline?”
This is especially useful before procurement awards and before shutdowns, when scope can still be contained. Clarifying an expectation before issuing a purchase order is much cheaper than after materials arrive. It is much safer to screen additional shutdown work before crews are in the field.
Build A Culture That Escalates Early Without Punishing Honesty
Scope osmosis persists when teams fear escalation. People stay quiet because they don't want to seem difficult, slow progress, damage the client relationship, or admit something. Clarifying expectations before issuing a purchase order is much cheaper than doing so after the baseline is unclear.
Senior project leaders set the tone. If every raised scope issue becomes a confrontation, teams will stop raising them. If teams accept every stakeholder request to preserve goodwill, the project will lose commercial control. The balance is to make early escalation normal, factual, and non-defensive.
Useful behaviors include:
praising early identification of potential change
separating technical merit from authorization
involving contracts before positions harden
giving field teams fast routes for urgent decisions
asking project controls to analyze scope movement, not just cost variance
requiring client and contractor teams to qualify actions in real time
treating operations readiness requirements as scope items, not late preferences
This also helps the client. Uncontrolled unofficial scope can damage owners and contractors. It can delay projects, consume contingency, create claims, overload operations teams, and delay revenue or service outcomes. Clear control protects capital efficiency and asset readiness.
Professional guidance across PMI, APM, ISO, AACE, CII, ICE, RICS, IOGP, the Energy Institute, and regulators varies in detail, but the common principle is consistent: define the baseline, manage change, keep records, control interfaces, and make decisions traceable. Scope osmosis is what happens when those principles exist on paper but not in daily project behavior.
A practical test is to ask these questions during monthly reviews:
What work are we performing that has no clear baseline reference?
Which meeting actions could be interpreted as instructions?
Which stakeholder expectations are growing without approval?
Which technical clarifications have cost or schedule impact?
Which assumptions remain open near execution?
Which operations readiness requirements are late or undefined?
Which field decisions need commercial follow-up?
Which items are being called defects but may be new scope?
If the project cannot answer quickly, unofficial scope is probably already moving.
The answer is not heavier paperwork for its own sake. The answer is sharper visibility at the points where work enters. A one-page field instruction protocol used daily is better than a perfect change procedure nobody invokes. A disciplined meeting action log is better than a sophisticated claims file built six months late. A clear exclusion stated early is better than a dispute over implied obligation at handover.
Capital projects do not fail from scope osmosis because teams lack intelligence or effort. They fail because small decisions become collective assumptions, and collective assumptions become obligations.
The professional takeaway is simple: unofficial scope must be identified before it becomes accepted project duty. Once unapproved work is embedded in drawings, schedules, procurement packages, field execution, commissioning tests, and handover expectations, the baseline has already moved. At that point, the project is no longer deciding whether to accept the work. It is deciding who will absorb the consequences.
