Project Portfolio Management Process: The Steps from Intake to Review

The project portfolio management process, often shortened to the PPM process, is the repeating set of decisions that determines which projects and programs an organisation funds together, in what mix, and whether each one continues. Project management delivers one piece of work to its scope, schedule and budget. Portfolio management decides whether that work should be funded at all, and instead of what.

For this page, a portfolio is the set of projects, programs and operational work competing for the same money and people in a period. A program is a group of related projects managed together. The process therefore works on requests and on components already funded, never on tasks.

The seven steps run as a loop. Review feeds the next intake cycle, which is why this is a lifecycle and not a one-off approval. Strategy alignment sets the criteria before the loop starts.

Flow: Intake → Categorise and evaluate → Select and prioritise → Balance → Authorise → Monitor and report → Review → back to Intake.

The table maps four published step lists onto the seven steps. The mapping is our reading of those lists as published in October 2026. A blank cell means the list has no matching step.

Of these four lists, only Portfolio Hub names an authorise step. Smartsheet and TheProjectGroup run on into execution and closure, which belong to project and program management.

How PMI's Standard describes the process: three editions, three structures

The structure of the portfolio management process in PMI’s Standard changed with each edition, and none of them prescribes this seven-step list from intake to review. The seven steps on this page are our grouping of the activities the Standard describes, not PMI’s own list.

• First Edition (2006) and Second Edition (2008): two process groups, Aligning and Monitoring and Controlling. A 2006 conference paper by Mathur describes the draft of the first edition. It is an IT-focused paper. It counts nine processes, seven in Aligning and two in Monitoring and Controlling. It defines the life cycle as collect, identify, categorise, evaluate, select, prioritise, balance, authorise and review.
• Third Edition (2013): three process groups, Defining, Aligning, and Authorizing and Controlling.
• Fourth Edition (November 2017): no process groups. It has a portfolio life cycle of initiation, planning, execution, optimization, and monitor and control. It also has six performance domains: strategic management, governance, capacity and capability management, stakeholder engagement, value management and risk management.

Step 1: Intake (the portfolio intake process)

Every request enters through one intake form and one register, owned by the PMO. Work that arrives any other way is not in the portfolio, whatever its sponsor says. The register puts every request on the same fields, which makes later comparison possible.

An intake form needs eight fields:

• requester and sponsor
• the problem and the outcome wanted
• the strategic objective it supports
• cost in ₹ crore
• effort in team-months
• expected benefit
• key risks
• any hard deadline, dependency or mandatory (regulatory or contractual) flag

Cut any field that would not change a decision. A form people complete honestly beats a thorough one they skip.

• Decision owner: the PMO lead.
• Decision record: a dated register entry with an ID.
• Pass test: every active component traces to a register entry. A component with none fails.

Pro Tip: Before changing anything, count the active components with no register entry. That count shows how much work reaches funding without a portfolio decision.

Step 2: Categorise and evaluate against strategy, value, risk, dependency and capacity

Sort each request into one class, then test it against five lenses. Classes keep unlike work apart. In our example they are mandatory, growth, cost or efficiency, enabler and operational, so a regulatory deadline is never scored against a growth bet.

The five lenses:

1. Strategy: which objective the request moves. Set the criteria before requests arrive; turning strategy into evaluation criteria shows how.
2. Value: the benefit in ₹ crore, with its evidence.
3. Risk: the request’s own risk plus any it shares with other components. Testing for causes that several projects share shows how to find shared risk.
4. Dependency: what must finish before the request, or alongside it.
5. Capacity: team-months needed against team-months available.

• Decision owner: the PMO lead.
• Decision record: a one-page evaluation sheet per request.
• Pass test: every request has a class and an entry on all five lenses. A blank lens fails.

Step 3: Select and prioritise

Rank the evaluated requests, then fund down the list until the budget or the capacity runs out, whichever comes first. Selection is limited by available capacity, so a request that fits the budget but not the team stays below the cut line (the point in the ranked list where funding runs out). Mandatory work is funded first.

Choose one ranking rule and apply it to every request in the same cycle. Changing the rule mid-cycle turns ranking into argument. Six prioritisation methods compared side by side helps you pick a scoring method, and a weighted scorecard for strategic initiatives shows how to rank them. A simple ordered list with a stated rule works.

• Decision owner: the PMO lead proposes.
• Decision record: the ranked list, the rule used, and the cut line.
• Pass test: the funded total sits within both the ₹ limit and the team-month limit.

Step 4: Balance the mix across risk, horizon and capacity

Check the funded list as a set, because a list that is right item by item can be wrong as a mix. Balancing tests the mix across risk (the share of spend in high-risk work), horizon (near-term against longer-term payoff), class and capacity. Balancing the mix includes capacity. Leave some team-months uncommitted, or the first change request breaks the plan.

Set the limits before the cycle starts. In the example below, growth must be at least 40% of spend and high-risk work at most 25%. The first-pass list fails the growth floor at 24%, so one swap is needed. We recommend keeping a visible capacity buffer. The example keeps 5%.

• Decision owner: the PMO lead.
• Decision record: the balance check, with each limit, the result and every swap made.
• Pass test: all limits met and the spare capacity written down.

