Definition Change and variation management is the systematic process of identifying, evaluating, capturing, approving, implementing, and documenting modifications to project scope, design, specifications, or execution approach—together with their associated cost, schedule, and contractual implications. It encompasses both internal change control (managing modifications within an organisation’s scope) and contractual variation management (managing modifications that affect contract terms between parties). In capital projects, change and variation management addresses several types of modification: Client/owner changes: Modifications requested by the client to scope, specification, or requirements Design development: Evolution of design from concept through detailed documentation Design changes: Modifications to approved design for technical, commercial, or regulatory reasons Field changes: Modifications arising from site conditions, constructability, or execution realities Regulatory changes: Modifications required by code changes, permit conditions, or regulatory intervention Value engineering: Modifications proposed to reduce cost or improve value without compromising function Corrective changes: Modifications to address errors, omissions, or non-conformances Effective change and variation management requires: Early identification: Recognising potential changes before they are implemented Impact assessment: Evaluating cost, schedule, quality, and contractual implications Formal approval: Obtaining appropriate authorisation before implementation Documentation: Recording the change, its justification, and its effects Cost recovery: Ensuring contractual entitlement is established and pursued Integration: Updating budgets, schedules, and forecasts to reflect approved changes Change management and variation management are related but distinct: Change management is the internal discipline of controlling modifications regardless of contractual impact Variation management specifically addresses contractual entitlement—the right to additional payment or time under contract terms Both must operate together. A change without contractual entitlement is a cost to absorb. A variation claim without proper change documentation is difficult to substantiate. Stakeholder Risk Exposure Change and variation management affects all project stakeholders, with exposure varying based on role, contract type, and the nature of changes. Risk Exposure by Industry Stakeholder Construction Marine & Offshore Shipbuilding Mining Project-Based Manufacturing Client / Owner 6 7 5 8 5 Contractor / Builder 7 8 8 7 7 Consultant / Supervisor 4 5 4 5 4 Designers 5 6 6 5 6 Laboratories / QC 2 3 3 3 3 QA and HSE 4 6 5 7 4 Lenders / Banks 5 7 6 8 4 Insurers 5 7 6 7 5 Rating Scale: 1 = Lowest risk exposure, 10 = Highest risk exposure Stakeholder Roles in Change and Variation Management Stakeholder Role in Change Management Key Concerns Owner / Developer / E&P Operator Initiates owner changes; approves cost and schedule impact; authorises variation payments Cost control, scope alignment with objectives, schedule protection Contractor / Shipbuilder / Mining Contractor Identifies field changes; assesses impact; submits variation claims; implements approved changes Margin protection, entitlement recovery, disruption minimisation Consultant / Independent Engineer / Employer’s Representative Evaluates change requests; certifies variations; advises owner on entitlement Fair assessment, contractual compliance, project protection Designer / Architect / Naval Architect Initiates design changes; assesses technical implications; updates documentation Design integrity, liability management, coordination QA and HSE Reviews changes for quality and safety implications Compliance maintenance, risk assessment Lenders / Project Finance Banks Monitors change impact on project cost and viability Budget adherence, completion risk, covenant compliance Insurers Assesses change impact on insured risks Coverage implications, additional premium requirements Context in Project-Based Industries Change and variation management operates across all project-based industries, with practices reflecting industry-specific contractual frameworks, regulatory environments, and operational characteristics. Construction In construction, change and variation management addresses: Change Category Typical Sources Contractual Treatment Client variations Owner requirements, stakeholder input, market changes Variation order with valuation per contract Design development Detail evolution from concept to construction Often within design contingency; may trigger variation if beyond scope Design errors Coordination failures, specification conflicts, calculation errors Designer liability; may involve PI insurance Site conditions Unforeseen ground, utilities, contamination Contract-dependent; often shared or owner risk Regulatory changes Code updates, permit conditions, authority requirements Often owner risk; contract-specific provisions Contractor proposals Value engineering, alternative methods Shared savings or contractor benefit per contract Key characteristics: Standard contract forms (FIDIC, NEC, JCT) provide variation mechanisms Quantity surveyor role in valuation and certification Strong linkage between variation register and final account Time implications often contentious (extension of time claims) Typical variation process (FIDIC-based): Instruction or Event │ ▼ ┌─────────────────────┐ │ Contractor Notice │ │ (within time limit) │ └──────────┬──────────┘ │ ▼ ┌─────────────────────┐ │ Engineer's │ │ Determination │ └──────────┬──────────┘ │ ▼ ┌─────────────────────┐ │ Contractor │ │ Detailed Claim │ └──────────┬──────────┘ │ ▼ ┌─────────────────────┐ │ Engineer's │ │ Assessment │ └──────────┬──────────┘ │ ▼ ┌─────────────────────┐ │ Agreement or │ │ Dispute Resolution │ └─────────────────────┘ Marine and Offshore In marine and offshore projects, change management reflects engineering complexity and execution constraints: Change Category Typical Sources Contractual Treatment Scope changes Reservoir data, operability requirements, interface evolution Variation order per EPC/EPCI contract Weight growth Design development, equipment changes, structural modifications Often contractor risk within limits; variation beyond threshold Offshore methodology Installation approach, vessel changes, weather response May trigger variation if owner-directed Hook-up and commissioning System integration, performance requirements, punch-list Contract completion criteria; variation if scope expands Regulatory and classification Class society requirements, flag state, HSE regulations Varies by contract; often shared risk Key characteristics: Engineering changes often have cascading effects (weight, structure, installation) Offshore execution changes are costly due to vessel day rates Strong document control requirements for change tracking Lender scrutiny of change orders affecting project cost Shipbuilding In shipbuilding, change management addresses specification evolution over long build cycles: Change Category Typical Sources Contractual Treatment Owner changes Specification modifications, operational requirements, market response Change order with price and schedule adjustment Classification requirements Rule changes, surveyor requirements, notation additions Often shared; contract-specific allocation Design development Detail engineering beyond contract specification Shipbuilder risk if within specification intent Regulatory changes SOLAS, MARPOL, flag state requirements Often shared; sometimes owner risk Owner-furnished equipment OFE changes, delivery impacts, interface modifications Owner risk for OFE; interface negotiated Key characteristics: Long build cycles mean external changes (regulations, rules) are common Currency of contract (USD, EUR, etc.) affects change valuation Milestone payment impact of changes requires careful management Specification interpretation disputes common Mining In mining projects, change management addresses geological and regulatory evolution: Change Category Typical Sources Contractual Treatment Scope changes Resource updates, process modifications, capacity changes Variation per EPCM or construction contract Geotechnical changes Ground conditions, pit design, foundation requirements Often owner risk in mining; shared in tunnelling Regulatory and permitting Environmental conditions, community requirements, government changes Typically owner risk Process optimisation Commissioning learnings, throughput enhancement Often within ramp-up contingency Remote site conditions Logistics, weather, access constraints Contract-dependent allocation Key characteristics: Geological changes can be significant and difficult to anticipate Community and regulatory changes increasingly common Multiple contractor interfaces complicate change allocation EPCM contracts place more change risk with owner Project-Based Manufacturing In project-based manufacturing, change management addresses specification and delivery modifications: Change Category Typical Sources Contractual Treatment Specification changes Client requirements, design development, regulatory Change order with price and schedule adjustment Design changes Engineering modifications, BIM coordination, interface Depends on design responsibility allocation Material substitution Availability, cost, specification refinement May be contractor-proposed or client-required Delivery changes Site readiness, sequence modifications, acceleration Schedule variation; may affect price Quality and inspection Additional requirements, non-conformance resolution Depends on cause and contract terms Key characteristics: BIM/design integration creates rapid change identification Production planning impact of changes must be assessed Delivery sequence changes can significantly affect cost Clear specification baseline essential for change identification Why This Concept Exists Change and variation management exists because capital projects operate in conditions where change is inevitable, consequences are significant, and contractual clarity is essential. Project scope evolves through execution Capital projects begin with incomplete information: Design is developed progressively from concept to detail Site conditions are discovered through execution Owner requirements emerge and refine over time Regulatory and market conditions change Technical solutions evolve based on engineering development This evolution means the work executed will differ from the work originally contemplated. Change management provides the framework to control this evolution. Changes have cost and schedule consequences Every change affects project economics: Direct cost of additional or modified work Indirect cost of disruption, delay, and coordination Schedule impact affecting completion and revenue Knock-on effects to related work packages Administrative cost of managing changes Without systematic change management, these consequences accumulate without visibility or control. Contracts create entitlements and obligations In project-based industries, work is performed under contracts that allocate risk and define payment mechanisms: Some changes entitle the contractor to additional payment Some changes are within the contractor’s risk and price Some changes entitle the contractor to time but not cost Some changes require formal variation orders to be valid Change management ensures that contractual entitlements are identified, documented, and pursued—and that obligations are understood and fulfilled. Unmanaged change destroys project outcomes The consequences of unmanaged change are severe: Failure Consequence Changes not identified Work proceeds without authorisation; cost absorbed without recovery Impact not assessed Decisions made without understanding consequences Approval not obtained Contractual entitlement lost; liability unclear Documentation inadequate Claims cannot be substantiated; disputes unresolvable Cost not recovered Contractor margin eroded; project economics impaired Scope creep Progressive expansion without corresponding authorisation Systematic change management prevents these failures. Stakeholder alignment requires process Multiple stakeholders—owners, contractors, designers, subcontractors—have different interests in change: Owners want to control cost and scope Contractors want to protect margin and recover entitlement Designers want to achieve technical objectives Subcontractors want clear direction and fair compensation Change management provides the structured process for aligning these interests through documented assessment, negotiation, and agreement. How It Works Conceptually Change and variation management operates through integrated processes for identification, assessment, approval, implementation, and administration. Change Identification Changes must be identified before they are implemented: Sources of change identification: Source Examples Client instructions Formal variation instructions, meeting minutes, correspondence Design development Drawing revisions, specification updates, RFI responses Site conditions Inspection findings, survey results, unforeseen conditions Regulatory intervention Permit conditions, code changes, authority requirements Contractor proposals Value engineering, alternative methods, claims Subcontractor/supplier Technical submittals, non-conformances, delivery issues Third parties Utility companies, neighbours, public authorities Change identification process: Potential Change Identified │ ▼ ┌─────────────────────────┐ │ Is this different from │ │ contracted scope? │ └──────────┬──────────────┘ │ ┌─────┴─────┐ │ │ YES NO │ │ ▼ ▼ ┌──────────┐ ┌──────────────┐ │ Register │ │ No change │ │ as │ │ action │ │ potential│ │ required │ │ change │ └──────────────┘ └────┬─────┘ │ ▼ ┌──────────────────────────┐ │ Assign for impact │ │ assessment │ └──────────────────────────┘ Change Register: Field Description Change ID Unique identifier Title Brief description Source Who/what initiated the change Date identified When first recorded Category Type of change Affected scope WBS elements, packages, contracts impacted Status Pending assessment, under review, approved, rejected, implemented Owner Person responsible for progressing Impact Assessment Every identified change requires impact assessment: Assessment dimensions: Dimension Assessment Questions Scope What work is added, deleted, or modified? Cost What is the direct cost impact? Indirect cost? Schedule What is the time impact? Critical path effect? Quality Does the change affect quality requirements or risk? Safety Does the change affect HSE risk or requirements? Resources Does the change affect resource requirements or availability? Contractual What is the contractual basis? Who bears the cost? Risk What new risks does the change create or affect? Cost impact assessment: Element Consideration Direct cost Labour, materials, equipment, subcontract for changed work Indirect cost Extended preliminaries, supervision, facilities Disruption Impact on productivity of unchanged work Acceleration Cost to recover schedule if required Delay damages Exposure to liquidated damages if delay results Mark-up Overhead and profit per contract terms Schedule impact assessment: Element Consideration Activity duration Change in duration of affected activities Critical path Effect on project critical path Float consumption Use of available float Logic changes New dependencies or constraints Resource constraints Resource availability affecting schedule Milestone impact Effect on contractual milestones Impact assessment form: Section Content Change identification ID, title, description, source, date Scope impact Description of work added/deleted/modified Cost impact Estimated cost by category; basis of estimate Schedule impact Time impact; critical path effect; milestone impact Risk impact New or affected risks; contingency implications Contractual assessment Entitlement basis; contract clause references Recommendation Proceed, reject, or modify; conditions Approvals Signatures per authority level Change Approval Changes require formal approval before implementation: Approval authority matrix: Change Value Cost Impact Schedule Impact Approval Authority Minor <£25K <2 weeks Project Manager Moderate £25K–£100K 2–8 weeks Project Director Significant £100K–£500K 2–6 months Change Board / Steering Committee Major >£500K >6 months Executive / Board Approval process: Impact Assessment Complete │ ▼ ┌─────────────────────────┐ │ Determine approval │ │ authority per matrix │ └──────────┬──────────────┘ │ ▼ ┌─────────────────────────┐ │ Submit for approval │ │ with supporting │ │ documentation │ └──────────┬──────────────┘ │ ▼ ┌─────────────────────────┐ │ Review by approving │ │ authority │ └──────────┬──────────────┘ │ ┌─────┴─────┬────────────┐ │ │ │ APPROVE REJECT MODIFY │ │ │ ▼ ▼ ▼ ┌──────────┐ ┌──────────┐ ┌─────────────┐ │ Issue │ │ Document │ │ Revise and │ │ approval │ │ rejection│ │ resubmit │ │ and │ │ and │ │ │ │ proceed │ │ close │ │ │ └──────────┘ └──────────┘ └─────────────┘ Change Freeze and Design Freeze: Projects may implement change freezes to control late changes: Freeze Type Purpose Typical Timing Design freeze Prevent design changes affecting procurement End of detailed design Procurement freeze Prevent changes affecting awarded contracts Contract award Construction freeze Prevent changes affecting ongoing construction Construction start Change freeze Prevent all non-essential changes Approaching completion Freeze does not prevent all changes—safety, regulatory, and critical changes may proceed with elevated approval. Variation Management Variation management addresses contractual entitlement for changes: Variation notice process (typical contract requirements): Step Timing Content Initial notice Within days of event Brief identification of potential variation; intent to claim Detailed particulars Within weeks of event Full description; contractual basis; preliminary quantum Final claim Within months of event Fully substantiated claim with supporting documentation Variation valuation methods: Method Application Contract rates Apply existing BoQ rates to varied quantities Analogous rates Derive rates from similar BoQ items Cost-plus Actual cost plus agreed mark-up Lump sum Negotiated fixed amount Daywork Agreed daywork rates for work as directed Variation order documentation: Element Content Variation order number Unique identifier linked to contract Instruction reference Source instruction or event Scope description Detailed description of varied work Valuation Cost value and valuation method Schedule impact Time entitlement (if any) Contract basis Clause references establishing entitlement Signatures Authorised representatives of both parties Change Implementation Approved changes must be implemented systematically: Implementation steps: Step Activity Communication Notify all affected parties of approved change Documentation update Revise drawings, specifications, schedules as required Budget update Incorporate variation value in project budget and forecast Schedule update Incorporate time impact in project schedule Work direction Issue instructions to execute changed work Progress tracking Monitor implementation of changed work Cost tracking Capture actual cost of changed work Closeout Confirm completion and final valuation Change Administration Change administration maintains records and enables analysis: Change register maintenance: Activity Frequency Register update Continuous as changes progress Status review Weekly at progress meetings Trend analysis Monthly in project reports Forecast update Monthly or with significant changes Register reconciliation Quarterly and at project completion Change metrics: Metric Calculation Interpretation Change value (approved) Sum of approved variation values Total scope change impact Change value (pending) Sum of submitted but unapproved variations Potential additional exposure Change frequency Number of changes per period Change control effectiveness Change value as % of contract Approved changes / Original contract value Scope stability indicator Approval cycle time Days from submission to approval Process efficiency Disputed variations Value of unagreed variations Commercial risk exposure Risk Exposure by Contract Type Change and variation management exposure varies significantly by contract type: Stakeholder Fixed-Price Design-Build EPC EPCM Cost-Plus PPP/BOT Client / Owner 5 4 3 8 9 6 Contractor / Builder 8 8 9 4 3 7 Consultant / Supervisor 4 5 4 7 5 5 Designers 5 8 8 5 4 6 Laboratories / QC 2 3 2 3 2 3 QA and HSE 3 4 4 4 3 5 Lenders / Banks 5 6 6 7 5 8 Insurers 5 6 6 5 4 7 Rating Scale: 1 = Lowest change exposure, 10 = Highest change exposure Key observations: EPC and Fixed-Price place change risk primarily on contractors—changes within scope are absorbed; only owner-initiated changes trigger variations EPCM and Cost-Plus place change risk primarily on owners—most changes flow through as cost Design-Build creates significant designer exposure when design changes affect construction PPP/BOT creates complex change dynamics affecting long-term concession economics Lenders are exposed in all structures through project cost impact Why Generic Approaches Fail Generic enterprise systems fail to support effective change and variation management because they lack the contract awareness, workflow capability, and integration that change control requires. No contractual variation framework Change and variation management operates within contractual frameworks: Notice requirements and time limits Valuation methodologies and rates Approval and certification procedures Dispute resolution mechanisms Generic systems have no concept of contract-specific variation procedures. No integration with project control Effective change management requires integration: Changes linked to WBS and cost codes Variation values incorporated in budget and forecast Schedule impact reflected in programme Risk register updated for change-related risks Generic systems treat changes as separate transactions without project control integration. No workflow for change approval Change management requires defined workflows: Multi-level approval routing Impact assessment coordination Document attachment and versioning Approval tracking and audit trail Generic systems lack change-specific workflow capability. No variation register capability Variation management requires structured registers: Variation status tracking Entitlement documentation Valuation record Dispute flagging Final account integration Generic systems cannot maintain the structured variation data that commercial management requires. Spreadsheet change tracking creates control gaps Many organisations track changes in spreadsheets: No integration with cost and schedule systems No workflow enforcement Version control problems Audit trail gaps Reconciliation burden at final account Where it Applies Design Development. Change control during design phases to manage scope evolution and design freeze compliance. Procurement. Change control during tendering and contract negotiation to maintain bid validity. Construction Execution. Comprehensive change and variation management throughout construction. Commercial Management. Variation administration, valuation, and negotiation as part of commercial function. Final Account. Change and variation reconciliation as part of project closeout and final account settlement. Claims and Disputes. Change documentation supporting or defending claims. Lessons Learned. Change analysis for estimating improvement and future project planning. Common Misconceptions Misconception: Change management is bureaucracy that slows projects down. Reality: Unmanaged change slows projects far more than disciplined change control. The time spent assessing and approving changes is recovered many times over through avoided rework, clearer direction, and preserved entitlement. Misconception: Good project management should prevent changes. Reality: Changes are inherent in capital projects—designs develop, conditions are discovered, requirements evolve. Good project management does not prevent changes; it controls them effectively when they occur. Misconception: Variations are adversarial and damage client-contractor relationships. Reality: Variations are a normal commercial mechanism for adjusting contracts when scope changes. Professionally managed variations, with clear documentation and fair valuation, maintain healthy relationships. Unmanaged changes create disputes. Misconception: Verbal instructions are sufficient for minor changes. Reality: Verbal instructions without documentation create disputes about what was instructed, when, and what it cost. Even minor changes should be documented to protect both parties. Misconception: Change control should be relaxed to maintain project momentum. Reality: Relaxed change control leads to scope creep, cost overruns, and disputes. Efficient change control—fast assessment, clear authority, prompt decision—maintains both control and momentum. Misconception: If a variation is not agreed, the work should not proceed. Reality: Contract provisions typically require work to proceed on instruction even if valuation is disputed. Entitlement is preserved through proper notice; work proceeds under protest if necessary. Stopping work over disputed variations escalates conflict unnecessarily. Related Topics What Is Risk Management in Capital Projects? — Changes often arise from risk events; change management integrates with risk processes. What Is a Risk Register? — Changes may create new risks requiring register update. What Is Contingency Management? — Contingency may fund owner changes; variation recovery affects contingency requirements. What Is Claims Management? — Unresolved variations may escalate to claims. What Is Contractual Risk Allocation? — Contract terms determine change entitlement. What Is Project Cost Control? — Change values must integrate with cost management. What Is a Bill of Quantities (BoQ)? — BoQ provides basis for variation valuation. RELATED ASSETS Related Industries Construction Project-based Manufacturing Marine and Offshore Construction Mining and Quarrying Shipbuilding and Repairs RELATED ASSETS Related Stakeholders Owner/Developer E&P Owners Mine & Quarry Owner Consultants General Contractors Marine Contractor Shipbuilders Mining Contractor RELATED ASSETS Related Roles C-level Executives Project Manager Bidding Manager Cost Estimator Cost Controller Go to Previous Topic Previous Topic Return to What is? Go to Hub Go to Next Topic Next Topic