Why Most Proposals Lose
Government proposal evaluation is more systematic than most agency owners realize. Evaluators typically score proposals against a defined rubric — assigning numerical scores to specific factors like technical approach, past performance, and management. The proposal that best addresses each criterion in the evaluator's rubric wins, regardless of the agency's reputation or the quality of its commercial portfolio.
Most proposals lose because they're written for the wrong audience. Agency owners write to impress — showcasing creativity, brand voice, and past client logos. Government evaluators score against criteria — looking for specific evidence that you understand the requirement and can deliver it. These are fundamentally different documents.
This guide explains how to write for government evaluators.
Before You Write: Understand the Evaluation Criteria
Every government RFP includes an evaluation section that describes exactly how proposals will be scored. Read it before you write a single word of your proposal. Common evaluation factors for marketing and creative service contracts:
- Technical approach / Understanding of the requirement — usually the most heavily weighted factor. Evaluators assess whether you understand what they need and have a credible plan to deliver it.
- Past performance — typically second. Do you have documented experience doing similar work for similar clients?
- Key personnel — who will actually do the work? Government evaluators evaluate specific people, not just your firm.
- Management approach — how will the project be managed? What is your quality assurance process?
- Price — evaluated separately, often on a best-value basis. You don't need to be the cheapest, but your price must be realistic and defensible.
Note the order and relative weighting. If technical approach is "significantly more important" than past performance, allocate your writing effort accordingly.
Structure Your Proposal Around Evaluation Factors
The most common proposal mistake is organizing around your agency's preferred narrative rather than the RFP's evaluation structure. Write your proposal with a section for each evaluation factor, in the same order the RFP presents them. Label your sections with the same language the RFP uses.
Example: if the RFP evaluates "Technical Approach" and "Understanding of the Requirement" as sub-factors of the technical volume, your proposal should have explicit sub-sections labeled exactly that. Evaluators who are scoring against a rubric need to find each piece of evidence quickly. Make their job easy.
Writing the Technical Volume: The Section That Wins or Loses
The technical volume is where most proposals succeed or fail. Government evaluators are looking for three things:
1. Demonstrated Understanding
Paraphrase the requirement back in your own words. Identify the specific challenges the agency faces. Reference details from the Statement of Work (SOW) that show you've read and understood it. Evaluators can immediately tell the difference between a proposal written for this RFP versus a recycled generic proposal.
What not to do: "We understand that this is a complex marketing challenge that requires creativity and strategic thinking." This says nothing specific and scores near zero.
What to do: "The agency's challenge is reaching the 18-25 demographic in rural markets, where traditional media penetration is declining and digital channels require localization. Our approach addresses this by..."
2. A Clear, Specific Methodology
Describe your process step by step. Not "we will develop a creative strategy" but: "In Phase 1 (weeks 1–3), we will conduct stakeholder interviews with the agency's communications office and program staff to document existing messaging frameworks, identify audience segments, and establish success metrics. Deliverables: Audience Analysis Memo (CDRL A001), Draft Communications Strategy (CDRL A002)."
Use phases, milestones, deliverables, and timelines. Government clients are accustomed to structured project management. Proposals that describe work in vague terms signal risk to evaluators.
3. Differentiators Supported by Evidence
Claim nothing you can't prove. "We have deep expertise in multicultural health communications" is a claim. "We developed the bilingual outreach campaign for [client] that increased enrollment among Spanish-speaking adults by 23% — a campaign referenced in the HRSA 2024 annual report" is evidence. Evidence wins.
Writing Past Performance: Be Specific, Be Verifiable
Past performance should be written as a factual record, not marketing copy. For each reference:
- Client name and agency/organization
- Contract value (or estimated project value)
- Period of performance (start and end dates)
- Scope description — 2–4 sentences describing what you did
- Results achieved — quantified where possible (reach, impressions, enrollment lift, website traffic increase)
- Reference contact — name, title, phone, and email. Government evaluators may call these references.
Relevance matters more than impressiveness. A $200,000 public health outreach campaign for a regional nonprofit is more relevant to a CDC RFP than a $5 million Super Bowl campaign for a consumer brand.
Key Personnel: The Section Most Agencies Underprepare
Government clients are buying people as much as they're buying a firm. The key personnel section should include:
- Abbreviated resumes (typically 2–4 pages each) tailored to the specific work
- A clear mapping of each person's role on this contract
- Specific relevant experience called out — not a generic career summary
Tip: For key personnel, highlight any prior government contract experience first, then relevant commercial experience. Government evaluators weight government experience more heavily.
Price Volume: Realistic, Defensible, Not the Cheapest
Government "best value" procurements evaluate price alongside technical factors. You don't need to be the lowest bidder, but your price needs to be:
- Realistic — based on actual labor hours, realistic rates, and appropriate overhead. Evaluators compare your labor categories and rates against market benchmarks. Rates that are too low raise concerns about your ability to staff the contract.
- Internally consistent — your price should reflect the staffing and hours described in your technical volume. If you said you'll dedicate a full-time Project Manager, your price should include those PM hours.
- Fully burdened — include direct labor, fringe benefits, overhead, G&A, and fee (profit). Government contracting officers understand these cost elements; provide them clearly.
Formatting and Compliance
Government RFPs often include specific formatting requirements: page limits, font size, margin requirements, file format. Non-compliant proposals can be disqualified before evaluation begins. Check every formatting requirement before submitting:
- Page limits (often strict — use them fully but don't exceed them)
- Font and margin specifications
- File format (typically PDF, sometimes specific portal upload formats)
- Volume organization (some RFPs require separate files for technical and price volumes)
- Submission method and deadline (a minute late is a disqualifying late)
After You Submit: Request Feedback Win or Lose
Government agencies are required to provide debriefs on request. Win or lose, request one. A 30-minute debrief with a contracting officer will tell you more about improving your proposals than any proposal writing guide — because it tells you exactly what scored well and what didn't for this specific agency on this specific procurement.