Understanding Recompetes in Federal Contracting (2026)

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

Somewhere between year four of a contract and the moment an RFP drops, many recompete decisions are already made. The stakes are large: more than 1,000 federal contracts with $100M or more obligated reach the end of their current period of performance by April 2028. Incumbents who treated the performance period as purely a delivery exercise are rebuilding capture context from scratch. Challengers who engaged 18 months out already shaped requirements. Understanding exactly what a recompete is, and how it differs from a bridge, a follow-on, or an option exercise, is where that gap starts.

TLDR:

• A recompete occurs when an agency re-solicits a requirement competitively at contract end; the incumbent holds no contractual right to continue.
• Incumbents start a recompete with real advantages, but poor CPARS ratings, price drift, and key personnel turnover can close that gap quickly.
• Many recompetes are effectively decided before the RFP posts; the capture work that moves PWin happens 12 to 18 months out.
• Cross-reference USAspending.gov, SAM.gov notices and contract award data, and agency forecasts to build a recompete pipeline before a solicitation ever appears.
• GovEagle brings Continuous Monitoring, black hat review, and bid/no-bid analysis into one workspace, and win themes saved on an opportunity feed proposal drafting.

What Is a Recompete in Federal Contracting?

A recompete is a new competition for work an existing federal contract already covers. As the contract nears the end of its period of performance, the requiring agency re-solicits the requirement instead of extending it through options or a bridge contract. The agency publishes a new solicitation, the incumbent and challengers respond, and the work is awarded competitively.

The term appears in several forms across the industry: "recompete," "re-compete," and "contract recompete" all describe the same event. What makes it distinct from a routine option exercise is that competition reopens. The incumbent holds no contractual right to continue the work, regardless of performance history.

Recompete vs. Related Terms: Extension, Bridge, Follow-On, and Rebid

These five terms surface constantly in pipeline reviews, and conflating them puts capture resources in the wrong place. A follow-on mistaken for a routine option, for example, gets ignored until the RFP drops.

Term	What It Means	What Triggers It	What It Signals for Capture
Recompete	Agency re-solicits the requirement competitively at contract end	Period of performance nears its end; agency competes the work again, openly or as a set-aside	Begin capture 12 to 18 months out; incumbents and challengers compete under the same evaluation criteria
Option-Year Extension (FAR 17.207; 17.204-1 under the FAR Overhaul)	Contracting officer exercises a prenegotiated option period	Options remain on the existing contract; within scope and ceiling	Low capture urgency; monitor CPARS and relationship health for the eventual recompete
Bridge Contract	Short-term sole-source or limited-competition award that extends work while the recompete solicitation is prepared	Recompete delayed past contract expiration	Recompete is coming; use the bridge window to shape requirements and deepen agency access
Follow-On Contract	New contract awarded to continue substantially the same work, sometimes without full competition (FAR 6.302-1 or 6.302-2; 6.103-1 or 6.103-2 under the FAR Overhaul)	Unique capability or urgency supports limited competition	May precede a future competed recompete; read the J&A for plans to compete the next contract, and watch for protest risk
Rebid	Informal term for any competitive resubmission, including recompetes	Used interchangeably with recompete in BD conversations	Clarify with the capture lead which formal mechanism applies before resourcing the pursuit

How the Recompete Process Works

Agencies rarely announce a recompete the moment a contract ends. The signal arrives earlier, through a pre-solicitation notice (FAR 5.204; 5.101 under the FAR Overhaul), giving industry advance visibility before the formal solicitation releases. For capture teams, that notice confirms work that should already be underway.

Four phases define the process where contractor action matters:

• Pre-solicitation window: The agency posts a notice on SAM.gov, may issue an RFI or sources sought, and sometimes holds an industry day. Incumbents reinforce relationships here; challengers begin shaping their approach.
• Solicitation release: The RFP drops, usually under FAR Part 15, with Section L instructions and Section M evaluation criteria governing how proposals are structured and scored. Many recompetes are instead task orders under an existing IDIQ or GSA Schedule, with their own ordering rules.
• Evaluation and award: An evaluation team rates proposals against stated criteria, with past performance, technical approach, and price weighted according to Section M, and the source selection authority makes the award decision.
• Transition: The outgoing and incoming contractor execute a handoff period, often 30 to 90 days, during which knowledge transfer becomes both an obligation and a competitive variable.

