Three exec summaries I rewrote this week, part 12

Short one today. Three exec summaries hit the editing desk this week, all from teams in the middle of bids due in the next 10 days. The pattern in all three was the same pattern we have been writing about for a year: the summary was written last, no executive had read it before it reached us, and the proof points were slogans in dress clothes.

The first was a commercial SaaS bid for a mid-market logistics buyer. The original summary opened with “a trusted partner in supply chain transformation.” We cut that and replaced it with a specific claim about cutover performance on the last three migrations of a comparable buyer profile — verifiable numbers, references attached. The rewrite was 200 words shorter and did more work.

The second was a federal task-order response against an IDIQ the vendor had already won. The original treated the summary as a courtesy and skipped the rubric entirely. We rebuilt it around the published evaluation factors, named the program lead in the first paragraph, and cited the past-performance ratings the rubric weighted at 30%. The contracting officer’s cover sheet had been staring at the team the whole time; they had just stopped reading it.

The third was a managed-services renewal. The original told the customer what the vendor already provided — the customer knew — and skipped the forward commitment. We rebuilt it around what the next three years look like: three changes to the scope, three new SLAs, one pricing concession, one named incident the vendor had fixed and the trend line since. Renewals lose when the summary is backward-looking. This one is now forward-looking.

All three rewrites took under an hour each. The pattern is worth repeating because the rewrite cost is always trivial relative to the bid value. PropLibrary’s swap-name test is the cheapest instrument in proposal craft and the least-used.

A common thread across all three: the team that wrote each original summary did so at the end of the response, after the technical and management volumes were drafted. In each case, the rewrite was easier than the drafters expected because the volumes already contained the specific claims the rewritten summary needed. The summary did not need new content; it needed a different selection of the content the response already held. The failure mode was not effort. It was order-of-operations.

The second thread: none of the three originals had been read by the signing executive. Two of the three had not even been scheduled for that read. The executive sign-off is the discipline that catches the swap-name-test failures, and skipping it is the single most common reason summaries ship weak.

The long version — the pillar post — lands Monday. If you have been reading this field-note series for the past year, Monday is the one where it all gets put together. The short version of the argument, as a preview: the executive summary is not the last section you write. It is the first, and the one you rewrite the most. Every week that evidence accumulates.