The project portfolio management process is the six-step cycle a PMO follows to turn a new idea into a funded, tracked, and eventually reviewed piece of delivery work: capture, evaluate, approve, group, track, and review. Each step exists to answer a specific question before work moves to the next stage, and skipping any one of them is usually where portfolio drift starts.
Most PMOs run some version of this cycle informally, whether or not they call it a process. The difference between an informal version and a disciplined one usually shows up months later, in a portfolio nobody can fully explain to a board. This guide walks through each of the six steps in detail: what it requires, who owns it, what commonly goes wrong, and how to know it's working.
Step 1: Capture
What it does. Every new idea, initiative, or opportunity enters a structured intake process before it consumes any budget or resource, rather than starting life as an informal request that quietly becomes a project.
What it requires. A single place to log candidate ideas, a minimum set of fields (name, description, type, submitter, rough scale), and a rule that nothing skips this step, regardless of who is asking for it or how senior they are.
Typical owner. PMO Manager or Portfolio Manager, though anyone in the organisation should be able to submit an idea into the pipeline.
Where this step commonly breaks down. Senior stakeholders route around the intake process because they assume their idea is obviously worth doing. Every exception made here weakens the gate for everyone else, and it is usually how portfolio bloat starts.
How to know it's working. Every active project in the portfolio can be traced back to a captured idea with a submission date, a submitter, and a stated rationale. If a project exists with no origin record, the capture step was skipped for it.
Step 2: Evaluate
What it does. Each captured idea is assessed against current strategic objectives, not against how good it sounds in isolation, to determine whether it deserves to compete for funding at all.
What it requires. A scoring framework that weighs strategic fit alongside cost, effort, and risk, and a defined set of objectives to evaluate against. Without a current objectives list, evaluation collapses into a subjective judgement call made under pressure.
Typical owner. PMO Manager, often supported by whoever owns the relevant strategic objective the idea claims to support.
Where this step commonly breaks down. Evaluation happens once, informally, in a meeting, with no recorded score, so there is no way to compare ideas consistently or explain later why one was prioritised over another.
How to know it's working. Every idea that reaches a decision has a recorded score against strategic fit, not just a verbal agreement in a meeting that nobody wrote down.
Step 3: Approve or reject
What it does. This is the gate. Based on the evaluation, an idea moves to Approved, Rejected, or is sent back to Draft for more information, before it becomes a funded, resourced project.
What it requires. A clear decision-maker or approval body, a defined turnaround time for a decision, and a consistent threshold for what counts as strong enough strategic fit to proceed.
Typical owner. Portfolio Manager or a nominated governance board, depending on the organisation's PMO model.
Where this step commonly breaks down. The gate exists on paper but functions as a formality, with almost every submitted idea eventually approved regardless of score. A gate that approves everything is not prioritising, it is rubber-stamping with extra paperwork.
How to know it's working. A meaningful proportion of submitted ideas are rejected or sent back for revision. If the approval rate sits near 100% over time, the evaluation step is not actually filtering anything.
Step 4: Group
What it does. Approved ideas are assigned to a programme and a portfolio aligned to the strategic objective they support, so the new project inherits strategic context rather than existing as a standalone entry on a list.
What it requires. An existing portfolio and programme structure to assign into, or a decision to create a new one if nothing currently fits. A project with no portfolio or programme home is a project with no clear line back to strategy.
Typical owner. Portfolio Manager, in coordination with the relevant Programme Manager if one exists.
Where this step commonly breaks down. New projects get created without being assigned to an existing portfolio or programme, either because the process is skipped under time pressure or because no obviously fitting portfolio exists yet, and the gap never gets resolved later.
How to know it's working. Every active project sits inside a portfolio and, where relevant, a programme, with no orphaned projects existing outside the structure.
Step 5: Track
What it does. Once work begins, delivery status, budget, resource allocation, and RAG status are monitored continuously at both the project and portfolio level, not just within isolated project reports.
What it requires. A consistent reporting cadence, defined RAG thresholds applied uniformly across the portfolio, and a way to aggregate project-level status up to the portfolio and organisation level without manual reassembly each time.
Typical owner. Project Managers report status; PMO Manager and Portfolio Manager monitor the aggregated view.
Where this step commonly breaks down. Tracking happens at project level only, with no portfolio-level roll-up, so a PMO can answer "is this project on track" but not "is this portfolio, taken as a whole, still healthy" without manually compiling the answer before each review.
How to know it's working. A PMO Manager can pull an accurate, current portfolio-level RAG and budget status at any point, not just on the day a report happens to be due.
Step 6: Review and rebalance
What it does. Portfolios are periodically reviewed against current strategy, and projects that have drifted from the objective they were funded to support get flagged, defunded, or stopped, rather than continuing on momentum alone.
What it requires. A fixed review cadence, typically quarterly, and the willingness to actually stop or defund a project that no longer earns its place, not just note the drift and move on.
Typical owner. PMO Manager and Portfolio Manager, with sign-off from the relevant Operational Director or C-suite sponsor for any project that gets stopped.
Where this step commonly breaks down. This is the step most PMOs skip entirely, or perform without genuine willingness to kill anything. A review that never results in a stopped or defunded project is not really reviewing, it is confirming what was already decided months ago.
How to know it's working. At least some proportion of reviewed projects are genuinely stopped, paused, or redirected as a result of the review, not just re-approved by default because stopping something feels harder than continuing it.
The process as a cycle, not a line
These six steps are usually drawn as a straight line, capture through to review, but the more accurate picture is a loop. Step six feeds back into step one: a defunded project frees resource and budget that becomes available for the next round of captured ideas, and a drifted objective identified in review becomes the trigger for re-evaluating everything grouped under it.
A PPM process that only runs forward, never looping back through review, tends to accumulate work over time without ever shedding any. This is how portfolios grow steadily heavier every year without becoming any more strategically focused, and it is usually the single biggest gap between an organisation that says it does PPM and one that actually does.
Common mistakes across the whole process
Running steps out of order. Grouping a project into a portfolio before it has been properly evaluated, because the requester is senior or the deadline is tight, undermines every step that follows it.
No feedback loop from step six back to step one. Review findings that never inform future evaluation criteria mean the same kind of low-alignment idea keeps getting approved every cycle.
Inconsistent ownership across steps. If capture, evaluation, and review are owned by three different people with no shared view of the data, each step effectively runs in isolation, and nobody can see the whole cycle end to end.
How software supports the PPM process
Each step in this process depends on data created in the step before it. A platform that supports the full cycle should let that data flow forward automatically rather than requiring manual re-entry at each stage.
A structured ideas pipeline covers capture and evaluation, letting ideas be scored against strategic fit and moved through Draft, Under Review, Approved, and Rejected status without leaving a spreadsheet trail behind.
Portfolio and programme structures with inheritance cover the grouping step, so an approved idea becomes a project that automatically carries its portfolio and programme's strategic context.
Portfolio-level RAG and budget aggregation covers tracking, rolling project status up without manual reassembly.
Objective and KPI health reporting supports the review step, showing which portfolios have drifted from their linked objectives and are due a rebalancing conversation.
Project Director's Ideas and Opportunities module covers capture and evaluation directly, with status tracking through the gate and alignment scoring against portfolio objectives. Once approved, ideas become projects that inherit their programme and portfolio's context automatically, and the Home dashboard aggregates RAG, budget, and objective health across the organisation, giving a PMO the data it needs for the review step without rebuilding the picture by hand each quarter.
Frequently asked questions
How long does a full PPM cycle take? Capture and evaluation can happen continuously, as ideas arrive. The review and rebalance step is typically run on a fixed cadence, most commonly quarterly, so the full loop, from a new idea through to a portfolio-level review that might affect it, usually plays out over one quarter at minimum.
Which step in the PPM process do most PMOs skip? Review and rebalance is the most commonly skipped or weakened step. Capture, evaluate, and track tend to get built out first because they are more visible day to day, while a genuine willingness to stop funded work is harder to institutionalise.
Does every organisation need all six steps? Smaller organisations running a handful of projects can often combine steps informally, for example handling capture and evaluation in the same conversation. The full six-step discipline becomes more valuable as the number of concurrent ideas and projects grows past what one person can track from memory.
What is the difference between the PPM process and a project lifecycle? A project lifecycle (initiation, planning, execution, closure) describes how a single project is delivered once approved. The PPM process operates one level above that, deciding which projects get to exist in the first place and reviewing whether they should continue to.
The practical takeaway
The project portfolio management process only works as a loop. Capture and evaluation decide what gets funded, grouping and tracking manage it while it runs, and review and rebalance decide what keeps running and what gets stopped, feeding straight back into the next round of decisions. Skip the last step, and the other five just get better at building a portfolio that never gets any lighter.
See whether your portfolio still matches your strategy. Start your 14-day free trial, no credit card required.
