How to Benchmark Your GovCon Win Rate

GovEagle is not affiliated with, sponsored by, certified by, or otherwise associated with Shipley Associates.

A 28% win rate can mean two completely different things depending on what's inside it. If that number mixes incumbent recompetes with full-and-open new business pursuits, it can hide two very different performance problems. GovCon also lacks reliable public data that breaks win rates out by segment, so the most useful benchmark is usually one you build from your own submissions. This guide covers how to calculate it, how to segment it, and how to use PWin, bid/no-bid, and debriefs to move it.

TLDR:

• Segment your win rate by competition type and incumbent status before comparing it to anything; a blended number often hides two separate performance problems.
• Public win rate benchmarks are thin: award data can't show losing bids, and survey figures are self-reported and blended, so treat outside numbers as rough context and build your own segmented baseline.
• Shipley Associates reports that firms moving from ad hoc to defined capture and proposal processes see win rates rise from below 35% to 51-80%.
• Track PWin against actual outcomes, gate bids with a written bid/no-bid decision, and feed debrief findings into the next pursuit.
• GovEagle keeps bid/no-bid analysis, black hat review, and P-Win scoring on the same opportunity as the proposal, so saved win themes and capture answers inform the draft.

What Is a GovCon Win Rate and How Is It Calculated?

Win rate in federal contracting is straightforward on its surface: divide the number of contract awards by the total number of submitted proposals. What complicates that formula is everything contractors count, or fail to count, consistently.

Common measurement disagreements include whether to count no-bid decisions in the denominator, how to treat recompetes versus new business, and whether IDIQ task orders count separately from the base vehicle award. A firm that counts every task order submission alongside full RFP responses will report a very different number than one tracking only competitive FAR Part 15 procurements.

Cross-industry benchmarks compound the confusion. The average RFP win rate across industries mixes commercial and government work, short-turnaround RFQs with multi-volume proposals, and sole-source awards with full-and-open competitions. Any external benchmark is only useful after your own data is properly segmented first.

What Public Win Rate Data Exists, and Its Limits

There's no authoritative public dataset of federal win rates by firm size, competition type, or incumbency. Federal award data, such as FPDS and USASpending, records who won but not who bid and lost, so any win rate calculated from award data alone rests on assumptions. Read published figures with that in mind.

The sources worth knowing:

• Contractor surveys. The 2026 Deltek Clarity Government Contracting Study, a survey of more than 900 contractors, puts the industry average win rate at 48%, based on what respondents report. It isn't broken out by competition type or incumbency, so it's a blended number, the kind this post recommends against benchmarking to directly.
• Process benchmarks. Shipley Associates reports that, across 400+ assessments and 20+ years of benchmarking, firms that move from ad hoc to defined capture and proposal processes see win rates rise from below 35% to 51-80%, and about twice the effectiveness on large, strategic programs.
• Incumbency surveys. Contractor surveys from 2012 to 2016 put the incumbent recompete win rate anywhere from about half to three quarters. The figures moved a lot from year to year, which is a reason to measure your own recompete rate instead of assuming one.

Use these as context, not targets. The benchmark that tells you the most is your own win rate, segmented the same way every quarter: same competition type, same incumbency status, same contract vehicle.

The Incumbent Advantage and Recompete Benchmarks

Incumbents usually hold an advantage on recompetes, though how large it is varies by agency, contract, and year. That advantage is reason enough to track recompete win rate and new-business probability of win as separate metrics entirely.

A firm with a 40% overall win rate might be defending recompetes at 75% while losing new business pursuits at 15%. Blending those into one number obscures where performance is actually breaking down.

Several conditions erode the incumbent advantage: weak CPARS ratings, key personnel turnover, LPTA evaluation methods where pricing displaces relationship equity, and documented performance issues that show up in public GAO protest decisions. Under LPTA, price can outweigh the relationship and past-performance edge an incumbent usually brings, which narrows the gap. If you hold an incumbent position, your recompete benchmark should reflect the conditions of that specific recompete, not a general assumption about incumbency.