Many recompetes are effectively decided before the solicitation is published. Teams that engage during the pre-solicitation window influence requirements; teams that wait until RFP release respond to requirements someone else shaped. Response speed in that window matters, since RFIs and sources sought often carry short deadlines: Chevo, a federal Mission Support Services contractor facing 2 to 5 day turnarounds on RFIs, cut RFI prep time by 30 to 40% after adopting GovEagle and reached full team adoption in one week.

What Incumbency Is Worth, and Where It Fails

Incumbents start a recompete with real advantages: documented past performance, agency relationships, and detailed knowledge of the requirement.

The advantage is real, but conditional. LPTA evaluations narrow it where agencies still use them, since lowest-price-technically-acceptable awards reduce the weight of experience in favor of rate competition. Poor CPARS ratings do more damage on a recompete than on a new pursuit because evaluators can directly compare documented performance against the solicitation's requirements. Key personnel turnover carries similar risk; when the faces the program office trusts are no longer on the offer, the relationship advantage erodes fast.

The subtler risk is incumbentitis: the assumption that past performance alone will defend the award. Teams that stop capture activity after award and submit a recompete proposal mirroring the original technical approach are vulnerable to a challenger who has been working the opportunity for 18 months.

Why Incumbents Lose Recompetes

Incumbents can use this list as a self-audit. Challengers can use it to build a black hat assessment.

• Weak CPARS ratings: Marginal ratings signal unresolved performance gaps, and Satisfactory ratings give evaluators little reason to prefer the incumbent. Evaluators compare documented delivery directly against Section M criteria. A challenger with strong past performance at a comparable agency can close the incumbent's advantage quickly.
• Price complacency: Modifications accumulate over a contract period, and the incumbent's loaded rates often drift above market. USAspending shows how obligations and modifications grew over the contract, though not labor rates. Challengers price against obligation and modification trends, not the incumbent's actual rates.
• Key personnel substitutions: The program office built trust with specific names. When those people roll off and the proposal lists replacements, the relationship equity disappears. Evaluators have no documented basis to extend the same confidence.
• Undocumented performance outcomes: Incumbents that fail to capture measurable outcomes arrive at recompete with anecdotes. Challengers who did the research arrive with specific claims about what they will improve.
• Disengaged capture in year four or five: Treating the final performance year as purely a delivery exercise means missing the requirements-shaping window. Challengers who engaged during pre-solicitation can influence what Section C asks for.

The Recompete Capture Timeline

Three distinct phases define recompete capture, and the work that actually moves PWin happens in the first two. By the time a solicitation posts, much of the advantage is already locked in.

12 to 18 Months Before RFP Release

This is relationship and intelligence work. Map the program office contacts who will influence requirements and who see the incumbent's current performance. Challengers should be building agency access from scratch; incumbents should be reinforcing it. Pull USAspending data on the incumbent's contract history, obligation trend, and modification pattern to feed into a structured federal capture planning process that runs through the middle phase.

6 to 12 Months Before RFP Release

Solution shaping and competitive positioning. Submit comments on draft RFPs and respond to any RFI or sources sought. Run black hat analysis against the most likely competitors. Price-to-win modeling should begin here, before the RFP reveals what the agency telegraphed in Section M. Confirm teaming arrangements that close capability gaps identified in the prior phase.

Within 6 Months of RFP Release

Lock teaming, finalize pricing position, and translate capture intelligence into proposal strategy. Win themes should already be drafted before the RFP drops. The proposal team needs the capture artifacts at this stage, not after finishing Section L, consistent with how the Shipley proposal process sequences capture-to-proposal handoffs.

Where to Find Recompete Opportunities Early

