Align work packages
Map budget, orders and reports while separating shared and additional costs.
CONSTRUCTION / CAPABILITY
See cost changes
before the project closes.
Separate project budget, committed costs, payments and remaining estimates. Design reporting that relates progress to costs at a consistent work-package level.
Explore the delivery scope ↓OPERATING MODELILLUSTRATIVE
- 01Reports, orders & revisions
- 02Align projects and work types
- 03Budget, actuals & forecast
- 04Review progress and changes
Conceptual data-to-operation flow, adapted to the agreed project scope.
What makes
this workflow difficult.
Paid amounts omit open commitments, while adding orders and invoices can double count. Track costs through their lifecycle rather than summing every document.
THE SHORT ANSWER
Separate project budget, committed costs, payments and remaining estimates. Design reporting that relates progress to costs at a consistent work-package level.
DESIGN & DELIVERY
Design in the order the work happens.
Track states
Distinguish estimate, approval, order, acceptance and invoice without duplication.
Match decision cadence
Separate weekly site estimates from finalized management figures.
DATA READINESS
Required data and the conditions to check.
A consistent format does not ensure operational usefulness. Confirm meaning, refresh and exceptions with owners, and keep missing information explicit.
| Data | Required fields | Checks |
|---|---|---|
| Budget | Project, work type and approved version | Mixed budget revisions |
| Purchasing | Order ID, value and status | Partial acceptance and duplication |
| Progress | Plan, actual and reason for change | Earned progress versus elapsed time |
EVALUATION
Measure value in the workflow.
These are candidate evaluation measures. Establish a baseline and agree on data, period, targets and exclusions before work starts. They are not claimed performance results.
| Measure | Evaluation method |
|---|---|
| Reconciliation | Explain differences from accounting and registers |
| Unfinalized cost | Separate pending approval and uninvoiced commitments |
| Review time | Site and office time to reconcile the same figures |
Forecast costs depend on submitted information. Show uncertainty, owner and update date instead of presenting estimates as final.
Define deliverables
and acceptance.
Review data mappings, workflow, prototype and evaluation evidence before choosing production scope. Estimates distinguish assumptions because permissions and interface terms affect implementation.
Choose one document type or one cost work package within a project.
QUESTIONS BEFORE YOU START
Questions before starting
Can we start without BIM?
Yes, using registers, reports, spreadsheets and PDFs. Model integration requires a separate scope and data-access review.
Can an active project adopt this?
Start with read-only reporting after assessing disruption; preserve agreed submission and approval procedures.
RELATED FIELD GUIDE
CONSTRUCTION / GUIDE
Avoiding double counting in project cost reporting
Before moving a project register into a dashboard, distinguish commitments, payments, additional scope and budget revisions. Build figures that sites and head office can reconcile.
Read the guide ↗YOUR OPERATION / OUR STARTING POINT
Start with the work you do today.
Tell us about the workflow, systems and reporting or documents that need attention. We will define a suitable phase, deliverables and assumptions.
Construction and installation — discuss your project How scope and estimates work ↗