Skip to content
FonteumPublic-records evidence
Fonteum · Compare

Federal exclusion screening vs checking SAM.gov by hand

Checking SAM.gov by hand confirms whether a vendor is excluded today, but it leaves no dated record of what the list said at award time, doesn't scale across a vendor portfolio, and can't answer the point-in-time question every auditor asks. SAM.gov carries 324,126 active exclusion records; in one bounded Fonteum analysis, 112 prime awards worth $1.6M went to 21 recipients while each held an active exclusion.

Published June 20, 2026 · Last reviewed June 2026 · Capability comparison — public facts only

8-capability comparison

From a manual SAM.gov lookup to a retained, source-dated screen

From a manual SAM.gov lookup to a retained, source-dated screen
CapabilityManual SAM.gov checksFonteum
CoverageOne entity at a time, typed into the SAM.gov search box.The full GSA exclusion registry — 324,126 active records — screened in a single pass.
Point-in-time statusToday's status only — the screen shows what the list says now.Current screening plus bounded award-date analyses. Fonteum does not claim universal historical replay of SAM.gov rows.
Identity resolutionA name or UEI typed by hand, with no record of how it was matched.UEI-, CAGE-, and name-keyed match against the registry, with the basis recorded.
Portfolio scaleRe-check every vendor, by hand, every cycle.The free procurement workflow checks the first 10 UEIs on screen; it does not create a download or monitoring.
Award-time evidenceNo record of a vendor's status on the day the contract was awarded.An exclusion-active-at-award-date join — the mechanism behind the Leakage Report.
Match provenanceA screenshot with a timestamp you have to trust.Matches expose source record, exclusion type, and observation fields where the response supplies them.
Refresh cadenceAs current as your last manual lookup.Loaded SAM.gov observation dates are reported separately from publisher or job cadence.
Audit trailA folder of dated PDFs, assembled after the fact.The free procurement result stays on screen and does not create a report artifact.

Descriptions reflect the manual SAM.gov screening pattern — searching the public exclusion registry by hand — not any single vendor or service. SAM.gov remains the authoritative source; figures cite Fonteum's published federal-contracting research.

Why coverage, timing, and evidence matter

What a manual SAM.gov check leaves uncovered

An award to an excluded party is the failure mode

Federal rules bar awards to excluded parties (FAR 9.405; 2 CFR part 180). Yet in one bounded Fonteum analysis, 112 prime awards worth $1.6M went to 21 recipients while each held an active federal exclusion. A manual SAM.gov check at award time is the control that is supposed to catch this — and it is the control that is hardest to prove ran.

The point-in-time question is the one a manual check can't answer

A live SAM.gov lookup tells you current status. A past-date claim requires a retained row or a bounded published analysis using the source's effective-date fields. Fonteum has only a small procurement-history set and does not offer universal SAM.gov replay.

Manual checks don't scale across a vendor portfolio

Screening one vendor in the SAM.gov UI is quick. The free Fonteum workflow checks the first 10 UEIs on demand and stays on screen; larger procurement portfolios are outside that free workflow.

A clear result needs a record, not a screenshot

Suspension-and-debarment programs are judged on evidence. The free workflow exposes its result on screen but does not create a downloadable report, email, or monitoring schedule.

FAQ

Common questions

Can't I just check SAM.gov myself for free?
Yes — SAM.gov exclusion search is free and authoritative for a single entity's status today. The limits show up at scale and over time: a manual check doesn't retain what the list said on a past date, doesn't produce a dated audit record, and is impractical to run across a large vendor portfolio every solicitation cycle.
What does a manual SAM.gov check miss?
It misses the award-time record and the point-in-time question. A live lookup shows current status, not what SAM.gov said when a contract was signed. It also leaves no dated, re-derivable evidence trail, and it doesn't scale: each of the 324,126 active exclusion records and each vendor has to be checked one at a time.
How can a vendor receive an award while excluded?
Most often a screening gap, not intent: the award-time check is skipped, run against a stale copy, or matched on a name that doesn't tie to the excluded entity. In one bounded Fonteum analysis, 112 prime awards worth $1.6M went to 21 recipients during an active exclusion window — exactly the gap an award-time, point-in-time screen closes.
How does Fonteum prove a vendor's status at award time?
Fonteum does not claim universal SAM.gov row replay. Its bounded award analysis compares award dates with published exclusion-effective intervals, and production procurement history currently contains only a small retained set. A current screen alone cannot prove a past status.
Does this replace SAM.gov?
No. SAM.gov remains authoritative. Fonteum adds current registry screening with the observation metadata available in the response. The free workflow stays on screen and does not create a report artifact; there is no universal historical replay.
Request access

Screen the first 10 UEIs on demand.

Read the federal-contracting findings in the Leakage Report, see the exclusion landscape in the Debarment Scorecard, or run the first 10 UEIs on screen. Request access only for a larger portfolio.

See also

What’s on file, by the numbers

Platform snapshot · 2026-08-14

13.4Mproviders & companiesProviders, organizations, owners, and facilities on file
26.2Msource-linked factsSource-linked field facts in the dated platform snapshot
90sources with dataDistinct snapshot source IDs with at least one positive record count
72fresh sourcesDistinct source IDs whose latest positive-data snapshot falls within the preceding 45 days
111sources integratedActive registry rows; integration does not establish a load
13state Medicaid jurisdictionsDistinct states represented in the state-exclusions serving table

Integrated, with-data, and fresh-observation counts are separate. No platform-wide source-completeness count is published. Completeness is source-specific and must be evaluated against the named source's expected scope. State coverage is a separate jurisdiction measure.

Source authority is record-specific

Use the issuer named on the record.

Fonteum spans federal, state, and global public publishers. A source page or returned record identifies its issuer and dataset where that metadata is available. A platform registry count does not assign every page to one authority or establish loaded, fresh, or complete coverage.

Browse source records and their stated limitations →

Reproducible by design

Inspect the evidence each published figure actually supplies.

Source and date

Research pages expose the named public file and observation date where those fields are available. Source-file SHA-256 coverage is separate; facts do not currently link deterministically to signatures.

Available derivation

Studies with a retained release and committed derivation link the SQL or method used. Other studies state the evidence and reproduction limits they actually have.

Daily observations

Dated table row-count observations can detect local drift. They do not imply that an upstream publisher released or Fonteum ingested new data that day.

Named medical review

Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.

Read the full provenance and attestation methodology →

Request access