Budget selection differs from rank order

A preference ranking answers which standalone option leads under the supplied attributes and tradeoffs. A funded portfolio answers which feasible combination of commitments the organisation should undertake within its constraints. Those questions can produce different answers. The highest-ranked option may consume an envelope that would otherwise support a more attractive combination, depend on an unfunded enabling asset or compete with another intervention for scarce delivery capacity. Selecting entries down a ranked list until the money runs out is a policy, not a general solution to portfolio allocation.

The distinction begins with the unit of decision. A standalone proposal can have an interpretable cost, impact, readiness and risk profile. A combination requires information about how these profiles interact. Benefits may overlap, delivery resources may be shared and costs may change when components are procured together. Summing standalone preference scores assumes more than the ranking model establishes. The committee should not treat the score as an additive portfolio benefit merely because it is expressed numerically. Its scale depends on the candidate set and its components mix unlike considerations.

A budget constraint is different from a preference for lower cost. The liquidity-mandate fixture changes the cost weight, which alters the attractiveness of standalone alternatives. It does not introduce an expenditure ceiling or enforce affordability. A very costly option can still receive a strong score if its other represented attributes compensate. Conversely, an affordable option can rank poorly. If the present decision has a binding envelope, feasibility must be checked explicitly in the selection method. Increasing the cost weight cannot substitute for that check.

Indivisibility matters when an intervention cannot be purchased in arbitrary fractions. A committee cannot always take part of the leading proposal and allocate the remaining envelope to another. A minimum viable scope, contractual package or enabling requirement may make the commitment indivisible. Greedy ordering can leave unusable capacity in the envelope or exclude a useful combination. The analyst should record whether each candidate is divisible, stageable or indivisible and whether a reduced version has its own credible performance profile. A fractional arithmetic solution is not automatically an implementable plan.

Mutually exclusive alternatives require particular care. If several proposals represent different ways to deliver the same service, their standalone ordering can support a choice within that family. It cannot justify selecting all of them. The committee should identify the family and the exclusivity rule before constructing a funded programme. Otherwise a collection of individually attractive options may become an incoherent set. The programme must describe what is implemented, which service it delivers and which alternatives it displaces.

Complementary interventions create the opposite problem. An enabling data architecture may have modest standalone impact but make several subsequent interventions possible. A high-ranked operating intervention may require it. Selecting only the operating intervention would then violate the scope underlying its performance claim. The analyst should examine packages or explicit dependencies, with benefits attributed consistently. A dependency graph can clarify the structure, but it does not by itself estimate the value of the package. The necessary relationship and the preference for the resulting outcome both need attention.

Shared benefits can make a sum of scores especially misleading. A monitoring proposal and a process redesign may both claim the same reduction in disruption. Funding them together does not necessarily double that outcome. The programme should identify the benefit mechanism and how the interventions interact. The issue is not solved by assigning each a lower subjective impact rating after the fact. A package-level evidence model should explain the incremental outcome and the assumptions supporting it. The standalone ratings remain useful only for their original comparison purpose.

A symbolic counterexample helps clarify the logic without pretending to solve a funded case. Suppose the leading proposal uses most of an envelope and leaves no room for another indivisible intervention. A pair of lower-ranked compatible proposals fits the envelope and creates a more desirable programme outcome under a separately defined package evaluation. A greedy selection from the standalone ordering will choose the leader; a constrained package comparison may choose the pair. Nothing in the standalone ranking proves which programme is preferable, because the required combination values and constraints were never represented.

The analyst should not respond by dividing the preference score by cost and declaring the result a universal efficiency measure. The score includes cost already, mixes transformed attributes and changes with the reference set. Dividing it again can double-count cost preference and create a ratio without a meaningful unit. A benefit-cost or cost-effectiveness analysis requires a defined outcome measure and consistent cost perimeter. The organisation may choose such a method, but it is a different analysis with its own assumptions and evidence requirements.

Time introduces another layer of feasibility. An intervention can fit a total envelope but require expenditures before funding is available, or compete with another proposal during the same delivery window. A programme may be feasible when staged and infeasible when launched concurrently. The selection method should represent the relevant timing and resource obligations explicitly. A readiness rating can summarise some delivery maturity, but it cannot replace a schedule or a cash requirement profile. The committee should know which temporal constraints remain outside the preference model.

A preliminary ranking can still make the allocation process more manageable. It can identify proposals worth detailed feasibility work, reveal tradeoffs among standalone options and organise questions for package design. Its role should be stated as screening or preference explanation rather than optimisation. The team can retain the ranking while building a separate constrained comparison of plausible packages. This preserves the work already done without letting its convenient format dictate the later decision rule.

Before handing individual options to package analysis, construct a compatibility ledger in words. For each proposed pairing, identify the shared resource, the reason simultaneous delivery could fail and whether sequencing would remove the conflict. A common operating team may create a temporary capacity conflict; two designs for the same asset may remain mutually exclusive; an enabling interface may make joint delivery more valuable. These relations cannot be recovered from the four standalone ratings. Transfer consistent raw commitments and their scope, while withholding preference totals as package benefits. This ledger defines the representation the allocation analysis needs without pretending that the present app has optimised it.

Use the next funding round as a diagnostic of the reason an option was left out. A deferred candidate excluded by an annual envelope should return when that envelope changes, subject to current evidence. A candidate excluded because the selected programme now supplies its function may no longer add anything even if money becomes available. A rejected design with an unresolved incompatibility should not re-enter simply because its old score was high. These are queue, redundancy and feasibility branches. The carry-forward register should preserve the applicable branch, since retaining only the ranking would confuse a temporary constraint with the disappearance of the underlying need.

A defensible allocation brief describes the selected programme, its feasibility and the tradeoffs accepted, then explains how the standalone analysis informed it. It does not claim that the ranking selected an optimal funded portfolio when no constraint model was run. If the organisation has not yet established package benefits or shared-resource requirements, the recommendation can be to perform that analysis before commitment. That is a concrete next action, not a failure to produce a convenient answer. The method boundary protects the meaning of the recommendation.