Here is a scenario that plays out somewhere in the SDVOSB community every single week. A firm spends five weeks building a proposal. The team is confident. The past performance is strong. The pricing is competitive. They submit it, wait six weeks for a decision, and then read a debrief that says something like: "Offeror did not demonstrate the required experience with [specific system] as outlined in Section H.4 and Attachment J, Exhibit 3."

Section H.4. Attachment J, Exhibit 3. Pages they skimmed, or skipped entirely, because they were focused on Section L (instructions to offerors) and Section M (evaluation criteria). Those are the sections that tell you how to write the proposal. They are not the sections that tell you whether you qualify to win it.

The disqualifying requirement was in the document the whole time. Nobody caught it. The firm burned five weeks and tens of thousands of dollars in labor on a contract they were never going to win.

This is not a proposal writing problem. It is an intelligence problem. And it is solvable.

Why firms read the wrong sections first

The instinct to start with Sections L and M is not wrong. Those sections contain the information you need to structure your proposal, format your volumes, and understand how you will be scored. For a firm that has already decided to bid, they are essential.

The problem is that most firms use Sections L and M to make the go/no-go decision too. They scan the evaluation criteria, confirm their NAICS code matches, verify the set-aside designation, and decide they're qualified. Then they start writing.

That sequence puts the effort before the intelligence. You are committing weeks of work based on incomplete information.

A federal RFP is not a linear document. The requirements that determine whether your firm is eligible are scattered across sections that were not designed with small business BD processes in mind. Contracting officers write solicitations to satisfy FAR requirements and agency standards, not to make your qualification assessment easy.

The five locations where disqualifiers actually live

1. Section H — Special contract requirements

Section H is where agencies put requirements that do not fit neatly into the standard contract clauses. It is also where some of the most specific and unusual eligibility requirements appear. Mandatory certifications beyond your SDVOSB status, facility clearance requirements, specific tool or platform proficiencies, geographic restrictions. None of these are in Section L. All of them can end your bid.

One of the most common Section H disqualifiers for IT firms is a requirement for specific government system access or accreditation. The solicitation says you need a certain clearance level or ATO (Authority to Operate) status that you cannot obtain before award. That requirement is sitting in Section H while you are building your management approach in Section L.

2. Attachment J — Exhibits and documents

Attachment J is a list of attachments. The actual content of those attachments varies widely. Some are benign (wage determinations, government-furnished equipment lists). Others contain detailed technical requirements that include specific experience thresholds, past project sizes, or mandatory system configurations.

The exhibit format makes them easy to deprioritize. They look like reference material. They are often reference material. But when they are not, and when they contain a specific requirement your firm cannot meet, that requirement is just as binding as anything in Section M.

Read every exhibit in Attachment J. All of them. Every page.

3. The Statement of Work or Performance Work Statement

The SOW or PWS describes what the contractor will actually do. It is the operational center of the solicitation. It also, frequently, contains embedded eligibility requirements that do not appear anywhere else.

A common example: the SOW requires the contractor to hold a specific industry certification (ISO, CMMI, FedRAMP authorization) as a condition of performance, not as an evaluation factor. It will not show up in Section M. It will not be mentioned in the evaluation criteria. But you are still required to have it, and if you do not, you either lose the contract after award or you disclose your lack of compliance in the proposal and lose it before.

4. Section C — Descriptions of supplies or services

Section C is the technical description of what is being acquired. On service contracts, it overlaps significantly with the SOW. On supply contracts, it can contain equipment specifications that implicitly require specific manufacturing capacity, origin requirements (Buy American Act provisions), or supplier certifications.

For SDVOSB firms that manufacture or resell products, this is where Buy American Act and Trade Agreements Act compliance requirements live. Getting caught out on country-of-origin requirements after award is not a minor compliance issue. It can result in contract termination.

5. Section I — Contract clauses

Section I incorporates FAR and agency-specific clauses by reference. Most of these are standard. But certain clauses impose obligations that smaller firms genuinely cannot meet. Mandatory subcontracting plans with specific small business utilization targets. Reporting requirements that require dedicated compliance infrastructure. Insurance minimums that exceed standard small business coverage.

These are not disqualifiers in the technical sense. You can submit a compliant proposal without meeting them perfectly. But if you cannot actually perform to those clauses after award, you have a problem that is worse than a lost bid.

Compliance checklist with checkmarks verifying bid requirements
A systematic compliance check before submission catches the disqualifiers that debriefs reveal after the fact.

What you are actually looking for

When you read outside of Sections L and M, you are looking for four categories of hidden requirements.

