The first time you open a federal solicitation, it reads like a legal document written by a committee. That is because it is. Understanding what you are looking at before you start writing is what separates firms that win from firms that produce expensive, unread documents.
This guide covers the structure of a federal solicitation, the standard proposal volumes, how the government scores your submission, and the mistakes that knock out first-time bidders.
The anatomy of a solicitation
Federal solicitations issued under the Federal Acquisition Regulation (FAR) use a standard section format labeled A through M. You do not need to memorize all 13 sections, but you must know two cold.
Section L contains the instructions to offerors. It tells you exactly how to organize your proposal, what volumes to submit, page limits, font requirements, file format, and due date. If Section L says 12-point Times New Roman, single-spaced, with one-inch margins, that is what you submit. Contracting officers have rejected proposals for using 11.5-point font.
Section M contains the evaluation criteria. It tells you what the government cares about, in what order, and how proposals will be scored or ranked. Read Section M before you write a single word. Every paragraph in your technical volume should trace back to a criterion in Section M.
The other sections you will regularly reference:
- Section C (Statement of Work or Performance Work Statement): the actual work you are being asked to do
- Section H (Special contract requirements): agency-specific clauses, reporting requirements, security clearances
- Section K (Representations and certifications): where you self-certify your business size, socioeconomic status, and compliance with various FAR clauses
Standard proposal volumes
Most federal proposals require four volumes. Some solicitations combine them; some add a fifth for oral presentations. The standard four are:
Technical volume. Your plan for doing the work. This is usually the longest volume and the one evaluated most heavily in best-value competitions.
Management volume. Your plan for managing the contract. Key personnel, organizational structure, quality assurance, and transition planning live here.
Past performance volume. Evidence that you have done comparable work before. The government wants to see that you can deliver, not just that you understand the requirement.
Price or cost volume. Your bid. On firm-fixed-price contracts, this is a price. On cost-reimbursable contracts, the government evaluates your cost estimate plus a proposed fee.
How evaluation criteria work
There are three main evaluation approaches, and which one applies changes your strategy.
Lowest Price Technically Acceptable (LPTA). The government defines a minimum technical bar. Any proposal that clears the bar is "technically acceptable." Among acceptable proposals, the lowest price wins. In LPTA competitions, there is no upside to being more technically impressive than the threshold. Write to pass, not to impress, then price aggressively.
Best Value Tradeoff. The government scores technical merit and past performance separately from price, then makes a tradeoff. A higher-priced proposal can beat a lower-priced one if the technical and past performance scores justify it. This is where diverse firms with strong technical approaches can win against larger incumbents on price.
Technically Acceptable, Best Value. A hybrid. Proposals must first be technically acceptable, and then the government selects the best value among acceptable ones, often with price as the dominant factor after the technical threshold.
Section M will tell you whether the evaluation is LPTA or tradeoff, and if it is tradeoff, the relative order of importance of the factors. "Technical is more important than past performance, and both are more important than price" is a common formulation. That sentence should shape how you allocate your writing effort.
What belongs in the technical volume
The technical volume is your answer to Section C, point by point. Evaluators are assigned to specific sections of the SOW. If the SOW has 12 paragraphs and your technical volume skips paragraph 7, the evaluator scoring paragraph 7 has nothing to score. That is a weakness finding, sometimes a deficiency.
A strong technical volume includes:
Understanding of requirements. Restate the problem in your own words. Not a copy-paste of the SOW. Show that you understand what the agency is actually trying to accomplish, including constraints they may have buried in Section H.
Technical approach. Describe how you will do the work. Be specific. If the SOW calls for weekly status reports, describe what is in the report, who produces it, and how you handle a situation where a milestone slips. Vague answers score as weaknesses.
Staffing plan. Who is doing the work and why are they qualified. Attach resumes for key personnel in the format Section L specifies. If the solicitation asks for resumes in a two-page format, a three-page resume is non-compliant.
Relevant experience. Not the same as past performance. The technical volume may include a brief section on relevant experience to support your approach narrative. Keep it short here; the detail goes in the past performance volume.
What belongs in the management volume
Key personnel. Federal contracts often designate specific roles as "key," meaning you cannot replace those people without contracting officer approval. Identify who fills each key role, and for your first proposal, be conservative about committing people who are not actually available.
Transition plan. If there is an incumbent contractor, the government wants to know how you will take over without disrupting the agency's operations. Typical transitions run 30 to 90 days. Describe your day-by-day or week-by-week milestones for standing up the contract.
Quality assurance surveillance plan (QASP) response. Many solicitations include a draft QASP in Section J. Your management volume should address how you will meet each performance standard the government plans to measure.
How to format past performance
Past performance is evaluated separately from technical merit on most best-value solicitations. Evaluators are looking for recency, relevance, and ratings.
Recency is typically defined in the solicitation, often the past three to five years.
Relevance means similar scope, complexity, and dollar value. A $200,000 IT support contract is not strong past performance for a $4 million cybersecurity operations center bid. Match the size and nature of your references to the work being bid.
Ratings come from two sources. The Contractor Performance Assessment Reporting System (CPARS) contains the official government ratings on federal contracts over certain dollar thresholds. Agencies can access your CPARS record directly. For non-federal work or contracts below the CPARS threshold, you submit customer references.
For each past performance entry, include: the contract number (for federal work), the contracting agency and point of contact, the period of performance (start and end dates), the total contract value, a brief description of the scope, and a summary of performance challenges and how you resolved them.
Do not submit five thin references. Two or three detailed, well-matched references will outscore five generic ones.
How price and cost are evaluated
On firm-fixed-price contracts, the government compares your total evaluated price to other offerors. In LPTA competitions, lowest price among technically acceptable proposals wins. In tradeoff competitions, the contracting officer documents why a higher price is or is not justified by technical superiority.
On cost-plus contracts, the government audits your cost estimate. The Defense Contract Audit Agency (DCAA) or agency cost analysts will assess whether your labor rates, overhead rates, and fee are realistic. They calculate a "most probable cost" that may differ from your proposed cost. You are evaluated on the government's adjusted number, not your proposal number. Understating your indirect rates to look cheap will backfire.
For a diverse firm's first federal bid, fixed-price contracts are simpler to price and to win. Cost-reimbursable vehicles require established accounting systems that can segregate costs by contract, which is an audit requirement that takes months to set up.
The most common mistakes
Not answering the SOW paragraph by paragraph. Create a compliance matrix. List every SOW requirement in a spreadsheet. Map each requirement to a specific page in your proposal. If you cannot fill in that cell, you have a gap.
Exceeding page limits. The contracting officer does not have discretion here. Many agencies use automated tools that stop reading at the page limit. Write to the limit, not over it.
Missing required representations. Section K requires certifications. If you are bidding as an 8(a), WOSB, SDVOSB, or HUBZone firm, your SAM.gov registration must reflect that status before the proposal due date. An expired SAM registration disqualifies you automatically.
Using the same proposal twice. Federal agencies are different. The Department of Defense and the Department of Health and Human Services have different cultures, priorities, and contract types. A proposal written for one rarely reads well for the other.
Ignoring the deadline. Proposal extensions are rare. The FAR permits them only in narrow circumstances, usually when the agency amends the solicitation so late that offerors cannot respond in time. If the deadline is 2:00 PM Eastern, a submission at 2:01 PM is late. Most agencies use electronic portals that lock at the deadline timestamp with no appeal.
Where to start
Read Section M first. Then read Section C. Then read Section L. Write your compliance matrix before you write your first sentence of proposal text. If you are bidding as a diverse firm under a set-aside, verify your SAM.gov record reflects the correct certifications before you submit.
The government awards over $160 billion per year in contracts to small and diverse businesses. The firms that win consistently are not always the most technically sophisticated. They are the ones who answer every question, follow every instruction, and submit on time.
