# The Contract Award Lead Run, From Award Notice to a Matched Requisition ID

*After one weekly cycle you will have a dated lead sheet where every award has a winner, site, scope, and start date, and only leads with a matched requisition ID say Apply.*

- Canonical URL: https://www.refolk.ai/candidates/guides/contract-award-lead-run
- Pillar: Reading the market
- Format: Playbook
- Published: 2026-11-13
- Last reviewed: 2026-11-13
- Reading time: 19 min
- Keywords: how to find jobs from government contract awards, find out who won a federal contract to apply for jobs, contract recompete job search incumbent, defense contractor jobs before they are posted, what happens to my job when the contract changes hands

## Key takeaways

- Defense awards appear on USAspending about 90 days late, so for DoD work the free daily contracts page, posted on business days around 5 p.m. Eastern, is the only same-day record of who won.
- The DoD daily list only announces actions with a face value over $9 million, excluding unexercised options, so smaller awards and most IDIQ task orders never appear there.
- No award lead should be tagged Apply until a requisition ID on the winner's own career site matches the program, place of performance, and clearance level.
- The nondisplacement rule giving workers on an outgoing service contract a right of first refusal was rescinded, so the surviving protections are the SCA section 4(c) wage floor and the successor's right to interview incumbents on site.
- A sustained bid protest can stall a confirmed award for up to 100 days, or 65 on the express option, so competitive awards with several offers stay at Watch until the protest window closes.
- In Refolk's index of professional profiles, Program Managers with TS/SCI in the headline outnumber TS/SCI Systems Engineers 3.8x, and 28% of that Program Manager sample works directly for the Air Force rather than a contractor.

This is the weekly run for people in government contracting or defense who want to find jobs from government contract awards before the openings show up on job boards. It starts with the DoD daily award notice and the civilian award databases and ends with a dated lead sheet. Every lead on that sheet is tied to a named winner, a place of performance, a scope mapped to your role, and a start date. One rule covers the whole sheet: a lead is never tagged Apply until you find a matching requisition ID on the winner's own career site.

## What counts as a contract award lead?

A contract award lead is a public record that a named company has won, or is about to recompete, work that matches your role in a place you can commute to. It tells you hiring may happen. It doesn't tell you there's an opening.

A few terms, defined once:

- **Period of performance:** the dates the contract work runs, from start to completion.
- **Place of performance:** where the work is actually done. This is often not the awardee's address.
- **Recompete:** a new competition for work that is already under contract. The company that holds it now is the **incumbent**.
- **Requisition ID:** the employer's internal number for an approved opening, shown on the posting on its career site.
- **IDIQ:** an indefinite-delivery, indefinite-quantity contract. It sets a ceiling and funds work later through individual task orders.

Each lead on your sheet gets one of three tags:

| Tag | Condition | What you do |
|---|---|---|
| Apply | Award confirmed, requisition ID matched | Apply to that requisition this week |
| Watch | Award confirmed but no requisition yet, contingent posting, or protest stay possible | Set a next-check date |
| Drop | Wrong scope, outside radius, modification, or unfunded ceiling | Remove and note why |

> **Rule:** No requisition ID, no Apply
>
> An award never counts as an opening until a posting on the winner's own career site matches its program, place of performance, and clearance level, and you have recorded that posting's requisition ID.

The rule exists because the gap between an award and a real opening is wide and unmeasured. Nobody has published the share of award-linked leads that never get a public requisition. Contractors can also start clearance processing for people while they are still bidding, under 32 CFR 117.9(e)(1). So some hiring activity happens before any award, and some awards never turn into a public posting.

> An award is a hypothesis about hiring. A requisition ID is the only proof the hiring is real.

## Which free award feeds should a job seeker read, and when?

For defense work, read the DoD daily contracts page every business evening. For civilian agencies, pull USAspending or SAM.gov Contract Awards once a week. The order matters because USAspending and SAM.gov show defense awards about 90 days after they happen.

| Feed | What it covers | Access | When it is current |
|---|---|---|---|
| DoD daily contracts page | DoD actions over $9M face value | Public | Business days, around 5 p.m. ET |
| USAspending.gov | All agency award data | No account | Civilian: days. DoD and USACE: +90 days |
| SAM.gov Contract Awards | Same award data, more search fields | Free login via Login.gov | Civilian: days. DoD: +90 days |
| SAM.gov Wage Determinations | Service Contract Act pay rates by locality | Public | Check per lead |

### The DoD daily contracts page

