AWPBI

How EWP Changes Are Managed After IFC

By AWPBI Planning Team · Updated Oct 2026 · 4 min read

Once an engineering work package is issued for construction its scope is frozen, and every change to it runs through a controlled process with an auditable record. The reason is downstream. Each EWP drives procurement sequencing and installation work packages, so a quiet drawing revision moves material, crews and the schedule.

Five Kinds of Change

The procedure sorts changes into five categories, and the category decides the paperwork.

Changes before IFC are internal. Drawing revisions, model updates, vendor data integration and the addition or voiding of a drawing are incorporated before release with no change notice, as long as controlled documents follow the contractor's management of change. Deleting a planned EWP at this stage still goes through the AWP lead, because the AWP Matrix is updated before anyone touches the schedule, the register or the AWP software.

Changes after IFC that stay inside the existing scope, such as a drawing revision, a model update, a vendor document revision or an added drawing, require an EWP change notice and a revised package.

Changes that grow or re-baseline scope, meaning new EWPs, scope moved between EWPs, or packages combined or split, are requested through the AWP lead, land in the matrix first, and then flow to the Level 3 schedule, material planning, the change notice, the new package, the review and the release.

Changes driven by safety or regulation, anything touching P&IDs, plot plans, process safety data, cause and effect diagrams, interlock logic or hazardous area classification, go through the full management of change workflow and process safety approval before any EWP is updated.

Changes raised from the field, through an RFI, a deviation notice or a variance, trigger a change notice whenever the engineering answer revises a drawing after IFC, along with updated IWPs and schedule and procurement adjustments. Every RFI names the affected EWP at submission, and the RFI log sits in the AWP software so each one is visible as a constraint on its CWPs and IWPs.

The Sequence After Approval

Every change gets an impact assessment covering scope, safety, engineering effort, construction, procurement, fabrication, schedule, cost, model and data changes, and alignment with the path of construction. Significant changes after IFC, taken as more than 25 hours of craft, need the owner's approval.

The change notice goes out before any revised drawing is published, through the document system, to construction management, superintendents, workface planners, procurement, fabrication, the owner's engineering team and project controls. The revised EWP is then transmitted as a complete package under a new revision number, every current document included, with a cover page that states the revision, the reason and each document that changed, was added, was removed or was placed on HOLD.

Transmittal is not the end of the revision. Workface planners revise the affected IWPs, and procurement and fabrication update their plans. The 3D model, the MTO, the piping files and the structural models are regenerated and reconciled against the revised drawings, and the master document register, the schedule, the data warehouse and the reporting all reflect the new revision. The AWP lead records the change in the EWP change log and updates the EWP Skyline. Only when all of that has been verified does the revision count as complete.

Running this process with an engineering contractor, from the categories to the log, is part of AWP consulting. The change log, the notices and the revised packages are the project's record of what changed and why, and they remain with the owner.

Questions Readers Ask

Related Articles

What Is Advanced Work Packaging?

A plain-language definition of AWP, why capital projects use it, and how it changes execution planning.

7 min read · Updated Jul 2026

How Workface Planning Fits Into Advanced Work Packaging

Workface planning is the last step in AWP, turning engineered scope into packages a crew can execute.

5 min read · Updated Jul 2026

Advanced Work Packaging Without a 3D Model

What the 3D model does in a full AWP procedure, what still works when a project has no usable model, and which controls have to be rebuilt by hand.

4 min read · Updated Oct 2026

Self-Hosted AWP Software with P6 and Power BI

What self-hosting AWP software means for project data, how it divides work with the Primavera P6 schedule, and how Power BI reads package data from it.

4 min read · Updated Oct 2026

Which Project Phases AWP Software Should Cover

What AWP software should hold from FEED to turnover, covering the path of construction, EWPs and PWPs, IWPs and the lookahead, testing, and system completion.

4 min read · Updated Oct 2026

What It Takes to Set Up AWP Software on a Project

How AWP software is set up from FEED, with the structures agreed before engineering packages, data loaded every week, the model link, and full-time leadership.

3 min read · Updated Oct 2026

How the AWP Package Hierarchy Maps to Software

The eleven AWP package types from CWA to SWP, who owns each one, and the rules AWP software has to hold for parents, one-to-one packages, and the register.

3 min read · Updated Oct 2026

How to Evaluate Advanced Work Packaging Software

Seven areas to evaluate in AWP software, drawn from what an AWP procedure asks of it, from building IWPs from the model to completing work by system.

3 min read · Updated Oct 2026

How Advanced Work Packaging Software Is Priced

The three parts of AWP software cost, which are the license, the setup, and support through execution, and what each one covers on a capital project.

3 min read · Updated Oct 2026

AWP for Brownfield Projects and Turnarounds

How advanced work packaging applies inside an operating plant, from the existing plant in the model and site-controlled drawings to MOC and turnarounds.

3 min read · Updated Oct 2026

How Owners Run AWP Across Several EPC Contractors

How an owner runs AWP across several EPC contractors with a standard set before contracts are signed, owner roles, one naming convention, data, and audits.

3 min read · Updated Oct 2026

The AWP Record Should Outlive the Contract

The AWP registers, the matrix and the readiness history sit in the contractor's system and leave when the contract ends. The fix is where the standard lives.

9 min read · Updated Oct 2026

What Complete Means for Each AWP Package Type

The definition of complete for all eleven AWP package types, fixed in the procedure, plus the one binary rule of credit that measures EWP progress.

5 min read · Updated Oct 2026

An EWP Release Plan the Owner Can Audit

How an engineering contractor runs an EWP release plan an owner can audit, with four statuses, one rule of credit, weekly forecasts and a skyline.

5 min read · Updated Oct 2026

Placeholders Are the Earliest Warning an EWP Will Be Late

Why a short placeholder count eight weeks before an EWP release predicts a late package, who owns the count, and the weekly check that catches it early.

4 min read · Updated Oct 2026

What the AWP Matrix Is and Who May Change It

The AWP Matrix is the one controlled list of every work package and its relationships, owned by the owner's AWP lead and issued weekly before systems change.

4 min read · Updated Oct 2026

What an Owner Checks in an Engineering AWP Audit

The items an owner checks in an engineering AWP audit, when the audits happen, and the weekly routine that lets an engineering contractor pass every time.

4 min read · Updated Oct 2026

What a HOLD Register Must Contain

What every row of an engineering HOLD register carries, how HOLDs are accepted at the EWP review, and why a HOLD is released by revising the package.

3 min read · Updated Oct 2026

What a Document Allocation Matrix Does

How a Document Allocation Matrix assigns each document to an EWP, VEWP or FEWP when its placeholder is created, with an example and the rule on unassigned ones.

4 min read · Updated Oct 2026

The Lean Owner AWP Organization

The small set of AWP roles an owner needs from FEED, who reports to whom, the deliverables each lead owns, and where a partner fills the gaps.

4 min read · Updated Oct 2026

Why the Module Yard Is an Extension of the Site

Why module fabrication follows the same AWP requirements as site construction, what FEWPs and MWPs are, and the review two weeks before a module ships.

4 min read · Updated Oct 2026

When a Project Moves from IWPs to System Work Packages

When a project repackages remaining scope into system work packages, what an SWP contains, and why the lookahead and constraint process stay the same.

4 min read · Updated Oct 2026

What Model Conditioning Is and Why AWP Needs It

What model conditioning covers, from attributes per the data requirements and CWP volumes to an EWP-structured tree, tag checks, and vetted vendor models.

3 min read · Updated Oct 2026

See How openAWP Supports Advanced Work Packaging

Explore the product these articles are about, or book a live demo to see it on your own project.