The structured review gates — Blue, Pink, Red, Gold, and Black Hat — that turn a rough draft into a competitive, compliant proposal.
Last reviewed on May 12, 2026 by the Government.biz editorial team. Color team practice follows widely used industry methodology (e.g., Shipley/APMP), not a federal regulation.
Government source-selection teams score proposals against published evaluation criteria, and they read a great many submissions. Small weaknesses — an unaddressed requirement, a vague approach, a missing discriminator — quietly cost points and lose awards. Color team reviews are scheduled, independent checkpoints designed to catch those problems while there is still time to fix them, rather than after submission when nothing can be done.
The colors are an industry convention (popularized by the Shipley methodology and used across the capture/proposal profession), not a government rule. Different companies vary the names and the exact draft percentages, but the underlying logic is consistent: review early for strategy, review late for score, and keep the reviewers independent of the writers.
When: before serious writing (capture phase)
Validates the win strategy, solution architecture, and themes before the team commits words to paper. Confirms you have a real, differentiated approach — not just a decision to bid.
When: ~50–60% draft
Checks that the proposal is structured to the solicitation, that win themes are present, that the solution is adequate, and that there are no major compliance gaps. The output is a recovery plan, while there's still time to execute it.
When: ~90–100% draft
Independent reviewers score the proposal the way the government will, against the evaluation factors. They hunt for weaknesses, risks, and unsubstantiated claims, and they assign strengths/weaknesses the way a source-selection board would.
When: 100% draft, pre-production
Senior leadership, contracts, and pricing do the final polish, confirm compliance, approve risk and price, and make the last go/no-go call before the proposal goes to production.
When: capture, before writing
The team role-plays competitors to predict their solutions, pricing, and discriminators, so you can position against them and "ghost" their likely weaknesses.
When: parallel to Gold and final
Green Team reviews the cost/price strategy for competitiveness and realism; White Glove is the final compliance and formatting pass to ensure the document is flawless and meets every submission instruction.
| Review | Typical participants | Duration | Primary output |
|---|---|---|---|
| Blue Team | Capture lead, solution architect, executives | 1–2 days | Approved win strategy & themes |
| Pink Team | Capture lead, SMEs, proposal manager | 2–3 days | Recovery plan |
| Red Team | Independent reviewers, former evaluators, executives | 3–5 days | Scored evaluation & findings |
| Gold Team | Contracts, pricing, executives | 1–2 days | Go/no-go decision |
| White Glove | Proposal coordinator, editor | 1 day | Final compliant document |
The single most important rule: Red Team reviewers must be independent of the writers. People who wrote the draft cannot see what's missing because they fill the gaps from memory. Bring in reviewers — ideally former government evaluators or source-selection members — who read it cold, exactly as the real evaluator will.
Color teams sit on top of a compliance matrix — a line-by-line mapping of every "shall," "must," and instruction in the solicitation to the place in your proposal that satisfies it. Pink Team confirms the matrix is built and the structure follows Section L; Red Team confirms the response would earn strengths under Section M; White Glove confirms nothing was dropped during production. Reviews are only as good as the criteria you give reviewers to measure against.
Blue (solution/strategy, before writing), Pink (~50–60% draft, structure and approach), Red (~90–100% draft, scored like the evaluator), Gold (final executive/contracts review), and White Glove/Green for production and pricing. Black Hat competitive analysis happens earlier, during capture.
Pink Team reviews an early draft to confirm structure, themes, and approach while there's time to change course. Red Team reviews a near-final draft and scores it as a government evaluator would against the Section M criteria, surfacing weaknesses and risks.
Reviewers independent of the writing team — ideally former government evaluators or source-selection members, plus SMEs and senior staff — who can read the proposal cold and score it objectively against the evaluation factors.
A capture-phase exercise where your team role-plays competitors to predict their solutions, pricing, and discriminators. It informs your win strategy and lets you position (and ghost) against likely competitor weaknesses.
No. Color teams are an industry best practice, not a government regulation. The FAR governs how the agency evaluates; color teams are how smart contractors prepare for that evaluation.
This page describes widely used proposal-management practice. For the underlying evaluation rules, see FAR Part 15 — Contracting by Negotiation. General information, not legal advice.