Portfolioproject controls
One job a little behind is a portfolio problem.
Every project has its own controls. The book has almost none. A job that is a few weeks behind reads as manageable on its own report, and only when every project is rolled up into one view does it become clear that this one job is the reason the whole portfolio is behind, and that the money and people to fix it are sitting on the jobs next to it.
What portfolio project controls means
Portfolio project controls rolls every active project up into one view, so cost, schedule, and risk are read across the whole book instead of one contract at a time. Each job keeps its own baseline. The portfolio layer blends the results, weights them by size, and shows which projects are moving the total.
The term borrows from the Project Management Institute, whose Standard for Portfolio Management treats a portfolio as the set of projects and programs an organization manages as a group to meet its strategic objectives. In construction the strategic objective is usually blunter: finish the book at the margin you bid it, with the people and cash you actually have.
That makes the portfolio the level where allocation happens. A project manager can resequence crews inside a job. Only someone reading the whole book can move a crew, a piece of equipment, or a slice of contingency from one job to another, and they can only do it well if the roll-up tells them where the drag is.
One job vs the book
The two views are built from the same source data and answer different questions. Neither replaces the other. The failure is running a company on the first one alone.
| Project-by-project view | Portfolio roll-up | |
|---|---|---|
| What it reveals | This job against its own baseline: its CPI, SPI, EAC, and float | Which project is pulling the blended numbers, and by how much |
| What it hides | That a modest slip here is the largest slip on the books | The line-item detail behind each score; that stays on the project |
| The unit of variance | Dollars and days on one contract | Concentration: how much of the book is riding on the weakest job |
| Who reads it | The project manager and the field team | The owner, the executive, the controls lead who allocates |
| What it lets you move | Crews and sequence inside the job | Money, people, and equipment between jobs |
Why a slipping job reads fine on its own
A project report compares the job with its own plan, and inside one contract a gap between percent complete and time elapsed always looks recoverable. The PM has a plan for it. The narrative says the next two months are heavy on installed quantity. Nothing on the page says how large this gap is relative to every other gap the company is carrying.
The roll-up asks a different question: of everything we are behind on, where is most of it? When the answer is one job, the recovery plan stops being that PM's problem and becomes an allocation decision. The crew that could close the gap is on another site. The contingency that could fund acceleration is on another budget. Those moves are invisible from inside the project and obvious from above it.
This is also why the roll-up has to be weighted. Six jobs averaged as equals will tell you the book is a little behind. Six jobs weighted by what each one is worth will tell you that the book is behind because of one of them.
A worked example
Take an illustrative book of six projects worth $128M in total. Scored on schedule, cost, and safety, three read green, two amber, and one red, and the simple average health is 74. Weighted by contract value the same book scores about 73, a first hint that the weak project is not a small one.
The red project is Millbrook Water Plant: 33 percent complete with 54 percent of its time gone, a health score of 41, and $22M of contract, about 17 percent of the book. Its own monthly report calls the 21-point gap recoverable. Read alone, that is a defensible sentence.
Rolled up, the book is 51 percent complete against 56 percent of its time elapsed, five points behind overall. Take Millbrook out and the remaining $106M reads 55 percent complete against 56 percent of time, essentially on plan. One project is carrying most of the portfolio's slip, and it is one of the largest contracts on the books. That is not a PM's recovery plan. That is a decision about where the next crew and the next dollar of contingency go.
The roll-up
Six bars, one per project, sized to health and colored by band. Each one pours into the single portfolio bar on the right, which settles at the blended 74 over $128M of contract. The ring marks Millbrook: the shortest bar, the one the book cannot afford to average away.
Where the money and people move
A roll-up earns its place by changing decisions, and the decisions it changes are about allocation. With the drag named, the questions become concrete. Cedar Grove is 80 percent complete with 77 percent of its time gone and a health of 91; which of its crews can be released early toward Millbrook? Vale is small and healthy; is any of its unspent contingency better deployed on the water plant than held against a job that is nearly done?
The book also surfaces patterns a single job cannot. If the same mechanical subcontractor is on Millbrook and North Line, and both are amber or worse, the problem may be the sub, not the site. If overtime is concentrated on one project while another is short of crew, the fix is a transfer, not a hiring plan.
None of this is available from six separate reports, however good each one is. It only appears when they are read together, weighted by what each job is worth, and refreshed often enough that the move can still be made.
Progress against time elapsed for every project in the book, with each bubble sized to contract value and colored by health. On-plan jobs sit on the diagonal. Millbrook is the large red bubble well below it: a lot of contract, a long way behind.
Portfolio Health Map
POD- The diagonal. A project whose percent complete matches its time elapsed sits on the dashed line. Above it is ahead; below it is behind.
- Bubble size. Contract value. A small bubble below the line is a project problem. A large one is a portfolio problem.
- Color. On this map, green is 80 and above, amber 60 to 79, red under 60.
- The drag. Millbrook Water Plant: 33 percent done at 54 percent of time, health 41, $22M of the $128M book.
Four ways a roll-up lies
A simple average treats a $6M job and a $34M job as equals. Weight each project by its contract value and the blended health drops from 74 to about 73 here, because the weakest job is also one of the largest. The weighting is what makes the drag visible.
If the portfolio view is built from each PM's one-line status rather than from the schedule, cost, and safety data each job actually produced, it inherits every optimistic sentence. The roll-up has to read the same source data the project reads.
A project that has not reported cost or schedule figures is not healthy; it is unmeasured. Treating a missing signal as a passing score quietly lifts the blend and hides the job you know least about.
A monthly executive deck is a roll-up, but it arrives after the period it describes. By the time Millbrook shows red in the deck, the money that could have moved toward it has already been committed elsewhere.
A monthly deck vs a live book
Most companies already have a portfolio view. It is a slide, assembled by hand from six status emails, and it is right about the month that just ended. The difference that matters is whether the roll-up is built from the same source data the projects run on, and whether it is current enough to act on.
- ·Each PM writes a status line; someone pastes six of them into a deck
- ·Projects are averaged as equals, whatever they are worth
- ·A job with no cost data yet is quietly shown as fine
- ·The drag becomes visible one reporting cycle after it started
- ·POD reads the schedule, cost, and safety data each project already produces
- ·Progress and cost blend with each project weighted by its contract value
- ·A project with no reported signal is marked unmeasured, not scored healthy
- ·Total value, the at-risk count, and a portfolio health score stay current
POD rolls every active project in your organization up into one portfolio view. Each project's health is scored from the schedule, cost, and safety signals it actually reported, progress and cost are blended with each project weighted by its contract value, and total portfolio value, the at-risk count, and a portfolio-level health score sit at the top of the page. A portfolio brief reads across the projects for the patterns no single job can show, such as the same subcontractor producing at very different rates on two jobs. The roll-up rests on the per-project figures covered in earned value management and the estimate at completion; the book is only as honest as the jobs feeding it.
The project controls library
The pillar guide: the full controls stack from schedule of values to earned value, one job at a time.
The CPI and SPI each project reports are the raw signals a portfolio health score is built from.
Sum the EACs across the book and you have the first honest number for where the portfolio lands.
Portfolio controls questions
What is portfolio project controls in construction?▾
Portfolio project controls is the practice of rolling every active project up into one view so cost, schedule, and risk can be read across the whole book rather than one contract at a time. Each project keeps its own baseline and its own controls; the portfolio layer blends their results, weights them by size, and shows which projects are moving the total, so money, people, and equipment can be allocated between jobs on evidence.
How is portfolio controls different from program management?▾
A program is a set of related projects managed together because they share an outcome, such as the phases of one campus. A portfolio is every project an organization is carrying, related or not, managed as a group so that priorities and capacity can be balanced across them. Portfolio controls is the measurement side of that: the roll-up of health, progress, and cost that the allocation decisions rest on.
Why does a slipping project look fine at the project level?▾
Because the project view only compares the job with its own baseline, and a 21-point gap between percent complete and time elapsed can still read as recoverable inside one contract. The same gap read across the book is different: if that job is also one of the largest, its slip is the single biggest drag on the blended progress, and the recovery it needs competes with every other job for the same people and cash.
How should projects be weighted in a portfolio roll-up?▾
By contract value, or by remaining cost where that is available. A simple average lets a small job count as much as a large one and understates the effect of a big project in trouble. Weighting by value makes the blended progress and health reflect where the money actually sits, which is the question a portfolio view exists to answer.
What should a portfolio roll-up show?▾
At minimum: total contract value, blended progress and health weighted by size, a count of projects by health band, and a clear view of which projects are pulling the blend down. Beyond that, the useful additions are cross-project patterns a single job cannot see: a subcontractor slipping on two sites at once, or overtime concentrated on one job while another is short of crew.
How does POD roll projects up into a portfolio?▾
POD reads the schedule, cost, and safety data each project already produces, scores each project's health from the signals it actually reported, and blends progress and cost across the organization with each project weighted by its contract value. The portfolio view shows total value, the at-risk count, and a portfolio-level health score, and a portfolio brief reads across the projects for patterns no single job can show. A project that has reported no cost, schedule, or safety signal is marked unmeasured rather than scored as healthy.
POD reads the whole book, not one job
Put every active project into POD and the roll-up builds itself from the schedule, cost, and safety data each job already produces. The projects pulling the book down show by name on the health map, each weighted by what it is worth.