A food facility's $800K CIP system project starts with well-defined scope. Partway through, requests emerge: "While we're upgrading, can we also improve the chemical storage system?" "Can the new CIP handle this product variant?" "Our supplier suggested a better valve—can we upgrade?"
Each request seems reasonable. Each is a small addition: $15K here, $20K there, $10K elsewhere. Six months later, the project has $150K in change orders. The budget is exceeded 18%. The schedule has slipped 6 weeks.
This is scope creep—the incremental addition of work beyond original scope.
Why Change Orders Happen
- Incomplete Original Scope: Requirements weren't fully understood upfront
- Discovered Conditions: Site conditions different than expected (infrastructure gaps, equipment conflicts)
- Stakeholder Additions: Different departments want improvements added mid-project
- Vendor Suggestions: Equipment manufacturers recommend upgrades
- Regulatory Changes: New requirements emerge during execution
Each is legitimate, but accumulation kills budgets.
The Three-Level Approval Process
Level 1: Determination ($0-$10K)
Plant manager and project manager jointly determine necessity:
- Is this within original scope? (If yes, no change order needed)
- Is this essential to functionality? (If no, defer to future project)
- Can it be accomplished within schedule? (If no, cost rises due to expediting)
Level 2: Authorization ($10K-$50K)
Requires Plant Director + CFO approval:
- Document why change is necessary
- Provide three-quote comparison if possible
- Identify impact on schedule and budget
- Specify who pays (project or business unit requesting addition)
Level 3: Strategic Review ($50K+)
Requires PE Operations Team or Board approval:
- Changes of this magnitude require executive visibility
- May indicate scope definition failures during FEL
- May indicate market opportunity (strategic addition vs. scope creep)
The Paper Trail That Matters
Effective change order management requires documentation:
- Original scope statement (crystal clear)
- Change request (submitted on standard form)
- Change order approval (authorized before work starts)
- Revised budget and schedule (documented)
- Completion documentation (proof of installation and testing)
Without this discipline, disputes emerge: "We never approved that." "That was supposed to be in the original scope."
The Prevention Strategy
Better than managing change orders: Preventing unnecessary ones.
- Thorough FEL Studies: Identify requirements and site conditions upfront
- Clear Scope Statements: Document explicitly what IS and ISN'T included
- Strong Project Governance: Clear approval authority and decision-making
- Regular Status Meetings: Surface stakeholder requests early, evaluate impact
- Stakeholder Alignment: Get sign-off from all departments BEFORE project starts
The Cost Impact
Every $10K change order in a $800K project:
- Adds 0.4% to project cost
- Adds 2-3 days to schedule (at minimum)
- Creates one approval and documentation requirement
Ten $10K changes = $100K overrun + 20-30 day schedule slip.
For food manufacturing companies, strong change order discipline and clear scope definition during planning prevents budget and schedule overruns that compound during execution.
