Probability of win (pWin)

There is no formula the government recognizes; pWin is an internal judgment. Teams usually build it from the factors that drive awards: how well they know the customer and its problem, whether there is an incumbent and how it is performing, how many competitors are likely, how well their past work matches the scope, and whether their price can compete under the stated evaluation factors.

Many organizations derive pWin from a weighted scorecard instead of asking someone to type a number. That keeps the estimate tied to reasons a reviewer can challenge.

pWin is useful for two things: deciding whether to bid (see bid/no-bid decision) and weighting a pipeline, where the value of each pursuit is multiplied by its pWin to forecast revenue. It is less useful as a single point of truth, because early estimates are mostly guesses.

Common mistakes: inflating pWin to justify a bid already wanted, never updating it after the RFP lands, and not comparing estimates with actual results. Tracking estimated pWin against wins and losses over a year shows whether your team is optimistic.

pWin also changes during the pursuit, and the changes are informative. A customer meeting that confirms your understanding, a partner who fills a capability gap, or a draft RFP that matches your past work should raise it; a new requirement you cannot meet, a strong late entrant or an incumbent who is clearly favored should lower it. Recording each change with the reason gives leadership an honest picture at every gate review and makes it easier to stop a pursuit early, before the expensive writing starts, when the estimate drops below the team's threshold.