CAPTURE, THEN THE RESPONSE.

Capture ideally starts well before the solicitation is published, in a window you largely control, and it can continue during the response period. Proposal writing runs after publication, on a timetable the buyer sets and can change. Release dates often slip or arrive early, so the length of the capture window is influenced by the buyer too.

In the capture window there is more room to change your position: develop evidence, resolve a licensing question, arrange a teaming conversation. Once the request is out, the published requirements and dates govern, though they can be revised through official addenda, and the work shifts towards proving what you can support, in the format the buyer requires.

When capture has not happened, those first decisions do not disappear. They get made in week one of the response period, under pressure, usually by whoever is available, which is the most expensive possible time to make them.

Capture produces internal working material: a pursuit profile, an eligibility checklist, an evidence register, teaming questions, win themes with proof attached, and a milestone plan. It is prepared for your team rather than for the buyer.

Proposal development produces two different things, and the distinction matters. The compliance matrix, the approved outline and the readiness sign-off are internal planning and quality control documents, and they are not submitted unless the solicitation specifically asks for them. What goes to the buyer is the required response: the narrative sections, the completed forms, the pricing in the buyer's template and any required attachments.

Hypothetical example, used for illustration only. A regional water district is expected to re-compete a five year inspection and maintenance services contract in about four months, and a mid-sized specialty firm wants it.

Through the capture lens the questions are: what has the district bought before and how did it structure the contract, what eligibility conditions appeared last time, can the firm prove comparable public agency work held by the company itself, what bonding would be needed, does the certification the district favours need to be obtained now rather than later, and is a teaming partner required to cover one service element. The output is a decision to pursue, three evidence items to develop, one certification question owned by operations with a date, and a plan through release.

Through the proposal lens, once the request is published the questions become: what exactly does the instruction require in each section, what are the page limits and forms, which of the prepared evidence items map to which scored criterion, what changed from the previous procurement, how does the pricing workbook need to be completed, and who approves the commitments before submission. The output is the response itself.

Same pursuit. The capture work made the proposal an assembly job rather than an invention job.

With a live deadline in front of you, do the response properly; a missed mandatory requirement cannot be recovered by good strategy. Over a year, invest in capture, because it is what stops you spending the year responding to the wrong requests.