How to respond to a SAM.gov solicitation: a small-business walkthrough

The Situation Most Small Businesses Face

A small IT services firm in Reston spots a SAM.gov solicitation for a network operations support contract. The NAICS is 541512, the set-aside is total small business, and the period of performance is one base year plus four options. The contracting officer wants proposals in 14 calendar days. The firm has two people who can work on it part-time. This is not unusual. Most small federal contractors do not have a dedicated proposal shop. What they need is a repeatable sequence that does not waste the hours they have.

Below is that sequence, with the specific failure points called out at each step.

Step 1: Read Section M Before You Read Anything Else

Section M is the evaluation criteria section. It tells you exactly how the agency will score your proposal: which factors matter, how they are weighted, and whether price is evaluated separately from technical merit. Most first-time bidders skip straight to the Statement of Work because it describes the actual job. That instinct is backwards.

Consider two common Section M structures. In a best-value tradeoff, the agency might weight Technical Approach as most important, Past Performance as second, and Price as least important. In a Lowest Price Technically Acceptable (LPTA) evaluation, the agency sets a pass/fail technical bar and awards to whoever clears it at the lowest price. These two structures require completely different proposal strategies. A beautifully written technical volume is worth almost nothing in an LPTA competition if your price is not competitive. Spending two days on prose when the award is price-driven is how small businesses lose bids they were qualified to win.

Read Section M first. Write down the factors, their order of importance, and whether the evaluation is best-value tradeoff or LPTA. Then decide whether you can actually score well before you spend another hour on the solicitation.

Step 2: Confirm You Are Actually Eligible

Eligibility has three components, and all three must be true before you invest proposal time.

• Set-aside status. The notice will state whether the acquisition is a total small business set-aside, an 8(a) sole-source or competitive, a WOSB (Women-Owned Small Business), an SDVOSB (Service-Disabled Veteran-Owned Small Business), or unrestricted. If the set-aside requires a socioeconomic certification you do not hold and cannot obtain before the response deadline, stop. There is no workaround.
• NAICS code and size standard. Every solicitation lists a primary NAICS code. That code carries a size standard, either an annual revenue ceiling (for most services) or an employee count ceiling (for manufacturing). Look up your own average annual receipts or headcount and confirm you are under the threshold. SBA publishes the full table at sba.gov. A firm that self-certifies as small when it is not faces False Claims Act exposure, not just disqualification.
• SAM.gov registration status. Your Unique Entity Identifier (UEI) and CAGE code must be active. Log into SAM.gov and check the expiration date on your registration. An expired registration is an automatic disqualifier under FAR 4.1102, regardless of how strong your proposal is. Renewals take time, so do not assume you are current because you registered last year.

Step 3: Build Your Requirements List from Section L

Section L (Instructions to Offerors) is the proposal rulebook. It specifies what volumes to submit, what goes in each volume, page limits, font and margin requirements, file naming conventions, the submission portal or email address, and the deadline including time zone. Government solicitations frequently specify Eastern Time, but some agencies use local time for field offices in other zones. Getting this wrong costs you the bid.

The right approach is to read Section L slowly and convert every instruction into a line item on a checklist. A typical Section L checklist for a mid-size services solicitation might include entries like:

• Volume I: Technical Approach, 30 pages maximum, 12-point Times New Roman, 1-inch margins
• Volume II: Past Performance, 15 pages maximum, three references minimum
• Volume III: Price/Cost, no page limit, use the government-provided spreadsheet
• File naming convention: CompanyName_VolumeI_TechnicalApproach.pdf
• Submission portal: beta.SAM.gov or agency-specific portal (confirm the exact URL)
• Deadline: Day, date, time, and time zone

A 31-page technical volume against a 30-page limit can be rejected without evaluation. Contracting officers are not required to read past the page limit, and many do not. The compliance failure that kills a proposal is almost never a capability gap. It is a missed format rule that a checklist would have caught.

Step 4: Pull Every "Shall" and "Must" from the SOW or PWS

