How to check the SAM exclusion list: a step-by-step guide for federal contractors

The SAM Exclusion List — formerly known as the Excluded Parties List System (EPLS) — is the federal government's official record of entities barred from receiving federal contracts and certain federal assistance programs. Checking it is not optional for prime contractors. FAR 9.405 requires contracting officers and prime contractors to verify that entities are not excluded before making awards or approving subcontracts. The list contains 167,681 records spanning decades of federal enforcement actions across every agency with debarment authority.

This guide walks through each step of a manual exclusion check: how to access the search, what fields to use, how to interpret results, and how to verify active status. It also covers what manual searches cannot tell you — specifically, the geographic context of who else is at the same address as an excluded entity — and how state intelligence reports fill that gap.

What is the SAM Exclusion List (and what happened to EPLS)?

Before 2012, exclusion records were maintained in a separate system called the Excluded Parties List System (EPLS), administered by the General Services Administration. In November 2012, EPLS was consolidated into the System for Award Management (SAM.gov) as part of a broader federal procurement systems integration effort. The data is the same — only the interface and the name changed.

Today the exclusion database is officially part of "SAM Entity Information" under the Exclusions tab. But most compliance professionals still search for "GSA exclusion list," "GSA excluded parties list," or "EPLS list" when looking for it. All of these terms refer to the same dataset, now maintained at SAM.gov by GSA.

The exclusion list contains several categories of records:

• Debarments — the most severe action, typically lasting three years or longer, barring an entity from all federal procurement and nonprocurement programs
• Suspensions — temporary exclusions pending investigation, usually limited to 12 months
• Proposed debarments — indicates an active administrative process; the entity is excluded during the proceedings
• Voluntary exclusions — entities that have agreed to exclusion, often as part of an administrative settlement
• Ineligible designations — statutory exclusions that result automatically from certain conditions (e.g., Davis-Bacon Act violations)

The legal basis for mandatory checking is FAR 9.405, which requires agencies to check the exclusion list before awarding contracts and requires prime contractors to verify that subcontractors are not excluded before approval. This is not a suggestion — it is a contractual obligation flowed down through FAR 52.209-6.

Step 1 — Access the exclusion search

The exclusion search is available directly at SAM.gov without an account. To reach it:

1. Navigate to sam.gov
2. Click "Search" in the top navigation
3. Select "Entity Information" from the search domain dropdown
4. Toggle the filter to "Exclusions" (by default, the search shows active entity registrations)

Alternatively, navigate directly to the exclusions search index at sam.gov/search with the exclusions filter pre-applied. The direct path saves a few clicks when you know what you are looking for.

No SAM.gov account is required for basic exclusion searches. The data is public. You can search, view records, and verify exclusion status without logging in. An account is only needed if you want to set up alerts, download bulk data extracts, or access entity registration details beyond the exclusion records.

Step 2 — Search by entity name

The most common search method is by entity name. Enter the legal business name of the entity you are checking into the search field. A few practical notes:

Partial matching: The SAM exclusion search supports partial name matching, which means a search for "Delta" will return all exclusion records containing that word. This is useful when you are unsure of the exact legal name, but it can also produce a large volume of results for common terms.

Name variations: Federal exclusion records use the legal name as it appeared at the time of the excluding action. This means the same entity may appear differently depending on when it was excluded. Common discrepancies include:

• LLC vs. L.L.C. vs. no suffix at all
• Inc vs. Incorporated vs. Inc.
• DBA names that may or may not be listed
• Abbreviated forms (Svcs vs. Services, Intl vs. International)

Practical tip: When searching by name, run the search both with and without the entity suffix (LLC, Inc, Corp). If you get no results with the full legal name, try the root name alone. Name variation is the single most common reason a manual exclusion check returns a false negative — the entity is excluded, but the record uses a slightly different name form.

Step 3 — Search by UEI or CAGE code

If you have the entity's Unique Entity Identifier (UEI), searching by UEI is the most reliable method. UEI matching eliminates all of the name variation problems described above. When the UEI matches, the entity match is deterministic.

CAGE codes (Commercial and Government Entity codes) are also searchable and provide similarly reliable matching for entities that have them. CAGE codes are assigned by DLA and are particularly common for defense contractors.

One important caveat: not all exclusion records have UEIs. The UEI system replaced DUNS numbers in April 2022. Exclusion records from before that transition may only have DUNS numbers, and older records may have only the entity name with no unique identifier at all. For records without a UEI, you must fall back to name-based searching and manual verification.

When checking an entity you are considering for a subcontract, the ideal workflow is: search by UEI first (highest confidence), then confirm with a name search (catches records that predate the UEI assignment), then verify any matches are actually the same entity and not a name collision.

