Key Statistic
The average win rate for federal proposal submissions across all agencies runs between 20% and 35% for experienced contractors. First-time bidders typically win on their 3rd to 5th attempt. Targeted bidding — using a strict bid/no-bid filter — can push win rates above 40% by concentrating effort on opportunities you are genuinely positioned to win.
Anatomy of a Government Proposal
Every federal solicitation uses the Uniform Contract Format (UCF), dividing the solicitation into Sections A through M. As a contractor, the sections you care most about are:
| Section | Contents | Your Action |
|---|---|---|
| Section C | Statement of Work / Performance Work Statement | Read thoroughly — this is what you are being asked to do |
| Section H | Special Contract Requirements | Review for CMMC levels, clearances, key personnel rules |
| Section I | Contract Clauses | Map compliance requirements; identify flow-downs for subs |
| Section J | List of Attachments | Download and review all attachments — some are critical |
| Section L | Instructions to Offerors | Follow exactly — format, page limits, submission method |
| Section M | Evaluation Factors | Structure your entire proposal to address these criteria explicitly |
Most solicitations also require separate Technical and Price volumes. Some add a Past Performance volume. Never combine volumes unless Section L explicitly allows it — price information in a technical volume can result in rejection.
Technical Approach: How to Structure Yours
The Technical Approach is where most proposals are won or lost. Evaluators are looking for evidence that you understand the problem, have a credible plan to solve it, and have done something similar before. Generic, template-sounding responses consistently score lower than specific, detailed ones.
Mirror the PWS language
Use the exact terminology from the Performance Work Statement. Evaluators often do keyword searches. If the PWS says 'agile sprint planning,' your technical approach should say 'agile sprint planning' — not 'iterative development methodology.'
Show your understanding of the problem, not just your solution
A strong technical approach restates the key challenges the agency faces before describing how you will address them. This shows you read the solicitation carefully and understand what the agency actually cares about.
Include specifics, not platitudes
'We will leverage our experienced team to deliver quality outcomes' scores zero. 'Our team includes 3 PMP-certified project managers with a combined 22 years delivering similar work at DHS and VA' scores well. Specifics always beat generics.
Describe your management approach
How will you communicate with the contracting officer? What is your escalation process? Who is the key person and what makes them qualified? Evaluators want to know you have thought through execution, not just capability.
Address risks proactively
Identify 2–3 realistic risks and describe your mitigation approach for each. Counterintuitively, showing risk awareness scores higher than claiming there are no risks — it demonstrates maturity and experience.
Past Performance: What to Include
Past performance is typically the second most-weighted evaluation factor after technical approach. The government wants evidence that you have done similar work, for comparable customers, at comparable scale — and that you did it well.
For each past performance example, include: contract number (if federal), agency/client name, period of performance, contract value, scope description (2–3 sentences matching the current PWS), and a point of contact who will speak positively about your work.
Relevance is everything. A $50K commercial project that closely mirrors the current requirement scores higher than a $5M federal contract in a different domain. Select your examples to maximize relevance, not total dollar value.
Always verify your references
Evaluators sometimes call past performance references. Confirm before submission that your contact is still reachable and will speak positively about the work. A call that goes to a disconnected number, or a lukewarm reference, can tank an otherwise strong submission.
Track all your past performance in your pipeline — including project scope, client contacts, and outcomes — so you can pull the right examples quickly for each new proposal.
Pricing: Cost Proposal Basics
Government price proposals vary dramatically by contract type. Fixed-price contracts require a single price per deliverable or period. Cost-reimbursement contracts require detailed cost buildup with support for every line item. Time-and-materials contracts require labor category rates and an estimated number of hours.
Firm Fixed Price (FFP)
You bear all cost risk. Government pays the stated price regardless of your actual costs. Most common for well-defined commercial services.
Contractor riskCost-Plus (CPFF / CPAF)
Government reimburses allowable costs plus a fixed or award fee. Requires DCAA-compliant accounting system. Common for R&D and high-uncertainty work.
Government riskTime & Materials (T&M)
Government pays for labor hours at set rates plus actual materials. Common for professional services where scope is hard to define. You must track hours carefully.
Shared riskCommon pricing mistakes: not loading fringe benefits, overhead, and G&A on labor rates; not including escalation for multi-year contracts; underpricing to win and then losing money on performance. Use market data to validate your price is competitive — not just that it covers your costs.
For cost-reimbursement contracts over $2M, you must have a DCAA-compliant accounting system. Work with a government accounting consultant to set this up before bidding cost-type work.
Compliance Matrix: Why It Matters
A compliance matrix is a spreadsheet with every Section L requirement in one column and a reference to where your proposal addresses it in the other. It serves three purposes: it ensures nothing is missed during proposal drafting; it helps you review for completeness before submission; and it makes it easy for evaluators to find your responses, improving scores.
Some large procurements require contractors to submit a compliance matrix as part of the proposal. For others, it is optional but strongly advisable for any solicitation with more than 20 Section L requirements.
FAR and DFARS clauses included in your contract also generate compliance obligations beyond the proposal itself. Our clause library provides plain-English breakdowns of what each clause requires during contract performance — not just proposal preparation.
The Capability Statement
A capability statement is your company's one- to two-page marketing document for government contracting. It is not a proposal — it is a leave-behind for agency small business specialists, contracting officers, and potential teaming partners. Every government contractor needs one.
Core Competencies
3–5 bullet points describing what you do. Match the language to government NAICS codes and PSC codes.
Past Performance
3–5 recent projects with agency/client, contract value, and one-line outcome. Government performance preferred.
Differentiators
What makes you different? Certifications, speed, specialized expertise, proprietary tools. Be specific.
Company Data
UEI, NAICS codes, CAGE code, SBA certifications, SAM.gov active status, cage/DUNS, business size.
Contact Information
Name, title, phone, email. Make it easy to reach you. Many small businesses lose opportunities because their contact info is buried or outdated.
Logo and Branding
Professional design matters. A capability statement with typos and clip art sends the wrong signal.
Common Evaluation Criteria: LPTA vs Best Value
How the government evaluates proposals depends on the procurement type. The two most common frameworks are LPTA (Lowest Price Technically Acceptable) and Best Value (tradeoff between price and non-price factors).
| Attribute | LPTA | Best Value (Tradeoff) |
|---|---|---|
| Decision driver | Price | Price + technical + past perf |
| Technical quality | Pass/fail only | Scored and compared |
| Price premium for quality | Not allowed | Explicitly allowed |
| Typical procurement type | Well-defined, commodity-like services | Complex, judgment-intensive work |
| Winning strategy | Pass the technical bar, price lowest | Differentiate technically, price to win |
| Common NAICS examples | Janitorial, security guard, staffing | IT, R&D, engineering, professional services |
Know which type you are competing in before you invest in proposal development. In an LPTA competition, spending 80 hours on a brilliant technical narrative is wasted effort. In a best value competition, the lowest price with a weak technical volume loses to a moderately higher price with a superior technical approach.
Proposal Writing Timeline
A disciplined timeline prevents the common failure mode: rushing the review and submitting with preventable errors. This is a model timeline for a 30-day response window on a mid-complexity solicitation.
Read solicitation completely
Section C (SOW), L, M, H, I, J. Flag questions. Note all deadlines. Identify Section L requirements.
Submit Q&A questions
Submit written questions by the Q&A deadline. Review all issued amendments.
Build compliance matrix
Map all Section L requirements to proposal sections. Assign owners. Set internal milestones.
Draft technical volume
Write technical approach, management approach, staffing plan. Gather past performance examples and contact info.
Draft price volume
Build cost/price model. Validate rates against market data. Prepare required pricing exhibits.
Internal review (Red Team)
Have a fresh set of eyes read the entire proposal as an evaluator. Score it against Section M criteria. Identify gaps.
Revise and finalize
Address all review comments. Verify every Section L requirement is addressed. Check page counts and formatting.
Compliance check and packaging
Final compliance matrix review. Package per Section L instructions. Test submission portal.
Submit — 24 hours early
Submit at least 24 hours before deadline. Confirm receipt. Keep confirmation records.
Frequently Asked Questions
Section L (Instructions, Conditions, and Notices to Offerors) tells you exactly how to format and organize your proposal — page limits, required sections, font size, file format. Section M (Evaluation Factors for Award) explains how the government will score proposals and which factors matter most. You must respond to every Section L requirement and structure your response to directly address Section M criteria.
As long as the solicitation allows, and no longer. Section L typically sets page limits. Stay within limits — exceeding them can result in disqualification. Within the limit, include everything that demonstrates compliance and differentiates you. Do not pad with generic language. Evaluators read dozens of proposals; concise, specific writing wins.
Past performance is your documented track record on prior contracts — what you did, for whom, the contract value, and how well you performed. If you are new to government contracting, commercial work of similar scope and complexity counts. Subcontracting to an established prime is the fastest way to build a government past performance record. Document everything now — project details, client contacts, outcomes.
LPTA stands for Lowest Price Technically Acceptable. The government evaluates all proposals for technical acceptability (pass/fail), then awards to the lowest-priced acceptable offer. In an LPTA competition, a stronger technical proposal does not win you the contract — only passing the technical threshold matters. Price is the decision. LPTA procurements are most common for commodity-like services with well-defined requirements.
Always. Most solicitations include a question-and-answer period with a submission deadline. Read the entire solicitation before the Q&A cutoff and submit written questions about anything ambiguous. All questions and answers are distributed to all offerors — so your questions can actually improve the whole playing field. Never assume; always ask.
A compliance matrix is a spreadsheet that maps every Section L requirement to the corresponding section in your proposal. It ensures nothing is missed and helps reviewers find your responses quickly. Large procurements sometimes require you to submit one. Even when not required, building one for your own use dramatically reduces the risk of a non-compliant proposal.