The SAM.gov notice is a pointer. The requirements live in the attached solicitation, in clauses the solicitation incorporates by reference without printing, and in restricted attachments you may not be able to open until you’ve met a condition stated somewhere else in the same package. Read the attachment end to end once, then build a locator map: document, page, requirement, checkpoint, state. Nothing in the summary substitutes for that read.
This is Step 2 of the solicitation review. The rows you find here go into the requirements matrix.
A 24-character description and a 75-page package
On 21 August 2026, DLA Land Warren posted a solicitation for an engine assembly, SPRDL1-26-R-0121. The description field on SAM.gov reads, in full: “Please see solicitation.”
The attached package runs 75 pages. Here’s where five requirements sat.
| Requirement | Where it was | Page |
|---|---|---|
| Acknowledge every amendment by number and issue date | Narrative AS7001, a fill-in block after the SF 1449 | 2 |
| First article test, one unit, report required under FAR 52.209-3, waiver possible | Line item 0001AB and its narrative | 7–8 |
| How to obtain the technical data package, who may request it, what applies if it carries an export-control warning | Narrative CS6334, “Technical Data Package Information” | 11–12 |
| CMMC Level 2 (Self) required prior to award for each system that will handle FCI or CUI, status and affirmation in SPRS | DFARS 252.204-7025 printed in full on a continuation sheet | 35 |
| Instructions to offerors, including amendment acknowledgment as an offer element | FAR 52.212-1, incorporated by reference in block 27a, not printed | Block 27a, page 1 |
A reader who searched the notice for “CMMC” would have found nothing. A reader who opened the PDF and stopped at the schedule would have missed the access instructions and the provision that decides award eligibility.
Five places requirements hide
Form blocks. The SF 1449 or SF 18 on page 1 carries set-aside status, response date and the incorporated-clause list in small checkboxes. In this package the set-aside block was left blank, which is itself a fact to record.
Coded narratives. DLA packages use narrative codes (AS7001, AS7311, CS6334) with a header and an “End of Narrative” line. Each is a self-contained instruction. Search the PDF for “End of Narrative” and read every block between them.
Continuation sheets. Long provisions get printed across numbered continuation pages with the solicitation number repeated in the header. The CMMC provision in this package starts on page 35 with the contracting officer’s insertion, “CMMC Level 2 (Self)”, already filled in. Page-number citations matter here because the same provision appears in other packages with a different insertion.
Clauses incorporated by reference. Block 27a says the solicitation “Incorporates By Reference FAR 52.212-1, 52.212-4.” Neither is printed. FAR 52.212-1(b)(9) lists acknowledgment of solicitation amendments among the contents of an offer. If you don’t fetch the clause, you don’t know that. And this package carries an addendum that modifies paragraph (h) of 52.212-1, so the clean clause from acquisition.gov isn’t the whole story either. Check for addenda before you rely on the standard text.
Restricted attachments. The technical data package for this solicitation “resides within sam.gov” and is requested by clicking the document title. Only one person in the company may request it, and that person “must be registered as the Data Custodian, as identified in the JCP.” You may be reading a solicitation whose most important attachment you can’t open yet.
The incorporation check
For each clause or provision incorporated by reference, obtain the text matching the number and edition date listed in the solicitation. Record applicable deviations, alternates and addenda. Acquisition.gov’s current text may differ from the incorporated edition. Use its archives or request the governing text from the contracting officer when needed. For each named attachment, record whether you hold it and how the package says to obtain it.
That second half produces the interesting rows. In this package, narrative CS6334 says that TDPs carrying an Export Control Warning Notice require “a current DD 2345, Militarily Critical Technical Data Agreement on file” and DLA Enhanced Validation, and it gives the buyer’s own estimate: “Processing time is estimated at six (6) to ten (10) weeks after receipt.” Whether this TDP carries that warning isn’t stated in the text. You find out by having the custodian request it.
So the row reads: requirement conditional, applies if the TDP is export-controlled, state unresolved, next action custodian requests access, owner named, and a note that, against the response window posted on 21 Aug 2026, the buyer’s own DEV processing estimate ran longer than the time available.
What the same check looks like elsewhere
The Navy’s Hellfire adapter RFQ (N6833526Q1186, issued 25 August 2026) put its access conditions in prose on page 2, ahead of the schedule, and made them unconditional: a certified DD Form 2345 and a verified CMMC status before the drawings are released. Same kind of requirement, different location, different certainty. The map has to record both.
The locator map
| Document | Page or block | Requirement (verbatim or marked paraphrase) | Checkpoint | State | Next action |
|---|---|---|---|---|---|
Keep it beside the requirements matrix. The map answers “where did this come from”. The matrix answers “what do we do about it”.
Where Deep Fathom fits
The locator map helps your team identify security requirements that need supporting evidence. Deep Fathom’s current scope includes evidence management and obligation-to-work traceability. Bring the public source and the evidence question to a platform evaluation so our team can demonstrate the applicable workflow.
Reading the package is yours. Keeping the rows you find connected to their evidence is what Deep Fathom does.
If a row you’ve traced names a security or evidence requirement, tell our team which document and deadline you’re working through. We’ll show which Deep Fathom workflow applies. Review bid requirements