Should I write the executive summary first or last?

Write a working draft of the executive summary first to force strategic clarity on win themes and discriminators, then refine it after Red Team. Teams that write it last often produce a recap of the technical approach rather than a standalone volume that leads with what the agency's evaluation panel actually weights.

What's the best way to carry capture intelligence into proposal development without losing it between teams?

The capture plan is the bridge: it should record win themes, competitive assessments, and customer analysis in a format the proposal team can use directly when the RFP drops. In practice, capture intelligence often stays in CRM notes or personal files and never reaches the writers, which produces proposals that respond to requirements but lack strategic context. CRM integrations that feed opportunity data and capture notes directly into the proposal workspace close that gap without requiring manual re-entry.

What is a Black Hat Review and when in the pursuit cycle should you run one?

A Black Hat Review is a competitive analysis session where your team role-plays as the likely incumbent or primary competitor to stress-test your own strategy before Red Team. Run it after your capture plan is drafted but before proposal kickoff — findings should feed directly into win theme refinement and discriminator validation, not arrive too late to reshape the approach.

What goes into a Proposal Development Plan and why do teams skip it?

A Proposal Development Plan defines the proposal schedule, volume structure, writer responsibilities, and review milestones for a specific pursuit. Teams skip it under deadline pressure, then compress the Red Team timeline to compensate — which defeats the purpose of having a color team sequence at all.

How is PWin calculated and when should it change during a pursuit?

PWin is a working estimate of your probability of winning a given opportunity, built from factors like competitive position, incumbent relationships, customer access, and resource fit. It should be updated at each gate review as capture intelligence matures — a PWin locked in at Gate 0 and never revisited is a resource allocation risk, not a strategic tool.

Storyboard vs. first draft — which one should proposal writers produce first?

Storyboards come first: they map each section to its win theme, discriminators, features, benefits, and evidence before a single draft line is written. Writers who skip straight to a first draft tend to default to generic capability descriptions that are disconnected from the Section M criteria evaluators will actually score.

What does the Gold Team actually review, and what should it leave alone?

The Gold Team focuses on pricing strategy, risk posture, and overall competitive positioning — not content rewrites. If Gold Team is catching compliance gaps or rewriting technical sections, the Red Team review was not complete enough, and the problem traces upstream to a compressed or skipped Pink Team.

What is the White Team review in the Shipley color team sequence?

The White Team (sometimes called White Glove) is a final pre-submission quality check covering formatting compliance, cross-reference accuracy, and Section L responsiveness after Gold Team approval. It is not a substantive content review — it catches production errors and formatting deviations before the proposal goes out the door.

How do I write a past performance write-up that actually scores well under Section M?

Connect each prior contract directly to the specific scope, task areas, and complexity described in the current PWS — evaluators score recency, relevance, and quality, and generic write-ups that describe what your firm did without tying it to the evaluation criteria leave scoring on the table. Lead with the outcome and the relevance to the current requirement, not the contract background.

How do you ghost the competition in a federal proposal without naming competitors?

Ghosting means structuring your discriminators so that the evaluation criteria your competitors cannot meet become the criteria you emphasize most — without naming anyone. Effective ghosting requires knowing the incumbent's weaknesses from Black Hat analysis and then writing win themes that highlight strengths your competitors structurally cannot match, making the gap visible to evaluators through your own narrative.

Can a small GovCon team run a full Shipley color team review process without dedicated proposal staff?

Yes, though the review sequence often gets compressed — a lean team may combine Pink and Red Team into a single structured review at roughly 60–70 percent completion. The bigger risk for small contractors is that SMEs who should be Red Team reviewers are also the section authors, which removes the independent scoring perspective the process depends on.

What is a capture plan supposed to contain by the time the RFP drops?

By RFP release, a capture plan should record the competitive landscape, win themes tied to known agency priorities, a teaming strategy with identified partners, past performance candidates mapped to the anticipated scope, and a preliminary PWin assessment. A capture plan that arrives at proposal kickoff as a CRM export with no strategic synthesis forces the proposal team to reconstruct intelligence that should already be documented.

Shipley Proposal Glossary for GovCon | July 2026

Federal proposal teams operate under deadline pressure that leaves little room for miscommunication. When capture managers, proposal writers, and subcontractors use the same terms to mean different things, the gaps surface in misaligned sections, unvalidated assumptions, and compliance omissions that evaluators read as execution risk. The Shipley proposal glossary gives pursuit teams a shared vocabulary across the full capture-to-submission lifecycle.

TLDR:

The Shipley proposal glossary gives capture and proposal teams a shared working vocabulary across BD, capture, and proposal functions.
A discriminator only qualifies if it's relevant to what the customer will evaluate (typically Section M), backed by provable evidence, and something competitors can't credibly claim or match.
Color team reviews follow a defined sequence: Pink Team at 25-50% completion (compliance/strategy check), Red Team at 75-95% (simulated customer evaluation), and Gold Team as a final senior-leadership review before submission. Pricing strategy is typically reviewed separately (often called a Green Team).
Treating the Red Team as the first real review compresses the feedback cycle and leaves structural gaps too late to fix.
Proposal automation tools purpose-built for federal contracting can parse Section L and Section M requirements directly from the RFP, keeping capture intelligence connected to proposal development and closing coverage gaps before Red Team.

What Is the Shipley Proposal Glossary?

The Shipley proposal process is one of the most widely referenced methodologies in federal contracting, covering everything from early opportunity identification through final proposal submission. Over decades of use across government contractors, it has generated a working vocabulary that capture and proposal professionals rely on daily: terms like PWin, color teams, Black Hat, and discriminators are thrown around in pursuit meetings and proposal kickoffs without pause for definition.

That shared language matters in practice. When a proposal manager calls for a Pink Team and a capture lead is thinking of a Red Team, the miscommunication costs time that BD cycles rarely have to spare. The Shipley glossary serves as the common reference point that keeps pursuit teams aligned on what each phase, review, and deliverable actually means.

How This Glossary Is Organized

Capture and business development terms that govern pre-RFP pursuit strategy
Proposal development terms covering the writing, review, and submission process
Evaluation and competitive strategy terms that inform how teams position against the competition
Review and quality terms tied to color team methodology and gate reviews

Shipley Proposal Glossary: Core Capture Terms

The Shipley Business Development and Proposal Process gives GovCon teams a shared vocabulary that cuts across BD, capture, and proposal functions. These terms appear constantly in color team reviews, gate reviews, and pursuit decisions, so having a working command of them matters across the whole pursuit lifecycle.

Capture and Pursuit Terms

Bid/No-Bid Decision: A structured go or no-go determination made by BD and capture leadership based on factors like PWin, competitive position, resource availability, and strategic fit. Most mature organizations tie this decision to a formal gate review with defined scoring criteria.
Black Hat Review: A competitive analysis session where the team role-plays as the likely incumbent or primary competitor to stress-test its own strategy. The goal is to identify gaps in win themes and discriminators before Red Team.
Capture Plan: The working document that records opportunity intelligence, competitive assessments, teaming strategy, and win themes from early pursuit through RFP release, feeding the capture manager's proposal handoff.
Customer Analysis: Research into the agency's mission priorities, budget environment, key decision-makers, and incumbent relationships.
Discriminator: A strength that is both relevant to the agency's Section M evaluation criteria and provably better than what competitors can claim. Vague differentiators that any firm could assert do not qualify.
PWin (Probability of Win): A working estimate of how likely the firm is to win a given opportunity, updated as capture intelligence matures and used to focus pursuit resources across the pipeline.
Win Theme: A concise, customer-benefit-focused message that connects a contractor's strength to an agency need and positions it against the competition. Effective win themes run consistently from the executive summary through every technical section.

Shipley Proposal Glossary: Proposal Development Terms

The proposal phase is where capture intelligence either pays off or exposes gaps. The terms below reflect the core vocabulary of the Shipley process as it applies to proposal development, from the first draft through final submission.

Proposal Manager (PM): The individual responsible for the end-to-end proposal effort, including schedule management, writer assignments, compliance tracking, and color team coordination. The PM owns the process, not necessarily the content.
Proposal Development Plan (PDP): A governing document that defines the proposal schedule, volume structure, writer responsibilities, and review milestones.
Storyboard: A pre-writing tool used in federal proposal development that maps each Section L-required section to its win theme, discriminators, features, benefits, and supporting evidence before drafting begins. Storyboards keep writers aligned with capture strategy and Section M evaluation criteria instead of defaulting to generic capability descriptions.
Compliance Matrix: A structured cross-reference mapping every Section L and Section M requirement to the corresponding proposal section and evaluation criterion to the response that covers it. Evaluators use it to confirm responsiveness; proposal managers use it to track coverage gaps.
Color Team Reviews: Structured internal reviews conducted at defined draft stages. Pink Team reviews storyboards and outlines; Red Team scores a near-complete draft against Section M criteria; Gold Team reviews the final document for quality and compliance before submission.
Executive Summary: A standalone volume or section written for source selection officials and agency evaluators that leads with win themes and discriminators tied to Section M criteria, not a recap of the technical approach. Many teams default to writing this last, but Shipley treats that as a common mistake. Drafting it early is the recommended practice, since it forces strategic alignment before sections are written and can double as an internal alignment tool across the whole team.
Past Performance Volume: A proposal volume documenting prior contract performance relevant to the current requirement, typically scored against recency, relevance, and quality.

Shipley Proposal Glossary: Color Team Review Terms

The Shipley method assigns each review gate a color designation tied to a distinct stage of proposal maturity and a defined evaluation focus.

Color Team Review Definitions