The DFARS requires DoD components to announce contract actions with a face value over $9 million, excluding unexercised options. That includes modifications. The threshold is adjusted for inflation and used to be $7.5 million, and older pages still quote the old figure. Read the current text of DFARS 205.303 to confirm it before you assume anything is missing. The regulation only says components submit announcements by close of business the day before the proposed award. The 5 p.m. Eastern posting time and the absence of weekend and federal-holiday postings come from secondary sources, so treat them as a habit that can change, not a rule.

Each announcement can carry fields that are useful to a job seeker:

- The winner and the contract number.
- The place of performance, where significant work is done somewhere other than the awardee's location.
- The number of solicitations mailed and the number of offers received. This matters for protest risk.
- The expected completion date.

What it leaves out: under an IDIQ, individual orders aren't announced until the estimated value is reached. Classified awards never show up in the public databases at all. One practitioner source describes the daily page as naming winners weeks before the same award becomes visible in SAM.gov and USAspending. That matches the documented 90-day display delay for DoD and Army Corps of Engineers data. GAO had already flagged the undisclosed DoD delay in GAO-20-75.

### USAspending and SAM.gov Contract Awards

The public FPDS search has been retired, and its contract-award search now lives in SAM.gov Contract Awards. The legacy FPDS ATOM feed is being replaced by the SAM.gov Contract Awards API. In SAM.gov you can search by solicitation ID, Procurement Instrument Identifier, supplier name, Unique Entity Identifier (UEI), CAGE code, agency, date, NAICS, PSC, place of performance, or competition field. You need a free account created through Login.gov.

USAspending carries the same award data with no account. Its records include place of performance, industry (NAICS), product or service, and set-aside type. I haven't verified the exact USAspending filter names for period-of-performance start and end dates or for number of offers. Open the advanced search and check which filters exist before you build your weekly query around them.

#### Lead order for a defense award

1. **Daily list** - Winner named the same evening, contract number logged
2. **Scope and radius** - Work description mapped to role, place of performance checked
3. **Career site** - Winner's postings searched for program, place, clearance
4. **Requisition match** - ID recorded, lead moves to Apply
5. **Database confirm** - Record appears on USAspending about 90 days later

*For defense awards the daily list and the winner's career site come first, because the databases show DoD awards about 90 days after the fact.*

## The weekly run, step by step

The run has eight steps. One happens every business evening, and the rest happen once a week. Using the dossier's time budgets, that comes to roughly 2 to 2.5 hours of fixed time a week, plus about 35 minutes for each lead that survives the radius filter.

#### Contract award lead run, one weekly cycle

1. **Read the DoD daily contracts list** - Each business evening after the posting, copy every action matching your NAICS codes or role keywords, with winner, place of performance, contract number, and completion date. 10 to 15 minutes.
2. **Pull civilian awards weekly** - Filter USAspending (no login) or SAM.gov Contract Awards (free login) by NAICS or PSC plus place-of-performance state. Done is rows with awardee UEI and dates, in about 30 minutes.
3. **Map scope to role and commute** - Keep only work descriptions your role would staff, and drop any place of performance outside your commute radius. About 20 minutes.
4. **Check protest exposure** - Count 10 days from award, or 5 days after a required debriefing, whichever is later. If the award was competitive with several offers, allow up to 100 days of delay. 10 minutes per lead.
5. **Find recompetes** - Use SAM.gov award records to find contracts whose period of performance ends in the next 6 to 18 months, and log the incumbent. About 30 minutes.
6. **Look up the SCA wage determination** - For service roles, record the wage determination number and your occupation's rate and fringe for the place of performance. About 10 minutes per lead.
7. **Match a requisition ID** - Search the winner's own career site for the program name, contract vehicle, location, and clearance level, and record the requisition ID. About 15 minutes per lead.
8. **Tag and date the sheet** - Tag each lead Apply, Watch, or Drop, and put a next-check date on every Watch. Done is a dated sheet.

Most guides to award data are written for companies chasing bids. They treat the DoD feed as a trigger and then go to the database to confirm. For a job seeker looking at defense work, that order is a quarter too slow. Step 2 can't confirm a DoD award for about 90 days, so for defense leads run steps 1 and 7 first and let the database confirm later. For civilian leads the database is close to current, because agencies report on cycles measured in days, so step 2 is your primary source.

On the recompete window in step 5: 6 to 18 months is a practitioner convention. No regulation or published study sets it. Use it as a starting filter, and tighten or widen it once you see how far ahead the contractors in your niche post transition roles.

## How long from award to first day?

No published figure exists for the typical gap between a contract award and the start of the period of performance. You bound it with three documented clocks: the protest window, the protest decision, and the handover period.

