Define Scope – Before You Build.
PMWEB's planning module gives capital works owners and program managers structured tools to define scope, establish governance frameworks, set stage gates, and baseline their program — before a contract is signed or a dollar committed to construction.
The Foundation of a Well-Managed Capital Program
Poor planning is the leading cause of cost and schedule blowouts in capital works programs. PMWEB's planning capability gives owners, directors, and program managers a structured, auditable starting point — from scope definition and WBS setup through to governance frameworks and delivery baseline — so that every decision made downstream has a documented foundation.
Explore the Plan phase
Scope Definition and Program Structure
PMWEB allows capital works owners to define the full scope of a program from the outset — establishing the Work Breakdown Structure, project hierarchy, and cost account coding before procurement begins. This gives all stakeholders a shared reference point that persists through design, construction, and into operations.
Governance Frameworks and Stage Gate Controls
Capital works programs in the public and regulated private sector operate within formal governance structures — Treasury approval thresholds, Cabinet endorsements, and board sign-off requirements. PMWEB's stage gate functionality allows these decision points to be built directly into the platform, so no work proceeds without documented authorisation.
Program Schedule and Milestone Management
PMWEB's scheduling capability at the planning phase focuses on the program-level milestones that matter to owners — key decision dates, funding submission deadlines, design completion, construction start, and practical completion. These milestones cascade through the project hierarchy and connect to the stage gate framework, so slippage is visible immediately.
Early Risk Identification and Register Setup
Risks identified late in a capital program cost exponentially more to resolve than those captured at the planning stage. PMWEB's risk register is active from program setup, allowing owners to document, categorise, and assign ownership to risks before design begins — with direct linkage to the contingency budget and the stage gate framework.
Planning-Phase Dashboards and Reporting
From the moment a program is set up in PMWEB, reporting is live. Dashboards show program status, outstanding approvals, upcoming milestones, and risk exposure — giving executives and program boards the visibility they need to make informed decisions before construction commences. All reports drill through to the underlying data.
The PMWEB Planning Setup Process
PMWEB structures the planning phase into four disciplined stages — from initial program definition through to a fully governed, approved baseline ready for estimating and procurement to commence.
Establish the program hierarchy, Work Breakdown Structure, cost account coding, and scope documentation — the shared reference for all downstream planning, estimating, and delivery activity.
Set up stage gates, approval workflows, financial delegation thresholds, and role-based access — aligned to your organisation's methodology (PMBOK, PRINCE2, or internal standards).
Define baseline program milestones, link them to stage gates, and populate the risk register with identified risks — assigning ownership and linking contingency allowances before design commences.
Route the planning documentation through the approval workflow. Once approved and baselined, the program is locked — all scope changes, schedule adjustments, and budget revisions follow the formal variation process.
Planning Works Alongside Every PMWEB Module
The program structure, governance framework, and baseline you establish in the Plan phase flows through to estimating, procurement, contracts, cost controls, and reporting — all within the same platform. No re-entry. No data gaps between phases.
We went live with PMWEB at program setup — before a single contract was signed. Having the WBS, stage gates, and governance framework in the system from day one meant every team member was working from the same structure. When the first variation came, the audit trail was already there.
Ready to Set Your Next Program Up for Success?
Talk to our team about how PMWEB's planning module can be configured to your governance framework, WBS structure, and delivery methodology.