Capture Plan

A capture plan is the central strategic and operational document that a government contractor maintains for a specific contract opportunity from initial identification through RFP release, detailing the customer intelligence gathered, win strategy developed, competitive analysis conducted, teaming decisions made, and the discrete actions required to improve the firm's probability of winning.

What is a Capture Plan?

A capture plan is not a static deliverable, it is updated continuously as the team learns more about the customer, the incumbent, and the competitive landscape. At minimum, a capture plan typically includes: opportunity summary (agency, program, NAICS code, estimated value, anticipated procurement timeline); customer intelligence (key stakeholders, their priorities, pain points with the incumbent, budget situation); win probability (Pwin) assessment; competitive analysis identifying likely competitors and their strengths/weaknesses; a win strategy with discriminating themes; teaming strategy and partner status; pricing strategy and initial price-to-win range; customer engagement plan (planned meetings, events, responses to sources sought); and a task-and-owner action register with milestones.

Gate review processes use the capture plan as the primary briefing document. At each gate, from initial opportunity identification through the final go/no-go decision before proposal submission, the capture manager presents the plan's current state to leadership, who decide whether to continue investment, adjust strategy, or stand down. The discipline of maintaining and presenting a rigorous capture plan prevents firms from sleepwalking into proposals on opportunities they are unlikely to win.

The capture plan also feeds the proposal: the win themes and discriminators developed during capture become the narrative spine of the technical and management volumes. A well-executed capture plan means the proposal team starts writing with a strategy, not blank pages.

Why the Capture Plan Matters for Government Contractors

Firms without written capture plans routinely submit undifferentiated proposals that address the solicitation's stated requirements without demonstrating genuine customer understanding. The capture plan is the mechanism that translates customer intelligence into proposal strategy. A capture plan also forces honest resource allocation: if a team cannot articulate a realistic win strategy, the gate review process should surface that the opportunity is not worth pursuing.

Example

A capture manager maintains a capture plan for a $22M DHS IT support contract 15 months before the expected RFP. The plan tracks three customer meetings that revealed a dissatisfaction with the incumbent's help desk responsiveness, identifies two likely competitors and their labor rate positions, documents a teaming partner relationship with a HUBZone firm to improve set-aside competitiveness, and lists a price-to-win target of $18.5M based on GSA CALC rate benchmarking. When the RFP arrives, the proposal team opens the capture plan, not a blank strategy document.

Frequently Asked Questions

How long should a capture plan be?

Length scales with opportunity complexity. For a $2M IDIQ task order, a two-to-four-page capture plan covering the key intelligence points, win strategy, and competitive assessment is sufficient. For a $50M full and open competition, a capture plan spanning 15 to 25 pages with detailed sections for each customer stakeholder, a full competitive matrix, and a pricing model is appropriate. Format and length should be driven by decision-making utility, not documentation for its own sake.

Who owns the capture plan?

The capture manager owns and maintains the capture plan. In smaller companies where the business development lead wears both the capture and proposal management hats, that individual owns the document throughout. In larger organizations, the capture manager transitions the plan to the proposal manager at RFP release, with the capture manager remaining available for strategy questions during proposal development.

When is a capture plan retired?

A capture plan is retired when the opportunity is either won (transitioning to contract performance) or lost/abandoned (following the go/no-go gate or debrief). Lessons learned from both wins and losses should be documented in the plan before it is archived, the historical capture file becomes invaluable intelligence for future recompetes or similar opportunities at the same agency.

Should small businesses maintain formal capture plans?

Yes, even if the format is simpler. A small business pursuing a $3M set-aside should at minimum document: why they believe they can win, what they know about the customer's priorities, who the likely competitors are, what their teaming approach is, and what their target price range is. These are the same questions a large firm answers in a 20-page capture plan, the discipline matters regardless of document length.