GSA excluded parties list vs SAM exclusion list: what changed and what you need to know

Every year, thousands of compliance professionals, contracting officers, and procurement teams search for the "GSA excluded parties list" or the "EPLS list" when they need to verify that a contractor is not debarred or suspended from federal contracting. The search makes sense — the Excluded Parties List System was the name of this database for over a decade and it was maintained by GSA. But the name changed in 2012, and understanding what happened clarifies where the data lives today and how to access it.

The short answer: the GSA Excluded Parties List System (EPLS) is now the SAM Exclusion List, accessible at SAM.gov. The data is the same. The records are the same. The legal requirements to check it are the same. Only the interface and the name changed. This article covers the history, explains how to access the current system, and describes what the 167,681-record database contains.

A brief history: EPLS to SAM.gov

The Excluded Parties List System was established as a standalone government database maintained by the General Services Administration. Its purpose was simple: provide a centralized record of all entities and individuals excluded from receiving federal contracts, certain subcontracts, and certain federal assistance and benefits. Federal agencies would submit their exclusion actions to GSA, and GSA would publish them in EPLS. Contracting officers and prime contractors would check EPLS before making awards.

In November 2012, the federal government consolidated several procurement systems into a single platform called the System for Award Management (SAM.gov). EPLS was one of the systems absorbed into SAM, along with the Central Contractor Registration (CCR), the Online Representations and Certifications Application (ORCA), and the Federal Agency Registration (FedReg). The goal was to create a single point of entry for all federal procurement-related data.

After the consolidation, EPLS ceased to exist as a separate system. Its data — all historical exclusion records plus all new exclusions going forward — became part of SAM.gov under the "Exclusions" search tab. GSA continues to maintain the data; only the front-end interface and the system name changed.

Why people still search for "GSA excluded parties list"

More than a decade after the transition, searches for "GSA excluded parties list," "EPLS list," and "GSA exclusion list" remain common. This is not surprising for several reasons:

• Training materials. Many organizations still have compliance training documents, SOPs, and desk guides that reference EPLS by name. These documents get passed from one compliance officer to the next without always being updated.
• Old bookmarks and muscle memory. Professionals who checked EPLS for years before 2012 still associate the task with the old name, even if they know the new location.
• FAR references. While the FAR has been updated, many organizations' internal compliance checklists still use older terminology. A checklist item that says "check EPLS" means "check the SAM exclusion list" — same action, different name.
• Third-party tools. Some compliance screening tools and due diligence platforms still reference EPLS in their documentation or interface labels.
• Word of mouth. When a senior compliance professional tells a junior colleague to "check the excluded parties list," the junior colleague searches for exactly that phrase.

All of these searches lead to the same place: SAM.gov, Exclusions tab.

How to access the exclusion list today

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

1. Go to sam.gov
2. Click "Search" in the top navigation
3. Under the search domain, select "Entity Information"
4. Toggle the filter from "Registrations" to "Exclusions"

You can also navigate directly to the exclusions search index (sam.gov/search with the exclusions filter pre-selected). No login is required for viewing exclusion records. The data is public.

From there, you can search by entity name, UEI (Unique Entity Identifier), CAGE code, or other fields. For detailed step-by-step instructions on conducting a search and interpreting results, see our companion guide: How to check the SAM exclusion list: a step-by-step guide.

What the exclusion list contains

As of March 2026, the SAM Exclusion List contains 167,681 records. These span decades of federal enforcement actions from every agency with debarment or suspension authority. The database includes:

• Debarments — entities barred from federal contracting for a specified period (typically three or more years) or indefinitely
• Suspensions — temporary exclusions, usually pending investigation, limited to 12 months
• Proposed debarments — entities excluded while the debarment process is underway
• Voluntary exclusions — entities that have agreed to exclusion as part of an administrative settlement
• Ineligible designations — statutory exclusions triggered by specific regulatory violations

Each record includes the entity name, classification (Firm, Individual, Special Entity Designation, or Vessel), the excluding agency, action and termination dates, the exclusion type, and the exclusion program (Procurement, Nonprocurement, or Reciprocal). When available, the record also includes the entity's UEI or historical DUNS number.

It is important to note that an exclusion is an administrative action, not a criminal conviction. Entities may be excluded for contract performance failures, regulatory violations, certification misrepresentation, or other administrative reasons. The record reflects a federal determination about contracting eligibility — nothing more.

Geographic patterns in the exclusion data

One dimension of exclusion data that the SAM.gov interface does not surface is geography. When you cross-reference exclusion records against the physical addresses where federal contractors are registered, patterns emerge that individual lookups cannot reveal.

Our analysis of 2,684,826 SAM.gov entities organized into 70,115 address clusters found that 129 clusters nationally contain at least one entity matching an exclusion record. That is roughly 1 in 524 clusters — uncommon but not rare, and heavily concentrated in certain states.

The geographic distribution:

• Virginia — 19 exclusion-matched clusters (the highest, driven by DC Beltway contractor density)
• California — 19 exclusion-matched clusters (tied with Virginia, spread across defense and technology hubs)
• Texas — 12 exclusion-matched clusters
• Maryland and Florida — 10 each
• New York — 9 exclusion-matched clusters

These six states account for over 60 percent of all exclusion-matched clusters nationally. The pattern tracks with overall federal contracting volume — states with the most contractors also have the most exclusion-matched addresses in absolute terms.

This geographic layer is what distinguishes a manual exclusion check from systematic geographic screening. A SAM.gov search tells you whether one entity is excluded. A state intelligence report tells you whether the address where your subcontractor is registered also houses excluded entities — context that manual searching cannot provide.

What this means for your screening workflow

If your current compliance process involves checking the "GSA excluded parties list" or "EPLS" on a per-entity basis, you are meeting the minimum FAR requirement. That individual check remains mandatory and is not going away.

What geographic intelligence adds is the second layer: address-level context. When you know that your subcontractor's registered address is also home to an excluded entity, that is information worth having — even though it does not affect the subcontractor's own eligibility. It may inform your responsibility determination, prompt additional verification, or simply give your compliance file more complete documentation.

State intelligence reports pre-cross-reference every address cluster against the full 167,681-record exclusion database. The companion CSV lets you filter by excluding agency, search by address, and see every entity at every location in seconds. The manual version of this — looking up every entity at an address one by one — is the work that takes hours and that most teams simply cannot do at scale.