The capture-to-proposal handoff checklist
Seven fields the capture team has to deliver before the proposal team starts writing. Why most handoffs fail on three of them, and how to enforce the handoff as a gate rather than a courtesy.
Most capture-to-proposal handoffs fail in the same three places. The capture lead says the handoff happened. The proposal manager says it did not. Both are telling the truth, because what the capture lead called a handoff was a Slack message and what the proposal manager needed was a document.
Seven fields. These are the fields we enforce on every handoff. The proposal manager is expected to refuse the handoff if any of them are missing, and the refusal is not a political move — it is a gate.
The seven fields
- The buyer, named. Organization, division, contracting office, named point of contact on the buyer side if we have one. Not “the state agency” — the agency, by name, with the acronym spelled out.
- The strategic context, one paragraph. Why this buyer is buying this thing right now. What initiative is this RFP downstream of. What changed in the buyer’s world in the last six months that created this spend. This is the paragraph writers read before they write a single word.
- The evaluation panel, to the extent known. Who sits on the panel. What are their job titles. Which one is likely to read the technical section, which one reads pricing, which one reads past performance. Where this is unknown, the capture lead says “unknown” rather than guessing.
- The incumbent, named, with status. Is there one. If yes, their likely renewal posture. Their known weaknesses from the buyer’s point of view. Their contract end date if available. If there is no incumbent, “greenfield” is a valid answer.
- The three to five win themes. Draft quality. The themes the capture lead thinks should carry through the response. Writers are free to push back on them — and often should — but the capture lead has committed to a position.
- The known disqualifiers. Clauses we cannot accept, certifications we lack, past history with this buyer that has to be addressed in the response. The writers need these upfront so they do not spend a week drafting a section that will fall on a clause we were going to exception.
- The capture plan document, linked. Whatever artifact the capture team produced during the capture window, linked in the handoff record. Not summarized, linked. The proposal manager reads it. The writers reference it.
Where handoffs fail
Fields 3, 5, and 6 fail more often than the rest.
Field 3 — the evaluation panel fails because capture leads do not want to admit they do not know. They write generic placeholders; the proposal team treats them as real. An honest “unknown” is a better field than a plausible guess.
Field 5 — win themes fails because they are generic. “Superior,” “trusted partner,” the interchangeable words PropLibrary called fluff — they show up because the capture lead wrote them in 10 minutes to clear the handoff. Generic themes at handoff produce a generic proposal.
Field 6 — disqualifiers fails because the capture lead is worried that naming one will kill the bid. It does not. Naming early gives the proposal team a chance to structure an exception or mitigation. Hiding it until draft-3 means the writers discover it the hard way.
Why the gate matters
Quilt has documented that sales engineers spend 100 to 300 hours per RFP response. Some fraction of that is re-work from missing handoff context — a section drafted against the wrong evaluation criteria, a missing win theme that surfaces in red team, a disqualifier hit in week 3 that was known in week 0.
The seven-field handoff prevents the reworks that come from context the capture team had and did not pass forward. That category is worth eliminating. The checklist lives in the proposal function’s runbook. The proposal manager runs it before the kickoff. If the handoff is incomplete, the kickoff does not happen.