Run a portfolio review around comparable records and real exceptions.
Multi-site visibility is not a larger status meeting. It is a shared reporting rhythm that makes each project’s progress, constraints, approvals and commitments comparable.
The practical method in one minute
Define the minimum update every site must submit, use the same status and exception vocabulary, set clear daily and weekly cut-offs, and review the portfolio by deviation—not by asking every manager to retell the whole project. Keep actions with named owners and return approved decisions to the site record.
The fields worth keeping
The goal is not to collect more data. It is to preserve the context the next responsible person needs.
Comparable project identity
Use consistent site, client, manager and project-stage information.
Progress boundary
Compare against the project’s approved plan or milestone set, not an undefined percentage.
Current exceptions
Record what changed, its impact, owner and decision route.
Resource context
Include labour, materials or equipment only where they explain a constraint or priority.
Open approvals
Show pending decisions with age, owner and next action.
Client commitments
Keep due reports, decisions and promised actions visible across projects.
A practical sequence
Keep the steps visible enough that a new team member can follow the same operating rhythm.
- 1
Set the common minimum
Agree the daily and weekly records every active site must maintain.
- 2
Create a reporting rhythm
Use known cut-offs for site capture, manager review and portfolio review.
- 3
Standardise exceptions
Describe risks and blocked work with owner, impact and required decision.
- 4
Review by deviation
Start with overdue, changed or unsupported items instead of reading every update aloud.
- 5
Close the loop
Return decisions and actions to the relevant project record and confirm ownership.
A portfolio view built around exceptions
The example is illustrative. Replace it with reviewed project facts and the terms your team actually uses.
| Project | Current exception | Owner | Decision / next action |
|---|---|---|---|
| Warehouse fitout | Fire-door approval blocks two areas | Design manager | Consultant response required by 8 Aug |
| Solar rollout · Cluster 3 | Two sites missing access confirmation | Rollout lead | Escalate with client coordinator |
| Residential Block B | No active exception | Project manager | Continue planned Level 4 sequence |
Review checklist
- All sites use the same update cut-off
- Status labels have shared meanings
- Exceptions include impact and owner
- Approvals are not buried in messages
- Client commitments are visible
- Decisions return to the project record
What weakens the record
- Comparing unsupported completion percentages
- Collecting updates in a different format for every manager
- Escalating every delay without impact
- Keeping portfolio actions outside project records
- Treating missing data as ‘on track’
AI can prepare. A person must decide.
Automation can collect comparable updates and surface overdue or missing information. Managers decide priorities, resolve trade-offs and communicate commitments; the operating view supports those decisions rather than replacing them.
Use the guide, take the template or see the product.
Every link below is complete and available now.
Clarify the operating boundary.
Use the project’s authorised processes whenever contractual, legal, safety, tax or professional judgment is required.
What should every site report in the same way?
Standardise the minimum information needed for comparison: progress boundary, current exceptions, important resources, open approvals, client commitments and the next responsible action.
How do managers avoid too many status meetings?
Collect reviewed updates before the meeting and use live time for exceptions, trade-offs and decisions that require management attention.
Should every project use the same milestones?
No. Projects can keep their approved milestone structure, while portfolio reporting uses consistent definitions for status, exception, ownership and reporting cut-offs.