Portfolio approval is the decision that an initiative may consume capacity. Not that it is a good idea, not that it is funded in principle, and not that it belongs on a list of things the organization cares about. Approval is the point at which specific people become unavailable for other work. It is made in the Align practice, after candidates have been scored and ranked, and it is the last decision before an initiative moves into planning.
What does a real approval name?
A real approval names which teams, for how long, and what was deferred to make room. Approvals go wrong when they stop at the first clause. Leadership approves a list, capacity is never actually reserved, and the approved work competes the following week with whatever arrives next, on equal footing, because nothing about the approval was specific enough to defend.
An approval that holds up ties the initiative to one measurable objective, names the teams (and the scarce people) it takes for the length of the stability window, lists what was deferred to make room, and records one approver holding the decision right, with the date and the reason. The deferral is the part organizations skip, and it is the part that makes an approval a decision rather than an agreement. Written that way, an approval is checkable six months later, which is the only test that matters.
How does portfolio approval work?
Approval is the fourth step in a sequence, and it is weak whenever one of the first three is missing. Objectives are set, candidates are scored against a weighted scoring rubric, candidates are ranked, and then the line is drawn where WIP limits and real capacity say it falls. Everything above the line is approved. Everything below it is sequenced with a date.
The line is what makes the approval mean something. Approving above the line is a decision about the whole portfolio, because it says what the organization is now unable to do. Approving without a line is an endorsement, and an endorsement costs nothing, which is why organizations that approve this way end up with more approved work than they can staff and a delivery function that looks like it is underperforming.
Approval is also the natural place for the second half of the decision, the agreement to protect what was assigned. That half is portfolio commitment, and it is a separate act with a separate failure mode.
What does a good portfolio approval look like?
A good approval meeting has the ranked list and a current capacity view on the table at the same time, and it draws the line before anyone argues for a particular candidate. Every approval states what it displaces. Every deferral carries the date it will next be considered, because a deferral with a date is a decision and a deferral without one is a rejection people will keep relitigating. Overrides of the ranking happen, and they are recorded with the reason. The result is published in both halves: what was approved and what was not.
A common way an approval fails is that it assigns a number of people rather than particular people. The number exists across the organization. The particular people are already on three other things, and nobody finds out until the plan is built. If the capacity cannot be named, the initiative is not ready to be approved; it is ready to be planned in more detail.
Here is what that protects. Say a utility's portfolio forum approves an outage communication replacement and records the named integration engineer it takes. In week six, when another business unit asks for the same engineer, the conversation starts from a recorded assignment rather than from two people's recollections.
What are the common mistakes?
Approving a list rather than a set of decisions. A list approves everything at once, which means the trade-offs between items were never made. Approve items individually against a capacity position that decreases as you go.
Approving at the business case, then again at the plan, then again at the funding gate. Multiple approval points with no clear final one produce work that starts before the real decision and stops after it. Name the one approval that allows capacity to be consumed.
Leaving the deferral list unwritten. If nobody records what did not get approved, the portfolio has no memory, and next cycle's intake arrives as if the question had never been asked.
Approving without the sponsor of the displaced work present. The displacement will be discovered later, and it will be reversed informally.
Approving work that has no named objective. An initiative approved on narrative alone cannot later be evaluated or stopped, because there is nothing to measure it against.
Treating carry-over as pre-approved. Work already in flight consumes the same capacity as new work. If it is not re-approved against the current ranking, the portfolio is really deciding only at the margin.
Portfolio approval vs funding approval
A funding approval releases money. A portfolio approval releases people. In organizations where those two decisions are made by different bodies on different cycles, which is common, the gap between them is where portfolios break down.
Money and capacity are not interchangeable at the speed a portfolio moves. Funding an initiative does not create the integration engineer it needs, and in a specialist-constrained portfolio the binding constraint is usually the people rather than the budget. That is why a funded initiative can sit for two quarters without progress while everyone points at the approved budget line as evidence that it was prioritized.
Keep the two decisions connected but distinct. Funding should follow the ranking rather than precede it, and a portfolio approval should be granted only when the capacity it names is actually available in the period it names. Where the funding cycle is annual and the portfolio cadence is shorter, the practical fix is to fund at the objective level and let the portfolio approval allocate capacity to initiatives inside it.
For the rest of the vocabulary, see the glossary of agile portfolio management terms. A PPM4Agile implementation sets up the approval record and the decision point that produces it. If you are not sure how your current portfolio was approved, a 60-minute Portfolio Clarity Session is a place to start.