Past performance specificity. The evaluation criteria in Section M may say "relevant past performance." What relevant means is often defined somewhere else. Look for specific dollar thresholds (must demonstrate experience on contracts of $X million or more), specific subcategory requirements (VistA experience, specific NAICS subcodes), and recency windows (within the last three years, not five).
Certifications and accreditations. Beyond SDVOSB certification, agencies often require additional credentials as conditions of contract performance. ISO 9001, CMMI Level 2 or 3, specific cybersecurity framework compliance (CMMC), FedRAMP authorization. Some of these take months or years to obtain. If you do not have them, you cannot perform the contract even if you win it.
Clearance requirements. Personnel clearance requirements are often listed in the SOW or PWS rather than the evaluation criteria. The solicitation may require a percentage of proposed key personnel to hold active clearances at a specific level. If your team does not have them, and if getting cleared takes 12 months, this is a disqualifier regardless of what the evaluation scorecard says.
Geographic or facility requirements. Federal contracts occasionally require the contractor to maintain a physical presence within a certain distance of the work location, or to operate from a government facility or cleared facility. These appear in Section H, the SOW, or the DD Form 254 (for classified work). They are non-negotiable.

The page 84 problem

The phrase "page 84" comes up a lot in post-bid debriefs. It is not literally always page 84, but it is always late in the document. The solicitation is 120 pages. Your team read the first 40 pages carefully and skimmed the rest. The disqualifying requirement was on page 84.

This is not a failure of effort. It is a failure of process. Reading a 120-page RFP thoroughly enough to catch every embedded requirement is a full-time job during the reading period. Most small firms do not have a full-time proposal reader. The owner reads the summary, the BD lead reads Sections L and M, and someone scans the SOW. That is the standard process for a firm that does not have dedicated proposal staff.

The only reliable solution is to have a systematic checklist for what you are looking for, or to use a tool that reads the entire document and surfaces potential disqualifiers automatically. You cannot catch what you do not read.

Building your own pre-bid checklist

Before committing to any RFP, run through this sequence:

  1. Confirm SDVOSB set-aside designation and verify no teaming requirements that dilute eligibility.
  2. Read Section H completely. Flag any requirement that is not standard and that touches certifications, clearances, facilities, or specific systems.
  3. Open every exhibit in Attachment J. Read the ones that contain technical requirements or past performance standards in full.
  4. Read the SOW or PWS from beginning to end. Flag every "contractor shall" statement that implies a qualification, certification, or resource you may not have.
  5. Search the full document for the words "minimum," "required," "shall demonstrate," and "must have" and read every sentence that contains them in context.
  6. Check Section I for clauses that impose obligations you cannot meet at your current size or with your current infrastructure.

This takes time. On a 150-page solicitation, doing it properly takes three to four hours of focused reading. That is a significant investment before you have even decided to bid.

But consider the alternative. If you skip this process and proceed to proposal development on a contract you were going to lose, you have spent forty hours minimum, often a hundred or more. A four-hour front-end investment to avoid that outcome is not optional. It is the most important thing you do on any potential bid.

What to do when you find a disqualifier

Finding a disqualifier before you commit to a bid is good news, even though it does not feel that way. You have saved weeks of work. The question then becomes whether the disqualifier is addressable.

Some are not. A past performance threshold you cannot meet, a clearance requirement your team does not hold, an accreditation that takes 18 months to obtain. These are genuine no-go signals.

Others are addressable through teaming. If the disqualifier is a specific technical capability or certification, a teaming partner who holds that qualification can bring you into compliance. The decision then becomes whether teaming makes economic sense for this contract, which is a separate analysis.

A third category of apparent disqualifiers are actually ambiguous requirements. When you are uncertain whether a requirement applies to you, the right move is to submit a question during the questions-and-answers period, not to assume you are disqualified and walk away. Contracting officers have the authority to clarify requirements, and a specific question sometimes reveals that the requirement is not what it appeared to be.

Soldiers do reconnaissance before the assault, not after. The same discipline applies here. The intelligence you gather before committing to a bid determines whether you are fighting a winnable battle.

The bottom line

Most hidden disqualifiers are not hidden on purpose. They are the result of how federal solicitations are structured, which is by FAR section rather than by what a small business needs to evaluate quickly. The information is there. It just requires reading the entire document, not just the evaluation-focused sections.

The firms that consistently win federal contracts are the ones that have built this full-document review into their standard process. It is not glamorous. It does not feel like strategy. But it is the difference between a firm that spends its proposal budget on bids it can win and one that spends it on bids it was never going to survive past page 84.