How to Write a Government Proposal

A winning government proposal rests on two pillars: compliance and evaluation criteria. Compliance means following every instruction in the solicitation exactly as written. Evaluation criteria tell you how your proposal will be scored. Pursuit costs of 3 to 5 percent of contract value are a commonly cited rule of thumb among proposal professionals, and most proposals lose, so bid selectively. Building a compliance matrix before you write a single word is the most important step you can take.

What Is the Uniform Contract Format?

Most federal solicitations follow the Uniform Contract Format (UCF) defined in FAR 15.204. The UCF organizes the solicitation into lettered sections from A through M. As a proposal writer, you need to understand two sections above all others:

• Section L (Instructions to Offerors): Tells you exactly what to submit, in what format, with what page limits, and in what order. Non-compliance with Section L instructions is the most common reason proposals are eliminated before evaluation.
• Section M (Evaluation Criteria): Tells you how your proposal will be scored. Evaluation factors are listed in order of importance (or stated as equal). Your proposal should allocate the most space and effort to the highest-weighted factors.

Before writing anything, read Section L and Section M at least three times. Highlight every "shall," "must," and "will" statement. These are your mandatory requirements, and missing even one can result in your proposal being rated non-responsive.

How Do You Build a Compliance Matrix?

A compliance matrix is a spreadsheet or table that maps every requirement from the solicitation to a specific location in your proposal. It should be the first document you create after receiving an RFP. Here is a basic structure:

• Column 1: Requirement reference (e.g., "Section L.5.2.1")
• Column 2: Requirement text (verbatim from the solicitation)
• Column 3: Proposal section where addressed
• Column 4: Compliance status (compliant, partial, non-compliant)
• Column 5: Notes or approach summary

RFI Hawk's Proposal Architect automatically extracts requirements from solicitation documents and generates a compliance matrix, identifying "shall," "must," and "required" statements across all attachments. This can save days of manual parsing on complex solicitations.

How Do Evaluation Criteria Shape Your Proposal?

Section M tells you exactly how proposals will be scored. This is your roadmap for where to invest your proposal effort. Common evaluation structures include:

• Best Value Tradeoff: The government considers both technical merit and price, with one potentially being more important. Read Section M carefully; it will state whether technical factors are "significantly more important than," "more important than," or "approximately equal to" price.
• Lowest Price Technically Acceptable (LPTA): Proposals either meet the technical threshold or they do not. Among those that meet it, the lowest price wins. For LPTA, focus on clear compliance rather than exceeding requirements.
• Highest Technically Rated with Fair and Reasonable Price: Technical rating drives the decision, with price evaluated only for fairness. Invest heavily in technical differentiation.

Pay close attention to the order and weighting of evaluation factors. If Technical Approach is the highest-weighted factor, that is where your best writers and strongest content should go. Do not spread effort equally across all volumes; weight it to match the evaluation criteria.

How Do You Write Win Themes?

Win themes are the core differentiators that set your proposal apart. They should answer the question: "Why should the government choose us over the competition?" Effective win themes share these characteristics:

• Specific, not generic: Example: "Our team has delivered 47 similar systems across 12 DoD agencies" beats "We have extensive experience."
• Substantiated with evidence: Every claim must be backed by a past performance reference, metric, or concrete example.
• Tied to evaluation criteria: Win themes should directly address what evaluators are scoring.
• Focused on benefits, not features: Example: "Our automated testing framework reduces deployment risk by 40%" is stronger than "We use an automated testing framework."

Develop 3 to 5 win themes before you start writing. Place them prominently in your executive summary and reinforce them throughout every volume. Use callout boxes, graphics, and bold text to ensure evaluators cannot miss your key differentiators.

What Should the Technical Approach Include?

The technical approach (sometimes called the technical volume or technical capability section) is typically the highest-weighted evaluation factor. It must demonstrate that you understand the problem and have a credible plan to solve it. Strong technical approaches include:

• A clear restatement of the problem or mission need (proving you understand the requirement)
• Your specific methodology, tools, and processes for delivering the work
• A staffing plan with key personnel qualifications and organizational chart
• Risk identification and mitigation strategies
• A transition or phase-in plan (especially for recompetes)
• Measurable outcomes tied to the Performance Work Statement requirements

Avoid generic statements like "we have extensive experience" without supporting evidence. Evaluators read hundreds of proposals. Specific details, metrics, and examples from past work are what distinguish a competitive proposal from a mediocre one.

How Important Is Past Performance?

Past performance is usually the second or third most important evaluation factor. According to FAR 15.305, past performance evaluation assesses the offeror's probability of meeting the solicitation requirements based on the offeror's record of relevant contract performance. "Relevant" is the key word; evaluators are looking for contracts similar in scope, size, and complexity to the current requirement.

If you are a new company with limited federal past performance, you can use:

• Commercial contracts that demonstrate relevant capabilities
• Subcontract experience on federal programs
• Key personnel experience from previous employers (when the solicitation allows it)
• State and local government contracts

For each past performance reference, include the contract number, customer point of contact, period of performance, contract value, and a brief narrative explaining relevance to the current opportunity.

What Goes in the Management Approach?

The management volume convinces evaluators that your team can execute the technical approach effectively. Core components include:

• Organizational structure: Include an org chart showing clear lines of authority between your team and the government. Identify the Program Manager and key personnel by name.
• Key personnel qualifications: Provide detailed resumes for all key personnel. Highlight their relevant experience, certifications, clearances, and specific contributions to the proposed program.
• Quality assurance: Describe your QA/QC processes, metrics, and continuous improvement methodology.
• Staffing and transition: Explain how you will recruit, retain, and (if applicable) transition incumbent staff. Provide a realistic transition timeline with milestones.
• Subcontractor management: If using subcontractors, explain how you will manage their performance, ensure quality, and maintain schedule compliance.

What Are the Most Common Proposal Mistakes?

After reviewing thousands of proposals, government evaluators consistently identify the same categories of errors. Win rates of 25 to 30 percent are a commonly cited rule of thumb among proposal professionals, which means most proposals lose. Here are the most frequent reasons:

• Non-compliance: Failing to follow formatting instructions, exceeding page limits, or missing required sections
• Generic content: Reusing boilerplate text that does not address the specific solicitation requirements
• Missing evaluation criteria: Failing to organize your proposal around the stated evaluation factors
• Weak past performance: Citing contracts that are not relevant in scope, size, or complexity
• No win themes: Failing to articulate what makes your approach uniquely valuable
• Late submission: Government deadlines are absolute; there are no extensions

Pursuit costs of 3 to 5 percent of contract value are a commonly cited rule of thumb among proposal professionals. For a $1 million contract, that is $30,000 to $50,000 in proposal preparation. Factor this cost into your bid/no-bid decision before committing resources.

Related Resources

Frequently Asked Questions