How Process Maturity Affects Win Rate

Raw win rate tells you what happened. Process maturity tells you why.

Shipley Associates reports that organizations with ad hoc capture and proposal processes win less often than firms with defined, repeatable ones, and that the gap is largest on large, strategic programs.

Process maturity in practice means gate reviews that actually gate, structured capture that feeds proposal strategy, formalized bid/no-bid decisions, and color team reviews that run before deadline pressure has compromised the draft. Many firms claim these practices; running them consistently is what shows up in win rate data.

Treat maturity as a parallel benchmark. A 28% win rate reads differently for a firm with no formal gate process than for one running structured Pink and Red Team reviews on every pursuit. The number without process context is incomplete.

Why Your Raw Win Rate Is Misleading Without Segmentation

A single win rate number without segmentation is less a performance metric and more a confidence interval around an unknown quantity.

The segmentation cuts that matter most:

• New business vs. recompete
• Full-and-open vs. set-aside
• Sole-source vs. competitive
• IDIQ task orders vs. standalone contract awards

A firm reporting 60% overall may be defending incumbent positions at 75% and winning sole-source extensions regularly, while losing every competitive new-business pursuit it enters. Strip those out and the real number might be 15%. Conversely, a 20% rate on crowded full-and-open new business pursuits may be stronger than it looks.

Before comparing your number to any external benchmark, build a denominator that matches the benchmark's construction. Mixing IDIQ task order submissions with FAR Part 15 standalone proposals inflates submission counts without adding signal about competitive performance.

Segment your last 24 months by competition type and incumbent status. If your new-business competitive win rate and your recompete rate differ by more than 20 percentage points, you have two separate performance problems that a blended number was masking.

How PWin Scoring Connects to Win Rate Benchmarking

PWin scoring is where benchmarking moves from retrospective to predictive. Most capture teams assign PWin estimates before submission, but tracking how those estimates perform against actual outcomes is less common.

That gap has real consequences. A team that consistently scores pursuits at 60-70% and wins them at 25% has a calibration problem. The scores feel right in the room but systematically overstate competitive position, which makes the pipeline look healthier than it is and keeps bid/no-bid decisions soft when they should be hard gates.

Tracking PWin against actual outcomes over 18-24 months surfaces these patterns. If your 70%+ bucket closes at 35%, your PWin factor scoring model is overweighting incumbent relationships or underweighting competitor strength. If your 40-50% bucket closes at 45%, your mid-range scoring is well-calibrated and you can trust those numbers in pipeline forecasting.

The calibration loop closes when PWin scores are treated as hypotheses to test, not consensus outputs to archive. Tag each submitted pursuit with its PWin score at bid submission, record the outcome, and run a quarterly comparison by score tier. Updating scores as capture evidence changes, and recording the final score at submission, makes the comparison meaningful. In GovEagle, Continuous Monitoring re-scores tracked opportunities on a schedule and shows how scores such as P-Win change over time, which gives you that history without a separate spreadsheet. Over time, this tells you whether your capture team is systematically overconfident on certain agency relationships, contract types, or competition structures.

Accurate PWin calibration feeds directly into pipeline revenue forecasting. A pipeline weighted by uncalibrated scores will consistently overstate projected revenue, which misleads capacity planning and hiring decisions downstream.

Bid/No-Bid Discipline as a Win Rate Lever

Bid/no-bid discipline changes the win rate denominator before a single word of the proposal is written.

The 2026 Deltek Clarity Government Contracting Study found that 38% of contractors named pricing defensibility as the top reason proposals were not selected, ahead of both technical deficiencies and uncompetitive pricing. In our view, a price that can't be traced to supportable assumptions is often a risk you can spot at the bid/no-bid gate.

