Skip to content

Search RFP.co

Pages across the product, solutions, opportunities and resources.

Type to search. Press Enter to open the full results page.

Start free trial
Reference

What is in the database, and where it came from

A searchable database of open solicitations, filterable by issuing agency, category, geography and closing date, with a link back to the original posting on every record.

Public procurement is published, but it is published across thousands of portals that share no format, no schedule and no identifier. The database is the result of reading those sources continuously and reducing what they publish to one record per procurement, with the original posting attached to every one.

Start here

Soonest deadline first

Open RFPs

Published requests for proposal, with the buyer, the closing date and a link to the original posting on every record.

Shorter cycles

Open RFQs

Quote requests, which are answered in days rather than weeks and close sooner than formal solicitations.

Agencies and their components

Federal

Solicitations from federal agencies, carrying the solicitation number, the set-aside and the response deadline.

States and public universities

State

State agencies and public university systems, deduplicated into one record per procurement.

The most fragmented tier

Local

Cities, counties, school districts and special authorities — thousands of buyers, each publishing on its own terms.

Facets

By industry, place or buyer

Every list page carries facet navigation built from what has actually been published, rather than from a list of categories somebody hoped would fill up.

What a record holds

Sources publish the same procurement in materially different shapes. One portal gives a closing time with a timezone, another gives a date; one names the issuing department, another names the parent agency; one assigns a category, another leaves the title to carry it. A record is what survives normalizing all of that into fields that mean the same thing everywhere.

Field, Normalized to, Where it is missing
FieldNormalized toWhere it is missing
BuyerOne organization, with its tier and parent resolvedLeft as published rather than guessed at
InstrumentRFP, RFQ, RFI, ITB or qualification requestClassified from the document where the portal does not say
Closing dateAn instant, with the buyer’s timezone appliedShown as a date without a time, never as midnight
Solicitation numberThe buyer’s own identifier, unalteredAbsent — some local buyers do not assign one
CategoryAn industry classification, where the source supplies or implies oneUncategorized rather than assigned by guess
SourceA link to the original postingNever — a record without one is not published

Empty is a value. A field the source did not publish is shown as absent, because a blank inferred into a plausible default is the kind of error that is discovered at the submission deadline.

One procurement, one record

The same solicitation is frequently posted in several places — a state portal, an aggregator that mirrors it, and the issuing department’s own site — with different titles, different formatting and sometimes different dates where one copy was updated and another was not.

Matching them is done on the stable parts: the issuing buyer, the solicitation number where one exists, the closing date and the substance of the title. Where copies disagree, the version from the buyer itself is preferred over the version from an aggregator, and the others are kept attached to the record rather than discarded, so the disagreement is visible instead of silently resolved.

What it is safe to conclude

Always confirm against the original posting before you bid

The database is a finding aid. Deadlines move, addenda change requirements, and a portal can amend a posting without changing anything a scraper would notice. Every record links back to its source, and the source is what governs.
  • Absence is not evidence

    A procurement missing from the database has not necessarily gone unpublished. It may sit behind a registration wall, on a portal not yet read, or in a format that carried no machine-readable posting at all.

  • Closed does not mean awarded

    A closing date passing means the submission window shut. Awards are published separately, on their own timescale, and frequently months later.

  • A category is a convenience

    Industry classification is assigned to make browsing possible. Eligibility is decided by the code the buyer put in the solicitation, which is the one that sets the size standard.

Browsing versus being told

The public database answers the question you thought to ask. The problem in practice is the opposite one: most opportunities that fit a firm are never searched for, because nobody knew the buyer existed or that the requirement was coming.

That is what the product does with the same corpus — matching each new record against a capability profile, showing the contributions behind the score rather than only the number, and surfacing evidence of demand before a solicitation is published at all.

Opportunity matching

Scored against your capabilities, past performance and set-aside eligibility, with the reasons shown.

Buying signals

Budget lines, board approvals and expiring contracts — evidence that a purchase is coming, before anything is published.

Common questions

Is the RFP database free to search?

Yes. The listing pages are public and need no account. An account is what adds monitoring, matching against your capability profile, and the response tooling.

How often is it updated?

Sources are read continuously rather than on a fixed daily cycle, because portals publish on their own schedules. Each record carries the time it was last seen at its source.

Where do the listings come from?

From the buyers’ own published postings — federal, state, local and public authority procurement portals — with a link back to the original on every record. Nothing is republished without its source.

Why does the same solicitation sometimes appear on several sites?

Because buyers post to their own site and to aggregators, and the copies can differ. The database matches them into one record and prefers the buyer’s own version where they disagree.

How do I have a listing corrected or removed?

Send a notice through the directory takedown process, which sets out what the request must contain and what happens next.

Related

Open RFPs

Published requests for proposal, soonest deadline first.

RFP calendar

Closing dates, pre-bid meetings and question deadlines.

RFP glossary

Procurement terms, defined plainly.

Directory takedown requests

How to have a public listing corrected or removed.

See what you are not bidding on.

Connect a source, describe what your company does, and look at the opportunities that come back before deciding whether any of this is worth your time.