How to use the old contract without blindly dragging old requirements, old assumptions, and old problems into the new acquisition.
It's tempting to copy the old contract and call it a head start. Sometimes the old file is useful. It shows what the Government bought, how the contractor performed, what the quantities looked like, and what the last team thought mattered.
But a recompete isn't a photocopy. Regulations change. The market changes. Prices change. Technology changes. The mission changes. The contractor's performance teaches lessons. And many service contracts run for years, often a base year with options, which is plenty of time for the old package to become stale.
One framing note before we go further: if you've been tracking your contract portfolio (covered in the timeline training), this recompete was on your radar months ago. The option dates were on your spreadsheet, the end date was on your calendar. If you haven't been tracking, the option dates probably surprised you, and the rest of this page turns into a fire drill instead of a normal acquisition. Either way, this is the work.
Working from the old package isn't bad practice. Starting from nothing when the Government already has years of contract history can waste time. The problem comes from treating the old package like it's still correct.
Use the old documents to ask better questions:
Right now is probably one of the worst times to blindly copy an old contract. The FAR overhaul changed structure and language. Agency deviations and class deviations may have moved requirements. Thresholds have changed. Cybersecurity, CUI, privacy, software, supply chain, and labor expectations keep moving.
Even if the contract text still looks familiar, the acquisition environment around it may not be the same.
RFO FAR Part 10 still points the acquisition team back to market research appropriate to the circumstances. A recompete isn't exempt from that just because the Government already bought something similar last time.
Most recompete packages get stale in predictable places. Start here.
| Area | What might have changed | Why it matters |
|---|---|---|
| Mission need | Different workload, mission priority, users, hours, locations, quantities, or performance expectations. | The old PWS may no longer describe the real work. |
| Market | New vendors, new commercial practices, new technology, supply chain shifts, changed pricing, or market consolidation. | Old market research can hide better competition or better solutions. |
| Performance history | Turnover, poor supervision, late deliverables, quality problems, invoice disputes, or lessons from CPARS (Contractor Performance Assessment Reporting System) ratings. | The new requirement should fix known pain instead of re-buying it. |
| Rules and policy | RFO changes, thresholds, clause updates, wage determinations, cybersecurity, CUI, privacy, or agency guidance. | The old solicitation may point to stale rules or miss new requirements. |
| Funding and price | New budget reality, inflation, labor rates, escalation, option structure, or changed funding source. | The old IGCE may not support the new acquisition or funding request. |
| Schedule | Option dates, expiring contract period, transition time, lead times, protest risk, or customer review delays. | Late planning creates bridge pressure and weakens strategy choices. |
Treat the prior contract as evidence, not just a template. The customer should look at how the incumbent actually performed and decide what the follow-on package should learn from that performance.
If retention was a problem, the new acquisition may need a sharper staffing approach, key personnel controls, or an evaluation factor around recruiting and retention.
If the COR kept finding the same defects, the PWS standards or QASP methods may need to change.
If deliverables were ignored, late, or unusable, rewrite the deliverable matrix instead of copying it.
If transition was rough last time, build transition evidence, milestones, or acceptance points into the follow-on.
Example: if a janitorial contract struggled because the contractor could not retain night-shift cleaners, the answer may not be "copy the same PWS." The new package might need better staffing expectations, a QASP that checks vacancy-driven failures, and an evaluation factor that asks offerors how they recruit, retain, and backfill for high-turnover positions.
This is the practical checklist. If you are recompeting old work, review these before sending the package forward.
"We already have a contract" is a fact, not market research. The fact may help the research — you know who performed, what worked, what didn't, and what scope the Government really used — but the research still has to happen on the recompete.
For a recompete, market research should answer:
Ask industry what changed. Not "can you do this exact old PWS?" Ask whether the old approach still reflects current commercial practice, where vendors see risk, and what information they need to price the follow-on cleanly.
Recompetes often become emergencies because nobody started early enough. The old contract end date isn't a surprise. The option dates aren't a surprise. The recompete shouldn't become a panic because the customer waited until the last quarter to start thinking.
Bridge contracts can be useful when the file supports them, but they aren't automatic. They cost time, money, and leverage. They can also reduce competition if industry sees the Government as disorganized or already committed to the incumbent.
| Schedule item | Review question | Why it matters |
|---|---|---|
| Period of performance end | When does the current contract actually end, including options? | Everything works backward from this date. |
| Transition time | How long would a new contractor need to start cleanly? | Award date isn't the same as full performance readiness. |
| Evaluation time | Who will evaluate proposals, and are they available? | Customer evaluators are often the bottleneck. |
| Protest or delay risk | Is the acquisition complex, high-dollar, incumbent-heavy, or likely to draw attention? | Risk should be built into the schedule before it becomes a bridge request. |
One more thing customers often forget: when a new contractor wins, the customer side has transition work too. Workspace, badging, system access, knowledge transfer from the incumbent (where possible), training, and equipment or property handover. The contractor's transition plan only covers their side. Plan yours — the first 30 days of performance can blow up if the customer isn't ready to let the contractor actually start working.
Send contracting the old documents only after you've annotated them with what changed, what worked, and what failed.
The incumbent's performance should inform the follow-on, but the follow-on still has to compete fairly. Don't write the new package around the incumbent's internal process unless that process is truly the Government's minimum need and can be justified.
Before you send the recompete package, mark every copied section as "keep," "revise," or "delete." If nobody can explain why a copied section still belongs, it doesn't belong yet.