Proposal Writing Playbook

Writing a winning government proposal is fundamentally different from commercial sales. In the federal marketplace, evaluation criteria are defined upfront in the solicitation, and contracting officers must follow a structured evaluation process. Your proposal is essentially a written exam — you're answering specific questions and demonstrating specific capabilities.

Every federal solicitation (whether an RFP, RFQ, or IFB) contains evaluation criteria that tell you exactly how your proposal will be scored. These criteria are typically weighted, with technical approach and past performance often carrying more weight than price. Read the solicitation multiple times and highlight every requirement, evaluation factor, and instruction.

The most common mistake new contractors make is treating a government proposal like a marketing brochure. Government evaluators don't want flashy graphics and vague promises — they want specific, verifiable evidence that you can perform the work as described. Every claim should be backed by data, examples, or references.

The executive summary is your first impression and often the most-read section of your proposal. It should be written last (after you've completed all other sections) but placed first in the document. A strong executive summary accomplishes three things: it demonstrates your understanding of the agency's mission and needs, it highlights your unique value proposition, and it summarizes your technical approach.

Start with a clear statement of understanding — show the evaluator that you grasp not just the requirements, but the underlying problem the agency is trying to solve. Reference specific language from the solicitation to demonstrate alignment.

Then present your solution at a high level. What is your approach? Why is it the best approach? What makes your team uniquely qualified? Use concrete metrics where possible: 'Our team has delivered 15 similar projects for DoD agencies, averaging 12% under budget and 98% on-time delivery.'

Keep the executive summary to 1-2 pages for most proposals. Use clear headings, short paragraphs, and avoid jargon. Remember that the executive summary may be read by senior officials who aren't subject matter experts.

The technical approach is the heart of your proposal. It must demonstrate that you understand the work, have a viable plan to execute it, and can manage risks along the way. Structure your technical approach to mirror the solicitation's Statement of Work (SOW) or Performance Work Statement (PWS).

For each major task or requirement, follow this framework: First, restate the requirement to show understanding. Second, describe your approach — what you'll do, how you'll do it, and what tools/methodologies you'll use. Third, explain why your approach is effective — reference industry best practices, lessons learned, or proven methodologies. Fourth, identify potential risks and your mitigation strategies.

Use a compliance matrix to ensure you've addressed every requirement. Create a table with three columns: the solicitation requirement (with section reference), your proposal section that addresses it, and a brief description of how you comply. This is both a planning tool for you and a navigation aid for evaluators.

Include a management plan that covers your organizational structure, key personnel, communication protocols, quality assurance processes, and reporting cadence. Show that you've thought through the practical aspects of contract execution, not just the technical work.

Past performance is often the strongest differentiator between competing proposals. Government evaluators want evidence that you've successfully completed similar work. The key word is 'relevant' — your past performance examples should be as close as possible to the current requirement in scope, complexity, dollar value, and agency type.

For each past performance reference, include the contract number and title, the contracting agency and point of contact, the period of performance and contract value, a description of the work performed, and specific results achieved with metrics. Quantify everything: cost savings delivered, schedule performance, quality metrics, customer satisfaction scores.

If you're a new contractor without federal past performance, you can reference commercial contracts, subcontracting experience, or work performed by key personnel at previous employers (with appropriate disclaimers). Some agencies also accept relevant experience from grants, cooperative agreements, or other transaction agreements.

Always contact your references before submitting a proposal. Let them know they may be contacted, remind them of the project details, and confirm their current contact information. A reference who doesn't respond or gives a lukewarm review can sink an otherwise strong proposal.

Pricing in government contracting follows strict rules depending on the contract type. For firm-fixed-price (FFP) contracts, you're committing to a total price regardless of actual costs. For cost-reimbursement contracts, you're estimating costs that will be audited and reimbursed. For time-and-materials (T&M) contracts, you're proposing labor rates and estimated hours.

Start with a detailed cost buildup. Identify every cost element: direct labor (by labor category and hours), fringe benefits, overhead, materials, travel, subcontractor costs, other direct costs, general and administrative (G&A) expenses, and profit/fee. Each element should be traceable to your technical approach.

Your pricing must be 'fair and reasonable' — the government will compare your price to independent estimates, historical data, and competing offers. Pricing too high loses on cost evaluation; pricing too low raises concerns about your ability to perform (and may trigger a cost realism analysis).

For competitive procurements, understand the evaluation methodology. If it's 'best value' with technical factors more important than price, invest more in your technical approach and price competitively but not necessarily lowest. If it's 'lowest price technically acceptable' (LPTA), your price must be the lowest among technically acceptable offers.

Before submission, conduct a thorough review process. Start with a compliance review — verify that every solicitation requirement is addressed and your proposal follows all formatting instructions (page limits, font size, margins, file naming conventions). Non-compliant proposals can be eliminated without evaluation.

Conduct a 'Red Team' review where colleagues who weren't involved in writing the proposal read it fresh. They should evaluate it against the solicitation criteria and identify weaknesses, gaps, or unclear sections. Give them a scoring sheet based on the evaluation factors.

Check all cross-references, page numbers, and table of contents entries. Verify that all attachments, certifications, and representations are included. Ensure pricing is consistent across all volumes — a discrepancy between your technical approach and cost volume is a red flag.

Submit early — at least 24 hours before the deadline if possible. Technical issues with submission portals (like SAM.gov or agency-specific systems) are common near deadlines, and late submissions are almost never accepted regardless of the reason. Keep confirmation receipts and screenshots as proof of timely submission.