| Event | Window | What it means for your lead |
|---|---|---|
| DoD announcement | Business days, around 5 p.m. ET | Winner is public the same evening |
| CICA stay trigger | 10 days after award, or 5 after debriefing | Lead stays at Watch until this passes |
| GAO protest decision | Up to 100 days (65 express) | A protested award can stall a full quarter |
| Phase-in and phase-out | Up to 90 days after expiry | Handover overlap on recompetes |
| DoD on USAspending | +90 days | Database confirmation lags the daily list |

### Reading the protest clock

An automatic stay under the Competition in Contracting Act (CICA) applies if a losing bidder protests within 10 days after award, or within 5 days after a requested and required debriefing, whichever is later. While the stay is in place, the winner can't start performance. The stay lasts until GAO decides, which takes up to 100 days, or 65 on the express option.

To estimate exposure, check the "offers received" field on the DoD announcement. A sole-offer award has no losing bidder to protest. An award with several offers does. Until the window closes, a requisition for that program may be live while the work itself is frozen. Look for the solicitation number on GAO's bid protest docket. I haven't verified the exact search path there, so confirm it the first time you use it.

### Reading the handover clock

On a recompete, FAR 52.237-3 lets the government require the incumbent to provide phase-in and phase-out services for up to 90 days after its contract expires. That overlap is when the successor recruits. It's also when it interviews the incumbent's people on site, which is covered in the next section.

## What happens to my job when the contract changes hands?

You have no guaranteed right to be rehired by the incoming contractor. The rule that created a right of first refusal for workers on service contracts, 29 CFR part 9, was rescinded at 90 FR 59734. Two narrower protections survive: a pay floor and a right for the successor to interview incumbents on site.

In practice, the rescission changed less than it sounds. The Labor Department said it was unaware of any solicitation that had ever incorporated the nondisplacement provisions. Workers lost a protection that, as far as anyone has shown, was never used. Incumbents keep their jobs through a recompete because bidders want named, badged people they can staff on day one, not because a rule forces it.

What survives:

- **The SCA section 4(c) pay floor.** A successor contractor in the same locality must pay at least the wage rates and fringe benefits in the predecessor's collective bargaining agreement (CBA). That holds even if the contracting agency fails to incorporate the 4(c) wage determination, and even if the same contractor wins the successor contract. It only applies where a predecessor CBA existed.
- **On-site interviews during handover.** Under FAR 52.237-3, the outgoing contractor must disclose necessary personnel records and allow the successor to conduct on-site interviews with its employees.
- **Vacation service credit.** SCA wage determinations count continuous service with predecessor contractors doing similar work at the same federal facility toward vacation eligibility.

> **Watch out:** Do not plan around incumbent rehire
>
> If you are on the outgoing contract, treat the successor as a new employer you have to win. Get your resume to the successor's recruiters during the phase-in window, and look up the wage determination so you know your floor before they make an offer.

Wage determinations are public on SAM.gov. Look one up by place of performance, find your occupation's rate and fringe, and write both on the lead. If the successor's offer comes in below a 4(c) floor that applies to you, you have a documented number to point to.

## Which clearance tier and region are you competing in?

In Refolk's index of professional profiles, Systems Engineers who put TS/SCI in their headline outnumber those who put Secret clearance 3.2x, and the two groups cluster in different regions. The radius filter in step 3 therefore decides more than distance. It also decides which talent pool you're up against.

| Title and headline keyword | Matching US profiles | Top employer in sample | Top region in sample |
|---|---|---|---|
| Systems Engineer, TS/SCI | 61 | Lockheed Martin, 4 of 25 | Colorado, 5 of 25 |
| Systems Engineer, Secret clearance | 19 | General Dynamics Mission Systems, 2 of 19 | DC-Baltimore, 4 of 19 |
| Ratio TS/SCI to Secret | 3.2x (derived) | | |

In the TS/SCI sample, the Colorado profiles were in Colorado Springs (2), Peyton (2), and Denver (1), against 2 in DC-Baltimore. The Secret sample leaned the other way. These samples are small, so read them as a pattern to check against your own market, not a measurement.

**3.8x - TS/SCI Program Managers per TS/SCI Systems Engineer in Refolk's index**

231 US profiles titled Program Manager put TS/SCI in their headline, against 61 titled Systems Engineer.

| Title, TS/SCI in headline | Matching US profiles | Share of sample at a government employer |
|---|---|---|
| Program Manager | 231 | US Air Force, 7 of 25 (28%, derived) |
| Systems Engineer | 61 | US Air Force, 2 of 25 (8%, derived) |
| Multiple | 3.8x (derived) | |

