Create evidence-backed messages that turn into evaluated strengths
Last reviewed on June 5, 2026 by the Government.biz editorial team. Win-theme practice follows widely used industry methodology (e.g., Shipley/APMP).
A win theme is a deliberate, repeated message that gives an evaluator a reason to choose your offer over everyone else's. It is not a slogan, a tagline, or a paragraph of marketing boilerplate. "We are uniquely qualified to deliver mission-critical excellence" is not a win theme — it is noise that every competitor in the room is also writing, and an evaluator cannot score it.
The single most important thing to understand is that a win theme is about the customer, not about you. It starts from what the agency is worried about, what it is trying to accomplish, and what keeps the program manager awake at night. Your capabilities only matter to the extent they resolve those concerns. A theme that opens by praising your company has already lost the reader; a theme that opens by naming the customer's problem and then resolving it earns attention and, more importantly, earns evaluated strengths.
Win themes are also recurring. A message that appears once in the executive summary and never again is a claim, not a theme. A true theme is introduced early, reinforced at the start of each major section, and proven repeatedly in the narrative so that by the end of the document the evaluator can state your central advantage from memory. That repetition, anchored in evidence, is what separates a theme from a sentence.
Strong win themes follow a consistent structure with four parts. Each part does a distinct job, and a theme missing any one of them collapses into either boasting or vague helpfulness.
Worked example. Suppose capture research shows the agency's dominant fear is transition risk — they have been burned before by a cutover that disrupted services for weeks. The hot button is service continuity. Your discriminator is that you retain 95% of the incumbent's cleared staff and execute a proven 30-day phased transition with parallel operations. The benefit is zero service disruption and full operational capability from day one, with no learning curve for end users. The proof is a cited transition you actually performed — for example, a comparable contract where you transitioned 220 personnel in 28 days with no SLA breaches, verifiable through that contract's past-performance record.
Assembled, the theme statement reads: "Because we retain the cleared workforce and run a 30-day parallel cutover proven on the [Agency X] contract, you experience no disruption to services during transition — the risk that delayed your last recompete is eliminated." That is a theme an evaluator can score, because it names a concern, offers something competitors can't easily match, states a measurable benefit, and points to evidence.
The word that ruins most proposals is "feature." Teams list everything their solution does and call it a strength. But a feature is only a discriminator if it survives three tests, and you should run every claimed discriminator through all three before it earns a place in your theme set:
A "24/7 help desk" is a feature; everyone has one. "A 24/7 help desk staffed by the same cleared engineers who built the system, with a documented 4-minute mean response on the incumbent contract" is closer to a discriminator, because it is specific, provable, and not trivially copied.
Themes are not invented at the writing table; they are harvested during capture, long before the RFP drops. Three sources feed them.
First, capture intelligence and customer hot buttons. Conversations with the customer, industry days, RFI responses, and prior debriefs reveal what the agency actually cares about. Hot buttons are the raw material of every theme, and a theme built on a real, sourced hot button beats one built on assumption every time.
Second, competitive and black-hat analysis. To know what makes you different, you must know who you are up against. A structured black-hat session — often run during color team reviews — models likely competitors, their probable themes, and their weaknesses, drawing on disciplined competitor analysis. A discriminator only counts as a discriminator relative to a specific competitive field.
Third, past performance. Your proof points live in the work you have already done. A strong past-performance record is the evidence engine behind every theme; without it, your discriminators are just claims.
Ghosting is the art of framing the evaluation around your strengths and your competitors' likely weaknesses — without ever naming a competitor. You never write "our competitor lacks cleared staff." Instead you elevate cleared-staff retention as a critical success factor and demonstrate your strength in it, so that when the evaluator turns to a competitor's proposal, the gap is obvious and self-inflicted.
Done well, ghosting makes your discriminators feel like requirements. If you can convince an evaluator that a proven 30-day transition is the standard any responsible offeror should meet, every competitor who proposes 90 days now reads as risky by comparison. Ghosting depends entirely on the competitive analysis above: you can only frame the evaluation around a weakness you have credibly identified. It must stay subtle and professional — overt attacks on unnamed competitors read as desperate and can backfire.
A theme that is not repeated is not a theme. The executive summary introduces your three or four themes up front, in the customer's language, leading with their concern and your resolution. Each major section then opens with a theme statement — a one- or two-sentence callout that tells the evaluator what advantage this section is about to prove. Inside the section, the narrative delivers the benefit and the proof, so the claim is earned rather than merely repeated.
The discipline that converts themes into a win is mapping every theme to the Section M evaluation factors. Section M tells you exactly how the proposal will be scored. Build a matrix that ties each theme to the evaluation subfactor it supports, confirm that every significant subfactor has at least one theme aimed at it, and cut any theme that maps to nothing. A theme that does not align to an evaluation factor cannot earn an evaluated strength, no matter how clever it sounds. This mapping should be checked at draft and again at color team reviews.
Themes interact with the rest of capture: confirm an opportunity is worth pursuing in your bid/no-bid decision, and make sure your pricing strategy reinforces — rather than undercuts — the value your themes promise.
A win theme is a recurring, evidence-backed message that connects something the customer cares about (a hot button) to a capability only you offer (a discriminator), states the benefit to the customer, and proves it. Strong win themes thread through the executive summary and every major proposal section.
A feature is something your solution has; a discriminator is something meaningful to the customer that you can offer and your competitors realistically cannot. Evaluators reward discriminators tied to benefits, not generic features or unsupported claims of being the best.
Win themes appear in the executive summary, as theme statements at the start of major sections, and woven into the narrative as benefits with proof. They should map directly to the Section M evaluation factors so every theme earns evaluated strengths.
Reference: FAR Part 15. General information, not legal advice.