Government Contract Writing: The Compliance Baseline That Wins Business

Federal procurement in the United States totaled approximately $760 billion in fiscal year 2024, according to the Office of Management and Budget. Of that, roughly 27 percent — approximately $205 billion — was awarded to small businesses, representing one of the largest accessible markets for companies with fewer than 500 employees. The path to that market is almost entirely determined by documentation: a proposal submitted in response to a Request for Proposals (RFP), evaluated against published criteria by a source selection team that is legally required to score what the proposal says, not what the company knows.

This is the fundamental principle that small businesses and first-time government contractors most frequently underestimate: the source selection authority cannot award a contract based on information that is not in the proposal. A company with 20 years of relevant experience that describes its approach in three paragraphs without specificity will score lower in the Technical capability evaluation than a company with 5 years of relevant experience that writes specific, evidence-based technical responses to every evaluation criterion. The score is on the document. If it is not in the document, it does not exist for evaluation purposes.

How FAR Part 15 Source Selection Actually Works

Federal Acquisition Regulation Part 15 governs the source selection process for negotiated contracts — the most common procurement method for significant contract awards. Under FAR 15.303, the Source Selection Authority (SSA) is responsible for selecting the best value offer based on the evaluation factors and subfactors specified in the solicitation. The SSA relies on the Source Selection Evaluation Board (SSEB) to document independent technical ratings for each proposal against each evaluation factor.

The evaluation factors and their relative importance are published in Section M of the RFP ("Evaluation Factors for Award"). Section L contains the instructions to offerors — the specific format and content requirements the proposal must satisfy to be evaluated. A proposal that does not follow Section L instructions — that omits required sections, exceeds specified page limits, or fails to address specified topics in the specified order — provides the SSEB with grounds to rate the omitted factor as "Unacceptable" regardless of the company's actual capabilities.

The five standard adjectival ratings used in most negotiated procurements (Outstanding, Good, Acceptable, Marginal, Unacceptable) are applied to each factor independently. A proposal rated Unacceptable on any factor is typically eliminated from the competitive range — meaning that a technically superior company can be excluded from competition for documentation failures that have nothing to do with capability.

Where Small Businesses Lose to Larger Incumbents

The competitive disadvantage of small businesses in federal procurement relative to larger incumbent contractors is not primarily a function of technical capability. SBA data consistently shows that small businesses win contracts across every NAICS code at competitive rates when they are in the competitive range. The disadvantage is earlier: small businesses are disproportionately eliminated from the competitive range before evaluation because their proposals are rated Marginal or Unacceptable on documentation factors that experienced proposal teams know how to address.

A 2022 analysis of GAO bid protest decisions — protests filed by disappointed offerors challenging agency award decisions — found that the most common grounds for successful protests related to evaluation inconsistency were in cases where the agency rated a proposal element Acceptable based on general discussion of approach rather than specific methodology. What this means for proposal writers is that "discuss your approach to [requirement]" does not mean "briefly describe what you plan to do." It means "demonstrate, with specific methodology, evidence of prior execution, and named personnel, that your approach satisfies the requirement."

How to Write Past Performance Narratives That Are Evaluated Fairly

Past performance is one of the most heavily weighted evaluation factors in federal procurement and one of the most consistently miswritten sections in small business proposals. FAR 15.305(a)(2) requires agencies to evaluate "the quality and extent of the offeror's relevant past performance," using the relevance determination specified in the RFP.

The most common small business past performance failure is listing contracts without establishing relevance. A past performance narrative that identifies a prior contract, states the contract value and period of performance, and claims good performance has technically provided past performance information. It has not established why the prior contract is relevant to the current requirement under the specific relevance criteria published in the RFP.

