Most firms write a proposal the way they would write a brochure: start with who they are, explain how good they are, and hope the reader is persuaded. Evaluators do not read that way. They score. A federal proposal is graded against a rubric the agency published in advance, factor by factor, and the firm that understands the rubric usually beats the firm with the better story.

That rubric lives in Section M of the solicitation — Evaluation Factors for Award. Section L tells you what to submit. Section M tells you how it will be judged. Confuse the two and you will write a beautiful proposal that scores badly, because you answered questions nobody asked and skipped the ones carrying the points.

Start with Section M, not with your company overview

Before drafting anything, read Section M end to end and write down, in plain language, every factor and subfactor, in the order the solicitation lists them. That order is usually the order of importance, and it should become the structure of your proposal. If Section M lists technical approach first, management second, and past performance third, your proposal should open with technical approach — not with a company history section the rubric never mentions.

Then note what each factor actually asks for. A factor called “technical approach” in one solicitation means staffing and methodology; in another it means understanding of the requirement and risk mitigation. The label is not the requirement. The paragraphs underneath it are. Quote them into your compliance matrix alongside the Section L instructions, so every scored item has a row and every row has a proposal section assigned to it.

How scoring actually works

Most federal evaluations work like this: individual evaluators read your proposal against the factors, note strengths, weaknesses, and deficiencies, and assign a rating — often adjectival, such as outstanding, good, acceptable, marginal, or unacceptable. A consensus panel then agrees the ratings, and the source selection authority makes the award, usually on a best-value tradeoff rather than lowest price alone. The exact scale and process vary by agency and solicitation, so always use the definitions printed in your solicitation, not a generic scale remembered from another bid.

Three words in that process deserve precise attention. A strength is an aspect of your proposal that exceeds a requirement in a way that benefits the government. A weakness is a flaw that increases the risk of unsuccessful performance. A deficiency is a material failure to meet a requirement — the kind of finding that can end a bid on its own. Notice what follows from those definitions: a strength must be tied to a requirement. A claim that is true but irrelevant to the stated factors earns nothing, however impressive it sounds.

Weighting: not all points are equal

Section M also tells you how factors relate to each other — whether technical merit outweighs price, whether past performance matters more than management, or whether all non-price factors combined are significantly more important than price. Read that paragraph twice. It changes your whole bid strategy.

If price is the least important factor, competing on the lowest price is a losing move: you sacrifice the technical strengths that actually carry the award. If price and technical merit are roughly equal, a technically strong but wildly expensive proposal is just as risky as a cheap but thin one. And if past performance carries heavy weight, a firm with thin relevant experience should think hard, before writing, about teaming or subcontracting to fill the gap — or about walking away. That honest calculation is exactly what a bid/no-bid review is for: deciding, on evidence, whether the points are winnable before the team spends weeks chasing them.

Strengths are earned with evidence, not adjectives

The single most common scoring mistake is writing claims instead of proof. “We provide world-class support” is not a strength; it is an adjective with no requirement attached. A strength looks like this: the solicitation requires a two-hour response time for critical incidents, and your proposal states the response time, names the role that delivers it, describes the escalation path, and cites a comparable contract where that response time was met. Requirement, answer, evidence — in that order.

Past performance works the same way. Evaluators score relevance and recency, not volume. Three comparable, recent contracts in the same kind of work beat ten contracts in adjacent fields. For each past performance reference, state plainly what the work was, how similar it is to this requirement, when it was performed, and what the outcome was. If a reference is weaker than the factor asks for, say so and explain what compensates — evaluators notice candour, and they penalise references dressed up as something they are not.

Write in the evaluator’s order

Evaluators work through dozens of proposals under time pressure. Make their job easy and your score goes up — not because they are being kind, but because a strength they cannot find is a strength you do not get. Mirror the Section M structure in your headings, answer factors in the order listed, and put the direct answer to each requirement in the first paragraph of its section, with supporting detail after it. Cross-references help: “as described in Section 3.2” beats making the evaluator hunt.

The same discipline applies to page limits. When a volume is capped, every page spent on un-scored company background is a page stolen from a scored factor. Cut ruthlessly. If a paragraph does not map to a Section M factor, it does not belong in the proposal — however proud of it the firm may be. Our government proposal writing work follows this rule without exception: the matrix decides the outline, Section M decides the emphasis, and everything else is cut.

Price: realism matters as much as the number

On best-value solicitations, evaluators do not simply pick the cheapest price. They assess whether the price is reasonable and, in many cases, whether it is realistic — whether the proposed staffing, hours, and rates can actually deliver the technical approach described. A price built on junior staff for work the technical volume describes as senior-level creates a contradiction the evaluators will find, and it reads as risk. Your price volume and your technical volume must tell the same story, with the same labour categories, the same hours, and the same assumptions. That consistency check belongs in the final review, every time, and it is one of the first things a red-team review tests before submission.

Score your own draft before you submit

The most valuable review is not a proofread. It is a mock evaluation: give a fresh reviewer the solicitation’s Section M, your draft, and nothing else, and ask them to score it factor by factor, listing the strengths and weaknesses they find. Where their reading differs from what you intended, the proposal is ambiguous — and ambiguity scores as weakness. Fix the draft, not the reviewer’s opinion.

Run that review with time to act on it. A mock evaluation the day before submission is a post-mortem, not a review. Build it into the schedule at least a week before the deadline, alongside the final compliance sweep: every Section L requirement answered, every amendment acknowledged, every matrix row pointing to a real page.

The one-page checklist

  • Section M factors and subfactors extracted, in order, before drafting begins
  • Weighting understood — and reflected in where the proposal spends its pages
  • Every strength tied to a stated requirement, with evidence, not adjectives
  • Past performance chosen for relevance and recency, stated plainly
  • Proposal structure mirrors Section M; direct answers come first in each section
  • Price volume consistent with the technical approach, category for category
  • Mock evaluation against Section M completed with time to revise

Section M is not hidden knowledge. The agency publishes its rubric, in full, before you write. Firms that treat it as the brief — and write to it, factor by factor — give evaluators something they can score highly. Firms that ignore it give evaluators a brochure. If you would rather have someone run that discipline for you, from matrix to mock evaluation, write to us by email and we will scope it for your tender.