The Statement of Work (SOW) or Performance Work Statement (PWS) contains the binding requirements of the contract. They are written in the imperative: "the contractor shall," "the contractor must," "the contractor will." Each one of those phrases describes something the government expects you to do, and each one is something your proposal must address.

Go through the SOW line by line and extract every "shall" and "must" into a separate list. A 10-page SOW might yield 40 to 60 discrete requirements. This list becomes the spine of your technical volume. If a requirement appears in the SOW but is not answered somewhere in your proposal, an evaluator will mark it as a gap. Gaps cost you points in a best-value competition and can trigger a deficiency finding that eliminates you entirely.

One practical note: some solicitations use a PWS instead of a SOW. The difference is that a PWS describes outcomes the government wants rather than tasks it prescribes. The extraction process is the same, but you are looking for performance standards and measurable outcomes rather than specific tasks. Either way, if the government wrote it as a requirement, your proposal has to answer it.

Step 5: Draft Each Volume Against the Lists, Not from Scratch

With your Section L checklist and your "shall" list in hand, you are not writing a proposal from a blank page. You are filling in a structured answer to a structured question set.

Map each SOW requirement to the volume and section where you will address it. Some requirements belong in the technical approach. Others belong in the management approach or the staffing plan. Past performance is its own volume. The mapping exercise forces you to account for every requirement before you write a word, which is far more efficient than drafting prose and hoping you covered everything.

For past performance specifically: only cite contracts you can document and that a contracting officer could verify through CPARS (Contractor Performance Assessment Reporting System) or through a reference who will actually respond. A past-performance claim that cannot be verified is worse than a thin record, because it raises questions about the credibility of everything else in your proposal. If you are a newer firm with limited federal history, cite relevant commercial work with specifics: contract value, scope, measurable outcomes. Acknowledge the limited federal history directly and explain what makes your team qualified.

Step 6: Run a Compliance Pass Before You Touch the Submit Button

Before you upload anything, return to both lists. Go through the Section L checklist line by line: correct volume structure, correct page counts, correct font and margins, correct file names, correct submission portal. Then go through the "shall" list: is every requirement addressed somewhere in the proposal? Is every past-performance reference real, current, and verifiable?

This pass is unglamorous work. It takes an hour or two on a typical solicitation. It is also the single highest-value hour in the entire process. The proposals that get eliminated are almost never eliminated because the offeror lacked capability. They are eliminated because someone skipped this step.

If you have a colleague who did not write the proposal, have them run the compliance pass. A fresh set of eyes catches the page count that crept over the limit and the SOW requirement that got answered in the wrong volume.

Step 7: Submit Early

Submission portals slow down under load near deadlines. PDF files generated from complex Word documents can be large. Agency portals sometimes require registration steps you did not anticipate. A late submission is a non-submission under FAR 15.208. There is no grace period and no appeal for a file that arrived one minute late.

Submit at least two to three hours before the deadline. Confirm receipt. Save the confirmation. If the portal generates a timestamp, screenshot it.

The Full Sequence in One View

1. Read Section M: understand the evaluation criteria and weighting before you commit to pursuing the bid.
2. Confirm eligibility: set-aside status, NAICS size standard, active SAM.gov registration.
3. Build the Section L checklist: every format rule, page limit, file name, and deadline as a line item.
4. Extract every "shall" and "must" from the SOW or PWS into a requirements list.
5. Draft each volume by mapping requirements to sections, not by writing from scratch.
6. Run the compliance pass against both lists before you upload anything.
7. Submit early and confirm receipt.

None of this requires a proposal department. It requires the discipline to convert a long government document into a checklist and answer every line. That discipline is what IT Custom Solution LLC built Winrove to support. Paste the solicitation, get the "shall" list sorted into the Section L volume structure, and before you submit, see exactly which requirements your draft has not yet answered. Plans start at $49 per month at winrove.com.

The takeaway: most small businesses lose solicitations they were qualified to win because they skipped the compliance work, not because a larger competitor outperformed them on capability. A checklist built from Section L and the SOW is not a shortcut. It is the actual method.