Capability
Project Controls Planning
Define the control-account structure, measurement rules, reporting calendar, and change path before the first status cycle is treated as optional.
C02 — The problem
The technical problem
A live project can produce weekly packs and still have no control system. Schedule, cost, change, and risk sit in different files, progress is claimed on a different structure from the budget, and the reporting calendar is whatever the last meeting demanded.
Project Controls Planning is the assignment that decides what will be controlled, on what evidence, by whom, and on what cycle — before those questions are answered by whatever spreadsheet happens to exist.
C03 — Engagement
When this capability is needed
-
01
Mobilisation
A new programme needs a control basis before the first progress cycle.
-
02
Control reset
Existing reports cannot be reconciled to one WBS, one baseline, and one forecast.
-
03
Governance change
An owner or PMC needs a reporting calendar and decision rights the contractors can actually feed.
-
04
Baseline integration
Schedule and cost are about to be locked and still do not share a structure.
C04 — Scope / method
How the work is approached
The work designs the control system: work breakdown and control accounts, measurement rules, data cutoff, review and decision points, and the path by which approved change updates the baseline. It does not replace the live schedule or cost forecast assignments that follow.
-
01
Establish the control basis
What must be visible: time, money, change, risk, and the decisions those views support.
-
02
Map WBS and control accounts
A structure schedule, cost, and change can share.
-
03
Set measurement and cutoff rules
How physical progress and remaining work will be evidenced each period.
-
04
Define the reporting calendar
Data date, review, and decision — not a slide deadline.
-
05
Define the change path
How approved change updates the baseline, and how unapproved change remains variance.
-
06
Issue the Project Controls Plan
A usable procedure, not a generic template.
C05 — Outputs
Typical deliverables
| Output | What it contains |
|---|---|
| Project Controls Plan | Rules for baseline, progress, change, risk, and reporting. |
| WBS / control-account map | Shared structure for schedule and cost. |
| Reporting calendar | Cutoff, review, and decision dates. |
| Measurement procedure | Evidence required for period progress. |
| RACI for control roles | Who owns data, review, and baseline change. |
C06 — Decision value
What this work is used to decide
Leadership can decide whether the proposed control system is sufficient to baseline against, who must feed it, and which reports will be treated as the official position. It does not decide the commercial outcome of the works.
C08 — Project environments
Relevant project environments
C09 — Who we support
Who commonly needs this capability
C10 — Boundaries
Important distinctions
This is not a substitute for the live programme, the cost forecast, or statutory project-management appointment. It is the control architecture those assignments should run on.
C11 — Next step
Discuss your project
If this is the technical problem you are facing, talk to Value Construction about the work, the records required, and what you would receive. Outcomes are not guaranteed.