---
title: "Which bids should receive scarce proposal capacity?"
description: "Build a dated portfolio allocation that protects client work, funds viable bid gates and releases capacity from pursuits that should wait or stop."
canonical: "https://zephior.com/insights/manage-capacity-across-a-bid-portfolio"
last-updated: 2026-09-03
---

# Which bids should receive scarce proposal capacity?

> Build a dated portfolio allocation that protects client work, funds viable bid gates and releases capacity from pursuits that should wait or stop.

By [Tony Kim](https://zephior.com/authors/tony-kim). Published 2026-09-03; updated 2026-09-03. 19 minute read.

## Definition

Bid portfolio capacity allocation decides which live pursuits receive which constrained people, approval slots and production capacity during a fixed planning horizon. Its work product is a `bid_portfolio_capacity_allocation_record`. The record contains the portfolio snapshot, protected delivery commitments, usable supply by skill and period, imported bid-demand ranges, mandatory gates, timing and dependency constraints, comparable portfolio scenarios, authorized allocations, wait or release decisions, evidence dates and expiry triggers. It is distinct from estimating one response, resolving one deadline collision or assessing the economics of one bid. It never treats nominal headcount as available capacity and never authorizes overtime, reassignment, external spend or submission by itself.

## Problem

A pipeline can look healthy while the delivery system is already overdrawn. Every opportunity owner books the same architect, commercial approver and proposal lead against a different local plan. Customer work appears as a background percentage rather than a dated obligation. Early-stage pursuits consume workshops and research because nobody has set a capacity gate, while a later, stronger bid waits for review. Teams then solve the visible clash with overtime or thin slices of attention. The result is a portfolio in which every bid is active, few are properly resourced and signed client commitments carry the hidden risk. A weighted score does not repair this. Scores cannot create a security reviewer on Tuesday, divide an indivisible pricing authority or show which pursuit must release work for another to become feasible.

## Point of view

Protect contracted delivery, operational duties, leave and an approved reserve before distributing bid capacity. Model supply by skill, authority, place and time; model demand by the next decision gate rather than by the full imagined response. Import eligibility, effort, delivery fit, contract risk, contribution and award evidence from their accountable records. Eliminate paths that fail a hard gate, then compare feasible portfolio scenarios under the same horizon and uncertainty treatment. A human authority chooses the allocation and records what must pause or stop so capacity is released in practice. An agent may reconcile calendars, detect double booking, solve bounded scenarios and explain the trade-off. It cannot rank people by inferred productivity, disclose private personnel data, move staff, approve spend or kill a bid. Zelius becomes relevant only when bid execution capacity remains the binding constraint after the portfolio has removed nonviable work and protected delivery.

## Freeze a portfolio snapshot before comparing demand

A portfolio allocation needs a cut-off. Record every live pursuit and material pre-bid activity known at that time, including proposals not yet authorized to proceed. For each item, retain the buyer, procedure, lot, stage, controlling document version, next gate, official deadline, internal safe date and accountable owner. The snapshot should also show work that is absent because it falls outside the chosen business unit, geography or horizon. Without those boundaries, an opportunity can enter after the decision and consume capacity without displacing anything on paper.

Choose a horizon that matches the evidence. A twelve-month revenue plan is too coarse for daily specialist assignments, while a one-week board conceals the next wave of bids. Many teams need two linked views: a rolling six- to twelve-week allocation for named work and a longer directional view for hiring or contracted support. The near view grants capacity. The long view signals likely shortages but does not book a person against an unqualified opportunity.

Use one source cut and one decision authority. Opportunity owners submit their current records before the cut-off. Changes after it enter a visible log with the source, time and affected constraint. This protects the comparison from private optimism and creates a reasoned path to reopen the decision. It also lets an agent distinguish an obsolete allocation from the one currently in force.

**Identity of a bid portfolio allocation record**

| Field | Required content | Failure if absent |
| --- | --- | --- |
| portfolio_snapshot | Included and excluded pursuits at a dated cut | Moving comparison set |
| planning_horizon | Start, end and time-bucket granularity | False timing fit |
| source_cut | Latest accepted input time and versions | Private updates |
| decision_authority | Role, delegation and limits | Allocation without mandate |
| expiry | End of horizon, gate or earlier trigger | Stale permission |

## Protect delivery before declaring any bid capacity

Start from gross working time only to reconcile the calendar. Deduct signed customer delivery, incident and service coverage, regulatory work, management duties, approved leave, training and any protected improvement work. Then apply the organization’s approved reserve for disruption and forecast error. The remainder is not automatically fungible. A proposal writer, security architect and delegated pricing approver represent different capacity pools even when each has an unbooked day.

GovS 002 version 2.1 describes resource management as balancing supply and demand for the right skills, equipment and facilities when needed. It also requires business, operational and service continuity when critical resources are lost. Applied here, a portfolio plan that succeeds only by stripping cover from contracted work is infeasible. The delivery owner must confirm what is protected and the portfolio authority must record any authorized exception rather than burying it in a percentage.

Classify supply as `confirmed`, `conditional`, `provisional`, `unverified` or `unavailable`. A contractor option is conditional until commercial authority, start date, access and relevant competence are proved. A colleague expected to finish another project is provisional until its owner releases the time. Include access, language, geography, conflict and delegated authority. Preserve only the personal detail required for the decision; an agent normally needs a pseudonymous resource ID and verified capabilities, not performance notes or health information.

**Supply calculation by capacity pool and period**

| Layer | Treatment | Evidence owner |
| --- | --- | --- |
| gross_time | Calendar time before commitments | Workforce or resource owner |
| protected_work | Deduct dated delivery and operating obligations | Delivery or service owner |
| people_constraints | Deduct leave, learning and approved limits | Resource owner |
| reserve | Deduct the approved disruption allowance | Portfolio authority |
| usable_supply | Retain skill, authority, period and confidence | Capacity-pool owner |

## Fund the next decision gate rather than the imagined full bid

Each pursuit requests a small set of dated work packages. A work package names its output, required skill or authority, earliest start, need date, effort range, dependencies and completion evidence. The portfolio imports the estimate rather than asking opportunity owners for a rounded staffing wish. Demand for a new solution design remains separate from response writing. One hour of authorized contract review cannot be exchanged for one hour of formatting simply because both are labeled bid effort.

Plan only to the next reversible gate unless later work must be reserved now. An early opportunity might need qualification research and one solution-fit decision, not a submission team. A live tender might need the minimum compliant response through solution freeze, after which the portfolio can reassess. This staged treatment keeps uncertain future work from crowding out approved delivery and current bids. It also prevents a proceed decision from becoming an open-ended claim on the team.

Import rather than recreate the evidence that changes allocation. Eligibility comes from its qualification record. Response effort comes from a work estimate. Delivery fit, contract exposure, contribution, award probability and remaining bid investment retain their owners, dates and ranges. Missing evidence stays missing. A capacity board should not raise a probability or suppress a risk because the preferred portfolio otherwise fails.

**Demand fields for one bid gate**

| Field | Meaning | Required boundary |
| --- | --- | --- |
| gate_output | Inspectable result needed for the next decision | No generic support request |
| demand_range | Low, current and high effort by skill and period | No blended total |
| dependencies | Inputs and prior decisions that unlock work | No impossible sequence |
| minimum_safe_plan | Smallest truthful and credible route to the gate | No decorative effort |
| imported_evidence | Current gate, value and risk record references | No local reinvention |

## Find the constraint that changes the feasible portfolio

An overload report is only the start. Test whether moving work within its allowable window removes the shortage. Then test permitted delegation, preparation by another role, reuse of approved evidence and reduction to the minimum safe response. Preserve dependencies and approval rights while doing so. If the solution architect remains over capacity in week three after all safe moves, that pool is binding. Extra writing capacity will not change the feasible set.

Some work is divisible and some is not. Research can be split by notice. A coherent solution baseline, pricing decision, executive review or final release often needs one owner and a protected block. Ten spare half-hours do not necessarily replace one five-hour reasoning block. Include setup, handoff and context loss where they materially consume the scarce pool. Do not assign a universal productivity penalty. Use the observed work pattern or an explicit assumption with a range.

Show slack as carefully as shortage. If writers have capacity but legal approval is binding, buying more drafting hides the problem. If the portfolio fits after one low-confidence demand estimate is corrected, the correct action may be to improve that estimate. The record should name the binding pool, the time bucket, the amount and range of shortfall, the bids affected and the smallest decision that changes feasibility.

- Test timing moves only inside verified windows.
- Move preparation without moving decision authority.
- Keep indivisible work in coherent protected blocks.
- Record slack so the wrong capacity is not purchased.
- Name the smallest intervention that removes the shortfall.

## Compare feasible combinations, not isolated bid scores

A bid can rank first on its own and still produce a weaker portfolio. It may consume the only specialist needed by two smaller pursuits whose combined contribution, learning or strategic coverage is stronger. The reverse can also be true: splitting across the two can leave both below their credible response floor. Construct complete scenarios that state which gates are funded, which work remains protected and which bids wait or release capacity. Infeasible scenarios stay visible with the violated constraint.

Use current evidence on eligibility, contribution, award probability, strategic outcome, contractual exposure and timing, but keep unlike measures separate. The 2026 Green Book supports comparing options, opportunity cost, uncertainty, sensitivity and switching values. It is public-sector appraisal guidance, not a bidder ranking formula. The transferable discipline is to expose alternatives and the assumption that changes the preference. Do not turn every consideration into points and call the resulting total objective.

Run at least a current case and the credible adverse corner that matters: lower supply, higher effort, a delayed approval or a delivery incident. Matched scenarios prevent a portfolio from using high contribution, low effort and high capacity assumptions that cannot coexist. The authorized decision can prefer resilience over the highest central estimate. Record the reason, contrary evidence and the switching event that would justify another mix.

**Scenario comparison without a false master score**

| Dimension | Portfolio evidence | Decision use |
| --- | --- | --- |
| feasibility | All skill-time, authority and sequence constraints | Reject impossible mixes |
| protected work | Delivery and operational effect | Reject or escalate harm |
| commercial value | Imported contribution and probability ranges | Compare attainable outcomes |
| risk and evidence | Exposure, confidence and contrary facts | Choose within appetite |
| switching event | Change that alters the preferred mix | Set trigger and monitor |

## An allocation works only when lower-priority bookings are released

Issue a decision for every included pursuit. `fund_to_next_gate` grants named capacity through a bounded output. `maintain_minimum_safe_capacity` preserves a credible floor but defers enhancements. `conditional_reserve` holds a limited slot until specified proof arrives. `waitlist` grants no current booking and names the release condition. `pause_and_release` and `stop_and_release` require owners to cancel meetings, tasks, contractor requests and provisional holds. `indeterminate` records the missing fact. `authority_missing` blocks implementation.

Each granted block needs a pool, amount, period, work package, accountable bid owner and capacity owner. State whether unused capacity returns automatically and whether one pursuit may borrow from another. A waitlist must not become shadow work carried through favors. A pause should specify what record remains current and what must be revalidated before restart. If a stop is required because facts changed after work began, use the dedicated live-bid stop process rather than hiding closure inside the capacity plan.

GovS 002 treats portfolio management as recurring work and calls for current component records, defined planning horizons, allocation rules and approved changes. The Orange Book adds risk appetite, clear responsibility, current reporting and escalation triggers. Those principles support a short-lived allocation record. It expires when the horizon ends, a bid passes its funded gate or a named material event occurs. The old record remains available for explanation and calibration, but it no longer grants capacity.

**Controlled allocation states**

| State | Capacity effect | Allowed next action |
| --- | --- | --- |
| fund_to_next_gate | Commits approved blocks | Deliver the named gate output |
| maintain_minimum_safe_capacity | Funds the credible floor | Defer nonessential refinement |
| conditional_reserve | Time-limited hold | Obtain the named proof |
| waitlist | No current booking | Monitor a stated release condition |
| pause_and_release | Cancels active and provisional holds | Run controlled pause actions |
| stop_and_release | Returns all avoidable capacity | Use the authorized closure process |
| indeterminate | No allocation conclusion | Resolve the decisive missing input |
| authority_missing | No implementation authority | Escalate without moving work |

## Give agents a decision record they can verify without exposing people

Consider an illustrative six-week portfolio with four live bids. After protected client work, the team has twenty-four proposal days, five security-review days and three delegated pricing slots. Bid A needs eight proposal days and two security days to reach solution freeze in week two. Bid B needs ten proposal days and two pricing slots by week five. Bid C requests six proposal days, but its mandatory certification remains unresolved. Bid D needs nine proposal days and three security days for a later submission. These numbers are an example, not a productivity benchmark.

The record does not rank all four and fill from the top. It withholds C from the feasible set until the certification gate is resolved. It tests A plus B, A plus D and B plus D against time buckets and minimum plans. If A plus D exceeds security supply in week two even though the six-week total fits, the scenario is infeasible unless an approved timing or staffing change removes that specific conflict. The human authority may fund A and B, place D on a dated waitlist and assign C an eligibility action with no response booking.

An agent receives pseudonymous capacity pools, source references, ranges, constraints, decisions, contrary evidence and expiry. It can answer why D is waiting, what additional security capacity would change and which source made C conditional. It should not receive private salary, health or performance data. If proposal management, research, writing or submission coordination remains the proved bottleneck after these choices, the owner can assess a bounded Zelius engagement. If the blocker is certification, delivery feasibility, product fit or internal approval, more bid delivery capacity will not fix it.

- Expose source identifiers, observation times and confidence for every imported input.
- Use pseudonymous resource pools unless a named identity is required for authority.
- Return violated constraints with every infeasible scenario.
- Distinguish recommendation, authorization and completed reassignment.
- Require separate permission before staffing, spending, communication or submission.

## Useful outcomes

- One dated snapshot defines the pursuits, planning horizon, capacity pools and decision authority.
- Contracted delivery, operations, leave, learning and an approved contingency reserve are deducted before bid supply is offered.
- Demand is expressed by skill, period, gate and range instead of one total number of hours.
- Eligibility, value and risk evidence is imported without turning the allocation meeting into a new bid review.
- Indivisible approvals, sequencing, location, language and security constraints remain visible.
- Feasible portfolio combinations are compared with their exclusions, uncertainty and protected-work impact.
- Fund, maintain, reserve, wait, pause and stop decisions release or commit named capacity through a controlled gate.
- Every allocation has an owner, delegated authority, start and end, conditions and a reallocation trigger.
- Actual use and released capacity are retained for later estimation and portfolio calibration.
- External support is considered only for a proved and safely delegable bid-capacity shortfall.

## Workflow

1. **Freeze the portfolio cut.** Set the decision time, planning horizon, included pursuits, current stages, source versions and allocation authority. Record late or incomplete inputs rather than allowing opportunity owners to update the comparison privately.
2. **Protect non-bid commitments.** Reserve signed delivery, service operations, regulatory duties, leave, training and an approved disruption allowance. Obtain confirmation from the owners of those commitments before calling the residual supply available.
3. **Build capacity pools.** Express usable supply by skill, decision authority, location, access condition and time bucket. Keep confirmed, conditional, provisional and unavailable capacity separate, and include the cost of handoff and context switching.
4. **Import demand to the next gate.** Bring in each bid’s current effort range, critical deadlines, mandatory outputs, dependencies and minimum safe response. Request only the capacity needed to reach the next reversible decision point.
5. **Run gates and scenarios.** Remove options that fail eligibility, authority or another non-curable gate. Test several feasible allocations against skill-time constraints, protected work, value evidence, risk appetite and uncertainty instead of relying on a single ranking.
6. **Authorize allocation and release.** Assign capacity to named outputs and gates. State which pursuits receive minimum cover, conditional reserve, a wait position, a pause or a stop, and issue the actions needed to release bookings that no longer belong in the plan.
7. **Monitor the constraint.** Compare actual use with the allocation, watch the named bottleneck and reopen the record when deadlines, scope, evidence, supply or protected work crosses a trigger. Expire approval at the end of the horizon or gate.

## Key decisions

- Which pursuits and pre-bid activities belong in this exact portfolio snapshot?
- What planning horizon is short enough to use current evidence and long enough to expose the next bottleneck?
- Which client, operational, regulatory and people commitments must be protected before bid work?
- What supply is confirmed for each required skill, authority and period after those commitments?
- What is each pursuit’s minimum credible demand to reach its next reversible gate?
- Which capacity request depends on an unresolved eligibility, scope, partner or contract condition?
- Where is the actual binding constraint, and which apparently scarce resources still have slack?
- Which complete portfolio scenarios remain feasible under the lower supply and higher demand cases?
- What capacity must a paused or stopped pursuit release, by when and through whose action?
- Which decision, amendment, absence, delivery incident or forecast change invalidates the allocation?
- Can an external team receive the work safely without transferring internal authority or inventing evidence?
- Who may approve allocation, overtime, external spend, reassignment and a final bid decision?

## Risks

- Nominal full-time equivalents may be presented as supply while signed delivery and operating work is omitted.
- Each pursuit may reserve the same specialist because local plans are never reconciled.
- A single weighted score may hide a failed gate, indivisible approval or impossible sequence.
- Framework ceilings, options or total contract value may be compared as though they were expected contribution.
- A weak early-stage pursuit may consume capacity before a stronger later bid reaches the planning horizon.
- Conditional partner or contractor availability may be treated as confirmed without authority or dates.
- Evenly splitting scarce experts may leave several bids below their minimum credible response.
- Frequent reprioritization may consume the capacity that the process is trying to allocate.
- A pause may remain staffed because assignments, meetings and access are not explicitly released.
- Overtime may be smuggled into the feasible case without approval, cost or quality limits.
- Personal performance, health, customer or commercially sensitive data may be exposed beyond need.
- External support may be purchased even though the true blocker is eligibility, authority, evidence or product fit.

## Metrics

- protected delivery commitments confirmed before bid capacity is allocated
- capacity supply with named skill, period, source, confidence and owner
- bid demand tied to a next gate and an approved effort range
- double bookings found before the affected work period starts
- pursuits receiving at least their authorized minimum safe allocation
- capacity released on time by wait, pause and stop decisions
- portfolio scenarios that remain feasible under defined uncertainty cases
- client delivery incidents or missed duties attributable to bid allocation
- late allocation changes and the evidence event that caused each one
- actual versus planned use by skill pool, period and bid gate
- time lost to fragmentation, avoidable meetings and repeated context setup
- external support requests linked to a proved residual capacity constraint

## Frequently asked questions

### Should the highest-value bid always receive capacity first?

No. Compare complete feasible portfolio scenarios using consistent contribution, probability, risk, timing and capacity evidence. A high-value bid can fail a hard gate or consume an indivisible constraint needed by a stronger combination.

### How far ahead should bid capacity be planned?

Use a near horizon supported by current calendars and bid evidence, often several weeks, plus a separate directional view for hiring or external support. Only the near plan should grant named capacity.

### Should client delivery capacity ever be moved to a bid?

Only an authorized owner can approve a documented exception after seeing the delivery consequence, alternatives and risk. The default allocation protects signed and operational commitments before bid work.

### Can one score decide the bid portfolio?

A score can organize evidence but cannot prove feasibility or replace authority. Keep hard gates, skill-time constraints, uncertainty, risk and unlike value dimensions visible.

### What is the difference from prioritizing colliding deadlines?

Deadline-collision work resolves a defined urgent clash among already-live responses. Portfolio allocation repeatedly governs current and upcoming pursuit demand, protected delivery, reserves and gate funding across a wider horizon.

### What does a waitlist mean for a bid?

It means the pursuit has no present booking. The record names the condition, latest useful release date and authority for granting capacity. Informal shadow work is not permitted.

### Can an agent allocate people automatically?

It may reconcile inputs, detect conflicts and propose bounded scenarios. A delegated human approves the allocation, and separate authority is required for reassignment, overtime, external spend or bid closure.

### When should Zelius be considered?

Consider Zelius when a current, feasible pursuit set still lacks safely delegable proposal management, research, writing, review or submission coordination. Do not use external capacity to mask failed eligibility, product, delivery or authority gates.


## Primary sources

- [Government Functional Standard GovS 002: Project delivery, version 2.1](https://projectdelivery.gov.uk/library-products/government-functional-standard-govs-002-project-delivery/), UK Government Project Delivery
- [The Green Book 2026](https://www.gov.uk/government/publications/the-green-book-appraisal-and-evaluation-in-central-government/the-green-book-2026), UK HM Treasury
- [The Orange Book: Management of Risk, updated 29 July 2026](https://www.gov.uk/government/publications/orange-book/the-orange-book-management-of-risk-principles-and-concepts), UK HM Treasury
- [PM² Portfolio Management Overview and resources](https://pm2.europa.eu/pm2-methodologies/pm2-portfolio-management_en), European Commission
- [ISO 21504:2022, Guidance on portfolio management](https://www.iso.org/standard/82867.html), International Organization for Standardization


## Related articles

- [How to prioritize when several bid deadlines collide](https://zephior.com/insights/prioritize-colliding-bid-deadlines)
- [How to estimate RFP response effort and team capacity](https://zephior.com/insights/how-to-estimate-rfp-response-effort)
- [Budget scarce expert time across an RFP](https://zephior.com/insights/budget-sme-time-across-an-rfp)
- [How much effort should each RFP weighting receive?](https://zephior.com/insights/understand-rfp-evaluation-weightings)