How to Run an FPDS Manual Search (and What It Can't Tell You)
Learn how to run a manual FPDS search in SAM.gov step by step, what contractors miss by relying on award history alone, and how live solicitation data and automated fit scoring close the gap.

FPDS is the Federal Procurement Data System, the federal government's official record of contract awards, modifications, and orders. Its public search and reports now live in SAM.gov, where all public-facing FPDS functionality has been transitioned. The problem for a pursuit team is simple: FPDS tells you who already won work the government has already bought, and nothing about what is open for bid right now, whether a scope fits your capabilities, or whether you are about to compete against an incumbent with years of embedded performance history. A manual FPDS search still has a place, but only once you know what it can and cannot answer.
- FPDS is a historical archive, not an opportunity feed; it captures awarded contracts, not the active solicitations your pursuit team needs.
- FPDS public search and reports now live in SAM.gov. GSA decommissioned the legacy ezSearch keyword tool on February 24, 2026, so fpds.gov is no longer the place to search.
- Manual FPDS lookups are keyword-dependent and miss semantically relevant opportunities that a shared NAICS code or search term will not surface.
- Compliance requirements, clearance levels, and set-aside restrictions live in attached documents that FPDS never indexes and keyword searches routinely skip.
- Layering FPDS award history with live solicitation data and automated fit scoring produces a competitive picture that manual workflows cannot replicate.

The short answer
FPDS manual research is the practice of querying the Federal Procurement Data System to understand an agency's buying history, and it works best as a depth layer, not a discovery engine. The system is authoritative and free, which is why procurement teams often start there, but it records contract actions after execution, not the solicitations actively accepting proposals. Treating FPDS as your primary source means you are always researching the past to find work the government has already awarded. The higher-leverage approach is to start with a live solicitation feed, score opportunities for fit, and then use FPDS to add incumbent context and market depth to the pursuits that score well.
What FPDS actually contains and what it was never built to do
FPDS-NG, now searchable through SAM.gov rather than the legacy fpds.gov site, is the authoritative record of federal contract actions. Every award above the micro-purchase threshold, every contract modification, every delivery order against an IDIQ vehicle is logged here. That makes it genuinely valuable for one specific task: understanding who an agency buys from, at what funding levels, and through which contract vehicles. Heading into a recompete cycle, that context is hard to replace.
What FPDS was never built to do is surface open solicitations, draft RFPs, sources-sought notices, or acquisition forecasts. For live opportunities, contracting teams check the SAM.gov opportunities search, agency-specific procurement portals, and published acquisition forecasts. The gap between a historical award record and a live opportunity feed is exactly where manual research becomes both slow and unreliable. The same gap exists far beyond federal work. A construction general contractor pursuing public projects monitors a state bid portal, several county procurement boards, and direct notice systems from project owners, with no centralized archive to reveal who won comparable projects or which owner consistently favors an incumbent. That contractor faces the same incumbent blindness and attachment-buried compliance risk as a federal contractor relying solely on FPDS, just spread across a different stack of siloed portals. Fragmentation like that is why modern solicitation platforms track 33,000+ sources across federal, state, local, and private markets rather than one database.
The real cost of manual FPDS research
A rigorous pursuit workflow built around FPDS typically requires pulling award data from the SAM.gov contract data search, cross-referencing spending trends on USASpending.gov, checking active solicitations in the SAM.gov opportunities search, and reviewing each agency's published acquisition forecast. Each step is a separate system with its own search syntax and export format. For teams working multiple opportunities at once, that process repeats for every pursuit on the pipeline.
As of October 2026, 54,681 solicitations are open right now across the 33,000+ sources we track. Of those, 1,357 mention the term "manual," and 614 of them close within the next 14 days. Another 1,368 new solicitations mentioning manual processes were posted in the last 30 days alone. Not one of them surfaces through an FPDS search, because FPDS does not track solicitations. That is the gap no manual workflow can close.
How to run a manual FPDS-NG search
Open SAM.gov, select the Contract Data search domain, and use its filters to pull award data by agency, NAICS code, Product Service Code (PSC), awardee name, and date range, with each filter narrowing the record set before you export. The legacy fpds.gov search and the ezSearch keyword tool no longer serve this purpose: all public-facing FPDS functionality has been transitioned to SAM.gov, and GSA decommissioned ezSearch on February 24, 2026. Keyword queries that once ran in ezSearch now run in the Contract Data search bar, with the same filters applied alongside them. The most productive combination for competitive intelligence is Agency Name plus NAICS code, which shows you what a specific buyer has awarded in your core capability area. Adding a date range covering the last two to three fiscal years keeps results relevant to current buying patterns rather than legacy programs that may have since ended. The PSC filter is especially useful when your work spans multiple NAICS categories, because PSC codes describe the type of deliverable rather than the industry classification of the performing company.
Once you have filtered to a manageable result set, use the export option to download the raw data as a CSV. Preserve at minimum: Contractor Name, Contract Number, Award Amount, Period of Performance, and Contracting Agency. Cross-referencing those contract numbers on USASpending.gov then adds cumulative obligated value and modification history for each award, giving you a fuller picture of how the agency has used each vehicle over time. To verify what the search results suggest at the aggregate level, open the SAM.gov Data Bank, where the FPDS contract data reports, including the ad hoc report builder, let you generate an agency-by-NAICS spend table and check it against your exported records.
Two data-quality issues to account for before drawing conclusions. Contracting officers sometimes apply NAICS codes based on the agency's primary mission rather than the nature of the actual work, so a logistics support contract at a defense agency may be coded under the agency's dominant NAICS rather than the supply chain services code you would expect. Filtering by NAICS alone will miss a meaningful share of relevant awards as a result. There is also a timing problem. FPDS reporting policy, published on fpds.gov and codified in the FAR 4.604 reporting requirement, directs agencies to report each contract action within 3 business days of award. Department of Defense actions, however, are withheld from public view for 90 days after award, and across every agency, reporting gaps and late entries mean the most recent awards are often incomplete. Relying on FPDS to capture current competitive activity in an agency can leave you with a materially incomplete picture of who is winning work right now.
The layers that FPDS data cannot supply
Beyond incumbent identification, FPDS research leaves three intelligence gaps that most contractors treat as unavoidable. The first is contract vehicle eligibility. FPDS records a contract number, but you have to cross-reference that number against the ordering procedures of each GWAC or IDIQ you hold before you know whether the agency is routing work through a vehicle you can actually use. The second is compliance. Clearance levels, set-aside restrictions, and facility requirements sit in statements of work and attachments that FPDS never indexes and keyword searches skip. The third is semantic fit. A shared NAICS code says nothing about whether the actual scope matches your capabilities, and the only manual way to find out is to read the documents yourself.
Each of these gaps is a decision point where teams either invest research hours or accept the risk of pursuing opportunities they are not positioned to win, while missing the ones they would have scored well on. Automated extraction changes that calculation. BidSparq pulls clearance levels, set-aside designations, and scope signals directly from attached documents, so compliance fit surfaces with each scored opportunity instead of at the end of a manual document review. When fit indicators are extracted from source documents continuously, the manual burden on each pursuit drops sharply.
Putting FPDS in its proper place in your pursuit workflow
Replace the reactive FPDS search loop with a monitored feed that surfaces, scores, and filters opportunities before you ever open a new tab. Semantic matching understands that a solicitation for "logistics support services" may be highly relevant to a contractor whose past performance is in supply chain management, even if those phrases never share a document. That connection disappears in a keyword search and never appears in FPDS at all.
Incumbent and contract vehicle context, the data you were mining FPDS to find, can be surfaced automatically alongside each scored opportunity. A 0-to-100 fit score gives your team a defensible basis for which pursuits to invest proposal resources in and which to pass on. FPDS becomes what it always was: a confirmation and context layer, not the discovery engine your pipeline depends on.
FAQ
What does FPDS show, and can you use it to find open federal contracts?
FPDS-NG records federal contract awards, modifications, and orders after they are executed. It is a historical database, not a solicitation board. Open solicitations are published in the SAM.gov opportunities search, not in FPDS. Manual FPDS research is most useful for pre-recompete competitive analysis: identifying the incumbent contractor, understanding which contract vehicle the agency prefers, and sizing the historical spend in your target area.
How do you find incumbent contractors using a manual FPDS search?
Search the FPDS contract data in SAM.gov by agency, NAICS code, or program office to identify recent awards in your target area. Note the awardee name, contract vehicle, contract number, and period of performance. Cross-referencing that contract number on USASpending.gov shows modification history and total obligated value. The process works but requires multiple systems and manual reconciliation for every pursuit target. Platforms that automate incumbent lookup pull this context alongside opportunity scoring, eliminating the separate research step entirely.
What is the difference between FPDS and SAM.gov for federal contracting?
FPDS is a backward-looking record of what federal agencies have already bought and from whom. SAM.gov, the System for Award Management, is where agencies publish active solicitations, sources-sought notices, and procurement forecasts, and it now also hosts the public FPDS contract data search and reports. Effective federal market research uses both: the opportunities search to find what is accepting bids now, and the FPDS contract data to understand the competitive history and incumbent context behind each live opportunity.
Start BidSparq's 14-day free trial and get scored matches across federal, state, local, and private solicitations, with incumbent context attached, instead of rebuilding the FPDS loop for every pursuit.
Find RFPs that match your business
BidSparq monitors 33,000+ procurement sources and uses AI to score every opportunity against your capabilities. Try it free for 14 days.
Start Free Trial →




