- Waiting for the RFP means the positioning window has already closed
- Ceiling utilization is the earliest and most-ignored recompete signal
- Option year delays signal incumbent dissatisfaction or budget uncertainty
- A bridge contract typically signals a coming recompete, not stability
- Quarterly ceiling burn tracking beats monitoring end dates alone
A contract with two years left on its period of performance can already be dead — not administratively, but obligationally. If an agency has burned through 90% of an IDIQ’s ceiling with two years still on the calendar, the vehicle is functionally finished, and the agency will be back in the market long before that end date arrives. Most teams don’t clock this until the solicitation posts, by which point the incumbent has an eighteen-month head start.
Why Is Waiting for the RFP to Post Already Too Late?
The real opportunity window opens when timing signals first appear, not when the RFP does. By the time a recompete shows up on SAM.gov, the incumbent has had months to shore up past performance and shape the requirements the agency is about to publish. Competitors watching the same agency and PSC code are already building teams. You’re reading a headline everyone else priced in months ago.
Most federal contract actions, by transaction count, never draw a second bidder, so the real competitive window opens early, not at solicitation. The table below shows roughly how far ahead each signal appears relative to posting.
| Signal | Typical Lead Time Before RFP Posts | What It Tells a Capture Team |
|---|---|---|
| Ceiling utilization approaching cap | 12–18 months | Agency will hit the ceiling before the period of performance ends |
| Option year exercised late or skipped | 6–12 months | Agency confidence in the incumbent or vehicle is wavering |
| Period of performance end date nearing | 0–3 months | Public confirmation of what smart watchers already knew |
| Solicitation posted on SAM.gov | Day zero | Positioning window has effectively closed |
What Are the Three Signals That Predict a Federal Contract Recompete?
Three data points, tracked together, predict a recompete months before any public notice: end dates, option year behavior, and ceiling utilization. Each alone is weak; together, they’re close to reliable.
Period of performance end dates
The end date is the baseline everyone tracks, and it’s the least useful signal alone. FPDS and SAM.gov fields get updated late, sometimes never, and a “final” end date can slip through an unannounced extension. Treat it as a floor, never a ceiling.
Option year exercise patterns
An agency exercising options on schedule, year after year, signals stability. One that lets an exercise decision slide months past deadline is often signaling budget uncertainty or dissatisfaction with the incumbent. Pattern recognition across years of award data is exactly the kind of work machine learning now does at scale in procurement analysis, faster than checking modification histories by hand.
Ceiling utilization on IDIQs
This is the signal most teams ignore. An IDIQ ceiling is a spending cap, not a promise to spend — FAR doesn’t obligate an agency to get near it. Once obligations close in on that number, the agency has three moves left: raise the ceiling by modification, let the vehicle run dry, or recompete. Obligations climbing toward a known ceiling, regardless of time remaining, is the earliest reliable tell in the framework.
Explore $492B in federal IT spend
Try FedSpend free for 14 days. Full dashboard access, no credit card required.
How Does FedSpend Show Ceiling Utilization and Obligation Trends in Practice?
FedSpend’s agency-spend views track obligations by PSC and NAICS code across fiscal years, flagging accelerating ceiling burn before an end date ever moves. A capture team sees how spend in a target agency’s service category trends year over year, instead of checking one contract file at a time.
The VA illustrates this, using FedSpend’s agency-spend dataset as of September 2026. Its total IT-related obligations held nearly flat between fiscal 2024 and fiscal 2025 — $9.46 billion to $9.40 billion — but that topline number hides a real shift.
| PSC Code | Description | FY2024 Obligations | FY2025 Obligations | YoY Change |
|---|---|---|---|---|
| DA01 | Business application dev support (labor) | $3.03 billion | $2.83 billion | −6.4% |
| DA10 | Business application SaaS | $1.07 billion | $2.16 billion | +102.8% |
| Agency-wide total | All IT-related PSCs | $9.46 billion | $9.40 billion | −0.7% |
VA’s SaaS-code obligations more than doubled year over year across 12,975 transactions in FY2025, while labor-based application development spend contracted. A flat agency total tells a capture team nothing; the PSC-level breakdown shows where money is actually moving. A basic watchlist needs only four fields: incumbent, agency, NAICS/PSC combination, and a timing estimate built from that trend line.
How Do You Build a Recompete Alert Workflow?
A working recompete alert system is a short, repeatable checklist, not a dashboard you check once. The discipline of running it on schedule is what most teams skip.
- Identify target incumbents by agency, NAICS, and PSC where your firm has a credible teaming position.
- Log baseline data: award ceiling, cumulative obligations, end date, and option year history.
- Review quarterly, checking obligations against the ceiling and option exercise timing.
- Cross-reference obligation trends against public award notices for context numbers alone don’t explain.
- Flag contracts crossing roughly 75–80% ceiling utilization for active capture planning.
That fourth step matters most. A rising ceiling doesn’t always signal a recompete — sometimes the opposite. The VA’s August 2026 modification to its Oracle EHR contract, raising the ceiling by $17 billion to nearly $27 billion, is a textbook case of an agency extending a vehicle rather than heading to market. Reading that as a recompete signal sends a team chasing the wrong opportunity. Tools like Sentry keep that distinction visible instead of buried in a modification record nobody reads.
What Mistakes Cause Capture Teams to Miss a Recompete Signal?
Three habits reliably cause teams to miss recompetes they should have seen coming.
- Trusting FPDS/SAM.gov period-of-performance fields at face value. These fields go stale or go unupdated after an extension — a common way to get blindsided.
- Reading a bridge contract as stability. A short extension is usually the opposite; it’s often the clearest sign an agency is buying time while structuring a recompete.
- Confusing a scope change or ceiling increase with a true recompete. Tools that only surface opportunity postings, not the underlying spending pattern, miss this — the core difference between an alert feed and genuine spend-pattern visibility.
Recompete Tracking Is a Discipline, Not a Calendar Reminder
Teams that only watch end dates are structurally late — by design, since the end date is the last signal to move, not the first. Teams watching ceiling utilization and option year behavior alongside it get months of runway to build relationships, price competitively, and shape a requirement before it’s frozen in an RFP. That’s the same foothold logic behind landing a smaller contract to build past performance ahead of a bigger recompete. It’s a quarterly habit, not a one-time project — and the firms treating it that way are in the room before the solicitation gets written.