Section M will specify what "relevant" means for the acquisition: contracts with similar scope, complexity, and scale within a defined recency window. The past performance narrative must explicitly map the prior contract to those criteria — "the following contract is relevant because it involved [specific technical element that matches current requirement] at a contract value within [the range specified in Section M] and was completed within [the recency period specified]." An evaluator reading a past performance narrative is applying the relevance criteria from Section M. The narrative must provide the mapping explicitly; the evaluator is not permitted to infer relevance the offeror did not articulate.

Section L and Section M: The Proposal Strategy Documents

Experienced proposal teams treat Section L and Section M as primary strategy documents. Section M specifies what the agency values and how much — the relative weighting of Technical, Past Performance, and Price factors. Section L specifies exactly how to respond to each factor and what content is required in each volume. The compliance matrix — a spreadsheet that maps every Section L requirement to the corresponding proposal section — is the first document an experienced proposal team produces, before writing begins.

First-time government proposers frequently read Section L as a formatting guide rather than a content specification. The instruction "Offerors shall describe their technical approach to [requirement]" means there must be a section in the technical volume, in the location specified, that describes the technical approach. It does not specify what a good description looks like — that is in Section M, which describes Outstanding performance on that factor as "significantly exceeds requirements and contains multiple strengths with no weaknesses or deficiencies."

The proposal strategy is determined by reading Section M (what Outstanding looks like for each factor) backward through Section L (where and how to demonstrate it) into the proposal content (what specific evidence, methodology, and team qualifications demonstrate Outstanding). Proposals that are written from the company's perspective outward — "here is what we do, here is why we are good at it" — rather than from the evaluation criteria inward will consistently score lower than proposals that reverse-engineer the Outstanding standard.

LPTA vs. Best Value: How the Evaluation Type Changes Writing Strategy

Federal procurements use two primary evaluation approaches that have substantially different implications for proposal writing strategy. Lowest Price Technically Acceptable (LPTA) evaluations award to the technically acceptable offeror with the lowest price. Best Value Tradeoff evaluations award to the offeror who offers the best combination of technical quality and price, allowing agencies to pay a premium for superior technical capability.

In an LPTA evaluation, the technical proposal is a pass/fail gate. The goal is to score Acceptable on every technical factor — not Outstanding, not Exceptional, but the minimum passing threshold — at the lowest possible cost that leaves the company's pricing competitive. Technical elaboration beyond what is needed to demonstrate Acceptability is wasted proposal cost and evaluator attention. The LPTA proposal strategy is compliance efficiency: demonstrate every requirement is met, concisely and without excess.

In a Best Value Tradeoff evaluation, the strategy inverts. The goal is to demonstrate differentiation on the factors that are most heavily weighted in Section M — to score Outstanding rather than Acceptable where Outstanding is achievable, because Outstanding scores on high-weight factors can justify higher prices and still win. The Best Value proposal demonstrates not just that requirements are met, but why the offeror's approach is significantly better than the minimum required, through specific methodology, named differentiating capabilities, and evidence of superior past performance outcomes.

A small business writing the same proposal structure for both evaluation types is systematically miscalibrated for one of them.

What a Compliant Proposal Looks Like vs. What a Competitive Proposal Requires

Compliance is the floor of federal proposal evaluation. A compliant proposal addresses all Section L requirements, falls within page limits, is formatted correctly, and includes all required attachments. Compliance does not produce an award in a competitive procurement — it produces eligibility for evaluation.

A competitive proposal goes beyond compliance to demonstrate Outstanding performance on the evaluation factors that matter most. For a Technical factor with five subfactors, an Outstanding rating on the two highest-weighted subfactors will outperform an Acceptable rating across all five — because Outstanding on the most important factors carries more comparative weight than uniform adequacy.

The proposal writing discipline required to produce a competitive government proposal is different from general professional writing. It requires specific knowledge of the FAR evaluation framework, the ability to reverse-engineer evaluation criteria into content requirements, and the judgment to distinguish between what is required for compliance and what is required for competitive differentiation. Small businesses that build this discipline — or that evaluate their proposals against these standards before submission — compete more effectively than those that do not, regardless of the underlying capability differential.