This video walks through the core concepts for this module. Watch it first, then use the slides below to go deeper.
The work was strong. The pricing was competitive. But Section L required a specific page format the team ignored, and Section M listed three evaluation criteria they never mapped to. Disqualified for non-responsiveness. $450,000 contract, gone — not because of bad writing, but because no one on the team knew how to read a solicitation the way an evaluator scores it.
Imagine a professor hands you a 200-page exam. Most students flip to Page 1 and start answering questions. The experienced student turns to the last page first — the grading rubric. Once they know that Question 7 is worth 40 points and Question 2 is worth 5, every decision they make about where to spend time changes.
That's exactly what Section M is. It's the grading rubric. Contractors who open Section C first and start building their technical approach before reading M are spending hours on a 5-point question without knowing a 40-point question exists three pages later. Read M first. Always.
Most contractors read a solicitation front to back like a narrative — trying to understand what the job is. Evaluators read responses back to front, checking boxes against a scoring rubric that's written in Section M. The contractor who writes to what the job is will lose to the contractor who writes to what the evaluator is scoring. Those two things are often different.
Federal solicitations use a standardized structure. Once you know it, you can navigate any federal solicitation efficiently — even a 300-page one.
| Section | Title | Why It Matters |
|---|---|---|
| Section M | Evaluation Criteria | How your proposal will be scored, and in what order of priority. Read this first — always. Section M is your proposal strategy document. |
| Section L | Instructions to Offerors | Exactly what to submit, how, when, in what format. Every "shall" in Section L is a potential disqualification if ignored. Your compliance matrix is built from this section. |
| Section B | Supplies / Services / Prices | Where pricing goes. On IFBs, this is the only section that matters for award. On RFPs, pricing format requirements here are binding. |
| Section C | Statement of Work (SOW) | The actual work the government wants done. Read this with Section M open — every SOW requirement maps to an evaluation criterion. That mapping becomes your proposal outline. |
| Section H | Special Requirements | Agency-specific clauses that often get overlooked: security clearance requirements, subcontracting plans (if you're a large business or if required), insurance minimums, reporting cadences, and key personnel notification requirements. These are contract obligations from day one. |
| Section I | Contract Clauses (FAR) | Legal requirements incorporated by reference. The ones that create immediate obligations: FAR 52.222-41 (Service Contract Act — wage rates), FAR 52.219-8 (small business subcontracting), FAR 52.222-26 (Equal Opportunity). Know these before you sign. |
| Section J | Attachments / Exhibits | Required forms, templates, and specs. Always check — missing a required attachment (wage determinations, SF-1449, representations and certifications) is an automatic disqualifier. |
Section M will tell you which evaluation methodology applies. This is one of the most important things you'll read in any solicitation, and most contractors skip past it.
LPTA (Lowest Price Technically Acceptable): Your proposal will be evaluated pass/fail on technical merit and past performance. If you pass, the lowest price wins. There is no benefit to exceeding the technical standard — zero. Spending time writing a brilliant technical approach on an LPTA is wasted energy. Your job is to meet the bar cleanly, then price aggressively.
Best Value: Technical merit, past performance, and price are weighed together. The agency can pay more for a demonstrably superior offer. This is where proposal quality wins contracts. On a Best Value RFP, your technical approach is an investment — not a cost.
Texas state solicitations (ESBD) use different section labels but the same principle applies. Look for an "Evaluation Criteria" or "Method of Award" section first — it's typically in the front of the solicitation document. HUBZone preferences and set-aside determinations will appear here as well.
When a new RFP lands, do not start writing. Spend the first hour doing this.
Print or digitally annotate your copy of the solicitation. Every "shall," "must," and "will" you encounter gets highlighted in red — these are mandatory requirements. Every "should" gets highlighted in yellow — these are preferences, not requirements. When you're done with Section C, your annotated copy is the draft of your compliance matrix. Nothing gets missed because you can physically see the unchecked requirements on the page.
A spreadsheet or table that maps every requirement from the solicitation to the section of your proposal that addresses it. Ensures nothing is missed.
| Solicitation Ref | Requirement | Proposal Section | Page/Count Limit | Assigned To | Status |
|---|---|---|---|---|---|
| L.3.1 | Technical Approach — 20 page limit | Volume I, Section 2 | 20 pages max | Sarah | In Progress |
| L.3.2 | Past Performance — 3 references required | Volume II | 2 pages each | Marcus | Not Started |
| L.4.1 | Signed SF-1449 form | Volume III | N/A (form) | PM | Not Started |
| M.2 | Key Personnel — PM must have PMP | Volume I, Section 3 | 1 page each | Sarah | Complete ✓ |
| H.4 | Insurance certificate — $1M general liability | Volume III, Tab 4 | N/A (cert) | Admin | Not Started |
| Amend. 2 | Acknowledge Amendment 2 — page limit changed to 18 | Cover letter / SF-1449 | N/A | PM | Not Started |
Before you submit, every row must be complete. Anything left undone is a potential disqualifier. Notice the two additions from the basic 4-column version: Page/Count Limit (so you don't discover on page 19 that you exceeded a limit) and Assigned To (so you know exactly who owns each piece). The amendment row at the bottom is critical — every amendment must be acknowledged in your submission. If the Q&A period changed any requirement, your matrix must reflect the updated version, not the original.
This happens. You're building the matrix and you find a Section L requirement that says "offerors must have a SECRET facility clearance" or "PM must have 10 years of specific-domain experience you don't have." This is the moment the decision gets made — not on day 18 of proposal writing. If it's a SHOULD or a preference, document it and address how you'll compensate. If it's a SHALL and you can't meet it, you have a material deviation. File a Q&A question asking for clarification on whether equivalent experience qualifies. If the answer is no, pass on the bid.
Working through a real solicitation? Alex can help you build your compliance matrix and identify the highest-weight evaluation factors.
The type of solicitation you're looking at changes how you respond — and whether you write a proposal at all. Know the difference before you spend a week writing something nobody asked for.
Lowest price wins. No technical approach, no past performance narrative — the government already knows exactly what it wants, has detailed specifications written, and just needs competitive pricing. Bids are publicly opened at the bid opening date — all prices are read aloud. The award goes to the lowest responsive and responsible bidder. "Responsive" means you met all submission requirements. "Responsible" means you're a capable, qualified vendor. Precision pricing is everything. You'll see IFBs most in construction, facility maintenance, and commodity buys.
Most common for service contracts. Evaluation includes technical factors, past performance, and price. This is where proposal writing skills matter most. Critically: check Section M for whether this is Best Value (quality and price balanced) or LPTA (pass/fail on technical, then lowest price). The answer changes your entire strategy. On Best Value, invest in your technical approach. On LPTA, meet the standard cleanly and price aggressively.
Used for smaller purchases — typically under $250K under simplified acquisition procedures — or orders against existing contract vehicles. Often just a price quote with brief capability confirmation. These are faster to respond to but also faster to lose if pricing is off. For SAP purchases under $10K (micro-purchases), you may not need to compete at all if you have an existing relationship with the agency.
If you're on a contract vehicle like GSA Schedule, OASIS, or SEWP, agencies issue task orders against it. Competition is limited to pre-competed vehicle holders — a dramatically smaller pool. Key distinction: single-award IDIQ means you're the only vendor (no task order competition). Multi-award IDIQ (MAC/GWAC) means you still compete for each order against other vehicle holders. Getting on the vehicle is only step one.
Think of LPTA like a job interview with a pass/fail skills test. Every candidate who passes the test goes into a pile ranked by how cheaply they'll work. Doing extra credit doesn't help you — it just wastes your time. Best Value is like a job interview where the hiring manager is willing to pay 20% more for the right candidate if they're clearly better. Know which interview you're in before you prepare.
Occasionally, a solicitation is written with a specific contractor in mind. Watch for: requirements so specific they could only be met by one company, extremely short response window relative to complexity, SOW that reads like an incumbent's capability statement, single option year contracts. If you see multiple red flags, ask about the specification rationale in Q&A — or pass on the bid.
You can't always tell, but these patterns are strong signals: requirements so specific only one vendor can meet them (proprietary software named as a mandatory tool, unusual certifications with no equivalency language), past performance requirements that demand identical contract size and scope — which only the incumbent has, extremely short response windows relative to the complexity (7–10 days for a 200-page technical proposal), and SOW language that reads like an incumbent's capability statement almost word for word. A single red flag is common. Three or more together is a pattern. File a Q&A about the specification rationale — the agency's written answer tells you whether there's real competition here.
Every solicitation has a formal Q&A period. Potential offerors submit written questions in writing. The agency publishes written answers as amendments, visible to all bidders. Most contractors don't use this effectively — they either skip it entirely or ask only the most basic clarifying questions.
Ask about: ambiguous SOW requirements, unclear evaluation criteria, formatting inconsistencies, any requirement that might prevent your business from competing. The agency's written answer becomes part of the solicitation — a permanent, binding clarification that benefits everyone who reads it.
The strategic question technique: The best Q&A questions don't just clarify — they reveal. Instead of "What does 'relevant experience' mean in Section M.3?" ask "What is the intended outcome of the relevant experience requirement in Section M.3 — is the concern about industry familiarity, contract size, or scope complexity?" The agency's answer tells you what they actually care about, which tells you exactly what story to tell in your past performance section.
Every amendment issued during Q&A must be formally acknowledged in your proposal submission. Most agencies require you to either sign the amendment document and include it in your package, or acknowledge each amendment number on the SF-1449 cover page. Missing even one amendment acknowledgment — even one that didn't change anything substantive — is grounds for automatic disqualification. Add amendment acknowledgment as a row in your compliance matrix with an "Assigned To" and a status. Check it last, right before submission.
After the Q&A period closes, the agency is not obligated to answer additional questions. You are stuck with the solicitation as written, including any ambiguities. If there's a requirement you genuinely cannot interpret, you have three options: (1) take your best interpretation and document your reasoning, (2) address both interpretations in your proposal and note the ambiguity, (3) pass on the bid if the ambiguity creates unacceptable risk. Never reach out to the CO directly after the Q&A period closes — see the CO communication rule from Module 9.
| Term | Definition |
|---|---|
| Section L / M | L = submission instructions (what to send and how). M = evaluation criteria (how it's scored and in what order of priority). Always read M first — it's your grading rubric. Every proposal decision flows from what M says. |
| Statement of Work (SOW) | Section C — describes exactly what the government wants done. Every requirement maps to an evaluation criterion in Section M. Read SOW with M open so you're mapping, not just reading. |
| Performance Work Statement (PWS) | Similar to a SOW but describes desired outcomes rather than specific tasks. Common in service contracts. Gives the contractor more latitude on how to achieve the result — but you're still evaluated on your approach to delivering those outcomes. |
| LPTA | Lowest Price Technically Acceptable — proposals are evaluated pass/fail on technical merit and past performance; if you pass, the lowest price wins. Exceeding the technical standard earns you nothing. Meet the bar cleanly and price competitively. |
| Best Value | An evaluation approach where technical merit, past performance, and price are weighed together. The agency may pay a premium for a demonstrably superior offer. Proposal quality directly affects award probability — invest accordingly. |
| Compliance Matrix | Tracking document mapping every solicitation requirement to the proposal section that addresses it. Includes page/count limits, assigned writer, and status. Also tracks amendment acknowledgments. Your completion checklist before submission. |
| Amendment | A formal change to the solicitation issued in response to Q&A or agency corrections. All amendments must be formally acknowledged in your proposal — typically on the SF-1449 cover page. Failure to acknowledge any amendment is grounds for automatic disqualification. |
| Non-Responsive | A proposal that fails to meet a mandatory requirement — automatically eliminated before quality evaluation begins. This is different from "technically unacceptable," which is a quality failure that may be correctable. Non-responsiveness is a compliance failure with no remedy. |
| IDIQ | Indefinite Delivery/Indefinite Quantity — a contract vehicle where agencies issue task orders. Single-award IDIQ: you're the only vendor, no task order competition. Multi-award IDIQ (MAC/GWAC): you compete for each order against other vehicle holders. |
A real scenario from the field. No answer permanently locks you out — but the consequences below are real. Choose one, then see what unfolds.
A 180-page federal RFP lands in your inbox. The deadline is 3 weeks away. You open the document and go straight to Section C — the Statement of Work — to understand what they need. You start building your technical approach.
Make a choice above, then continue to the knowledge check.
Three quick questions to lock in what you just learned. Click any answer — right or wrong, you'll see the full explanation. The goal is retrieval, not a grade.
Module 11 is about proposal writing — how to structure your technical volume, write to evaluation criteria, and demonstrate past performance in the format evaluators actually score.
Upload any solicitation PDF and get an instant AI summary: key requirements, evaluation criteria, deadlines, set-aside type, and red flags — in under 60 seconds.
Module 11 teaches you how to structure your technical volume, write directly to each evaluation criterion, and present past performance in the format evaluators actually score — so you move from readable to compelling.
Module 11: Proposal Writing →