Managing one project is a matter of detail: a late line item, an invoice that doesn't match, a snag left open. Managing ten projects is a different problem entirely — not more detail, but a prior question that has to be answered before any detail matters: which of the ten deserves your time today? Without a fast, trustworthy answer to that question, project managers move between sites in the order they last visited them, not the order the actual risk deserves.
Key takeaways
- A portfolio view is only useful if every project's health is computed the same way — otherwise you are comparing five different opinions, not five projects.
- A project sitting exactly on budget can still be drowning in unanswered RFIs or a punch list growing faster than it closes two weeks from handover — cost health alone is an incomplete picture.
- A project with no fully priced bill of quantities still deserves a real health signal, not a false zero and not a false green.
- A red project needs a reason before it needs a response — the same colour can hide three completely different problems.
- A portfolio average is comforting and dangerous at once: one disaster and one excellent project produce a number that looks acceptable while one of them is actually on fire.
Running one project is not running ten
A single-project screen is built to answer one question in depth: exactly how is this project doing? That is correct and necessary. But an owner running ten projects is not asking that question first — they are asking which of the ten needs me today? Opening ten screens every morning is not an answer to that; it is extra work demanded before the real work even starts.
| Level | The question | What it takes to answer |
|---|---|---|
| One project | Exactly where do we stand, in what detail? | Every line, every invoice, every snag |
| A portfolio | Which one needs my attention now, and why? | One trustworthy signal per project, and a short reason behind it |
Confusing the two levels is what makes a weekly review meeting long and unproductive: every project gets presented in full detail instead of the ten being scanned together first, with detail opened only for whichever one actually needs it.
One comparable signal, not ten different reports
A health signal that earns its place on a portfolio screen has one non-negotiable condition: it has to be computed for every project by exactly the same calculation. One project measuring progress by feel, another by the bill of quantities, a third by task hours — all three produce colours that cannot be compared no matter how similar they look on screen.
The reliable method is reusing the exact same earned-value calculation used at the single-project level: planned value, earned value and actual cost produce a cost performance index and a schedule performance index for each project individually, and those two indices — not a project manager's general impression — are what get translated into green, amber or red across the whole portfolio by one standard.
Cost alongside open issues, not cost alone
A project sitting exactly on budget is not necessarily a healthy project. It could be drowning in RFIs that have gone unanswered for weeks, or a punch list growing faster than it closes two weeks before handover, or repeated safety reports with no corrective action taken — none of which shows up in a cost figure before it turns into delay or a dispute.
| Signal | What it reveals | What cost alone would hide |
|---|---|---|
| Open RFIs | A wait that is stopping work on site | A project on budget because the work itself is temporarily paused |
| Open punch-list items | A close-out heading for trouble | A handover that will slip even though cost still tracks the plan |
| Open incident reports | Risk accumulating quietly | A financially sound project heading toward a serious incident |
Reading all three together — cost, schedule, and the open-item count across these three doors — is what separates a project that is genuinely green from one that is only green on paper because nobody had gathered the three signals in one place yet.
A signal even without a fully priced BOQ
Not every project is at the same stage of maturity: some have just started and have no fully priced bill of quantities yet, some run on tasks and hours rather than measured lines, and some still rely on an estimated percent-complete a manager types in by hand. A project in any of those states does not deserve to be excluded from the board, nor shown as a false zero or a false green just because finer-grained data is missing.
The practical fix is a fallback sequence: progress is measured from executed bill-of-quantities line values where they exist, else from estimated and logged task hours, else from the manually recorded percent-complete on the project. That sequence means a missing single input never silences the whole signal — it produces a real reading from the best data actually available, instead of a false one from its absence.
Where to send attention this week
Red is the start of a question, not the end of a decision. Three projects reading red for the same reason on screen could be three entirely different problems: a genuine cost overrun, a schedule slip from a late approval, or a snag list piling up near handover with no relation to cost at all. Treating all three with the same response wastes time and leaves the real cause unaddressed.
- Start with the red projects always, regardless of the usual visiting order.
- Before any action, separate the cause: cost, schedule, a documents backlog, or safety.
- Do not manage to the portfolio average — one disaster and one excellent project produce a number that looks acceptable while one of them is actually on fire.
- Watch the amber ones weekly; that is the early warning that keeps them from turning red next week.
The numbers leadership actually asks for
Above the grid of individual projects, four numbers summarise the whole company at a glance: total project count, how many of those are genuinely active, how many workers are on site today, and total open RFIs across every project.
- Total projects versus active ones: the gap between what is signed and what is actually being built right now.
- Workers on site today: an instant mobilisation signal that doesn't wait for a week-end attendance report.
- Total open RFIs: the size of the backlog waiting on the consultant or the engineering office as a whole.
- Tasks by status across every site: where real work is actually concentrated this week.
These numbers don't replace any project's own detail, but they answer leadership's first question before any meeting: are we bigger than we can actually manage right now, and where is our workforce concentrated?
How this works in muqawil
muqawil's portfolio screen gathers every one of a company's projects in one place: total and active project counts, workers on site today, total open RFIs company-wide, and tasks by status. For each project individually, the same line you would see on its own screen: a health status computed with the same earned-value logic, budget against actual, percent complete, and the count of open RFIs, punch-list items and incidents.
And when a project has no fully priced bill of quantities, the screen falls through to task hours, then to a manually logged percent-complete, instead of showing a misleading zero — so the signal stays real even for a project still at its start. The result is that opening one screen answers 'which of my projects needs me this week' without opening ten separate ones.
Frequently asked questions
What is the difference between a single-project EVM report and a portfolio view?
A single-project report explains the full detail of one specific project. A portfolio view uses the same calculation to produce one comparable signal per project, so you know which one is worth opening in detail before you dive in.
Can a project with no fully priced bill of quantities still show a meaningful health status?
Yes. When priced BOQ lines aren't available, progress is measured from estimated and logged task hours, and failing that from a manually recorded percent-complete — giving a real reading from the best available data instead of a false zero or a false green.
Should we manage to the portfolio average or to the worst project?
Not the average. One disaster and one excellent project produce a number that looks acceptable while one of them is actually on fire. The management decision should be based on the distribution of colours across projects, not a single figure summarising them with false optimism.
How many projects justify moving from separate spreadsheets to a portfolio dashboard?
The better measure is not a headcount but a question: does anyone need to open more than one screen to know which project needs attention today? Three active sites running at once is usually enough to justify answering that with one screen instead of three.
Does a portfolio view replace the weekly per-project review meeting?
It doesn't replace it — it reorders it. The meeting starts with a look at the whole portfolio to set the discussion priority, then opens full detail only for the projects that genuinely warrant it, instead of walking every project at the same depth regardless of need.
See the health of every project on one screen
Active project counts, workers on site today, and a health status for every project computed with one consistent logic — so you know which one needs you before you open its file.