Recompete leads surface across multiple data sources, and relying on any single one leaves gaps in your federal pipeline tracking.

USAspending.gov contract expiration data is the most reliable starting point. Filter by NAICS code and agency, then sort by period of performance end date to find contracts approaching expiration. Incumbent, obligated dollars, and contract duration are all visible. The limitation is latency: Defense Department contract data appears after a 90-day delay, so recent DoD awards are often missing.

SAM.gov pre-solicitation notices and sources sought give earlier warning. A pre-solicitation notice signals the agency is preparing a solicitation; a sources sought gauges market capability. Neither is guaranteed: task orders under an existing IDIQ often skip both, and GSA Schedule orders run through eBuy, not SAM.gov.

Agency procurement forecast pages publish planned acquisitions by fiscal year, often naming incumbents, estimated values, and anticipated solicitation windows. Coverage varies widely by agency and forecasts slip, but they surface opportunities months before any SAM.gov notice appears.

FPDS award data rounds out the picture. FPDS.gov's search was retired in February 2026, so search contract awards in SAM.gov by agency and PSC or NAICS code to identify active awards by incumbent, contract vehicle, and end date. USAspending draws its contract records from the same FPDS data, so use whichever search fits the question.

For a ready-made starting list, GovEagle's Federal Recompete Outlook lists the largest federal contracts ending in the next 18 months, with totals by agency and quarter.

The Scale of the Federal Recompete Pipeline

As of November 5, 2026, at least 1,072 federal prime contracts with $100M or more obligated reach the end of their current period of performance by April 2028, carrying about $465 billion in obligations to date. More than 500 of them end within six months, 65 carry $1B or more, and the Department of Defense accounts for 660. These figures come from the Federal Recompete Outlook, which updates monthly.

Each award is a research lead for a possible recompete, follow-on, or extension, not a confirmed solicitation. Periods of performance get extended, bridges get awarded, and some requirements get restructured before they ever re-solicit. The dollar figures reflect obligations to date, not contract ceilings. At this volume, tracking needs a system. A team that waits for a SAM.gov posting on any of these starts behind the incumbent.

How Incumbents Defend a Recompete

Defending a recompete starts the day after award. Incumbents who treat the recompete as a separate writing event lose the advantage incumbency is supposed to provide.

The most common failure is reconstructing performance data at proposal time. Measurable outcomes need documentation throughout the contract: cost savings, delivery timelines, quality metrics, and customer satisfaction touchpoints. By the time the RFP drops, that record needs to be evidence, not anecdotes rebuilt from scattered status reports.

Scope drift and staffing substitutions compound the problem. Modifications accumulate across a five-year contract, and the work an incumbent delivers by year four often diverges from what the original proposal promised. Evaluators scoring the recompete proposal against Section M may notice the gap, so check the current work against your compliance matrix before writing. Key personnel substitutions carry the same risk: the program office built trust with specific names, and replacements listed in a recompete proposal often carry no documented track record with that customer.

Requirements shaping through industry day comments and draft RFP feedback is where incumbent knowledge becomes structural advantage. The delivery team understands the requirement better than anyone, but that institutional knowledge rarely reaches the proposal team in usable form. Capture notes live in CRMs or personal files, performance data stays in program management systems, and proposal writers start from scratch on an opportunity the company has been running for years. Closing that gap before the solicitation posts is the incumbent's most important capture task.

How Challengers Take On a Recompete

Challengers start behind. The incumbent's relationships, performance record, and knowledge of the work are already built into the requirement. Catching up means starting early.

Agency presence is the first variable to close. Responding to sources sought, attending industry days, and engaging program office contacts before a draft RFP exists gives challengers access to the requirement-shaping window incumbents treat as their territory. Without that access, a challenger's proposal responds to requirements the incumbent helped write.

Public signals are where the opening appears for black hat analysis: modification history, protest decisions, and what program staff say at industry days. CPARS ratings and debriefs are not released to other companies, so challengers have to infer the incumbent's performance from indirect signals, mostly what the customer is willing to say. An incumbent with a long modification history or key personnel turnover is vulnerable, and a contract that has accumulated scope changes over five years often carries pricing a clean offer could undercut. Challengers who build black hat analysis around that record arrive at the RFP with a clear case for change.

