PCProject controls
Plan, procurement, risk, payment and change, in the project record
Project controls in BuildEase sit beside the documents, inspections and approvals they depend on. Progress is read from the plan your project approved and the work it measured.
01Planned registers
The plan your project approved, kept honest through every revision
Engineering, procurement and inspection-and-test plans are imported, approved and then measured against.
- Planned against actual by domain, with the difference opening its detail
- A revision cannot silently drop an item that already has history: each one is kept, cancelled or superseded, with a reason
- Until a plan is approved, the dashboard says so instead of inventing a figure
In BuildEaseProject Controls › Planned Registers
- FactWhere are we?148 of 172 planned deliverables submissions by the data date (86%).
- FactCompared with what?The current plan, version 3; the original baseline planned 160.
- SignalWhere is it concentrated?MEP accounts for 67% of the shortfall; the other disciplines are within two items of plan.
- FactWhy?Not yet submitted 9 · submitted, not yet approved 8 · returned for revision 5.
- ForecastWhat is forecast?At the demonstrated pace (6 items a week over the last 14 days) the current plan's quantity would be reached 5 weeks after its planned date. A projection, never a contractual position.
Current planActual
| Group | Planned | Actual | Short | Share of shortfall |
|---|---|---|---|---|
| Architectural | 48 | 44 | 4 | 17% |
| Structural | 36 | 34 | 2 | 8% |
| MEP | 62 | 46 | 16 | 67% |
| Civil | 26 | 24 | 2 | 8% |
Needs attention
- 9Planned items not submitted
- 5Returned for revision
- 3In review past the planned date
- 2Long-lead items past the required date
- 2Risk actions past target
Long-lead items
15 of 24 delivered · 2 past the required-on-site date · 2026-11-08
In BuildEase todayProject controlsPlanned registersProcurement & LLI
Illustrative data
02Procurement and long-lead items
Long-lead items followed from approval to purchase order
Procurement items and long-lead items are held with their vendors and purchase orders, next to the material approvals they wait for.
- Procurement and long-lead items with their vendors
- Purchase orders recorded against each item
- The procurement plan measured with the other planned registers
In BuildEaseProject Controls › Procurement & LLI
03Risk register
Risks rated the way your project rates them
The register holds the project's risks, a heat map and early-warning signals, for the people permitted to see them.
- A heat map of the open risks
- Early-warning signals raised from the record
- Open risks carried to the portfolio view, by each project's own rating
In BuildEaseProject Controls › Risk Register
04Commercial and payment certificates
From measured work to payment, one chain
Interim payment certificates move through their review and approval chain, built on verified contract facts and the measured work behind them.
- Contract value, earned, claimed, certified and paid, each against the contract value
- Contract facts verified by a second person before they count
- Certification is never recorded as payment
In BuildEaseProject Controls › Commercial / IPC
- Contract value184.5 M
- Earned (evidence-backed)76.3 M 41%
- Claimed79.8 M 43%
- Certified71.9 M 39%
- Paid64.2 M 35%
- Claimed − earned
- 3.5 M
- Earned − certified (gross works)
- 4.4 M
- Certified − paid
- 7.7 M
Earned and claimed are read from one valuation at its cut-off; certified and paid are to date. Certification is never payment.
Interim payment certificates
| IPC | Valuation period | Status | Claimed | Certified | Paid |
|---|---|---|---|---|---|
| IPC-08 | 2026-10 | PMC assessment | 9.6 M | — | — |
| IPC-07 | 2026-09 | Client approval | 10.1 M | 9.4 M | — |
| IPC-06 | 2026-08 | Finance & payment | 10.4 M | 9.8 M | — |
| IPC-05 | 2026-07 | Paid | 9.9 M | 9.3 M | 9.3 M |
| IPC-04 | 2026-06 | Paid | 9.2 M | 8.7 M | 8.7 M |
Where an IPC goes
- Draft
- PMC assessment
- PM approval
- PMC certification
- Client approval
- Finance & payment
- Paid
Workflow holder
Change and variation orders
| Order | Title | Current status | Quoted / claimed | PMC assessed | Approved |
|---|---|---|---|---|---|
| VO-007Variation order (contractor) | Additional waterproofing, basement 2 | Issued — effective | 1.2 M | 1.2 M | 1.2 M |
| CO-003Change order (client) | Façade specification change | Endorsed — with the client | 2.9 M | 2.4 M | — |
| VO-009Variation order (contractor) | Revised chiller selection | Assessed by the PMC | 0.6 M | 0.6 M | — |
| VO-010Variation order (contractor) | Site access road diversion | Submitted to the PMC | 0.3 M | — | — |
Current contract value
- Original contract value
- 182.3 M
- Issued orders
- + 2.1 M
- Current contract value
- 184.5 M
- Orders in progress (no effect yet)
- 3.3 M
Only an issued order changes the BOQ and the contract value. SAR, millions.
In BuildEase todayCommercial / IPCChange ordersProgress and value over time
Illustrative data
05Change and variation orders
Changes decided through their own chain
Change and variation orders are recorded and decided by the people with that authority, and stay attached to the contract they change.
- Each change recorded with its decision and who made it
- Closing a site instruction is never the approval of a variation
- The decided change shown in the contract position
In BuildEaseProject Controls › Change Orders / VOs
Where the controls are read
The same figures feed the project dashboard, the portfolio view and the progress reports, so a director sees what the planner and the quantity surveyor recorded.