A formal go/no-go gate stops this before B&P dollars are spent. A functional scorecard, built with dedicated bid/no-bid analysis tools, typically weighs customer access and relationship history, incumbent status and CPARS exposure, scope alignment with verified past performance, competitive intelligence depth, and pricing position relative to known contract history.

Setting a minimum pipeline PWin threshold for new business, for example 40%, creates a hard filter that requires explicit justification to proceed when a pursuit falls below it. Over time, a tighter threshold raises the average quality of the submission pool and lifts win rate without any change to proposal execution. In our experience, firms that beat their own baselines are often more selective about what they bid. Scorecards kept in spreadsheets are the first thing waived under pipeline pressure, which is why GovEagle's bid/no-bid analysis checks certifications, contract type, capability fit, the incumbent and competitors, and red flags, then gives a pursue recommendation before B&P spend starts. Book a Demo to see it applied to your own pursuit pipeline.

Using Win/Loss Debriefs to Build a Benchmarking Feedback Loop

Debrief data is one of the most underused inputs in GovCon benchmarking. Under FAR 15.506, an offeror has three days after receiving notice of award to submit a written request for a debriefing, and the agency should hold it within five days of that request when practicable. The debriefing can be oral, written, or another format the contracting officer chooses. Offerors excluded before award can request a preaward debriefing under FAR 15.505, and agencies following the FAR Overhaul Part 15 deviation have moved these rules to new section numbers.

What to pull from each debrief:

• Major weaknesses and deficiencies the agency found, plus any strengths it shares, mapped to Section M factors
• The overall price and technical rating for you and the winner, and the overall ranking if the agency developed one, which give you a competitive position reference point beyond a simple win or loss
• Evaluation language that signals recurring gaps across similar pursuits

Map those findings back to the original bid decision. If a flagged weakness in past performance surfaces across three debriefs on similar agency pursuits, that is a PWin calibration problem, not a writing problem. If pricing landed outside the competitive range repeatedly, pre-RFP price-to-win work needs earlier attention.

For recompetes, debrief records create a comparison baseline across award cycles. A firm tracking evaluation feedback over 18 to 24 months can identify whether weaknesses are narrowing or recurring, which directly informs whether the recompete PWin score should rise or fall from the prior cycle.

The loop closes when debrief findings feed forward into the next pursuit's capture strategy, not backward into a post-mortem that no one reads.

Building the Internal Accountability Structure for Win Rate Improvement

Lasting improvement usually traces back to ownership, not measurement alone.

Teams that improve their win rate over time usually have a clear accountability model across three roles:

• A BD leader owns the pipeline-level win rate as a business metric, reviewed quarterly by competition type, while the capture manager's role focuses on individual pursuit scoring.
• Capture managers own individual PWin scores across the federal capture planning process, from bid decision through submission, treated as tracked hypotheses and not consensus outputs.
• Proposal managers own compliance and quality outcomes, measured by scored weaknesses surfaced in debriefs.

Without that structure, win rate becomes a shared metric no one is actually accountable for. A single aggregate number reviewed annually rarely changes behavior because no one person owns a specific segment of it.

The measurement cadence matters as much as the ownership model. Quarterly reviews should break win rate by at least two cuts: new business versus recompete, and full-and-open versus set-aside. Annually, layer in contract vehicle and agency. That structure gives each owner a number they can act on, instead of a blended figure that obscures whether the problem sits in pipeline qualification, capture execution, or proposal quality.

How GovEagle Supports Win Rate Improvement Across the Pursuit Lifecycle

The capture-to-proposal continuity gap is a common cause of below-baseline performance: BD intelligence built during qualification, competitive analysis, and PWin scoring often never reaches the proposal team in a usable form. Strategic context stays in CRM notes while writers start from a blank page.

