A project portfolio does not manage itself. Left alone, requests pile up, the loudest sponsor wins, teams get stretched across a dozen top priorities, and nobody can say which projects actually move the strategy. The project portfolio management process is the repeatable cycle that replaces that drift with a decision: which work gets funded, in what order, and whether it still deserves the money once it is running.
To be clear about the term, this is the process of managing a portfolio of projects, not the process of building a portfolio to show your work. It is the operating loop a project management office runs to keep an organization's investment pointed at its highest-value work.
Key takeaways
- The process runs in a continuous loop, not a one-off project. You choose the portfolio, run it, then rebalance it as strategy and capacity change.
- The seven core steps are identify, categorize, evaluate, select, prioritize, balance, and authorize, followed by ongoing monitoring and review.
- PMI groups these into two sets: an aligning process group that formulates the portfolio and a monitoring and controlling group that keeps it on track.
- The step most portfolios skip is balancing against real capacity, which is where a good ranked list turns into an achievable plan.
What is the project portfolio management process?
The project portfolio management process is a continuous, repeatable cycle for selecting, prioritizing, and governing a set of projects so they collectively deliver an organization's strategy. It moves candidate work through identification, evaluation, selection, prioritization, and balancing into an authorized portfolio, then monitors and rebalances that portfolio on a regular cadence as conditions change.
The point of running it as a defined process rather than a series of one-off approvals is comparability. When every request goes through the same intake, scoring, and gate, leadership can weigh a cost-saving automation against a new revenue play without the decision collapsing into politics.
The 7 steps of the project portfolio management process
Most practical PPM frameworks describe the same sequence under slightly different labels. Below is the seven-step version, each step feeding the next. Strategy sits above all of them: without a clear set of objectives to score against, the process ranks projects against nothing.
| # | Step | What it does | Output |
|---|---|---|---|
| 1 | Identify | Collect every candidate project and request into one list | A master inventory of candidate work |
| 2 | Categorize | Group candidates by type so like competes with like | Categories (for example run, grow, transform) |
| 3 | Evaluate | Score each candidate against agreed criteria | A comparable value and risk score per project |
| 4 | Select | Decide which candidates qualify for funding | A shortlist that passed the funding gate |
| 5 | Prioritize | Rank the shortlist against strategy and value | An ordered list of funded work |
| 6 | Balance | Draw the cut line where capacity and budget run out | A feasible, resourced portfolio |
| 7 | Authorize | Formally approve and launch the chosen portfolio | Funded, staffed, active projects |
1. Identify. Pull every project idea, request, and mandate into a single pipeline. If work can enter through five different back channels, the portfolio is never complete and the process is compromised before it starts. A disciplined project intake process is the front door that makes this step real, capturing each request through one channel with a consistent minimum of information.
2. Categorize. Sort the candidates into categories so you are not comparing a mandatory compliance fix against a speculative growth bet as if they were the same. Common buckets are run the business, grow the business, and transform the business, or by strategic goal. Categories let you set investment targets per bucket rather than letting one type of work crowd out the rest.
3. Evaluate. Score each candidate against the criteria the organization has agreed on: strategic alignment, expected value, cost and effort, risk, and urgency. The exact set matters less than agreeing on it before the project names are attached. The factors and their weights are worth treating as their own discipline, laid out in project prioritization criteria, and the fuller decision toolkit lives in project selection methods.
4. Select. Decide which candidates clear the funding gate. Selection answers a yes or no question for each project: is this worth doing at all, given its value and what it costs. Everything that passes moves to ranking; everything that fails is parked or killed, which is a healthier outcome than starting it and stopping it three months in.
5. Prioritize. Order the survivors. Selection said which projects are worth doing; prioritization says which come first when they compete for the same money and people. This is where a consistent scoring model earns its keep, and the practical method is covered in how to prioritize a project portfolio. A ranked list is only useful if it forces a real order rather than a tie for first place.
6. Balance. Draw the cut line. Starting from the top of the ranked list, commit resources until capacity and budget run out, then stop. Everything above the line is funded; everything below waits, no matter how appealing. This is the step portfolios most often skip, and skipping it is why so many organizations approve more work than they can staff. Test the ranked list against real supply in resource and capacity planning before you commit to it.
7. Authorize. Formally approve the chosen portfolio, release the funding, and launch. Authorization is a governance act, not an administrative one, which is why it belongs to a decision forum with real authority rather than a spreadsheet. The decision rights, thresholds, and gates that make authorization stick are the subject of project portfolio governance.
The two PMI process groups
The PMI Standard for Portfolio Management organizes this work into two process groups that run continuously rather than in a straight line. The aligning group formulates the portfolio; the monitoring and controlling group keeps it aligned once it is live. The seven steps above map cleanly onto them.
| Process group | What it covers | Steps it contains |
|---|---|---|
| Aligning | Formulating the portfolio: what is managed, in which categories, and how components are evaluated and chosen | Identify, categorize, evaluate, select, prioritize, balance, authorize |
| Monitoring and controlling | Keeping the live portfolio on track and aligned to strategy as conditions change | Review performance, report, and respond to strategic change |
The practical takeaway is that the process does not end at authorization. A portfolio approved in January against one strategy can be misaligned by June, so the monitoring group re-runs the aligning decisions on a defined beat.
The project portfolio management process flow
The flow is a loop, not a line. Requests enter identification, move through evaluation and selection into a ranked and balanced portfolio, get authorized, and then run. As they run, performance data flows back into monitoring, which triggers the next review, which reopens prioritization and balancing against what has actually happened. A project that has burned its budget without landing its benefit is a candidate to be paused or stopped on the next turn of the loop.
How fast the loop turns depends on the organization. Delivery status is usually reviewed monthly, while the deeper question of whether the mix is still right is a quarterly or annual portfolio review meeting. A change in strategy can trigger a full re-run at any time. Whatever the cadence, the review only produces value if it sometimes changes the portfolio, and the evidence for those changes comes from PMO reporting and the portfolio metrics that show where money and capacity are actually going.
How the PPM process differs from the project management process
Project management and portfolio management run different processes toward different questions. Project management asks "are we delivering this project right," on time, on budget, in scope. Portfolio management asks "are we doing the right projects at all," and it is willing to stop a perfectly well-run project because a better use of the same money has appeared.
| Dimension | Project management process | Portfolio management process |
|---|---|---|
| Core question | Are we delivering this project correctly? | Are we investing in the right projects? |
| Scope | A single project's scope, schedule, and budget | The whole set of projects and their balance |
| Owner | Project manager | The PMO and a portfolio governance board |
| Success | Deliverables completed as planned | Strategy advanced with the resources available |
Who owns the project portfolio management process?
Ownership is shared but not vague. The PMO runs the machinery: it owns the intake, the scoring model, the calendar of reviews, and the reporting. A portfolio governance board, made up of the senior leaders who control budget and strategy, owns the decisions the process produces, above all the authorization and the stop or continue calls. Where these roles sit in the wider operating model is covered in PMO roles and responsibilities. At the enterprise level, the same process is run by an enterprise PMO across multiple portfolios.
Common mistakes that break the process
Three failures show up again and again. The first is an incomplete pipeline: work that starts without ever passing through identification, so the portfolio you are managing is not the portfolio that actually exists. The second is prioritizing without balancing, which produces a ranked list nobody can staff and a set of projects that all move at a quarter speed. The third is a monitoring loop that only ever approves, never pauses or stops, so the portfolio grows until everything crawls. The health check is simple: a working process occasionally kills a project it once funded.
The upstream tools that make the process run are worth getting right before you worry about anything fancy: a clean intake, an agreed scoring model, a capacity view, and a governance forum with teeth. For the software that assembles the cross-portfolio picture these steps depend on, see project portfolio management software.
Frequently asked questions
What are the steps in the project portfolio management process?
The core steps are identify, categorize, evaluate, select, prioritize, balance, and authorize, followed by ongoing monitoring and review. Identification gathers every candidate project, evaluation scores them, selection and prioritization decide which get funded and in what order, balancing draws the cut line at available capacity, and authorization launches the chosen portfolio.
What are the three phases of project portfolio management?
Practitioners often summarize the process into three broad phases: planning the portfolio (define strategy, gather and evaluate candidates), authorizing and executing it (select, prioritize, balance, and launch), and monitoring and rebalancing it (review performance and respond to change). PMI expresses the same idea as two continuous process groups, aligning and monitoring and controlling.
What is the difference between project management and portfolio management?
Project management delivers a single project correctly, managing its scope, schedule, and budget. Portfolio management decides which projects to fund at all and keeps that set aligned to strategy. Project management asks whether the work is being done right; portfolio management asks whether the right work is being done, and it can stop a well-run project for a better investment.
How often should the project portfolio be reviewed?
Delivery status is usually reviewed monthly, while the deeper question of whether the portfolio mix still fits strategy is reviewed quarterly or annually, depending on the size and pace of the organization. A significant change in strategy, budget, or market conditions should trigger an off-cycle review rather than waiting for the next scheduled one.
Who is responsible for the project portfolio management process?
The PMO owns and runs the process: intake, scoring, the review calendar, and reporting. A portfolio governance board of senior leaders owns the decisions it produces, especially authorization and the choice to continue, pause, or stop funded work. The two work together, with the PMO providing the discipline and the board providing the authority.
What is a project portfolio management process flow?
A process flow is the visual sequence of the cycle: candidate work enters through intake, moves through evaluation, selection, prioritization, and balancing into an authorized portfolio, then runs while performance data feeds a monitoring loop that triggers the next review. The flow is a closed loop because review reopens prioritization and balancing against real results.