Guide Pursuit review

SAM, UEI and CAGE: registration versus bid eligibility

Understand the difference between a SAM.gov account, active entity registration, a UEI and a CAGE code, then check the opportunity's separate conditions.

Reviewed · Deep Fathom

Wide tables scroll sideways to show all columns.

A UEI identifies an entity. A CAGE code identifies a facility at a specific location. SAM.gov entity registration records the information used to do business with the federal government. None of these, by itself, proves that your company meets a particular solicitation’s technical, access or cybersecurity requirements.

Check the actual entity and registration state before relying on an identifier copied from an old capability statement.

Four things that are easy to confuse

ItemWhat to verifyWhat it does not establish
SAM.gov user accountThe individual can sign in and has the appropriate entity role.The business has completed registration.
Unique Entity ID (UEI)The identifier belongs to the correct legal entity.The entity has an active registration or satisfies a particular requirement.
Entity registrationThe purpose, status, legal details and renewal information are correct.Technical qualification, drawing access or award eligibility on every opportunity.
CAGE codeThe code and facility/location match the proposed contracting and access records.JCP certification, CMMC status or permission to receive a controlled package.

SAM.gov’s registration guide distinguishes getting only a UEI from completing entity registration. It states that a UEI-only record does not enable direct applications for federal awards. Its instructions also distinguish creating an individual account from registering an entity.

DLA’s CAGE guidance describes CAGE as a standardized identifier for a facility at a specific location. That location detail matters when access records refer to a particular certified site.

Build a registration review record

Before assigning a pursuit as ready, capture the legal entity name, UEI, CAGE, registration status, date checked and responsible administrator. Record the exact solicitation instruction that makes any registration or identifier relevant, including the checkpoint at which it is required.

Do not replace an instruction with a generic rule such as “registration can wait until award.” Timing and exceptions depend on the applicable provision and procedure. If the package’s instruction is unclear, use the clarification method.

A saved screenshot or dated record can show what was checked. It does not make that state permanent. SAM.gov directs entities to renew every 365 days to keep registration active.

Check the next access condition separately

In the retained Navy lifting-cap synopsis, the drawing-access paragraph lists an active CAGE and an active, JCP-verified DD Form 2345 as separate conditions. One code does not satisfy both. The paragraph also addresses secure receipt and storage of CUI. Source notice action.

Use the controlled-package guide if obtaining drawings is the next task. Keep the entity, certified location and requester consistent across the relevant records. Ask the responsible program to resolve a mismatch.

Keep administrative readiness in proportion

Registration is a necessary review category, not the whole go/no-go decision. Technical fit, source approval, capacity, price and applicable security work need their own owners in the bid eligibility checklist.

SAM.gov registration is free, and its guide links to free APEX Accelerator assistance. Deep Fathom’s role here is the compliance evidence workflow where that is the open item. It does not issue UEIs, CAGE codes or registration approval. Explore the platform.

Official guidance read September 7, 2026. The solicitation example is dated retained evidence. Check later notice actions before acting.