Can every good capital project belong in the portfolio?

Can Every Good Capital Project Belong in the Portfolio?

Projects that each clear a hurdle rate can still form a portfolio that cannot be delivered. They may require the same engineers, shutdown window, supplier, data migration or cash trough; benefits may overlap; one project may make another obsolete. Individual approval ignores the system in which commitments must coexist.

Map projects to strategic outcomes and binding resources. Build an integrated calendar of capital, talent, operational downtime, permits and dependencies, using ranges rather than sponsor dates. Identify benefits counted by more than one proposal and costs that appear only when projects interact. The portfolio�s feasible frontier is set by its scarcest shared constraint.

Sequence matters. A foundation project may have modest standalone return but unlock several benefits; another attractive project may consume capacity before a higher-value option is ready. Model start, defer, stage, combine and stop�not only approve or reject. Preserve flexibility where uncertainty will resolve before irreversible spend.

The UK Project Delivery Functional Standard defines a portfolio as the investment required to achieve objectives and sets expectations for active governance across projects and programmes. Its 2025 revision makes portfolio roles mandatory. The point is not central reporting; it is the authority to change priorities as context, evidence and resource capacity move.

Approve a portfolio baseline with aggregate value, cash, risk, resource load and dependency logic. Set entry conditions for new projects and fund contingency at portfolio level where risks correlate. Review every project by its marginal contribution to the current whole. A good project belongs only when adding it improves the deliverable, resilient strategy more than the opportunity it displaces.