Insights  /  The Evaluator's Desk · Edition 1

Why Compliant Proposals Score Low

The first edition of The Evaluator's Desk: how government buying actually gets decided, from the other side of the table.

Welcome to The Evaluator's Desk.

This newsletter exists for one reason. Most coverage of federal contracting tells you what happened. Very little of it tells you how the decision gets made. I have sat on source selection boards and read proposals for a living. Today I help companies win the contracts those boards award. The Evaluator's Desk is where the two views meet.

Every edition has the same shape. The Radar covers what is moving in the space right now. Scored takes one trend or opportunity and evaluates it the way a board evaluates a proposal. From the Desk is the lesson underneath, drawn from how evaluators actually work. Worth Watching closes with one thing to keep an eye on.

This first edition leads with the lesson, because it explains everything else in the letter.

The Radar

The FAR overhaul is halfway home, and the working rules have already changed. The Revolutionary FAR Overhaul has published 8 of its 12 promised proposed rules, four on June 23, 2026 and four more on September 18. Fifteen FAR parts still wait for proposed rules, including Part 19 on small business, and no final rule had issued as of November 7. Meanwhile the model deviation texts are already operative through agency class deviations, and version 3.0 of the FAR Companion Guide, issued October 30, added guidance on non-federal past performance, contractor self-assessments, and outcome-based contracting.

Evaluator's read: your next proposal may be scored under deviation text, not the FAR you learned, so read the solicitation's own terms before you rely on habit.

GSA's AI clause is now in force. GSAR 552.239-7001, Basic Safeguarding of Data within LLM AI Systems, took effect October 19, 2026 as a class deviation for GSA procurements where large language model functionality is material. It follows a June 23 proposed rule covering LLM data protection, intellectual property, and flow-downs to subcontractors. If your offer puts an LLM to work on government data, safeguarding that data is now a contract obligation, not a selling point.

Evaluator's read: what you claim about your AI is now something the government can hold you to, so write those claims the way you would write any other commitment in the offer.

Consolidation survived its court test. On October 13, 2026, the Court of Federal Claims upheld the Department of Homeland Security's cancellation of the $10B FirstSource III vehicle on consolidation grounds. GSA continues consolidating common goods and services buying under Executive Order 14240, and it sunset the 2GIT blanket purchase agreement on September 30, pushing buyers toward the Multiple Award Schedule. Vehicles contractors built pipelines around can now disappear mid-strategy, with a court's blessing.

Evaluator's read: fewer vehicles means more offers crowded onto each one, which raises the value of a recorded strength and the cost of a generic proposal.

Scored

The item: the proposed FAR Part 15 change on late proposals. Under the current rule, late is late. A proposal that arrives after the deadline is not considered, with narrow exceptions. The proposed Part 15 rule, published as part of the FAR overhaul, would give contracting officers discretion to accept a late proposal when doing so is in the government's best interest. Here is how a board would grade that change.

Strengths. The government's interest is the point of the competition, and a bright-line deadline can defeat it. A strong offer that misses by minutes because of a transmission failure currently dies on a technicality, and the government loses the benefit of it. Discretion fixes that. It also treats the deadline as what it should be, a tool for orderly evaluation rather than an end in itself.

Weaknesses. A bright line is defensible, and discretion is not. Every accepted late proposal invites the losing offerors to ask why that one got in, and every answer has to be documented well enough to survive the question. Discretion will also be exercised unevenly. One contracting officer's best interest is another's unacceptable risk, and offerors cannot plan around a standard that changes with the person holding the warrant.

The discriminator. Whether the discretion gets used consistently, and whether the reasoning gets written down. A rule that depends on judgment lives or dies on the record behind each decision, the same way a proposal does. Contractors should take the practical point: discretion is not a promise. The contracting officer may accept your late proposal, and may not, and you will not know which until it happens. Bid as if the deadline is still absolute, because for planning purposes it is.

From the Desk

Every proposal team knows the feeling. The proposal was compliant. Every requirement was answered. The volumes were clean, the graphics were sharp, the compliance matrix was complete. Then the award went somewhere else, and the debrief used words like acceptable.

Here is what happened. Compliance got the proposal read. It did not get it scored well.

An evaluator does not score effort, and an evaluator does not score polish. An evaluator scores against Section M, the evaluation factors for award. For each factor, the evaluator looks for strengths: features of the proposal that exceed the requirement, or that reduce risk in a way that matters to the government. A strength has to be found, understood, and written into the evaluation record. If it is not in the record, it does not exist.

That last point is the one most teams miss. Evaluators cannot credit what they cannot cite. A capability buried in the wrong volume, described in general language, or implied instead of stated will not make it into the record. The evaluator may even believe the company can do the work. Belief is not a strength. The record is what gets briefed, defended, and decided on.

Consensus makes it harder still. A strength does not survive on one evaluator's say-so. In the room, the evaluator who found it has to point the rest of the board to the page and the sentence. If the panel cannot find it together, it comes out of the record. Proposals are not scored on the most generous reading. They are scored on the reading a room full of people can agree on and defend.

So a compliant proposal with no findable strengths scores exactly where it should: in the middle. It met the requirement. Meeting the requirement is the floor, not the argument.

Before your next submission, run this check.

  • Open Section M. List every factor and subfactor in order.
  • For each one, write the strength you want the evaluator to record, in one sentence.
  • Find that strength in the proposal and note the page. If you cannot point to it, the evaluator cannot either.
  • Check the language. A strength stated in general terms reads as a claim. A strength stated with specifics reads as evidence.
  • Read the proposal the way an evaluator reads: in sections, against the clock, looking for reasons to justify a score. Make those reasons easy to find.

The fix is not more content. Most proposals already say the right things somewhere. The fix is placement and precision: the right claim, stated specifically, in the section where the evaluator is looking for it, tied to the factor being scored.

None of this requires a better writer. It requires writing for the reader who scores, not the reader who approves internally.

That is the standard this newsletter will keep coming back to: how the work looks from the evaluator's chair.

Worth Watching

The rest of the overhaul. Fifteen FAR parts still await proposed rules, and Part 19, the small business part, is the one that decides how set-asides, follow-on contracts, and program eligibility work under the new FAR. Watch for its publication, and read the evaluation language first when it lands, because that is where the practical change will sit.

Thank you for reading the first edition. The Evaluator's Desk publishes every second Friday. If it is useful, subscribe, and pass it to one person who writes proposals for a living.

Calvin Hunt
Founding Partner, Aerocore Consulting

Have a proposal that needs to score, not just comply?

The Evaluator's Red Team scores your draft against Section M while there is still time to fix what it finds.

Discuss Your Requirements   More from the Desk