AWPBI

What a Document Allocation Matrix Does

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

A Document Allocation Matrix maps each discipline and document type to the work package type that carries it, and document control consults it every time a placeholder is created. It turns allocation into a lookup that every discipline performs the same way.

What It Decides

Every document in the master document register and the project document system is assigned to one work package at the moment its placeholder is created. The assignment is an EWP, a VEWP, an FEWP, or not applicable, and unassigned documents are not permitted. Only documents required for construction execution are allocated to a package, which keeps engineering studies and internal calculations out of the field set. Project-wide documents such as P&IDs, specifications, standards and typical details sit under a general construction work area reserved for scope common to several areas.

The matrix defines the approved relationships between disciplines, document types and package types, and the engineering contractor develops and maintains it under the AWP procedure. Discipline leads and document control use it as the governing reference when they assign documents to EWPs, VEWPs and FEWPs. An extract looks like this.

EWP codeDocument typeDiscipline
PIP-GENIsometric drawingPiping
STL-GENConstruction drawingStructural steel
CIV-CONFoundation design drawingCivil
ELE-GENSingle line diagramElectrical
INS-HUPHook-up diagramInstrumentation
MEC-MEQEquipment specificationMechanical static

How It Is Used

The register is developed by EWP and VEWP, issued weekly, and synchronized with the document system within days of any change. Discipline leads identify the deliverables and request placeholders, document control creates them, registers them in both systems and allocates each one using the matrix, and the whole list of placeholders for a package exists eight weeks before its planned release. Compliance is monitored through the EWP, VEWP and FEWP 8 week lookahead, and a package approaching release with incomplete allocation is flagged to the contractor's AWP manager and the owner's AWP lead.

The matrix is also the reason the one document, one drawing, one sheet rule can be enforced. A combined dossier has no single document type and no single package, so it cannot be allocated, and a document that cannot be allocated cannot be registered.

Why Allocation Happens at Creation

Allocating after issue is how documents go missing from packages. A drawing issued without a package sits in the document system, counts toward nothing, and surfaces when the construction contractor asks why an IWP is short a detail. Allocation at placeholder creation puts every planned document in a package before any file exists, which is what lets placeholder completeness work as a leading indicator. Writing the matrix and running the allocation rhythm with document control is part of information management. The matrix and the allocated register stay with the owner when the project closes.

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

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.