Step 4 — Interpret the results

When a search returns one or more exclusion records, each record contains several fields that together tell you the full story of the administrative action. Understanding what each field means is essential to reading the record correctly.

• Classification — whether the excluded party is a Firm, Individual, Special Entity Designation, or Vessel. Most supply-chain checks focus on Firm and Individual classifications.
• Excluding Agency — the federal entity that imposed the exclusion. Common excluding agencies include DLA, SBA, USAF, Army, Navy, HHS, EPA, and DOL. The agency provides context for the type of conduct that led to exclusion.
• Exclusion Type — Debarment, Suspension, Proposed Debarment, Voluntary Exclusion, or Ineligible. Each type has different legal implications and typical durations.
• Action Date — when the exclusion was imposed. Combined with the termination date, this tells you the exclusion's time window.
• Termination Date — when the exclusion expires. May be a specific date or "Indefinite" for certain exclusion types. This is the most important field for determining current status.
• Exclusion Program — whether the exclusion applies to Procurement programs, Nonprocurement programs, or both (Reciprocal). Reciprocal exclusions, which are the most common, bar an entity from both government contracts and grants.

Step 5 — Check the active status

Not every record in the exclusion database represents a currently excluded entity. The database retains historical records indefinitely, which means you will encounter exclusion records where the termination date has already passed. These records indicate that the entity was previously excluded but is no longer barred from federal contracting.

To determine whether an exclusion is currently active:

1. Find the Action Date — this should be in the past (the exclusion has already been imposed)
2. Find the Termination Date — if this date is in the future, or if it says "Indefinite," the exclusion is currently active
3. If the termination date is in the past, the exclusion has expired and the entity is no longer barred

A common mistake in manual screening is treating any exclusion record as a current exclusion without checking the termination date. An entity with a 2019 debarment that terminated in 2022 is not currently excluded — it is eligible for federal contracts again. Always verify the active window before concluding that an entity is currently barred.

Another subtlety: an entity may have multiple exclusion records. One may be expired while another is still active. Check all records associated with the entity, not just the first result.

What manual exclusion checks miss

The manual SAM.gov search answers one question well: "Is this specific entity currently excluded?" For one-off checks, that is often sufficient. But manual searching has structural limitations that become significant at scale:

• No geographic context. You can search one entity at a time, but you cannot see all other entities registered at the same physical address. If an excluded entity shares an address with your subcontractor, a name-based check of your subcontractor alone will not surface that proximity.
• No cluster visibility. You cannot identify locations where multiple federal contractor entities are co-located and where one or more have exclusion matches. These concentrations represent patterns that single-entity lookups cannot detect.
• No cross-referencing at scale. Checking one subcontractor takes 2-3 minutes. Checking every entity at the subcontractor's address against the full exclusion list is not practical manually.

Nationally, 129 address clusters contain at least one exclusion-matched entity out of roughly 67,500 clusters total — approximately 1 in 524 clusters. Virginia and California each have 19 exclusion-matched clusters, the highest of any state. 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 country.

This geographic context is invisible to manual exclusion checks. You would need to identify the address, look up every entity at that address in SAM, then check each one against the exclusion list individually — a process that could take hours for a single high-density address.

Beyond the manual check — geographic exclusion screening

State intelligence reports automate what manual checks cannot do. Each report pre-cross-references every address cluster in the state against the full 167,681-record exclusion database. When an excluded entity shares an address with active federal contractors, you see it immediately — the cluster is flagged, the excluded entity is identified with its excluding agency and action date, and every other entity at that address is listed alongside it.

The companion CSV makes this actionable in seconds. Open the file in Excel, filter by the "Excluding Agency" column to see all exclusion matches in the state at once. Or search for a specific address to see whether any co-located entities have exclusion records. What would take 15 minutes of manual cross-referencing becomes a 60-second geographic screen.

This does not replace the FAR-required exclusion check on the specific entity you are awarding to — that individual verification remains mandatory. What geographic screening adds is the layer of context that tells you whether the address itself has exclusion proximity that warrants additional diligence. Both checks serve different purposes; together they provide complete visibility.

Summary

Checking the SAM Exclusion List is a straightforward process: access SAM.gov, search by entity name or UEI, verify the active status by checking the termination date, and document the result for your procurement file. The manual process works well for one-off checks on specific entities.

Where it falls short is in geographic context. A manual check tells you about one entity. A state intelligence report tells you about every entity at every address, cross-referenced against the entire exclusion database, with the geographic patterns that reveal where exclusion-matched entities cluster. For compliance teams managing multi-state supply chains, that difference is the gap between checking a box and actually understanding the risk landscape.