Skip to content
BidPulsar
BidPulsar™FBP Product Division
Built by Federal Bid Partners • team has written hundreds of proposals
RP-Led CMMC
Need proposal or grant support? Talk with our capture and CMMC team.
GSA7 min readUpdated June 7, 2026

SAM Record Guide: UEI, CAGE, Entity Data, and Why the GSA Offer Must Match

A guide to the SAM record upload in a GSA MAS offer, including entity identity, UEI, CAGE, addresses, points of contact, and consistency with eOffer.

Built for
GSA MAS offer teams building an eOffer upload package from the Refresh 32 checklist
By the end
Know what the SAM Record file proves and how to prepare it without creating review friction.
Field guide

SAM Record review checks

Check 1
Entity-name or address drift between SAM, eOffer, and pricing files can create basic trust friction.
Signal
UEI, CAGE, legal name, and address match the offer.
Response
Make the file clear enough that a reviewer can follow it without calling the offer team for basic context.
Check 2
Do not let this upload contradict pricing, SAM data, or narrative responses.
Signal
SAM registration is active and not near an avoidable lapse.
Response
Make the file clear enough that a reviewer can follow it without calling the offer team for basic context.
Check 3
Do not let this upload contradict pricing, SAM data, or narrative responses.
Signal
Points of contact are current enough for review and post-award use.
Response
Make the file clear enough that a reviewer can follow it without calling the offer team for basic context.
Part 1

What this upload proves

The SAM record proves the offeror's federal entity registration and identity details.

It sits beside reps and certs, financial responsibility files, and eOffer company data.

Part 2

How to prepare it cleanly

Start by naming the proof role, file owner, source system, date pulled or signed, and whether the file is required, conditional, or optional for the selected offer.

Then compare the file against the pricing workbook, SAM record, eOffer narrative, and category/SIN instructions so the package tells one story.

  • UEI, CAGE, legal name, and address match the offer.
  • SAM registration is active and not near an avoidable lapse.
  • Points of contact are current enough for review and post-award use.
Part 3

What to watch before upload

Entity-name or address drift between SAM, eOffer, and pricing files can create basic trust friction.

Use filenames that help the reviewer understand the document before opening it. A clear file name with document type, company, SIN or category when relevant, and date is usually better than an internal shorthand.

The upload goal is calm review: current file, clear purpose, no contradictions.
Examples

What this looks like in practice

Real-world exampleHow a clean SAM Record upload helps

A contractor changes office addresses before a GSA offer. The team updates SAM first, then pulls the current record so the offer package does not contain two identities.

Frequently asked questions

Is SAM Record always required?

Treat it as required for planning purposes, then confirm the live requirement against the solicitation, eOffer prompts, and selected SIN/category instructions.

Where does SAM Record fit in the offer package?

It sits beside reps and certs, financial responsibility files, and eOffer company data.

What is the safest review habit?

Check the document against the pricing file, SAM record, narrative responses, and source instructions before uploading it.