The SAM Exclusion List is the federal government's record of entities and individuals barred from receiving federal contracts and many federal grant programs. With 167,681 records spanning decades of enforcement actions, it is the most comprehensive debarment database in the world. Every prime contractor is required to check it before awarding subcontracts. Every contracting officer is required to check it before making awards. And yet, despite its central role in federal procurement, the structure and contents of the exclusion list are widely misunderstood.

This article explains what the exclusion list contains, who gets excluded and why, what an exclusion actually means for an entity's supply-chain status, and how the geographic distribution of exclusion matches looks across the United States.

What is the SAM Exclusion List?

The SAM Exclusion List, formerly known as the Excluded Parties List System (EPLS), is maintained by the General Services Administration as part of the System for Award Management. It consolidates exclusion records from every federal agency that has authority to debar or suspend entities from receiving federal contracts or grants. When you query the exclusion list, you are querying the consolidated output of dozens of separate enforcement programs.

Each record in the exclusion list contains:

Who gets excluded and why

The exclusion list spans the full range of federal enforcement programs. Some patterns are visible in the data:

The Defense Logistics Agency is consistently among the most active excluding agencies, particularly for actions related to metals, aviation parts, and supply chain integrity. The Small Business Administration produces a steady stream of exclusions tied to small business certification misrepresentation — entities claiming 8(a), HUBZone, SDVOSB, or WOSB status they do not qualify for, or violating SBA size standards through undisclosed affiliations. The military services (Air Force, Army, Navy) issue exclusions tied to contract performance failures and integrity violations on specific programs.

Civil agencies including HHS, EPA, DOL, and HUD also produce regular exclusion actions, often tied to grant program compliance failures or specific regulatory violations within their mission areas. Each excluding agency has its own administrative process, its own grounds for action, and its own appeal procedures.

It is worth being explicit on one point: an exclusion is an administrative action, not a criminal conviction. Entities can be excluded for performance failures, regulatory violations, or other administrative reasons that do not involve criminal misconduct. The exclusion record reflects the federal government's determination that an entity should not receive contracts, but it does not establish wrongdoing in a legal sense. CDA frames exclusion data neutrally because the data itself is neutral — it is a record of administrative decisions, not a judgment.

The numbers behind exclusions

Understanding the scale and distribution of the exclusion list helps put any specific match into context. A few key numbers:

The geographic distribution of exclusion matches is uneven. Virginia and California tie at the top with 19 exclusion-matched clusters each. Texas has 12, Maryland and Florida have 10 each, and New York has 9. These six states account for over 60 percent of all confirmed exclusion-matched clusters in the database. The pattern correlates strongly with overall federal contracting activity — the largest contracting markets also produce the most exclusion-matched clusters in absolute numbers, even though the rate per cluster remains low.

How exclusions affect your supply chain

The direct rule is simple: federal prime contractors cannot knowingly award subcontracts to entities listed on the exclusion list. This is enforced through the FAR 52.209-6 contract clause and corresponding agency-specific provisions. Awarding a subcontract to an excluded entity can result in contract penalties, contract termination, and the prime contractor's own potential exclusion.

The harder question is what to do when an excluded entity shares an address with one of your subcontractors. Strictly speaking, this does not affect your subcontractor's eligibility — an excluded co-located entity is a separate legal entity with its own UEI and its own status. But the proximity is a screening signal that warrants understanding: who are these other entities, what is their relationship (if any) to your subcontractor, and is there a pattern that should inform your responsibility determination?

This is where geographic intelligence becomes valuable. Co-location screening automates the question of "who else is at this address?" so you can answer it in seconds rather than spending hours manually cross-referencing SAM and the exclusion list.

Reading an exclusion record

An exclusion record on its own is a snapshot of an administrative action. Reading it carefully — and understanding what each field does and does not tell you — is part of using the database responsibly.

The action date is when the exclusion took effect. Older actions may reflect entities that have long since closed, reformed under new names, or had the exclusion administratively reversed. Always check the termination date alongside the action date to understand whether the exclusion is still active or has expired.

The excluding agency tells you which federal entity took the action and provides context for the type of issue involved. A DLA debarment for metals fraud carries different implications than an SBA action for size standard misrepresentation. Both are exclusions; both prevent contracting; but the underlying conduct is different and the relevance to your compliance review may differ accordingly.

The exclusion type distinguishes between debarment, suspension, proposed debarment, and other categories. Debarment is the most severe and longest-lasting. Suspension is typically temporary and pending investigation. Proposed debarment indicates an active administrative process. Each type has different procedural implications and different durations.

The UEI when available is the strongest identifier. UEI matches are essentially deterministic — if the UEI matches, the entity matches. Older exclusion records that predate the UEI system rely on entity name matching, which is more error-prone and requires careful verification.

How to check the exclusion list

For individual entity checks, the SAM.gov website provides direct search at sam.gov/exclusions. You can search by entity name, UEI, DUNS, or other fields. The search returns matching exclusion records along with the relevant details. For one-off lookups, this manual interface is adequate.

For systematic supply-chain screening, manual lookups are not practical. You need a way to cross-reference every entity in every cluster against the full exclusion database, with geographic context for each match. That is exactly what state intelligence reports provide. Each report pre-cross-references every cluster in the state against the 167,681-record exclusion database and surfaces the matches with the excluding agency, action date, and full entity context. See a sample report to understand what the output looks like.

The exclusion list is one of the most important tools in federal procurement compliance, but its full value is only realized when it is cross-referenced against geographic context. A name lookup tells you whether one entity is excluded. A geographic check tells you whether the entity's address has any exclusion proximity that warrants understanding.

Frequently asked questions about exclusion records

A few questions come up consistently from compliance teams new to systematic exclusion screening:

Does an expired exclusion still matter? Generally no for forward-looking contracting decisions — if the termination date has passed, the entity is no longer barred. But expired exclusions remain in the database as historical records and can still be relevant context when reviewing the integrity history of an entity that is otherwise eligible.

What if the exclusion is under appeal? An exclusion remains in effect during the appeal process unless the agency specifically stays it. Treat the entity as excluded unless and until the record is removed or the termination date is updated.

How often is the database updated? The SAM Exclusion List is updated continuously by federal agencies as actions are taken and recorded. Our reports reflect the most recent monthly extract from the SAM database, ensuring screening data does not go stale between purchases.

Can an entity reform under a new name and avoid the exclusion? Federal procurement regulations include provisions to address this concern. The exclusion list captures known successor entities and affiliates when those relationships are established through the administrative process. However, manual screening cannot always detect a clean entity that is in fact a reformed version of an excluded one — this is one of the reasons compliance programs apply enhanced due diligence beyond the basic exclusion check.

Where to start

If your compliance program operates in one of the higher-density exclusion-match states — Virginia, California, Texas, Maryland, Florida, or New York — the state intelligence report for that jurisdiction provides immediate value. For multi-state compliance programs, regional bundles cover the relevant footprint at 25 percent savings versus individual state pricing. Either way, the value is the same: complete address-level visibility into where exclusion matches concentrate, automated and ready to query.

Related research