The next most common employers in the Program Manager sample were CACI and TekSynap, with 2 each. My inference, which the data suggests but doesn't prove: many of the most visible TS/SCI program managers sit on the government side. A contractor-side program manager requisition tied to an Air Force award is probably drawing from a pool that includes them. If you're a contractor-side program manager, lead with the delivery and contract-management detail that a government-side candidate can't show.

## Matching an award to a requisition ID

An award becomes an opening only when a posting on the winner's own career site names the same program or customer, the same place of performance, and a compatible clearance level, and carries a requisition ID you can record. Each posting signal proves something specific, and each one can mislead you.

| Posting signal | What it proves | How it misleads |
|---|---|---|
| Program or customer name in the title | The company is staffing that program | May have been posted while bidding, before any award |
| "Contingent upon contract award" | The company is bidding or planning | Can be resume collection for a proposal it loses |
| Clearance level, e.g. "Active Secret" | The tier the role needs | Shared by many programs, so it identifies none |
| A requisition ID on the winner's site | An approved, trackable opening | Only misleads if the program or place does not match |

A real example of the program-name pattern is "Program Manager, NAWCAD Mission Systems (Contingent Upon Award)". It names the customer and admits it's still contingent. Some proposal-stage postings say outright that if the contract is awarded, another position posting will be available on the company careers site. Treat that sentence as an instruction: the requisition you want hasn't been posted yet.

**Career-site search strings for one award lead**

```
"<program or customer name>" <place of performance city>
"<contract vehicle name>" <clearance level>
"contingent upon award" <customer name>
<your role title> <clearance level> <place of performance city>
<your role title> <place of performance city> transition
```

*Run each line in the winner's own career-site search, replacing the angle-bracket fields with values from the award record.*

Once a requisition matches, the work turns into a normal application, and the posting's own language is what you tailor to. [Refolk](/candidates) builds a resume from your own history, tailors it to that specific requisition, drafts the cover letter, and scores how well you actually fit. That last part helps you decide whether an Apply lead deserves the effort before you spend it.

## How the run goes wrong: failure modes and false positives

Most bad leads come from reading a record as something it isn't. The eight failure modes below account for nearly all the false positives in an award run. Each one has a check that takes a few minutes.

1. **Stale threshold.** If you use the old $7.5 million figure, actions between $7.5 million and $9 million look like they're missing from the daily list. They were never required to be there. Check: read the current DFARS 205.303 text before you set expectations for what the feed contains.
2. **Modification read as a new award.** Option exercises and modifications appear in the daily list, but they extend existing work and add no headcount. It shows up as a familiar contract number with the word "modification" and a cumulative face value. Check: search your sheet for the contract number. If it's already there, the action isn't a new lead.
3. **IDIQ ceiling read as funded work.** Multiple-award IDIQ announcements list many winners sharing one large ceiling, and orders under the estimated value aren't announced. The false positive looks like 10 or more awardees on a single big number. Check: drop it unless a specific task order with a place of performance is visible.
4. **Absence read as no award.** A DoD award that's missing from USAspending is normal for about 90 days, and classified awards never appear. Check: look up the contract number in the daily list archive instead of the database.
5. **Protest blind spot.** A lead goes to Apply during a CICA stay and then stalls for up to 100 days. Check: on any award with several offers, search GAO's protest docket for the solicitation number and keep the lead at Watch until the window closes.
6. **Contingent posting read as an opening.** "Contingent upon award" requisitions can be collecting resumes for a proposal. Check: keep them at Watch until the award to that same company is announced.
7. **Headquarters address read as place of performance.** The awardee's address is where the company is registered, not where the work happens. Check: use the place-of-performance field only, both for the radius filter and for the wage determination.
8. **Assuming incumbent rehire.** Nondisplacement no longer applies. Only the SCA 4(c) wage floor survives, and only where there was a predecessor CBA. Check: if you're the incumbent, apply to the successor like any other candidate.

> **Tip:** Log the contract number first
>
> The contract number is the one field that joins the daily list, the database record, a protest docket entry, and a recompete search. Capture it on every row, even for leads you expect to drop.

Failure modes 2 and 3 hit hardest on the daily list, because it reads like a stream of new wins. Failure modes 4 and 5 hit hardest in the weeks right after an award, which is exactly when you're most eager to apply.

## Tagging the sheet and keeping it current

The sheet is done when every lead has a tag, a source, a date, and, for every Watch, a next-check date. Each week you rerun steps 1 through 8, update your existing Watch leads first, and then add new ones.

#### Tagging a lead

