GovCon Glossary

A proposal outline expanded with section-by-section guidance (compliance references, win themes, discriminators, content direction, and page allocations) and handed to writers before drafting starts. It turns a bare table of contents into a writing tool that keeps every section tied to RFP requirements and strategy.

The state of having enough capture intelligence (customer insight, teaming, staffing, price-to-win, and compliance understanding) to commit resources to a compliant, competitive proposal. Bid readiness is what a bid/no-bid decision and capture gates are ultimately checking for before a pursuit is funded.

A formal go/no-go checkpoint where leadership scores an opportunity against qualification criteria (strategic fit, incumbency, competitive position, funding certainty, and win probability) to decide whether to invest capture and proposal resources. It can recur at multiple points as an opportunity matures.

A capture-phase session where the team thinks like a specific competitor to forecast their likely solution, staffing, pricing, and win themes. Unlike the color-team reviews, it looks outward at the competition rather than at your own draft, so you can adjust strategy to beat them.

The first color review, conducted on the annotated outline before writing begins. It checks that section assignments, compliance mapping, win themes, and discriminators are correctly reflected in the outline and flags gaps in solution, data, or SME coverage early, before drafting starts.

Decision checkpoints spaced through the capture lifecycle, typically at qualify, pursue, and propose milestones, where leadership reviews progress against exit criteria and decides whether to advance, hold, or kill an opportunity. Gates keep resources from flowing into pursuits that aren't maturing toward a win.

A living document built during capture that lays out the strategy for winning a specific opportunity: customer intelligence, competitive assessment, teaming and staffing approach, price-to-win, discriminators, and an action plan. It's the strategic input that later shapes the proposal outline and themes.

A requirement-by-requirement cross-reference between the RFP (Sections L, M, C, and the SOW) and where each item is addressed in the proposal outline and draft. It's used to verify nothing is missed and to structure the proposal so evaluators can trace compliance section by section.

Capabilities or attributes of an offeror's approach that competitors can't easily claim or match, and that matter to the customer's stated evaluation criteria. Discriminators give win themes proof and substance; without them, a win theme is just an assertion the customer has no reason to believe.

The opening proposal section that states the offeror's understanding of the customer's need, overall approach, and key win themes and discriminators in customer-focused language. It's often the only section every evaluator reads in full, so it's written to stand alone and persuade on its own.

A writing technique that highlights a competitor's likely weaknesses by emphasizing requirements or solution attributes where that competitor is known to fall short, without naming them directly. Done well, it plants doubt about the competition in the evaluator's mind while staying within ethical and compliance bounds.

The final executive-level review before submission, confirming that findings from Red (and Green/pricing) team reviews were incorporated, the proposal is fully compliant, priced to win, and messaging on win themes and discriminators is polished and consistent. It's the last checkpoint before the bid goes out the door.

The specific issues, concerns, or priorities that matter most to a customer's evaluators and decision-makers on a given opportunity (a cost risk, a technical pain point, a past performance concern, and the like). Capture teams surface them through customer engagement and competitive intelligence, then build win themes and discriminators that speak directly to them.

The meeting that launches proposal development, typically held once the bid decision is made and the RFP is released. It aligns the team on the compliance matrix, schedule, writing assignments, win strategy, and ground rules before drafting starts, so everyone begins work with the same understanding of what's being written and why.

An early go/no-go assessment applied to a potential opportunity before committing capture resources to it. The team evaluates funding, requirement fit, competitive field, incumbency, customer relationships, and realistic win probability to decide whether the pursuit belongs on the active pipeline or should be dropped.

A live presentation to government evaluators, used in some source selections in place of or alongside written volumes. The proposed team presents its approach, key personnel, and understanding of the requirement directly to the panel, often scored against its own evaluation criteria separate from the written proposal.

The first major color-team review, held on storyboards, outlines, or an early draft before most narrative is written. Reviewers check whether the proposed solution, structure, and win themes are compliant and on track, catching direction problems while there's still time to fix them before full drafting begins.

A working document built at or before kickoff that lays out the proposal schedule, section assignments, compliance approach, review cycle, and production logistics. It's the proposal manager's internal playbook for running the effort and the reference point the team returns to when priorities or deadlines shift.

An independent review of a near-complete draft in which reviewers score the proposal the way a government evaluator would, against the stated evaluation criteria. It tests compliance, clarity, and the strength of win themes and discriminators before the proposal locks for final production.

A matrix, often produced alongside or after the compliance matrix, that traces each RFP requirement to the exact section, page, and paragraph of the proposal where it's addressed. Reviewers and evaluators use it to confirm nothing was dropped during drafting, and some solicitations ask offerors to submit one directly.

The structured capture-and-proposal methodology originated by Shipley Associates and widely used in government contracting. It sequences business development from opportunity identification through capture planning, proposal development, and submission, using standardized color-team reviews and phase gates to control quality and risk at each stage.

The work of designing the technical, management, and/or price approach that will satisfy the customer's stated and unstated requirements and set the offer apart from competitors. It happens primarily during capture, before proposal writing, so the team is documenting an already-developed solution rather than inventing one on the page.

A page-level planning tool used before full drafting that lays out, for each proposal section, the compliance requirements it must cover, the win theme it should carry, a content outline, and a graphic concept. It gives writers a structured starting point and gives Pink Team reviewers something concrete to check.

The final check performed just before submission (sometimes called the 'white glove' review), confirming formatting, page limits, required forms, and RFP compliance are all correct. It happens after content is finalized through Gold Team and exists to catch last-minute production errors, not to re-litigate content or strategy.

The specific, evidence-backed statements that connect a proposal's discriminators directly to a customer's hot buttons and stated evaluation criteria. They're introduced early, carried consistently across every volume and section, and reinforced with proof points to persuade evaluators that the offeror is the strongest choice.