AWPBI

What a HOLD Register Must Contain

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

A HOLD is a controlled suspension of a document or a piece of work, and the register that tracks it has one row per document. Each row carries the EWP, the drawing number, the reason, a single accountable owner, the current status and a forecast release date, and a row missing any of those is already out of date.

What a Row Carries

Discipline leads raise HOLDs and the engineering contractor's document control compiles the register weekly. The reason for every HOLD is written on the drawing itself and delivered to the construction contractor in tabular form, so the field reads the same reason the register holds. One document per row is a rule, isometrics included, because the register links to the document system and to the EWP Skyline by document number, and a cell holding three drawings links to nothing.

HOLDs at Release

Every HOLD on a package is listed on the EWP cover page and in the transmittal. At the EWP review the construction contractor's workface planning manager accepts or rejects each one, and a rejected HOLD keeps the package from release. A package released with accepted HOLDs carries the status IFC with HOLDs, which is distinct from IFC, and it is issued only after the owner approves. The review tracker keeps it under that status until every HOLD is released.

Releasing a HOLD

A HOLD is released by revising the EWP. The engineering contractor issues a general notification through the document system and re-transmits the package, so the removal of the constraint travels the same channel every other engineering change travels and reaches the workface planners who are holding IWPs against it. That makes the release auditable. A HOLD closed by email leaves a constraint open in the AWP software with nobody able to say when it went away.

HOLDs as a Metric

The AWP manager oversees aging, escalation, reporting and closure across the register. HOLD aging and closure performance are reported with the AWP metrics, and open HOLDs appear on the EWP Skyline beside the packages they affect, so a package at 100 percent IFC with three open HOLDs looks different from one that is clear. The weekly EWP meetings carry the HOLD status to construction, where workface planners manage the engineering constraints on their IWPs.

The register sits beside the release plan and the change process as one of the three documents that tell an owner whether engineering is ready for construction. Setting them up together is part of AWP consulting. The register, with every HOLD's history, stays with the owner at the end of the contract.

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

How EWP Changes Are Managed After IFC

The five categories of EWP change, the change notice that precedes revised drawings, and the re-transmitted package that keeps every recipient on one set.

4 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.