Key takeaways
- The Question: How do owners and contractors manage many construction projects at once, so leadership sees problems early and puts people and money where they are most needed?
- The Answer: Portfolio management depends on a common standard: the same metrics, definitions, cut-off dates and capture methods on every site. On that base, a dashboard with numeric thresholds shows which projects need attention, a regular review routine turns that into decisions, and shared resources move to where the evidence says they matter most.
- The YelloSKYE Angle: Construct IQ records each site to one capture specification, from drone flights to 360° routes and fixed-camera views, and gathers the results in a single DEX dashboard, so projects can be compared on the same footing and checked without travelling.
Construction portfolio management is the practice of overseeing several projects as one set: comparing them on common measures, spotting the ones that need attention, deciding where scarce people, plant and money should go, and carrying lessons from one project into the next. It matters for any organisation running more than a handful of sites, whether that is an owner delivering a programme of buildings or a contractor managing a region.
The hard part is not the dashboard. It is making the information from each project comparable and trustworthy, so that a status on the screen means the same thing for every site. This guide covers how to set that standard, how to report by exception, what a control room adds, how to share resources between projects and how the task differs for owners and contractors. It also shows where Construct IQ supplies the common site record underneath.
Project management and portfolio management
The two disciplines use similar data for different purposes.
| Project management | Portfolio management | |
|---|---|---|
| Main question | How do we deliver this project? | Which projects need help, and what should we do about it? |
| Time horizon | This project's programme | Several years of current and future work |
| Typical owner | Project manager | Programme director, regional or executive leadership |
| Key decisions | Sequencing, resourcing within the job, contractor instructions | Priorities, shared resources, escalation, standards, bidding or investment |
| Information needed | Full detail for one site | A small set of comparable measures for every site, with the detail on request |
| Main risk | Missing a problem on the job | Seeing it too late, or acting on the wrong project |
Portfolio management does not replace project management. It relies on it, because every portfolio measure is built from figures each project team reports.
Building a common standard across sites
Most portfolio reporting fails at this step. When five project managers each report in their own format, leadership spends its time translating rather than deciding, and differences between projects reflect reporting habits as much as performance.
Common definitions
Agree, in writing, how each measure is calculated: what counts as complete, how percent complete is derived, what each milestone means and how forecast dates are set. Without that, one site's "80 per cent" is another's "60 per cent".
Common cut-off dates
Every project should report position at the same date each period. A portfolio view that mixes figures from the 15th on one site and the 30th on another compares different moments.
Common capture
Use the same capture methods and cadence on comparable work: the same drone flight pattern for structure and external works, the same 360° routes for interiors and fixed cameras at agreed milestones. Owners can write these requirements into contracts so every contractor follows them; our guide to reality capture standards for owners explains how.
A small core set of measures
Keep the portfolio set short. Each project will track much more, but leadership should see only what it compares and acts on.
| Area | Portfolio measure | Why it travels well |
|---|---|---|
| Schedule | Movement in forecast completion since last period | Shows direction, regardless of project size |
| Progress | Planned against actual progress, verified against site evidence | Comparable when definitions are shared |
| Cost | Forecast final cost against budget, as a percentage | Scales across project values |
| Change | Value of unagreed change as a share of contract value | Flags commercial exposure early |
| Risk | Number of high-rated risks and their trend | Shows whether risk is being reduced |
| Safety and quality | Recordable incidents and open non-conformances | Consistent definitions already exist in most firms |
Portfolio dashboards and exception reporting
A portfolio dashboard is a single view with one tile or row per project. Its job is to answer one question quickly: which projects need leadership attention this week?
Status by rule, not by judgement
Every status should come from numeric thresholds agreed in advance. A project turns amber or red because a measure crossed a line, not because someone felt uneasy. This removes the common pattern where projects stay green in every report until the month they are suddenly in trouble.
| Measure | Amber (illustrative) | Red (illustrative) |
|---|---|---|
| Forecast completion movement | Slipped in two consecutive periods | Beyond the contract date or a set number of weeks |
| Forecast cost | Above budget, within contingency | Contingency exhausted |
| Planned vs actual progress | Behind on a critical-path activity | Behind for two periods on the same activity |
| Unagreed change | Above an agreed share of contract value | Rising for three periods |
Thresholds will differ by organisation and project type; the point is that they are written down before the first report.
Management by exception
Leadership time goes to the projects that cross a threshold. Projects within tolerance get a short note and no meeting. This only works if the thresholds are trusted, which in turn depends on the common standard above.
Commentary from the project team
Numbers need context. A short note from each project manager every period, explaining the movement and the action being taken, tells leadership whether the team has the problem in hand. The note should explain the data, not replace it.
Drill-down to evidence
When a project is flagged, the reader should be able to open the detail behind it: the activities behind the delay, and dated site captures showing the actual condition. In our portfolio monitoring use case, a leadership team gets through a review of over ten sites in half an hour, since every tile opens onto a visual record built the same way.
The control room idea
Industries such as power generation, process plants and air traffic have long used control rooms: a place where live information on many operations is watched and acted on by people with clear authority. Applied to construction, the control room is less about screens and more about routine.
A construction control room, whether a physical room or a shared virtual space, needs four things to work:
- Current, trusted data from every site, captured to the common standard, so the room is not debating whose numbers are right.
- A fixed rhythm, such as a short weekly portfolio review and a longer monthly one, with an agenda driven by the exceptions on the dashboard.
- Clear decision rights. Who can move a crane, reassign a project manager or release contingency, and how quickly?
- Recorded actions. Every review ends with named owners and dates, and the next review starts by checking them.
The common failure is a room full of displays that nobody acts on. If the data is not trusted, or nobody in the room can make decisions, the control room becomes another meeting.
Fixed cameras help here because they show activity between scheduled captures. Our fixed-camera monitoring use case covers continuous records of critical zones, which let a central team see whether a stalled area has restarted without waiting for the next site visit.
Allocating people and plant between projects
Shared resources are where portfolio decisions have the most direct effect. Tower cranes, formwork systems, specialist supervisors, commissioning engineers and experienced project managers are all limited, and moving them is expensive.
Decide on evidence, not on volume
Resources tend to go to whichever project manager argues hardest. A shared view of verified progress across sites shows where work is genuinely held up and where a project is simply reporting loudly.
Set priority rules
Agree in advance how conflicts are resolved. Typical rules give priority to work on the critical path, to contracts with liquidated damages or fixed handover dates, and to activities where a short delay causes a long one later.
Plan the moves ahead
Plant and people are easier to move when the move is planned weeks ahead. A portfolio look-ahead, built from each project's forecast, shows when a crane or a commissioning team will be released by one site and needed by another.
Watch for systemic problems
When several sites report the same delay, such as a late supplier or a shortage of one trade, the answer is usually at portfolio level rather than on any single site. Common capture and definitions make these patterns visible.
Owner and contractor perspectives
Owners and contractors both run portfolios, but they ask different questions of them.
| Owner or developer | Contractor | |
|---|---|---|
| Main concern | Delivery dates, capital deployed, quality of the finished asset | Margin, cash, utilisation of people and plant |
| Portfolio made up of | Its own projects, often with several different contractors | Contracts for many clients, often of different types |
| Main standardisation lever | Contract requirements for reporting and capture | Internal procedures across regions |
| Key use of the data | Comparing contractors, approving payments, reporting to investors and lenders | Allocating resources, protecting margin, bidding |
| Learning across projects | Better design standards and contractor selection | Better estimates and productivity rates |
Owners with repeated programmes
Owners building similar facilities repeatedly, such as warehouses, data centres or retail stores, gain the most from portfolio management. With the same design and the same capture standard, each project becomes a benchmark for the next. Durations, sequences and recurring defects can be compared directly, and design standards improved between rounds.
Contractors across regions
For contractors, the portfolio is also a margin question. A consistent view of every job shows early which contracts are drifting, which teams consistently deliver and where productivity assumptions in estimates are proving wrong.
Where YelloSKYE fits
Construct IQ supplies the shared site record that lets a portfolio be compared fairly. Drone flights, 360° walks and fixed cameras follow one specification on every project, and laser scans are added where exact geometry matters. DEX holds all of it, indexed by site, date and position, and reports stage-wise completion and lag against plan for the whole portfolio on one screen.
Because every project is recorded the same way, leadership can open any flagged site and see its actual condition without travelling, and compare it with others on the same basis. The same approach works at site level: site managers on the project in our aerial progress capture use case each recovered upwards of 15 hours a week once drones flew the site weekly. Through APIs and standard files, the progress figures also flow on into MS Project, Procore or Autodesk Construction Cloud, so the portfolio view sits alongside the systems teams already run.
Getting started: a 60-day checklist
- Choose five or six portfolio measures and write down how each is calculated.
- Set one cut-off date for every project's reporting each period.
- Define amber and red thresholds for each measure before the first report.
- Agree a common capture method and cadence for comparable work, and add it to new contracts.
- Build the dashboard with one tile per project and a link to the evidence behind each.
- Start a weekly exception review with named decision makers and recorded actions.
- Agree priority rules for shared cranes, systems and specialist staff.
- After three periods, review which measures led to decisions and drop the ones that did not.
