A federal evaluator is not your customer. The evaluator is a contracting officer or technical assessor working through dozens of proposals on a tight timeline, scoring against a Source Selection Plan (SSP), and producing a record that will survive a bid protest. Proposals that win are written to match the evaluator’s criteria.
Compliance is not the same as responsiveness
Compliance means your proposal meets the literal requirements of the solicitation — page limits, font sizes, required sections, mandatory submittals, certifications, and the order of volumes called out in this section. Non-compliance is the fastest way to get tossed without scoring. Build a compliance matrix the day the RFP drops and update it.
Responsiveness means your proposal answers what the agency actually wants — evaluation criteria, the SOO/SOW/PWS objectives, and the hot buttons the capture team identified. Compliance gets you scored. Responsiveness gets you selected.
The GAO Bid Protest Annual Report to Congress for Fiscal Year 2024 (GAO-25-900611, submitted November 14, 2024) is direct on what tips a protest: the most prevalent reasons for sustaining protests during the 2024 fiscal year were unreasonable technical evaluation, flawed selection decision, and unreasonable cost or price evaluation. Each ground tracks back to a proposal that either failed to make its case explicitly against evaluation criteria or left the evaluator no clean basis to score it. Write to the evaluation criteria; do not make the evaluator translate.
Win themes, discriminators, and ghosting
A win theme is a short, repeatable claim about why your proposal is the best value for this customer’s specific problem. Good win themes are customer-grounded (they reflect actual pain points), benefit-led (they translate features into outcomes), substantiated (every theme is backed by a proof point), and consistent (the same theme appears in technical, management, and past performance sections).
A discriminator is something a competitor cannot credibly claim. “Cleared workforce” is not a discriminator if every offeror has one. “10 years of continuous incumbent performance with zero negative CPARS findings” might be. Discriminators are the specifics evaluators latch onto when defending a tradeoff decision.
Ghosting is the practice of pointing out competitor weaknesses without naming them. “Unlike approaches that rely on contractor-furnished proprietary platforms, our open-architecture solution avoids vendor lock-in” ghosts a competitor whose pitch is exactly that proprietary platform. Done well, ghosting plants doubt in the evaluator’s mind without ever crossing the line into disparagement.
A useful recent illustration of the documentation discipline that surfaces in source selection: in Kauffman and Associates, Inc., B-421917.2, B-421917.3 (January 29, 2024), GAO sustained the protest because the agency evaluated quotations unequally, the technical evaluation was unsupported by the contemporaneous record, and the price evaluation was unreasonable in part because the awardee proposed labor rates in excess of its Federal Supply Schedule contract rates. The case is a reminder that operational and pricing discipline — proposing rates you are actually authorized to charge — is itself a competitive asset.
Page limits and evaluator economics
Page limits exist because evaluators are time-constrained. A 50-page technical volume is a privilege, not a target. Tight, well-structured proposals with clear headings, evaluator-friendly tables, and proof-point graphics outscore dense academic writing every time. If a section requires a long narrative, lead with a one-sentence theme statement and let the evidence follow.
Evaluation criteria mapping
Every page of the proposal should map to a evaluation criteria factor or subfactor. Build a heat map during the storyboard phase: rows are factors, columns are your proposal sections, cells indicate where each factor is addressed. Gaps in the heat map are the difference between a Satisfactory rating and an Outstanding one.
Best value tradeoff vs. Lowest Price Technically Acceptable (LPTA)
DoD has stepped back materially from LPTA over the past decade. Sections 813 and 814 (FY 2017 NDAA), 822 and 832 (FY 2018 NDAA), 880 (FY 2019 NDAA), and provisions in the FY 2020 NDAA progressively restricted LPTA for IT services, cybersecurity services, knowledge-based services, audit services, engineering and manufacturing development of Major Defense Acquisition Programs, personal protective equipment, aviation critical safety items, and other categories. DoD’s October 2019 final rule codified the restriction at DFARS 215.101-2-70, and the policy posture is now clear: “to the maximum extent practicable”. Avoid LPTA where cost-technical tradeoffs would add value.
What this means for proposal strategy is straightforward. On tradeoff procurements (the vast majority of services work), evaluators are looking for strengths and significant differentiators that justify a price premium. Substantiate every claimed strength with a specific proof point. Quantify outcomes wherever possible. Recognize that adjective inflation — “world-class,” “best-in-class,” “industry-leading” — doesn’t move evaluators, evidence does.
Past performance: a separate evaluation, often a decisive one
Past performance under FAR 15.305(a)(2) is evaluated on relevance and quality. Pull recent contracts of similar scope, size, and complexity — and lead with the ones that have Exceptional or Very Good CPARS ratings (under the system in effect through April 2026). After the FY 2026 NDAA changes phase in, the absence of negative events becomes the asset.
Operational signals that show up in source selection
Three operational realities silently shape proposal evaluations:
Accounting system adequacy. If the procurement involves cost-reimbursable or flexibly priced work, evaluators look for evidence that the offeror’s accounting system is acceptable under SF 1408 criteria. A confident, specific statement — backed by a recent DCAA or third-party determination — is a low-cost strength.
Realistic indirect rates and wrap rates. Price realism evaluations under FAR 15.404-1(d) are increasingly used to disqualify offerors whose proposed labor rates are unrealistic given their cost structure. A wrap rate that doesn’t match the indirect rate structure on the books is an audit and protest risk.
Cybersecurity and CMMC posture. For DoD work, CMMC self-assessment scores in SPRS, a current System Security Plan, and a credible Level 2 path are now baseline evaluation inputs.
The takeaway
Proposals win on compliance, responsiveness, evidence, and operational credibility — in that order. The contractors who turn substance into score are the ones whose operations actually support what the proposal claims.
Check out the previous posts in the series here:
Winning GovCon Contracts in 2026
Where to Build Your GovCon Pipeline