Your IDIQ recompete strategy from two years ago probably needs a refresh. Agencies are retiring vehicles instead of re-soliciting them, the protest environment has grown more active, and small business eligibility rules have changed at the base contract level. If you're tracking any expiring IDIQ vehicles right now, the definitions and trends below are worth your time before you commit to a pursuit.
TL;DR
- Start capture 12 to 18 months before period-of-performance end by pulling expiration data from USASpending or FPDS-NG.
- Challengers win by tackling transition risk directly: named staffing plans, phased knowledge transfer, and continuity milestones tied to deliverable dates.
- Federal vehicle consolidation means some agency IDIQs will be retired at recompete, not re-solicited; confirm the agency's intent before committing to a full pursuit.
- GovDash links post-award contract records to pre-award capture so recompete proposal teams draw from structured CPARS and task area data, with teams seeing up to 60 percent reduction in proposal development time.
What an IDIQ Recompete Is
An IDIQ contract, governed under FAR Subpart 16.5, lets a federal agency place task or delivery orders over a set period without committing to exact quantities at award. The government defines a ceiling value and a timeframe. Within those bounds, agencies call off work as needed. Winning a seat on an IDIQ is, in practice, a license to compete for task orders, not a guarantee of revenue.
A recompete happens when that base contract's ordering period expires. The agency must re-solicit the vehicle competitively, and every bidder, including current holders who have performed work for years, starts from the same line. Incumbency carries influence, but the contract itself resets. According to GovSpend data on federal contract awards in FY25, IDIQ vehicles account for a substantial share of federal obligated spending, which means the stakes at recompete are rarely small.
How the IDIQ Recompete Process Works
The recompete cycle follows a predictable sequence, even if the timeline varies by agency and contract size.
It typically starts months before the ordering period ends. The agency may release a Sources Sought notice or RFI to gauge market interest, refine requirements, or satisfy small business outreach obligations. Contractors who engage at this stage shape the eventual solicitation, which is reason enough to pay close attention well before a formal RFP drops.
The formal RFP or RFQ follows. From solicitation release, proposal due dates generally fall in the 30 to 60 day window, though complex vehicles with multiple volumes can stretch longer. Evaluation criteria vary: best value tradeoff weighs technical and past performance factors against price, while lowest-price technically acceptable awards to whoever clears the bar at the lowest cost.
What Happens After Award
If a new contractor wins, a transition period kicks in. The agency and incoming contractor coordinate a handoff while the incumbent winds down. That window is rarely smooth, and how a challenger plans for it signals execution maturity to the evaluators reading the proposal.
- Sources Sought and RFI responses are not scored, but they inform how the agency scopes Section C requirements and evaluation factors, so substantive engagement here matters.
- Proposal due dates in the 30 to 60 day range leave little room for teams that wait on a kickoff meeting to begin writing.
- Transition plans should name specific mechanisms: staffing timelines, knowledge transfer procedures, and continuity-of-service commitments tied to contract deliverable dates.
Incumbent Advantages in an IDIQ Recompete
Incumbents enter a recompete with assets no challenger can manufacture overnight. The most concrete is a CPARS record tied directly to the program being re-solicited. A string of "Exceptional" or "Very Good" ratings on that specific vehicle carries more evaluator weight than comparable past performance from a different agency or contract vehicle, because it removes the inference gap. The government already knows what the incumbent delivers.
Beyond ratings, there is the harder-to-quantify advantage of relational proximity. Incumbents know the contracting officer's communication preferences, the program office's unstated priorities, and where the prior SOW created friction. That context shapes a more credible technical approach.
According to data from Primer, federal incumbent contractors win roughly 70 to 80 percent of recompetes on average, though that figure varies considerably based on agency, contract type, and actual performance record. The number is real, but it describes a historical pattern, not a given outcome. An incumbent who coasted through performance years, let key personnel turn over, or failed to track new requirements has already surrendered part of that structural advantage before the RFP releases.
"Incumbentitis" and Why Incumbents Lose Recompetes
"Incumbentitis" describes a specific failure mode: the incumbent treats the recompete as a formality, not a real competition. It shows up in predictable ways. The technical approach looks like a contract status report, recycling prior deliverables with updated dates instead of accounting for how the program's requirements have shifted. Pricing increases appear without scope justification. The past performance section narrates contract history instead of making a forward-looking case.
Agencies score every proposal against the published Section M criteria. Prior contract history is one input, not a trump card. A well-prepared challenger who maps directly to evaluation factors can outscore an incumbent whose proposal assumes the relationship does the talking.
"The agency doesn't owe you the recompete. They owe their program a competitive award."
The most vulnerable incumbents are those who stopped listening to the customer midway through the ordering period. Requirements evolve. Priorities shift. If the incumbent's technical approach reflects the program as it existed at original award and not where it stands today, evaluators notice. That gap is exactly where challengers find their opening.
What Challengers Get Right
Successful challengers do a few things that complacent incumbents skip.
- They read the current solicitation as a fresh document and map every proposal section to the updated evaluation criteria, without assuming prior knowledge fills any gap.
- They research how the program's scope, budget, or staffing changed since the original award, then write directly to those changes in their technical volume.
- They price competitively against current market rates instead of mirroring the incumbent's legacy rate structure.
| Factor | Incumbent | Challenger |
|---|---|---|
| Past performance | CPARS record tied directly to the program; "Exceptional" or "Very Good" ratings remove the inference gap | Must cite comparable scale and complexity from other programs; two strong references beat five weak ones |
| Relational proximity | Knows the CO's communication preferences and the program office's unstated priorities | Must build relationships through industry days and Sources Sought responses before the RFP drops |
| Win rate baseline | Wins roughly 70 to 80% of recompetes on average | Must overcome structural disadvantage with a superior technical approach and transition plan |
| Key vulnerability | "Incumbentitis": recycling prior deliverables, raising rates without justification, failing to track requirement changes | Aggressive underpricing that creates a performance problem in the first option year |
| Pricing challenge | Rate increases require concrete justification: wage determination updates, scope expansions, or documented productivity investments | Must model cost basis against the incumbent's published rate structure in USASpending and FPDS records |
| Transition risk | Minimal: no handoff required; continuity is an inherent advantage | Must handle transition risk with a named staffing plan, phased knowledge transfer schedule, and explicit continuity milestones |
| Capture timeline | Should begin briefing the program office 12 to 18 months before period-of-performance end | Should pull expiration data from USASpending or FPDS-NG and engage at Sources Sought stage to shape requirements |
Challenger Strategy for IDIQ Recompetes
Researching the incumbent starts with their CPARS record, which is publicly accessible through FAPIIS. Look for ratings below "Very Good," repeated comments about staffing turnover, or language around "met but did not exceed" expectations. Those are the cracks a challenger's technical approach should widen, not by attacking the incumbent directly, but by proposing a credibly better answer to the same problem.
Transition risk is the agency's biggest concern when considering a switch. A challenger who handles it with a named staffing plan, a phased knowledge transfer schedule, and explicit continuity milestones removes the primary reason an evaluator might default to the incumbent on risk grounds alone.
Past Performance and Pre-RFP Positioning
Past performance selection matters here too. Relevant work at comparable scale and complexity outweighs volume. Two strong references from similar-scope programs beat five references from contracts half the size.
Challengers who show up to industry days and respond substantively to Sources Sought notices before the RFP releases enter the proposal phase knowing how agency priorities have shifted since original award. Those who find the opportunity on SAM.gov the day the solicitation drops are already behind.
Pricing Strategy in an IDIQ Recompete
Pricing a recompete differs from pricing a cold pursuit. The agency holds years of cost data from the prior contract period, which means both incumbents and challengers are bidding against a known benchmark, even if that benchmark is never published.
Incumbents face the sharper challenge. Any proposed rate increases require justification tied to something concrete: a wage determination update, a shift in labor mix, a scope expansion, or documented productivity investments that change the cost structure. Vague increases without clear rationale invite scrutiny during evaluation and can undercut an otherwise strong technical proposal.
Challengers face a different trap. Aggressive underpricing to win the seat often creates a performance problem in the first option year. Contracting officers can reference prior cost actuals when assessing whether a proposed price is realistic. Reviewing price to win tools for government contractors can help teams model these scenarios more precisely. A price that looks attractive but cannot be maintained signals execution risk, not competitiveness.
Price-to-win analysis in a recompete starts with the incumbent's rate structure. USASpending records, prior task order award data, and FPDS entries give you a reasonable baseline for estimating their fully loaded labor rates by category. From there, you model your own cost basis against that range, identify where you have genuine structural pricing advantages, and price to those strengths instead of cutting across the board.
Building an IDIQ Recompete Capture Plan
Agencies typically begin recompete planning 12 to 18 months before the period-of-performance end date. That is your window. Contractors who wait for the RFP to confirm an opportunity exists are already behind the incumbents who have been briefing the program office for a year.
Pull contract expiration data from USASpending or FPDS-NG to map upcoming recompetes before they surface on SAM.gov. According to Primer's recompete radar, systematic expiration tracking is one of the clearest ways to build a forward-looking federal contract pipeline instead of a reactive one.
With a target identified, work through these capture activities in sequence:
- Pull the incumbent's accessible CPARS ratings and note any recurring language around staffing, communication, or "met but did not exceed" performance
- Attend agency industry days and read any Sources Sought responses the government publishes, which often reveal how priorities have shifted since original award
- Identify teaming gaps early, particularly if set-aside eligibility or specialized capability requirements have changed since the prior solicitation
- Develop win themes grounded in the agency's current objectives, not the program's original scope
- Run a formal go/no-go gate review before the RFP drops, using what you learned in capture to score the pursuit without bias
That last step matters more in recompetes than in cold pursuits. You have more intelligence. Use it to make a bid or no-bid decision instead of defaulting to "we're already tracking it."
IDIQ Recompete Trends for August 2026
Three developments are reshaping the recompete calculus heading into August 2026, and contractors who ignore them will find the ground has moved under their proposals.
The most consequential is the federal push to consolidate contract vehicles. Executive direction to reduce redundant acquisition infrastructure means agency-specific MAC IDIQs are increasingly being retired at recompete and not re-solicited. Agencies are redirecting spend toward GWACs and GSA MAS instead. If you are tracking an agency IDIQ contract with an expiring ordering period, confirm the agency intends to recompete it at all before investing in a full pursuit.
That context makes the overall channel numbers worth understanding. According to GovSpend's FY25 federal spending analysis, GWACs and IDIQs combined accounted for $72.4 billion, or 8.6 percent of total federal contracts awarded in FY25. The buying channel remains dominant even as individual vehicles consolidate.
Two other developments matter at the pursuit level. The protest environment around recompetes has grown more active in recent years, with unsuccessful offerors increasingly filing on evaluation methodology and documentation gaps, as reflected in GAO's FY25 bid protest annual report. That raises the bar on source selection documentation and gives challengers more avenues to contest awards they believe were scored inconsistently.
The FAR Part 19 overhaul (Revolutionary FAR Overhaul, effective September 26, 2025) adds another layer for small business set-aside vehicles. The rule eliminated order-level rerepresentation requirements, meaning size status is now determined at contract award and updated only for specific contract-level events rather than at each task order. Contractors with recent size changes should confirm how their current status interacts with any set-aside eligibility conditions on a given vehicle before committing to a recompete pursuit.
How GovDash Supports IDIQ Recompete Workflows
Recompetes punish contractors who treated post-award contract management as a filing exercise. When the RFP drops, they are searching SharePoint for CPARS documentation, reconstructing task area performance from email threads, and asking program managers to recall what changed in year three. That gap between what happened and what is written down costs proposal teams days they do not have.
GovDash's Contract module tracks deliverables, CPARS outcomes, and task area performance in structured records throughout contract execution. When a recompete opens, that institutional knowledge is already organized and searchable inside the Data Library instead of buried across shared drives. The proposal team building the recompete submission inherits everything the program team logged during the prior period of performance without starting from scratch.
Dash AI agents can generate recompete market briefs and past performance narratives directly from those contract records, with every output grounded in and cited back to the organization's own Data Library, keeping human reviewers in the loop at every step. The citations matter here: agencies review past performance claims closely during recompete evaluation, and a narrative that traces to actual contract documentation holds up to that review in a way that a manually assembled summary cannot.
The broader connection is what makes this defensible under time pressure. GovDash links post-award contract performance to pre-award capture, so competitive intelligence, win themes, and pricing scenarios developed during the recompete pursuit are built on the same institutional record the program team maintained. Teams using this connected workflow have seen up to a 60 percent reduction in proposal development time, which matters most on recompetes where the solicitation timeline rarely gives you extra runway.
Final Thoughts on Winning an IDIQ Recompete
Recompetes are won in the months before the RFP, not during the proposal sprint. Your performance record, your customer relationships, and your read on how the program has changed since original award all matter more than a polished cover page assembled under deadline. For challengers, thorough research and a credible transition plan remove the biggest reasons an evaluator defaults to the incumbent on risk alone. If you want to see how GovDash keeps contract performance data organized and ready for recompete submissions, book a demo and we can show you how it works in practice.
FAQs
How do you build an IDIQ recompete capture plan when the RFP hasn't dropped yet?
Start 12 to 18 months before the period-of-performance end date by pulling contract expiration data from USASpending or FPDS-NG. Use that window to pull the incumbent's CPARS ratings through FAPIIS, attend agency industry days, map teaming gaps against any set-aside eligibility changes, and run a formal go/no-go gate review before the solicitation releases, so your pursuit decision is based on real intelligence and not inertia.
What is "incumbentitis" in a federal IDIQ recompete?
Incumbentitis is the failure mode where a contractor treats a recompete as a formality, recycling prior deliverables, raising rates without scope justification, and writing a technical approach that describes the program as it existed at original award instead of where it stands today. Agencies score every proposal against published Section M criteria, so an incumbent whose proposal assumes the existing relationship does the work is vulnerable to a well-prepared challenger who maps directly to current evaluation factors.
GovDash vs. manual SharePoint workflows for tracking IDIQ recompete past performance?
SharePoint stores documents but doesn't connect post-award contract performance to capture or proposal workflows, so teams spend proposal time reconstructing CPARS outcomes and task area performance from scattered files. GovDash's Contract module tracks deliverables, CPARS records, and task area performance in structured records throughout contract execution, making that history searchable in the Data Library when the recompete opens, with Dash AI able to generate past performance narratives cited directly back to those contract records.
Should you price an IDIQ recompete aggressively to beat the incumbent?
Aggressive underpricing to win the seat often creates a performance problem in the first option year, and contracting officers can reference prior cost actuals when assessing whether a proposed price is realistic. A stronger approach is to build price-to-win analysis from the incumbent's published rate structure in USASpending and FPDS records, identify where your cost basis carries a genuine structural advantage, and price to those specific strengths instead of cutting across every labor category.
How do federal contract vehicle consolidation trends in 2026 affect IDIQ recompete strategy?
The federal push to reduce redundant acquisition infrastructure means some agency-specific MAC IDIQs are being retired at recompete and not re-solicited, with spend redirecting toward GWACs and GSA MAS. Before committing to a full pursuit on any expiring agency IDIQ, confirm the agency intends to recompete the vehicle at all, since investing capture and proposal resources in a vehicle the agency plans to consolidate away is a recoverable but avoidable loss.