Why your government contracting pipeline looks healthy but isn’t

· 9 min read · Advanced

Sources

Your pipeline report shows several times next year’s target. Why doesn’t that feel reassuring?

Quick answer

Because pipeline totals usually count contract ceilings, options and old odds of winning. They also include opportunities nobody is working. A pipeline is healthy when each opportunity has an owner, a realistic value, odds based on evidence and a next step. Its timing also has to fit the number of proposals your team can really write.

Most federal business development (BD) pipeline reports lead with one number: the total value of everything the team tracks. It makes an easy headline. But it’s a poor guide to next year’s revenue, staffing or proposal load.

Pipeline value is the least useful number in the report

The headline number adds up the value of every opportunity the team tracks. Sometimes each value is weighted by the chance of winning it (Pwin). The total grows whenever someone adds an opportunity. It shrinks only when an award is announced or someone cleans up. So it measures how much the team has noticed. How much the team will win is a separate question.

For a VP of Growth or a BD Director, the useful questions are narrower. Which opportunities are we really working? When will each one need a decision and a proposal team? What would have to be true for the weighted number to come in? This piece covers the signs that a pipeline is too big, and a review format built around those questions. For the step before, deciding what enters the pipeline at all, see why government contractors waste time pursuing the wrong opportunities.

Five signs your pipeline is overstated

Five signs a federal pipeline is overstated

A pipeline’s total shows what you noticed. It doesn’t show what you’ll win.

  1. Ceilings counted as revenue

    Use what you could expect to bill if you win.

  2. Probabilities that never move

    Update the probability of win when evidence arrives.

  3. Entries nobody is working

    No owner, no contact, no next step: move it to a watch list.

  4. RFP dates that ignore capacity

    Sort by expected RFP date and compare with your proposal capacity.

  5. Recompetes carried on reputation

    Check what changed in the acquisition before keeping a high probability.

Sources: USAspending.gov · FAR 17.207. Checked Oct 22, 2026. Practice, not a rule. Your own win history is the best check on your numbers.

1. Values are ceilings, not expected revenue

The value field often holds a contract’s ceiling, or the total of the base period and every option. That’s common with an indefinite delivery, indefinite quantity contract (IDIQ). When several companies win the same contract, they all share that ceiling. The government promises only the minimum, and the work comes through orders each holder competes for. On a contract with one winner, the agency decides whether to use each option. It can do so only when it has the money, under the Federal Acquisition Regulation (FAR 17.207). A more useful value is what your company could expect to bill over the forecast period if it wins. Keep the ceiling in a separate field for context.

2. Probabilities don’t change

The most common source of false confidence is a Pwin set on day one and never changed. It should move when new evidence arrives. That might be a draft request for proposals (RFP) whose scoring favors you or someone else. It might be a set-aside decision, or a meeting that went well, or one that never happened. If the odds in a pipeline haven’t changed in a quarter, the weighted total is last quarter’s guess.

The odds should also rest on evidence. A large ceiling makes an opportunity look important, but it says nothing about your chances. Past performance and access to the customer say more. First, do you have past performance the agency will see as relevant, such as similar work for a similar customer? Second, do you have real access to the customer? That means you have met the people involved and know what they care about. If you can’t point to either one, keep the Pwin low, however big the contract is.

3. Opportunities with no owner or next step

Here’s a simple test for each entry. Can someone name the capture lead, the last talk with the customer, and the next step with a date? Entries that fail belong on a separate watch list. There they stay in view without making the forecast look bigger.

4. Timing that ignores proposal capacity

Pipeline reports usually sort by value or stage. Try sorting by the date you expect each RFP instead. Then compare that with how many proposals your team can write in a month. Pile-ups show up fast: four large proposals due in the same six weeks, for a team that can do two well. Either some of those are no-bids waiting to be made, or the company needs to line up outside proposal help now.

5. Recompetes carried on reputation