Teaming decisions deserve the same rigor, and resourcing them correctly is part of what a capture manager does. A challenger without past performance at the target agency can close that gap through a subcontractor that worked the program, provided its people hold roles evaluators can see. Teaming for capability checkboxes without closing the relationship deficit misses how evaluators weigh past performance proximity.

Challengers often leave one advantage unused. When an incumbent has settled into a maintenance posture, a challenger can offer a genuinely fresh approach to documented agency pain points. Incumbents rarely propose structural improvements to a program they are already running. A challenger who spent 18 months understanding those pain points can credibly propose the changes the incumbent hasn't.

How GovEagle Supports Recompete Pursuits

In most recompete pursuits, the same breakdown recurs: capture intelligence gathered over months rarely reaches the proposal team in a form they can use. Incumbent teams lose institutional knowledge to CRM records and program management silos. Challengers researching the incumbent's modification history, obligation growth, and key personnel gaps face the same fragmentation. Neither surfaces automatically when the RFP drops.

GovEagle's BD and capture solution brings Continuous Monitoring of the opportunities you track, black hat review, and bid/no-bid analysis into one workspace, so capture work sits where the proposal team drafts. Win themes saved on an opportunity feed GovEagle's drafting, so writers start from what capture already decided. GovEagle's black hat review profiles likely competitors and the incumbent, maps competitive positioning, and produces a SWOT, discriminators, and a 14/30/60-day action plan. Since adopting GovEagle, Precise Software has won a recompete and a follow-on contract, and it reduced SME time on early-stage proposals by 80%. Integrity Defense Solutions achieved 3 to 4 times faster proposal throughput. Book a Demo to see how win themes saved on an opportunity carry into proposal drafting.

Final Thoughts on the Federal Recompete Process

Whether you're the incumbent or the challenger, the recompete outcome is largely determined by work that happens 12 to 18 months before anyone sees an RFP. Your agency relationships, your performance documentation, and your competitive intelligence either exist by then or they don't. Build your capture workflow around that window.

FAQ

What is a recompete in federal contracting, and how is it different from an option-year extension?

A recompete is when a federal agency re-solicits a requirement competitively after a contract's period of performance ends, meaning the incumbent has no contractual right to continue the work. An option-year extension, by contrast, exercises a prenegotiated period already on the existing contract; competition does not reopen. The distinction matters for capture planning: a recompete warrants active pursuit 12 to 18 months out, while an option year typically signals low capture urgency until the eventual recompete approaches.

How do I find federal recompete opportunities before a solicitation posts on SAM.gov?

Cross-reference three sources: USAspending.gov contract data filtered by NAICS code and agency and sorted by period of performance end date, SAM.gov pre-solicitation notices and contract award data, and agency procurement forecast pages. No single source gives complete coverage, and task orders under existing IDIQs or GSA Schedules often never appear on SAM.gov. By the time a solicitation posts, incumbents have often already shaped requirements, so pipeline visibility depends on catching expiration signals months earlier.

Incumbent vs. challenger recompete strategy: what actually separates the firms that win?

Incumbents usually start a recompete with the edge, but that advantage erodes when CPARS ratings are marginal, key personnel have turned over, or the team treated the final performance year as a delivery exercise and not a capture window. Challengers close the gap by building agency access during the pre-solicitation window, running black hat analysis on the incumbent's USAspending obligation history and modification record, and teaming with subcontractors who have direct program experience beyond capability checkboxes.

How can proposal automation tools help federal contractors manage overlapping recompete pursuits without rebuilding capture context from scratch each time?

Keep capture work in the same workspace as the proposal. GovEagle brings Continuous Monitoring, black hat review, and bid/no-bid analysis into one workspace, and win themes saved on an opportunity feed proposal drafting, so each new solicitation starts from what capture already knows.