Getting Workface Planners Productive in the First 90 Days

A new workface planner has roughly 90 days to earn the trust of field crews. In that time, the planner has to learn the project's Path of Construction (PoC), its constraint process and its Advanced Work Packaging (AWP) software while Installation Work Packages (IWPs) keep coming due. Structured workface planner onboarding has a new hire releasing constraint-free packages before the 90 days are up.

Why Change Management Decides Adoption

Change management is the most challenging part of adopting any new way of working on a capital project, and AWP software is no exception. O3 makes that process easier, because planners commit to the software once they see the value it brings to their own weekly work. Three things help them see that value sooner: training that matches the current release, onboarding built around the planner's role and plain AWP basics for Owners' own staff.

Workface planners feel the change first. They sit between engineering, materials and construction, so any delay in planning shows up as late work packages for field crews.

Every late package leaves a crew waiting and eats into the gains AWP is meant to deliver. Research from the Construction Industry Institute (CII) found that projects using AWP increased field productivity by up to 25%. Planners help a project capture the productivity gain by releasing constraint-free packages on time every week.

Releasing constraint-free packages on time is a skill that builds in stages. New planners rarely need deep AWP expertise on day one, so a team can start from the process it already runs and develop each hire over the first 90 days in three steps: train for the role, repeat with a coach and keep the weekly planning meeting going after go-live.

Days 1 to 30: Train for the Role First

Product training that walks through every screen leaves planners guessing which features matter to their job. A role-based path starts from the planner's weekly package cycle instead: scoping an IWP, checking constraints, requesting scaffolding, releasing work to the field and closing out completed scope against rules of credit.

Open the month with a short workshop that includes the construction manager and the field superintendent. The session sets the baselines everyone plans against: the PoC, the package numbering scheme and a named owner for each constraint category. From there, build the rest of the month around the weekly package cycle and run every exercise on the planner's own project data.

End the month with a skills check. By day 30, a new planner using ONBuild, O3's construction workface planning software, should be able to:

• Find the Construction Work Packages (CWPs) for an assigned area and read their sequence in the PoC
• Scope an IWP graphically from the 3D model
• Log constraints and see who owns each one
• Release an IWP through the approval workflow

Days 31 to 60: Repeat the Package Cycle with a Coach

Month two turns the day-30 skills into habit. Planners often need several runs through the full package cycle before the sequence sticks. Pair each new hire with an experienced colleague or one of O3's expert Project Managers for the first few releases. The planner drives the software while the coach watches and corrects. Short walkthrough videos of the same steps help between sessions, as long as every recording uses the current release and matches what planners see on screen.

Coaching works better when planners can see their own results. Built-in dashboards track package readiness against due dates and how quickly constraints close. Construction managers tend to ask about package readiness and constraint closeout in project reviews, so planners who check the dashboards weekly arrive with answers.

New planners ask many of the same questions in coaching sessions, so record the coach's answers in a short project playbook. The most common questions in month two cover package numbering rules, the constraint categories that need a second check and who signs off on scaffolding. A written playbook outlives any single coach and shortens onboarding for the next planner who joins mid-project.

Days 61 to 90: Protect the Planning Cadence

By month three, planners can run the package cycle alone, so the next challenge is keeping the weekly planning routine going without a coach. That routine is most likely to slip after go-live, when the implementation team hands over and schedule pressure rises. Planning meetings get skipped, constraints are cleared in hallway conversations and packages drift back into spreadsheets.

A planning meeting held at the same time every week keeps packages in ONBuild and out of spreadsheets. Keep the agenda to three standing items and run the meeting from dashboards or Team Boards, so the review takes minutes and the rest of the hour goes to decisions:

• IWPs due in the next three weeks
• Open constraints, sorted by owner
• Last week's released packages compared with the scope the field completed

The meeting only works if field crews use the packages planners release. When crews progress IWPs in ONField, planners have a live view that packages are being worked on. Seeing crews work from their packages keeps planners committed to the weekly meeting after the coaches leave.

Even with a live view of the field, the weekly routine can slip, so watch for three warning signs:

• IWPs released with constraints still open
• Meetings that end without decisions
• Fewer packages ready when they enter the look-ahead window

Each sign points to a skill gap or a lapse in the weekly meeting. A quick coaching session costs less than a missed release.

From Guided Implementation to Self-Sufficiency

O3 can support new planners at each step of the 90-day plan. Its team of expert Project Managers guides each deployment through setup, training and the first release cycles. SMARTStart, O3's implementation program, follows a crawl-walk-run path, so planners build skills in stages and teams move from guided support to independence.

For the wider organization, our maturity model for digital project execution describes four levels of self-sufficiency, from Dependent to Self-Scaling. Our complete guide to AWP covers PoC, CWPs and IWPs in more depth. To see how ONBuild supports workface planners from the first released package to a self-sufficient team, request a demo.