How to Write a Government Proposal That Wins

The First Rule: Compliance Is Everything

Government proposals are fundamentally different from commercial sales pitches. Evaluators use a structured scoring system defined in Section M of the solicitation. They are literally checking boxes against evaluation criteria. If your proposal doesn't address a specific requirement, it gets scored down — no matter how brilliant your solution is.

Before you write a single word, build a compliance matrix. This is a spreadsheet that maps every requirement in the solicitation (Sections C, L, and M) to a specific section of your proposal. Every "shall," "must," and "will" statement in the Statement of Work gets a row. If your compliance matrix has gaps, your proposal has gaps.

The compliance matrix is your proposal blueprint. It ensures nothing gets missed and forces you to address every requirement the government specified. I've seen technically superior solutions lose because they skipped a seemingly minor compliance requirement.

Step 1: Shred the RFP

Read the entire solicitation — every section, every attachment, every amendment. Most contractors skim. Winners dissect. Pay special attention to Section L (Instructions to Offerors) which tells you exactly how to format and organize your proposal, Section M (Evaluation Criteria) which tells you how your proposal will be scored, Section C (Statement of Work/Performance Work Statement) which describes what you need to deliver, and all referenced documents and clauses.

Highlight every instance of "shall," "must," "will," and "required." These are your mandatory compliance points. Missing any one of them can make your entire proposal non-responsive.

Step 2: Build Your Technical Approach

Your technical volume must demonstrate that you understand the problem, have a clear plan to solve it, and can execute that plan with your proposed team and resources. Structure your technical approach to mirror the evaluation criteria order — make it easy for evaluators to score you.

For each requirement, follow the STAR method: State the requirement (show you understand it), describe your Technical approach (how you'll do it), explain the Advantage (why your approach is better), and provide the Result (what the government gets).

Use discriminators — specific elements that differentiate your solution from competitors. If everyone can do the basic requirements, what makes your approach uniquely valuable? This might be proprietary tools, specific methodologies, relevant certifications, or geographic advantages.

Step 3: Past Performance That Proves Capability

Past performance is often the most heavily weighted evaluation factor. The government wants proof that you've successfully done similar work. For each reference, describe the contract (scope, value, period of performance), highlight relevance to the current solicitation, quantify results (cost savings, schedule performance, quality metrics), and provide references who will speak positively about your work.

If you're a new contractor with limited federal past performance, use commercial contracts that demonstrate similar capabilities, subcontracting experience under federal primes, work performed by key personnel at previous companies (with their permission), and relevant certifications or training that demonstrate competence.

Read our beginner's guide for strategies on building past performance from scratch.

Step 4: Price to Win

Pricing strategy depends on the evaluation method. If it's "lowest price technically acceptable" (LPTA), you need to be the cheapest compliant offer. If it's "best value tradeoff," you can price higher if your technical approach justifies it. The solicitation tells you which method applies.

Research the competitive landscape. Check FPDS.gov for pricing on similar contracts that have been awarded. Look at the Independent Government Cost Estimate (IGCE) if one is referenced. Price realistically — unrealistically low prices raise red flags and can lead to responsibility determinations.

Your pricing must be defensible. If questioned, you should be able to justify every cost element. Build your pricing from actual labor rates, realistic hours, and documented indirect rates.

Step 5: Quality Control Before Submission

Run a color team review process. A Pink Team reviews your outline and storyboard before you start writing. A Red Team reviews the near-final draft against evaluation criteria. A Gold Team does the final executive review before submission.

Check for compliance matrix completeness, page limits and formatting requirements, consistent use of terminology from the solicitation, all required certifications and representations included, and submission instructions (electronic vs. hardcopy, file formats, naming conventions).

Common Mistakes That Kill Proposals