Step 5: Authorise (who decides, and what the decision record holds)

The portfolio review board, the senior group that holds the investment decision, authorises the balanced list. Each sponsor accepts the funding conditions for their component. Authorisation is a decision with a written record, not a meeting outcome that people remember differently.

The record holds:

• the date
• each authorised component with its ₹ crore and team-months
• each deferred or declined request with the reason
• the named owner of every component
• the thresholds that trigger escalation, such as a cost variance of 10%
• the date of the next review

Setting up decision forums and decision rights is covered on its own page.

• Decision owner: the board chair.
• Decision record: the authorisation record above.
• Pass test: a person who was not in the room can read it and tell what was funded, what was refused and why.

Step 6: Monitor and report

Track a short set of portfolio-level indicators on a fixed rhythm and report exceptions, not the status of every project. Useful indicators are:

• spend against the authorised ₹ crore
• forecast cost variance per component
• capacity committed against capacity available
• components past their threshold
• any change in the strategy the portfolio serves

Project managers report component data, the PMO consolidates it, and sponsors escalate breaches. A five-question scorecard for portfolio performance shows how to design the review scorecard.

• Decision owner: the PMO lead.
• Decision record: the periodic portfolio report, with an exceptions list and the decisions requested from the board.
• Pass test: each indicator has a threshold set at authorisation. An indicator with no threshold describes but cannot trigger a decision.

Step 7: Review (the portfolio review process: continue, rebalance or stop)

At each review the board takes one decision per component, continue, rebalance or stop, and records the reason. Rebalancing moves funding, capacity or timing between components. Stopping releases funding and capacity.

Stop criteria and the evidence a project must show at each gate set out when stopping is right. Shared risks are re-examined here, using the shared-risk approach.

According to Mathur’s 2006 conference paper, the review period can run from quarterly to annual depending on size and complexity, and a change in strategy can trigger an earlier review. Each review also reopens deferred requests and sends findings back to intake.

• Decision owner: the board chair.
• Decision record: a review minute with one line per component.
• Pass test: every funded component has a decision and a reason at each review. "No change" counts only when written down.

The Project Management Office, the central team that standardises project and portfolio practice, is the natural process owner. The split below is our recommendation, and organisations assign these roles differently.

A decision sheet puts one cycle on a page. Eight requests asking for ₹83 crore are cut to five authorised components worth ₹60 crore, and each step has a check and a pass test. The figures are illustrative, not client data. The model is ours, built from the inputs below.

Assumptions (ours):

• Envelope: ₹60 crore and 400 team-months.
• Policy: mandatory work funded first, growth at least 40% of spend, high-risk work at most 25%, variance threshold 10%.
• One ranking rule gives the order A, B, C, E, F, D, G, H.

Working.

• Select: the first-pass list has growth of 14 ÷ 58 = 24%, below the 40% floor.
• Balance: removing E (₹10 crore, 60 team-months) and adding D (₹12 crore, 70 team-months) gives A, B, C, D and F. That totals ₹60 crore and 380 of 400 team-months. Growth is (14 + 12) ÷ 60 = 43.3%, cost or efficiency is 25 ÷ 60 = 41.7%, and mandatory is 9 ÷ 60 = 15%. High-risk work is 12 ÷ 60 = 20%.
• Why D and not G: swapping G in for E would leave growth at 22 ÷ 56 = 39.3%, just under the floor.

The process breaks at four points, one for each of these steps:

• Step 2: criteria are written after the requests arrive, so strategy ends up matching whatever the loudest sponsor proposed. Write the criteria before the cycle opens.
• Step 5: approval happens in a meeting with no written record, so deferred requests return unchanged next quarter. Decision rights belong with the board.
• Step 6: reports track every project's status instead of portfolio thresholds, so the board sees volume and makes no decisions. Use a short scorecard.
• Step 7: reviews only add work and never stop any, so weak components keep their funding. Agree stop criteria in advance.

In our reading, Steps 2 and 3 relate to strategic alignment, Step 5 to governance, and Steps 4, 6 and 7 to portfolio performance. The PfMP® (Portfolio Management Professional) examination is built on PMI’s Examination Content Outline, a separate PMI document from the Standard, and the exam is not built on this seven-step list. The outline version cited in Sources (copyright 2013) weights five domains: strategic alignment 25%, governance 20%, portfolio performance 25%, portfolio risk management 15%, and communications management 15%.

We have mentored and trained 6,000+ professionals. Our PfMP Self-Paced Program costs US$549 per enrolment as of October 2026, and pricing varies by program offering and market. Live versus self-paced PfMP training helps you choose a format. You can see the PfMP Self-Paced Program in our course store

Start with Steps 1 and 5. One intake register and one written authorisation record cost the least and expose every other gap. Then run last cycle’s decisions through the decision sheet, and fix the first step that has no owner or no record.

The process does not need new software or a bigger team. It needs one door for requests, one ranking rule, one written funding decision and one review that is willing to stop work. If you can show those four on paper for last cycle, the process exists.

If you are also weighing the PfMP®, this process is the working knowledge behind it. A free discovery consultation can help you choose a format and a timeline, with no commitment to enrol. You can contact our team to arrange one.