Anatomy of a 112-page DoD RFP

This is a composite teardown. We are not naming a specific solicitation number. The structure described below is drawn from the patterns visible across recent Department of Defense RFPs posted to SAM.gov — the public solicitation portal — synthesized into a representative 112-page document. Where we cite specific clause language, the language is FAR-standard and quoted from the regulation, not from any one solicitation.

The point of the teardown is structural literacy. If you understand how a DoD RFP is organized, you can read a new one in two hours instead of two days, and you can find the editorial weight quickly enough to make a real bid/no-bid decision.

The shape of the document

A typical DoD RFP arrives as a uniform contract format (UCF) document. The UCF is a thirteen-section structure mandated by the FAR. The sections do not vary across DoD solicitations, even when the underlying procurement does. Memorize the structure once and you can navigate every DoD RFP.

The thirteen sections, by letter:

Section A — Solicitation/Contract Form. The cover sheet. Names, dates, contract type, set-aside status.
Section B — Supplies or Services and Prices/Costs. The line-item structure of the procurement. CLINs (contract line item numbers).
Section C — Description/Specifications/Statement of Work. The Statement of Work. The substantive what-the-vendor-will-do.
Section D — Packaging and Marking. Logistics. Usually short.
Section E — Inspection and Acceptance. Quality and acceptance criteria.
Section F — Deliveries or Performance. Schedule of deliverables.
Section G — Contract Administration Data. Invoicing, points of contact, administrative mechanics.
Section H — Special Contract Requirements. Non-standard clauses specific to this procurement.
Section I — Contract Clauses. Standard FAR clauses, mostly by reference.
Section J — List of Attachments. Pointer to attachments — performance work statements, technical specifications, past performance forms, pricing worksheets.
Section K — Representations, Certifications, and Other Statements. Vendor certifications.
Section L — Instructions, Conditions, and Notices to Offerors. How to respond. Page limits, formatting, submission mechanics.
Section M — Evaluation Factors for Award. The scoring methodology. The most important section in the document.

A 112-page DoD RFP, in our composite, distributes roughly:

A through J: ~60 pages of substance and boilerplate, with C (the SOW) being the bulk and J pointing to attachments that may add another 40 to 80 pages.
K: ~10 pages of certifications.
L: ~15 pages of submission instructions.
M: ~5 to 12 pages of evaluation methodology — the highest-density section in the document.
Attachments: 40 to 100 additional pages, depending on the procurement.

When we say “112-page RFP,” we mean the main solicitation document. Attachments push the total reading load to 200 to 300 pages on a substantial procurement.

Read M first

The Federal Acquisition Regulation, Subpart 15.3, governs source selection for negotiated procurements. Section M of the RFP is where the FAR-required evaluation factors live. Read it before anything else.

A DoD Section M typically defines:

Evaluation factors and subfactors. A factor is a top-level dimension (Technical, Past Performance, Cost). A subfactor is a sub-dimension (Technical might decompose into Technical Approach, Management Approach, Key Personnel). The hierarchy matters because the rubric scores at the subfactor level and rolls up.

Relative weighting. Either explicitly numerical (“Technical is weighted at 50%”) or qualitatively ranked (“The Technical factor is significantly more important than Past Performance, which is approximately equal to Cost”). DoD source-selection procedures favor qualitative rankings on best-value tradeoffs.

Source selection method. Lowest Price Technically Acceptable (LPTA), best-value tradeoff, or in some commodity buys, technically acceptable / risk-adjusted price. The method is the single most important fact in the document — see Tuesday’s pillar piece on why this distinction reshapes the entire response.

Acceptable / unacceptable thresholds. Where applicable (most common in LPTA and in technically-acceptable procurements), the threshold the technical proposal must clear. Below threshold, the bid is non-responsive regardless of price.

Evaluation method per factor. Adjectival ratings (“Outstanding / Good / Acceptable / Marginal / Unacceptable”), color ratings (“Blue / Green / Yellow / Red”), or in some cases narrative-only with no rating scheme. The DoD Source Selection Procedures specify the standard adjectival scheme, but individual buying activities sometimes use variations.

Past performance evaluation methodology. How recent and relevant past contracts will be assessed. Often distinct from the technical evaluation methodology.

A composite Section M for our 112-page solicitation might read:

The Government will award a contract resulting from this solicitation to the responsible offeror whose proposal, conforming to the solicitation, will be most advantageous to the Government, price and other factors considered. The following factors shall be used to evaluate offers:

Factor 1 — Technical Approach (significantly more important than Past Performance) Subfactor 1A — Technical Solution Subfactor 1B — Management Approach Subfactor 1C — Key Personnel

Factor 2 — Past Performance (approximately equal to Cost)

Factor 3 — Cost/Price (least important factor)

All non-cost factors, when combined, are significantly more important than cost.

That paragraph tells you almost everything about how to allocate writing effort. Technical is the dominant factor. Within Technical, the subfactors are scored separately — your response should structure to address each subfactor in its own section, not blend them. Past Performance and Cost matter, but the editorial weight goes to Technical.

The weighting language also tells you the trade space. “All non-cost factors, when combined, are significantly more important than cost” means the evaluator will pay more for a meaningfully better technical proposal. This is best-value, not LPTA. Over-investing in cost reduction at the expense of technical quality is a strategy that loses in this procurement.