GovEagle keeps bid/no-bid analysis, black hat reviews, and P-Win scoring on the same opportunity as the proposal, so the win themes and capture answers your team saves there shape the draft instead of sitting archived in a pursuit folder. Integrity Defense Solutions, a small, lean defense team, reported roughly 3-4x faster proposal preparation after adopting GovEagle, letting it pursue more opportunities without adding headcount. Precise Software cut SME time on early-stage proposals by 80%. When each proposal takes less staff time, a team can keep its bid/no-bid bar where it is and still respond to more of the opportunities that clear it.

Final Thoughts on Tracking and Improving Your GovCon Win Rate

Many win rate problems trace back to the denominator, not the proposal. Teams that improve tend to bid a smaller, better-qualified set of opportunities, track PWin calibration as a metric in its own right, and use debrief data as a forward input and not a backward record. Your win rate is a lagging indicator, but the decisions that move it happen well before the proposal is written. To see how GovEagle keeps capture work on the same opportunity as the proposal, so the win themes and capture answers your BD team records shape the draft, request a GovEagle demo. That handoff is where small capture gaps tend to compound.

FAQ

How do I benchmark my GovCon win rate against industry averages?

Start by segmenting your submissions: separate new business from recompetes, full-and-open from set-aside, and standalone awards from IDIQ task orders. Then build a baseline from your own last 24 months in each segment. Public figures are thin: award data can't show losing bids, and survey numbers such as the 48% average in Deltek's 2026 Clarity study are self-reported and not broken out by segment. Use outside numbers as rough context and your own segmented baseline as the real benchmark.

How does PWin scoring connect to win rate improvement, and what should I do when my scores are consistently miscalibrated?

Tag each pursuit with its PWin score at bid submission, record the outcome, and run a quarterly comparison by score tier. If your 50-60% bucket closes at 20%, your mid-range scoring is inflated and those pursuits are being carried into the active pipeline when they should be no-bids. Recalibrate by identifying which variables (agency relationship, competitive intelligence depth, pricing position) are driving the inflation, then tighten bid/no-bid thresholds accordingly. Accurate PWin calibration feeds directly into pipeline revenue forecasting; uncalibrated scores consistently overstate projected revenue and mislead capacity planning downstream.

What is the incumbent win rate advantage in federal recompetes, and when does it erode?

Incumbents usually hold an advantage on recompetes, but published figures vary widely: contractor surveys from 2012 to 2016 ranged from about half to three quarters. The advantage narrows with weak CPARS ratings, key personnel turnover, documented performance problems, and LPTA evaluations where price can outweigh the incumbent's relationship and past-performance edge. Track your recompete win rate separately from new business instead of assuming incumbency is a reliable buffer.

How does bid/no-bid discipline raise win rate without changing how proposals are written?

Tightening the bid/no-bid gate changes the denominator before a single proposal section is drafted: submitting fewer, better-qualified opportunities raises average win rate even with no change to proposal execution quality. A functional go/no-go scorecard weighs customer access, incumbent status, scope alignment with verified past performance, competitive intelligence depth, and pricing position relative to known contract history; setting a minimum PWin threshold for new business, for example 40%, creates a hard filter that requires explicit justification to proceed below it. As noted earlier, the 2026 Deltek Clarity Government Contracting Study found that pricing defensibility was the top reason proposals were not selected, which in our view is often a risk you can catch at the bid/no-bid gate.

How do I use FAR Part 15 debriefs to build a win rate benchmarking feedback loop?

Submit a written request within three days of the award notice (or of a preaward exclusion notice), then pull the major weaknesses and deficiencies, any strengths the agency shares, the overall ratings and ranking where disclosed, and evaluation language that flags recurring gaps across similar pursuits. Map those findings back to the original bid decision: if a past performance weakness surfaces across three debriefs on similar agency pursuits, that is a PWin calibration problem, not a writing problem. The loop closes when debrief findings feed forward into the next pursuit's capture strategy instead of into a post-mortem file that no one revisits.