Your own recompetes often carry the highest odds in the pipeline, and they deserve the hardest look. The current contractor (the incumbent) does have an edge, but it has limits. The agency may reshape the work, move it to a different vehicle, combine it with other work, or set it aside a different way. For recompetes you hope to win from someone else, the reverse applies. A well-liked incumbent on steady work is hard to beat, however big the contract. Check what changed in how the agency is buying before you carry last time’s Pwin forward. Our guide to researching the incumbent shows how to find the current contract on USAspending.gov.

What a useful pipeline review looks at

A pipeline review is worth the time when it changes decisions: what to drop, what to invest in, and where to add people. Here is one format that keeps it on track:

A pipeline review that leads to decisions
Review questionWhat to bringThe decision it supports
What changed since the last review?New and removed entries, and every change to Pwin or dates, each with its reasonWhether the forecast is moving for real reasons
What needs a decision in the next 60 days?Each opportunity reaching a gate, with its qualification evidenceBid/no-bid and capture investment
What are we not working?Entries with no owner, no recent contact or no next stepDrop it, move it to a watch list, or assign it
Can we staff it?Expected RFP dates against proposal and technical capacityHiring, outside support or more no-bids
What would have to be true?The few opportunities that carry most of the weighted valueWhere leadership time and relationships should go

Keep the plain total and the weighted total side by side, and add a third. The third is the value of opportunities you have fully checked and have a capture plan for. It’s the smallest of the three, and usually the most honest.

Connecting the pipeline to the revenue forecast

Finance and leaders will use pipeline numbers as a forecast, whether or not BD meant them that way. A few habits make that safer:

  • Keep new business, recompetes and expected growth on current contracts apart. They behave differently and carry different risks.
  • Use a realistic amount you can bill, and the date work is expected to start, which comes after the award. A protest, a continuing resolution or a long handover can push revenue back by months.
  • Check your own history. Compare past Pwin guesses with what really happened, by stage and by type of opportunity. Your own record tells you more than any industry rule of thumb.
  • Show the range. A forecast that rests on a few large pursuits is lumpy, and it’s better to say so than to smooth it into one number.

Resource allocation is the real output

A cleaner pipeline matters because of the decisions it supports. With an honest one, a growth leader can see which accounts need more capture work and when to bring in proposal help. They can see which partners matter next year, and which opportunities to stop spending on. With an inflated one, those decisions happen by default, usually in favor of whatever is due next.

Most of these fixes are habits more than tools. Use a value field that means expected revenue, and odds that move with evidence. Give every entry an owner and a next step, and end each review with decisions. Software helps by keeping the evidence, dates and decisions in one place. Then the review starts from facts instead of memory. Our pipeline management guide covers the stages and a weekly routine.

Common questions

What is a weighted pipeline in government contracting?

You multiply each opportunity’s value by your chance of winning it, then add them all up. It is only as good as the values and odds behind it. Contract ceilings, and odds that are never updated, make it show more revenue than you’re likely to get.

How often should a BD team review its pipeline?

Often enough that the odds and dates are current when you make decisions. A common rhythm is a short weekly look at active pursuits and a fuller monthly review. A written record of what changed and why matters more than the schedule.

Should our recompetes carry a high probability of win?

Only if the evidence supports it. First check whether the work, the contract vehicle, the set-aside or the way bids are scored has changed. Also check how the customer feels about the current work. Then decide whether to keep the high odds.

What value should a pipeline use for an IDIQ contract?

Use the revenue your company could really expect from orders over the forecast period if it wins a spot. Don’t use the contract ceiling, which every winner shares. Keep the ceiling in a separate field for context.

How do you know if a pipeline supports the revenue forecast?

Look at the opportunities that carry most of the weighted value. Check that each has an owner, recent contact with the customer, odds based on evidence, and a request for proposals (RFP) date your team can staff. Then compare your past odds with what really happened, to see how far to trust the current ones.

How FedPath helps

FedPath keeps the record behind each opportunity in one place. Opportunity Watch and saved opportunities bring in what to look at. Change alerts flag amendments and new deadlines. Each Go/No-Go assessment records who decided, when and why. On every plan, the “Who won this work before” panel suggests the likely current contract from USAspending.gov. It gives its reasons and says whether a government record confirms it. On paid plans, follow-on alerts link a sources sought or presolicitation notice to the solicitation that follows it.

Search open opportunities