Read L second

Section L tells you how to write the response. Page limits, formatting, font requirements, file naming, submission portal, addenda procedures.

A typical L on our composite:

Volume I — Technical Proposal: 75-page limit, single-spaced, 12-point Times New Roman, 1-inch margins, separate volumes by subfactor.
Volume II — Past Performance: 25-page limit, including past-performance information forms (Attachment 4) for each cited contract.
Volume III — Cost/Price Proposal: no page limit, Excel pricing worksheet (Attachment 6) plus a cost narrative.
Volume IV — Contract Administrative: certifications (Section K), representations, executed signature pages.

The page-limit allocation across volumes is itself a clue. A 75-page technical volume in a procurement where Technical decomposes into three subfactors implies roughly 25 pages per subfactor — the procurement office is signaling that each subfactor deserves substantial treatment. A 25-page past-performance volume implies five to seven cited contracts, given the form length. A no-page-limit cost volume signals that the cost narrative is graded on completeness and traceability rather than concision.

L also names the submission mechanics. Federal procurements increasingly use the eBuy or DLA submission portals. Format compliance is enforced mechanically — a PDF that exceeds the page limit is rejected, not penalized. Read L carefully and build the submission checklist in week one. We have written about the Sunday-night compliance check that catches submission-mechanics issues early.

Read C third

Section C — the Statement of Work — is where the substantive scope lives. On our 112-page composite, C runs roughly 40 pages and references several attachments (a Performance Work Statement, a technical-requirements document, sometimes a Government Furnished Equipment list).

C is the section most teams jump to first. We argue you should read it third, after M and L. Here is why: M tells you what is being scored, L tells you how the response must be structured, and only with those frames in mind can you read C usefully. Read C without M and you build a response that addresses the SOW comprehensively but does not map cleanly to the evaluation factors. Read C without L and you build a response that does not fit the page limits.

When you do read C, read it for three things.

Requirements language. “Shall,” “must,” “will provide” — the contractor’s binding commitments. Highlight every instance. These are the rows of your compliance matrix.

Performance objectives. What the buyer is actually trying to accomplish. Often stated in the introduction or in a “purpose” subsection. Performance objectives are the win-theme target — your response argues that your approach achieves the performance objectives better than the alternatives.

Evaluation hooks. Phrases in the SOW that match the language of Section M. “Demonstrate technical innovation” in the SOW is a hook into the Technical Approach subfactor. “Provide qualified key personnel with relevant experience” is a hook into the Key Personnel subfactor. The hooks tell you which SOW elements are graded against which scoring dimensions.

The attachments

Section J lists attachments. On a 112-page composite RFP, the attachments are typically:

Performance Work Statement (PWS) or Statement of Objectives (SOO).
Technical Requirements Document.
Past Performance Information form.
Cost/Price worksheet (Excel).
Past Performance Questionnaire (sent to vendor’s references).
Wage determinations (if Service Contract Labor Standards apply).
Specifications and standards by reference.

The attachments often contain the most editorially distinct content. The main solicitation is templated; the attachments are where the procurement lead does the work the template constrains. Read every attachment. The cost worksheet’s structure tells you exactly what the cost evaluators expect to see. The PPI form tells you what fields the past-performance evaluation will assess.

Attachments also frequently contain the only place where specific quantitative or qualitative thresholds are stated. “The vendor’s proposed key personnel shall have at least 10 years of relevant experience and an active Top Secret clearance” may appear only in the technical requirements document, not in the main RFP. Missing the attachments means missing the threshold.

What we are reading for, by section

A working summary, in the order we read.

Section M — what is being scored and how, what the source-selection method is, what the trade space looks like.
Section L — how the response must be structured, formatted, and submitted.
Section C — the substantive scope, the requirements language, the performance objectives.
Attachments — the editorially distinct content, the thresholds, the cost worksheet.
Section H — special contract requirements, non-standard clauses.
Section K — certifications and representations the vendor must complete.
Sections A, B, D-G, I, J — administrative substance, read for non-standard items.

A two-hour first read of a 112-page DoD RFP, in this order, gets you the bid-shaping understanding. A second-day deeper read fills in the operational detail.

What this anatomy is not

It is not a substitute for reading the actual RFP. The composite walks the structure; the specific procurement is where the editorial decisions live. Two DoD RFPs with the identical UCF structure can want very different responses based on what is actually written in M, L, and C.

It is not a guarantee of standardization. Different DoD buying activities (Army Contracting Command, Naval Sea Systems Command, Air Force Life Cycle Management Center, DLA, and others) have stylistic variations in how they fill the UCF. The structure is uniform; the prose inside it is not.

It is not federal beyond DoD. Civilian agency RFPs use the same UCF when they use FAR Part 15 procedures, but many civilian procurements use simplified acquisition procedures (FAR Part 13) or commercial item procedures (FAR Part 12), which produce different document shapes. Our composite is DoD-specific.

Where we go from here

The next teardown in this series, landing in August, walks a state-government IT modernization RFP — a different shape, different procurement code, different evaluation methodologies. State and local procurement is structurally distinct from federal, and the differences matter for the bid/no-bid decision.

For now: the next time a DoD RFP lands in your inbox, read M first, L second, C third. The bid-shape decisions you can make in the first two hours, with that reading order, are the decisions that determine whether the next three weeks of work pay off.