Section 1: the executive summary nuances most teams miss
The executive summary is the section most teams write last, worst, and most generically. When you write it depends on the RFP's shape. Three shapes, three rules, and the nuances nobody tells you.
Most proposal teams write the executive summary last. Most executive summaries read like they were written last. Hurried, generic, pulled from the drafts of the sections they summarize instead of driving them.
I have shipped 400+ bids. I now write the executive summary first about half the time, last about a third of the time, and in parallel with the technical approach the rest of the time. When I do which depends on the shape of the RFP. This post is the three shapes, the three rules, and the nuances nobody tells you.
Shape one — the rubric is published and weighted
Public-sector RFPs and mature commercial procurements publish a scoring rubric. Technical approach 40%, past performance 20%, management 10%, cost 30%, best-value tradeoff. See the reading-the-RFP post for the full treatment of this.
Rule: write the executive summary first.
The executive summary is where your win themes live in compressed form. When the rubric is known, the win themes are the editorial choices you make about which rubric dimensions you are going to make the evaluator remember. Write the summary first because it forces you to commit to those choices before you write a single technical paragraph. Every section that follows is then drafted against the commitment.
The nuance: the first-draft executive summary is a working document, not a polished artifact. You will rewrite it three times as the technical sections develop and reveal which claims you can actually defend. The value of writing it first is that it keeps the sections honest — they inherit the themes instead of reinventing them.
Shape two — LPTA or checkbox-dominant
Some RFPs are lowest-price-technically-acceptable, or effectively so. The technical section is a threshold; the cost is the contest. I have seen agency RFPs where the exec summary is literally two paragraphs by format requirement, because the evaluator does not get scoring discretion on the narrative.
Rule: write the executive summary last, and write it short.
In an LPTA, the exec summary is a compliance artifact. It exists because the RFP requires it. It should do three things: state you meet the technical threshold, cite the specific sections where the threshold is demonstrated, and state the cost. Anything else is effort wasted. Effort you spend on a flourish-filled LPTA summary is effort you did not spend on driving your cost narrative.
The nuance: some LPTAs have a “best value within the acceptable” tiebreaker. If two vendors meet the threshold at similar cost, the evaluator can use qualitative discretion. When this is published, the summary does a little more work — but still much less than in shape one.
Shape three — the rubric is not published
Most commercial RFPs. The buyer does not tell you the evaluation methodology. You infer it from the question weight, from which sections have tight page limits and which are open-ended, from how much attachment space is devoted to each factor.
Rule: write the executive summary in parallel with the technical approach.
In this shape, you do not yet know what the rubric rewards. The technical approach you draft reveals your evidence — which capabilities you can defend, which case studies you can cite, where your differentiation holds up to detail. The executive summary and the technical approach co-evolve, each informing the other. I usually draft both in a shared document with a horizontal split, updating one when the other reveals something.
The nuance: in this shape, the executive summary is also intelligence-gathering. You write a summary that lands on two or three themes, you float it past the account team that knows the buyer, and you adjust based on what they tell you resonates. The document becomes a conversation, not an artifact.
What goes in every executive summary
Regardless of shape, four things:
A sentence about the buyer’s objective. In the buyer’s language, as stated in Section 1 of the RFP. Not your interpretation of it. A paraphrase that the procurement lead would nod at, because they wrote the original sentence and they will recognize you as having read it.
Your win themes, three to five. Explicit, named, and connected to the evaluation rubric where the rubric is known. PropLibrary’s swap test applies: if you can swap your company name with a competitor’s and the theme still makes sense, the theme is generic. Rewrite until the theme names something specific about your approach, your team, or your past performance.
A compliance statement. One sentence asserting that every requirement in the compliance matrix has a response somewhere in the proposal, with a pointer. Procurement leads who read a hundred proposals appreciate this because it tells them the team took compliance seriously.
A forward look. One paragraph that describes what the first 30 days of the engagement look like if you win. Operational, specific, dated. This is the paragraph that separates proposals that feel like capability statements from proposals that feel like plans.
What does not go in
A company history. The buyer is not evaluating you on your founding story.
A mission statement. The buyer is not evaluating you on your inspirational framing.
A thank-you for the opportunity. The buyer knows they posted the RFP. You thanking them is an adjective, and adjectives do not win bids.
A promise to deliver “superior” or “seamless” anything. Those words are pre-filtered as fluff by evaluators who have read a thousand proposals — and the PropLibrary swap test catches them every time.
A brief note on length
Exec summary: two pages, max. I wrote the longer argument there. Short version: the evaluator reads every executive summary. The evaluator does not read every technical appendix. Two pages is the limit at which the summary still gets read; at three or four pages, it starts getting skimmed, and skimming is where your win themes die.
Takeaway
When you write the executive summary depends on whether the rubric is published and what method the rubric uses. Write it first when you know the rubric; write it last when the rubric is a threshold; write it alongside the technical approach when the rubric is hidden. In every case, the summary is a commitment device — the themes you put in it are the themes you have to defend everywhere else. Treat it that way and it stops being the hurried last section. It becomes the section that makes every other section work.