Workface planning (WFP) is the process of developing, organizing, and delivering Installation Work Packages (IWPs) so a single crew can perform quality work safely, effectively, and efficiently. Identifying and removing constraints before work starts is part of the discipline. In practice, that means a workface planner inside the construction contractor's organization carves crew-sized packages out of larger construction scope, verifies that drawings, material, access, and equipment are actually in hand, and releases a package only when nothing can stop the crew. Everything else in workface planning exists to make that release trustworthy.
Where workface planning sits
Workface planning is one of four procedures that have to move together on a packaged project. Advanced work packaging (AWP) aligns engineering and procurement with construction during design: it establishes the path of construction and sequences engineering and procurement deliverables against it. Material management governs the flow of material across the project. Information management keeps every dataset coherent as it crosses from engineering to procurement to fabrication to the field. Workface planning is the fourth: it converts released packages into constraint-free crew work.
The division of labor matters. AWP governs design-phase alignment and lives largely with the owner and the engineering contractor. Workface planning stays with the constructor. The WFP manager and the workface planners sit inside the construction organization, because the decisions they make (how to cut a package, when to release it, what counts as ready) are construction decisions.
New to the parent discipline? Start with What Is Advanced Work Packaging?, or read how the two disciplines hand off to each other. The short version: AWP builds the pipeline of packages, and workface planning is what happens at the end of the pipe.
The IWP is the unit of work
Workface planning operates on two package types, and the sizing rules are the heart of the method.
A Construction Work Package (CWP) is a logical, single-discipline division of construction work inside one Construction Work Area (CWA), defined by a 3D envelope. The sizing convention: enough work for one general foreman, roughly three crews of eight, for six to eight weeks, which lands in the range of 7,000 to 12,000 hours.
An IWP is dissected from a single CWP: one foreman, one crew, seven to ten days of constraint-free work. Never two crews, never scope pulled from two CWPs, never "about a month of work." The sizing is deliberate. A package small enough to be verified completely, executed by one crew, and closed within days is a package whose status you can trust. Anything bigger turns into a rolling estimate.
Those packages live at fixed planning altitudes. CWAs shape the Level 2 schedule. CWPs appear as real activities in the Level 3 schedule, typically no more than eight weeks long, and every construction activity at Level 3 corresponds to a CWP. IWPs are Level 4 activities of one to two weeks, and they never appear in the Level 3 schedule: they live in the workface planning software, sequenced through the four week lookahead (4WLA). If your scheduler is loading IWPs into the Level 3 schedule, the altitudes have collapsed and both schedules will degrade.
Packages are the mechanism, not the paperwork. The objective is not to produce IWPs as administrative deliverables but to plan, execute, and measure the work through them. If crews are working from marked-up drawings while the packages sit in a binder, workface planning is not happening, whatever the org chart says.
What constraint-free actually means
An engineering package issued IFC is not, by itself, executable work. A crew can only follow a complete package: drawings, and material, and no open constraints. Workface planning treats each of those as something to verify, not assume.
Constraints are tracked as data against specific packages, not as a general worry list. On a well-run project that looks like this:
- Engineering HOLDs are registered one per row, each with an owner, a status, and a forecast release date, so a held drawing shows up against every package it touches.
- RFIs carry a mandatory engineering package reference at submission, and the RFI log is loaded into the AWP software so open RFIs appear as constraints against the affected CWPs and IWPs.
- Material is tracked as a countdown against required-on-site dates, package by package, and a material scope is complete only at 100% receipt with the PO closed. Material that is "mostly here" is still a constraint. Our materials management hub covers how that countdown is measured.
- Field constraints cover the rest: access, permits, scaffolding, construction equipment, and predecessor work.
The output of all that verification is a constraint-free backlog: a pool of IWPs that any qualified crew could start tomorrow. Keeping that backlog healthy is how the discipline absorbs upstream slips. When engineering runs late or a shipment stalls, the answer is not to release a partial package to keep people busy. It is to keep crews on the verified backlog while the pipeline gets fixed. A partial release just exports the problem to the field, where it gets discovered at craft rates.
The planning rhythm
Workface planning runs on two lookaheads. The CWP 90 day lookahead, reviewed monthly with the WFP manager, is a check on what should be entering the pipeline: which CWPs are approaching, whether their engineering is releasing on plan, whether material is tracking to its required-on-site dates. The 4WLA is the sharp end, worked weekly: the sequenced list of IWPs for the next four weeks, each one either constraint-free or carrying named constraints with owners and dates. The 4WLA sequences IWPs, but it is not itself a package, and nothing should reach the front of it that a crew cannot actually execute.
Scoping happens in the model. Because CWPs are defined as 3D envelopes, workface planners cut IWPs by carving those envelopes into crew-sized volumes, then assembling the drawings, material lists, and quality requirements that belong to that volume. When the model, the document register, and the material data disagree about what is inside a package, that disagreement is itself a constraint, and resolving it before release is part of the job.
Measuring the work
Workface planning changes what progress means. Performance is measured by work package, not by activity percent complete. For the constructor, the core measures are simple: material received by CWP, CWPs started on time, CWPs completed on time, and daily productivity by foreman.
The IWP cycle itself is one of the most honest metrics on a project. An IWP sized for seven to ten days that stays open longer means a constraint escaped the system, and someone is paying craft rates to wait for it. You do not need a productivity study to find the problem; you need the list of overdue IWPs and the constraint log behind each one.
Closeout is equally strict. A CWP is complete only when 100% of its IWPs are closed, the punch walkdown is done, and the quality documentation is delivered. Not 97%, not "essentially complete." That standard is what lets the last stage of the project run on the same rails as the first.
Running it to the last punch item
The end of a job is where projects traditionally drown in spreadsheets and walkdown chaos. Mature workface planning avoids that by re-cutting the packages instead of abandoning the method. After roughly 40% construction progress, soft-craft packages (insulation, painting, heat tracing) start development under the same rules. Around 70%, IWP planning shifts from bulk area sequence to the turnover sequence. At 75 to 80%, remaining scope is re-packaged into System Work Packages, each one carrying all remaining work for its system so commissioning can proceed safely and measurably.
The point of the phased gates is that there is never a moment with two operating logics in the same lookahead. Same packages, same constraint management, same lookaheads, right through systems completion. If your completions plan starts with "export everything to a spreadsheet," the discipline ended too early.
Software, and where we fit
Workface planning lives or dies in its software: the platform where IWPs are developed, constraints are tracked, and the lookahead is planned. openAWP is built as exactly that platform. Package forms, fields, and the package hierarchy are user-defined, so your project's CWP and IWP structures come through as-is. Constraints are tracked against packages, model scoping runs through a built-in 3D viewer, and it connects to Primavera P6, Smart 3D, Navisworks, Smart Materials, and Power BI, deployed on your own infrastructure.
If the gap is people and process rather than tooling, our workface planning team does this work embedded in project organizations: standing up the discipline, cutting the first packages, and running constraint management until your own planners own it.
To see the package and constraint workflow live, explore openAWP or book a demo.