Review	Completion Stage	Primary Focus
Pink Team	25 to 50%	Response strategy, win themes, and section structure alignment to Section M
Red Team	75 to 95%	Full-draft scoring against Section L and Section M; compliance gaps, weak discriminators, unsubstantiated claims
Gold Team	Final draft	Pricing strategy, risk posture, and overall competitive positioning
White Glove / White Team	Pre-submission	Formatting compliance, cross-reference accuracy, and Section L responsiveness

Pink Team: An early-stage review conducted when the proposal is roughly 25 to 50 percent complete. The Pink Team assesses whether the response strategy, win themes, and section structures are properly aligned to Section M evaluation criteria before writers invest substantial effort in full drafts.
Red Team: The primary full-draft review, typically conducted when the proposal reaches 75 to 95 percent completion. Red Team evaluators score the proposal against Section L and Section M requirements as if they were the government source selection board, identifying compliance gaps, weak discriminators, and unsubstantiated claims.
Gold Team: A senior leadership review focused on pricing strategy, risk posture, and overall competitive positioning. The Gold Team typically does not rewrite content but assesses whether the proposal's offer is competitive and defensible under evaluation.
White Glove or White Team: A final pre-submission quality review covering formatting compliance, cross-reference accuracy, and Section L responsiveness before the proposal goes out the door.

Where many pursuit teams get tripped up is treating the Red Team as the first real review, which compresses the feedback cycle and leaves structural problems too late to fix without blowing the schedule.

Why the Shipley Proposal Glossary Matters in Federal Contracting

Federal contracting proposals are not freeform documents. They are structured responses to regulatory requirements, scored against evaluation criteria that agencies publish in Section L and Section M of every RFP. Within that environment, shared terminology is not a courtesy; it is a functional requirement for keeping capture teams, proposal managers, and subcontractors aligned under deadline pressure.

The Shipley Method gives GovCon teams a common working language. Terms like PWin, Black Hat, color team reviews, and win themes carry precise meanings inside the Shipley framework, and when a pursuit team uses them inconsistently, the downstream effects show up in proposal quality: misaligned sections, unvalidated assumptions, and compliance gaps that evaluators flag as execution risk. A capture manager who defines "win theme" as a tagline and a proposal writer who treats it as a discriminator tied to Section M criteria are working from incompatible mental models, even if they use the same word.

How GovEagle Supports the Shipley Proposal Process

The Shipley proposal glossary defines the terms, but the gap most pursuit teams face is structural: capture intelligence stays in CRM notes, win themes get reinterpreted by each writer, and compliance coverage gaps surface at Red Team when the schedule has no room left. Shared vocabulary closes the communication problem; it does not close the workflow problem.

GovEagle closes that gap by connecting capture notes and opportunity data directly to the proposal workspace, parsing Section L and Section M requirements from the RFP into a compliance matrix in Excel, and generating an annotated proposal outline in Microsoft Word that maps requirements to sections before writers begin drafting.

GovEagle supports the full color team review sequence, generating compliance and quality reports for Pink Team, Red Team, and Gold Team reviews. For pursuit teams that follow the Shipley process, GovEagle turns the glossary into a working workflow.

FAQs

What is the difference between a win theme and a discriminator in the Shipley proposal process?

A win theme is a customer-benefit-focused message that connects your strength to an agency need and runs consistently across every proposal section. A discriminator is a subset of that: a strength that is both relevant to the evaluation criteria and provably better than what competitors can claim. Every discriminator can anchor a win theme, but a win theme built on a vague capability that any firm could assert does not qualify as a discriminator.

What's the right order for color team reviews, and when do most teams get it wrong?

The correct sequence runs Pink Team at roughly 25 to 50 percent completion, Red Team at 75 to 95 percent, and Gold Team for final pricing and competitive positioning. The most common failure is treating Red Team as the first real review, which leaves structural and strategy problems too late to fix without compressing the schedule past recovery.

How do I build a compliance matrix that maps Section L and Section M requirements?

A compliance matrix cross-references every Section L instruction to the corresponding proposal section and every Section M evaluation criterion to the response that covers it. Build it from the RFP directly, line by line, and update it as amendments are issued. GovEagle generates this matrix in Excel, parsing Section L and Section M requirements directly from the RFP and mapping them to the format proposal managers already use for tracking coverage gaps through color team reviews, so teams can close those gaps before Red Team instead of finding them under deadline pressure.

Final Thoughts on the Shipley Proposal Glossary

The Shipley proposal glossary works best when the whole team uses it the same way. Miscommunication on terms like discriminators or win themes typically surfaces at Red Team, the point in the schedule where fixes are most costly. GovEagle is built around this structure: it maps capture intelligence directly to proposal sections, parses Section L and Section M requirements from the RFP into a compliance matrix, and supports the full color team review sequence, so the shared vocabulary of the Shipley glossary is embedded in the workflow instead of left to chance.

Shipley Proposal Glossary: Key Capture and Proposal Terms Defined July 2026