Horizontal axis runs from No requisition match to Requisition ID matched. Vertical axis runs from Award unconfirmed or stayed to Award confirmed and clear.

| Quadrant | What it means |
| --- | --- |
| Confirmed, no requisition | Watch, recheck the career site weekly |
| Confirmed and matched | Apply this week, tailored to that posting |
| Unconfirmed, no posting | Drop, or Watch if a recompete is in window |
| Posting ahead of award | Watch until the award to that company is announced |

*Only a confirmed, unstayed award with a matched requisition ID earns Apply; everything else waits or goes.*

**Lead sheet entry**

```
Run date:
Lead number:
Source: DoD daily list / USAspending / SAM.gov Contract Awards
Contract number:
Solicitation number:
Winner and UEI:
Award date:
New award or modification:
Offers received:
Place of performance:
Work description, mapped to my role:
Protest window closes:
Period of performance start / end:
Incumbent (recompetes only):
SCA wage determination number and my floor:
Requisition ID and posting title:
Tag: Apply / Watch / Drop
Reason for tag:
Next check date:
```

*One block per lead; copy the run date to the top of the sheet each week and leave unknown fields blank rather than guessing.*

Some figures here can go stale, and you should recheck them on a schedule rather than trusting this page. The DoD announcement threshold is inflation-adjusted, so read DFARS 205.303 whenever you notice the daily list getting thinner or thicker. Award search keeps moving between federal systems, so if a SAM.gov or USAspending filter disappears, look for the replacement before assuming the data is gone. The Refolk index figures are point samples. Rerun the comparison for your own title and region before you lean on them.

When several Apply leads arrive in the same week, compare them on fit before you write anything. Refolk scores how well your history matches each requisition, so you can put your best application into the leads where you actually fit and not waste it on the first one that matched.

#### Before you call this week's sheet done

- [ ] Every lead has a contract number and a dated source.
- [ ] Place of performance came from the place-of-performance field, not the awardee's address.
- [ ] Modifications and option exercises are dropped or marked as no new headcount.
- [ ] Multiple-award IDIQ ceilings are dropped unless a specific task order is visible.
- [ ] Every award with several offers stays at Watch until its protest window has closed.
- [ ] No DoD lead was dropped only because it is missing from USAspending within 90 days.
- [ ] Every contingent-upon-award posting is at Watch until the award to that same company is announced.
- [ ] Every service-role lead has a wage determination number and a dollar floor.
- [ ] Every recompete lead names the incumbent and the period-of-performance end date.
- [ ] Every Apply lead has a requisition ID from the winner's own career site.
- [ ] Every Watch lead has a next-check date.

## Frequently asked questions

### How do I find out who won a federal contract so I can apply for jobs there?

For defense work, read the DoD daily contracts page each business evening. It names the winner, the contract number, and the place of performance on the day of announcement. For civilian agencies, search USAspending with no login, or SAM.gov Contract Awards with a free account, filtered by NAICS or PSC and place-of-performance state. Then search the winner's own career site for that program and record a requisition ID before you treat the award as an opening.

### Why can't I find a DoD contract award on USAspending?

USAspending shows Department of Defense and Army Corps of Engineers contract data about 90 days late, so a missing DoD award is normal for roughly a quarter. Classified awards never appear at all. Log the contract number from the DoD daily list and check the daily list archive by that number. Don't drop the lead because the database is empty.

### Do I keep my job if my contract is recompeted and another company wins?

Not automatically. The rule giving service contract workers a right of first refusal with the successor contractor was rescinded, and the Labor Department said it knew of no solicitation that had ever included it. What remains: the outgoing contractor must let the successor interview its employees on site during transition, and where a predecessor collective bargaining agreement existed, the successor must pay at least those wages and fringe benefits.

### Should I apply to defense jobs marked contingent upon contract award?

You can submit, but don't count it as an opening. Contingent postings are written while a company is bidding. Some of them are collecting resumes for the proposal, and the company may never win. Keep these at Watch until the award to that same company is announced. Some of these postings say a new posting will go up on the company's careers site if the contract is awarded, so watch for that requisition.

### How long after a contract award does hiring actually start?

There is no published typical figure. You can only bound it. A protest filed within 10 days of award, or 5 days after a required debriefing, triggers an automatic stay that can last up to 100 days, or 65 on the express option. On a handover, the outgoing contractor can provide phase-in and phase-out services for up to 90 days after its contract expires. Track each lead's period-of-performance start date instead of assuming one.

---

*From the Refolk guide library. I revise these guides rather than replacing them, so the current version is always at https://www.refolk.ai/candidates/guides/contract-award-lead-run*