How do you identify the incumbent on a federal contract from public data?

The 4-step recipe

1. Find the prior contract PIID (procurement instrument identifier).
2. Look up that PIID on USAspending /award/{piid}/.
3. Read recipient_name and parent_recipient_name (parent matters more for teaming).
4. Cross-check on SAM.gov Entity Management for live registration status.

Total time: 3 minutes per recompete.

When the prior PIID is in the SAM.gov notice

Recompete notices on SAM.gov often include the prior contract number under additionalInfoText or description. Common phrasings:

• "This is a recompete of contract VA786C-12345..."
• "Successor to W91RUS-21-D-0042..."
• "This requirement is currently being performed under task order N00178-25-F-0123."

Search the description for -d{2}-[A-Z]-d{4} (regex). If you find it, paste it into USAspending's award search.

When the PIID isn't published

Most pre-solicitation notices intentionally omit the prior PIID. You triangulate.

Method A: NAICS × sub-agency × period of performance

If you know the requirement (e.g., "VA Medical Records Modernization, NAICS 541512, 5-year base + options"), run USAspending:

{
  "filters": {
    "award_type_codes": ["A","B","C","D"],
    "naics_codes": ["541512"],
    "agencies": [{"type":"awarding","tier":"subtier","name":"Department of Veterans Affairs Office of Information and Technology"}],
    "time_period": [{"start_date":"2020-10-01","end_date":"2021-09-30"}]
  },
  "limit": 25,
  "page": 1
}

The top recipient over the prior period of performance, weighted by NAICS, is your most likely incumbent. Confirm by reading individual award descriptions.

Method B: PSC + dollar value

If you have a Product Service Code (PSC) and an estimated value, filter by both. PSC narrows tighter than NAICS for technical work — D399 (IT Other) vs D310 (IT Cybersecurity) catch different incumbents.

Method C: Public press releases

Search Google for "[awardee] [agency] [keyword]" with site:fcw.com, site:fedscoop.com, site:nextgov.com. Industry news catches awards that don't show up cleanly in USAspending for 60-90 days.

The parent-vs-recipient distinction

USAspending exposes both recipient_name and parent_recipient_name. They're often different:

• recipient_name: ManTech International Corporation
• parent_recipient_name: Carlyle Group (post-acquisition)

For capture purposes:

• The recipient is your tactical competitor — they're the team currently delivering.
• The parent is your strategic competitor — they're the cap table you'd be teaming against if you go after the parent's wider portfolio.

For teaming inquiries, name the recipient, not the parent. For competitive analysis (M&A, lobbying, market share), name the parent.

Validating with SAM.gov

USAspending data lags by ~7-30 days. SAM.gov Entity Management has a real-time registrationStatus. Pull the entity:

curl "https://api.sam.gov/entity-information/v3/entities?api_key={KEY}&legalBusinessName=BOOZ%20ALLEN%20HAMILTON"

Check for:

• registrationStatus: "Active" — they can still bid recompetes.
• exclusionStatusFlag: false — not debarred.
• NAICS list includes the relevant code — they're approved to bid.

If the incumbent is suddenly inactive or debarred, the recompete dynamics flip — non-incumbents have a real shot.

The CPARS signal

If you can pull the incumbent's CPARS rating on the prior contract, you have a strong signal of recompete vulnerability. CPARS is published on FAPIIS for contracts > $1M.

Don't pursue marginal recompetes assuming the incumbent will lose; assume they'll lose something and capture the opportunity to be the credible alternative.

Common mistakes

1. Reading the parent and forgetting the recipient. Parent is M&A; recipient delivers.
2. Using NAICS too tightly. Incumbents often hold contracts with adjacent NAICS — a 541512 incumbent may also hold 541519 awards under the same program.
3. Ignoring set-aside changes. A non-set-aside contract recompeted as SDVOSB-only locks out the previous incumbent. Check the new typeOfSetAside against the incumbent's certification.
4. Trusting press releases over USAspending. Press releases are wins; USAspending is dollars actually obligated. They diverge by ~6-12 months.

What our agent does

When you say "who is the incumbent on demo-va-cloud-2026", the agent:

1. Reads the SAM.gov notice via get_opportunity.
2. Extracts any prior PIID from the description.
3. Falls back to NAICS × sub-agency triangulation via search_individual_awards.
4. Cross-checks the top result via search_entities.
5. Returns the incumbent name, parent, share-of-wallet, and CPARS-equivalent vulnerability score.

Total agent runtime: 8-15 seconds. Total human time: 0.