A code list can grow without anyone noticing that its underlying evidence has disappeared. One employee adds a code while pursuing an opportunity. Another copies the list into a capability statement. Years later, the business cannot explain which activities support the entries. Keep a dated research record behind the profile.
SAM.gov distinguishes entity registration from obtaining only a Unique Entity ID. Its registration guidance also explains renewal and update options. A code worksheet is not a completed registration, and a saved profile draft does not demonstrate that a change is active in SAM.gov.
Create a source-of-record list
For each researched code, record its exact title, version, supporting activity statement, evidence owner, and last review date. State whether the activity is current, occasional, or planned. Do not let a planned capability read like established operating experience.
Add a short explanation of why the code appears in the profile. If the original reason was simply that a competitor listed it, send it back for definition research. A competitor's code is not evidence about your establishment's work.
Fictional example: a stale capability sheet
Fictional Pine Harbor Services stops offering a specialized repair service but leaves its code on a PDF capability sheet. A prospective partner asks for supporting experience. The team discovers that the website, profile, and sales attachment now describe different businesses.
Pine Harbor reviews the actual activities, updates its approved internal record, and assigns owners to review each published surface. The process includes checking the authoritative system after any authorized changes. Editing the internal spreadsheet alone does not prove that all external records changed.
Review language as well as codes
Use the activity statement to check headlines, service descriptions, and claims about experience. A correct code cannot repair an exaggerated narrative. Conversely, a truthful service description can help an outsider understand the business even when the classification title is unfamiliar.
Keep procurement screening separate. A business profile supports discovery and recordkeeping, but the code assigned to a particular solicitation and its applicable size requirements still need review. Do not interpret presence on a profile as automatic qualification for every opportunity carrying that code.
- Maintain one dated internal research record.
- Identify the employee responsible for each activity description.
- Review official definitions and code versions.
- Remove or clarify services no longer offered.
- Track which public surfaces need an authorized update.
- Verify the authoritative record after a change.
Use business changes as review triggers: a new service line, acquisition, closure, or major shift in delivery can justify a fresh look. Preserve the earlier reasoning and record what changed. That history helps a future employee distinguish a deliberate classification decision from an unexplained edit and keeps the company's public story aligned with actual operations.
Official sources & further reading
Sources checked for this edition: October 26, 2026. Recheck the current source and applicable contract before acting.
Keep the next step concrete
Use the working tool to capture your assumptions, supporting sources, and the decision that still needs review.