What is project portfolio management?

Project portfolio management is the practice of choosing which projects an organization funds, staffing them against the capacity it actually has, and governing them as one connected set rather than as separate efforts. It answers a different question from project management. A project manager asks whether the work is on track; portfolio management asks whether it should still be running at all.

Most organizations do not fail at portfolio management because they lack a tool. They fail because more work is approved than can be staffed, nothing is ever formally stopped, and the same scarce specialists appear in a dozen plans that were each built as if the others did not exist. The articles below are written to fix those specific problems, in the order the work usually runs.

The portfolio cycle, and where each stage is covered

A working portfolio moves through the same six stages every year, whatever the framework is called. Each stage answers one question, and each has a starting point here.

StageThe question it settlesWhere to start
IntakeHow does a request become a candidate rather than a rumor?Project intake process
PrioritizationWhich candidates get funded, and in what order?How to prioritize a portfolio
CapacityCan we actually staff what we just approved?Resource and capacity planning
GovernanceWho decides, at what threshold, and how does work get stopped?Project portfolio governance
ReportingWhat does the board need to see, and how often?PMO reporting and dashboards
BenefitsDid the investment return what the business case promised?Benefits realization management

The stage that breaks first is almost always capacity, and it breaks quietly. Approval and staffing are usually separate meetings, so a portfolio can approve a year of work in one room without anyone in that room holding the number for how much delivery capacity exists. If you only tighten one stage, tighten that one.

The artifacts a portfolio actually runs on

Portfolio management happens through a small number of documents that carry decisions. Each one exists to settle something specific, and a portfolio missing one of them tends to argue about the same thing repeatedly.

ArtifactWhat it decidesGuide
Intake formWhat a requester must supply before anyone reviews itProject intake form
Business caseWhether the investment is worth making, and on what assumptionsBusiness case template
Scoring modelHow competing requests are ranked without the loudest voice winningProject scoring model
Capacity planWhether the approved list fits the people availableCapacity planning template
Stage gate packWhether an initiative continues, pauses, or stopsStage gate review template
RAID logWhat could go wrong, what already has, and who owns itRAID log template
Portfolio dashboardWhat the current state of every initiative is, in one viewProject portfolio dashboard
Status reportWhat changed since the last cycle and what needs a decisionPortfolio status report

If you are standing up a portfolio function from nothing, the useful order is intake, then scoring, then capacity. Governance and reporting are easier to build once there is a real list of work to govern, and a dashboard built before the intake is fixed just displays the confusion faster.

Who this is written for

Portfolio Hub is written for the people who run the work rather than the people who write about it: PMO leads standing up a function, portfolio and program managers deciding what to stop, resource managers trying to make a plan match the team, and executives who want a portfolio review that produces decisions instead of a status parade. Every guide is meant to be usable the same week you read it.

A reasonable starting sequence is what a PMO is and does, then how to prioritize a portfolio, then how to run the portfolio review meeting where those decisions get made. If your problem is that nothing ever stops, start instead with the project cancellation checklist.

Last updated September 2026.