If someone told you “the pink team is Thursday” and walked off, here is what they meant. Color team reviews are staged quality checks on a proposal, each one named after a color, each one reading the document at a different point in its life and through a different lens. They run in a rough sequence as the proposal matures: an early-draft review, a near-final critique, an executive sign-off, and a final polish. The four you will hear named most often are pink, red, gold, and white glove.

None of this is a grammar check until the very end. The early reviews are about whether the proposal is going to win, and your section is part of that judgment. This page explains what each review is actually looking for, who tends to run it, and what it means for you as the technical person whose content is on the table.

Where the colors come from, and why they vary

The color team system comes from Shipley Associates, a proposal consultancy whose methodology became the closest thing the industry has to a standard. It was built for large, complex federal pursuits, the kind with multiple volumes, many contributors, and enough budget to staff independent review panels.

That origin matters, because it tells you two things. First, the framework is convention, not regulation. Nothing in the FAR requires a “red team.” A company runs these reviews because the discipline tends to produce better proposals, and it can run them however it likes. Second, because it is convention, the labels drift. One company’s pink team is another’s first draft review. Some shops add a blue team at the front and a green team for pricing. Smaller or faster pursuits compress the whole sequence into one or two combined sessions, or skip the color names entirely. If your organization’s definitions do not match what you read here, your organization’s definitions win. Use this page to understand the intent behind each gate, then map it onto whatever your shop actually calls them.

What stays consistent is the underlying idea: a proposal moves through increasing levels of maturity, and at each level a fresh set of qualified reviewers checks it against the things that win or lose, namely compliance with the solicitation, responsiveness to what the customer asked, and the presence of a clear, compelling story.

The sequence at a glance

In the fullest version of the model, the reviews run in this order:

  • Blue team: strategy and outline, before serious writing begins.
  • Pink team: the early draft. Is the structure right and is the win strategy showing up on the page?
  • Red team: the near-final draft, read the way the government evaluator will read it.
  • Green team: the pricing and cost review.
  • Gold team: the executive review and the decision to submit.
  • White glove (white team): the final line-by-line polish.

Most pursuits do not run all six. Pink, red, and gold are the backbone. White glove shows up on bids important enough to justify it. Blue and green appear when the organization and the deal are large enough to warrant dedicated strategy and pricing gates.

Pink team: is the strategy on the page yet?

The pink team reviews an early draft. The document is not finished and is not supposed to be. A useful standard is that every section exists and contains real content, approach, or at minimum a clear statement of what will go there. No blank sections, no placeholder shrugs. You will sometimes hear “65 to 70 percent complete,” but the percentage matters less than the substance: is there enough on the page to tell whether this proposal is heading toward a win?

What the pink team checks is execution of the win strategy and compliance with the solicitation’s structure. Are all the required sections present and in the right order? Does the draft respond to what Section L instructed and address what Section M will score? (If those terms are unfamiliar, start with the guide on Section L and Section M, because every review after this one is measured against them.) Is the intended story actually visible, or is the section a wall of capability statements with no thread?

What the pink team is not is a proofreading pass. Bringing comma corrections to a pink team wastes the gate. Reviewers are told explicitly to focus on content and strategy and to ignore polish, except where an inconsistency signals a deeper problem. More proposals are sunk by a weak or skipped pink team than by any other review, because this is the cheapest moment to fix a structural mistake. After this point, fixes get expensive.

Red team: read it as the evaluator will

The red team is the critical one. The draft is now near-final, often described as 85 to 90 percent complete, with the changes from pink team already worked in. The review is usually scheduled with two-thirds to three-quarters of the schedule gone, deliberately leaving time to act on what it finds.

The job of a red team is to predict the score. Reviewers read the proposal the way the government’s evaluators will, against Section M, and they rate how well it would actually do. This is the dress rehearsal for the real evaluation. A red team reviewer asking “where does this win points under Factor 2?” is doing exactly what a source selection board member will do for real a few weeks later.

Two things follow from that. The reviewers should be independent of the writing team, because the people who wrote a section are too close to see it the way a stranger will. And the writers usually do not get to defend their work in the room. If your section gets marked down at red team, the feedback is the gift. The reviewer just showed you, for free, where a real evaluator is likely to dock you. The instinct to explain what you meant is the instinct to suppress. The evaluator will not have you there to explain it either, so the section has to stand on its own.

Green team: the pricing review

The green team reviews cost and pricing. It checks that the numbers follow the format the solicitation requires, that the price is competitive, and that it is also executable, meaning the company can actually deliver the work at the price it bid. Technical contributors get pulled into this when pricing depends on technical assumptions: level of effort, labor mix, the hours behind a given approach. If your architecture drives the cost, expect questions here. Green team often runs in parallel with the content reviews rather than strictly after them.

Gold team: the decision to submit

The gold team is the executive review and the final gate before submission. The reviewers are senior leaders in the chain of authority over the work, usually a small group, ideally people who have been kept current on the pursuit rather than seeing it cold. Their focus is high level: are the win themes and discriminators clear, did the proposal absorb the corrections from red and green, and is it priced to win? The gold team is where the organization formally decides the proposal is ready to go out the door. It is the last chance to catch a problem big enough to matter.

White glove: the final polish

The white glove review, also called the white team, is the page-by-page pass at the very end. This is where polish finally becomes the point. Reviewers comb the near-final document for printing errors, layout breaks, formatting drift, broken cross-references, inconsistent terminology, and any correction from an earlier gate that did not get made. It is largely a visual and compliance check on a document that is otherwise done. Not every pursuit runs one, but high-value bids usually do, because at that level a sloppy table or a misnumbered page is a needless self-inflicted wound.

Review colors are not rating colors

Here is a trap worth naming, because it catches technical contributors constantly. The reviews have colors. The ratings reviewers assign also have colors, and they are a different system. A reviewer scoring your section might rate it red, yellow, green, or blue, where red typically flags a major deficiency that could make the section non-compliant or non-competitive. So “the red team gave my section a red” is a coherent sentence: the red team is the review, and red is the worst rating it can hand out. When someone says you “got a red,” ask whether they mean the review or the score. They are unrelated uses of the same word.

What this means if you are the technical contributor

You usually will not run these reviews, but your content goes through every one of them, so a few habits help:

  • Bring the right feedback to the right gate. Strategy and compliance concerns belong at pink. Line edits belong at white glove. Raising polish early or strategy late annoys everyone and helps no one.
  • Write your section to be scored, not explained. Red team is simulating an evaluator who will never hear you talk. If the section only makes sense with you narrating it, it is not done.
  • Treat red team markups as evaluator intelligence. A markdown there is a preview of where you would have lost points for real. Fix it now, while it is still free.
  • Know which Section M factor your section serves. Reviewers will check your content against the evaluation factors, and so should you, before they do.
  • Map your section to the compliance requirements before pink. The compliance matrix is the document reviewers use to confirm nothing required is missing. If you have already checked yours against it, pink team becomes a confirmation instead of a discovery.

When the whole thing is overkill

Honesty matters here, because the full color sequence is not always the right tool. On a small or fast-turnaround bid, running six separate review gates with distinct independent panels is overkill, and the handoffs can cost more time than they save. Many teams on tight timelines collapse the model into one or two focused review sessions that still ask the core questions: does it comply, does it answer the customer, and does it tell a clear story. The colors are a means to that end. If your shop runs a lean version, that is a reasonable adaptation, not a failure to do it properly. The questions are what matter. The rainbow is optional.

The Proposal Stack is a newsletter for technical GovCon professionals who get pulled into proposal work and want to contribute well without becoming full-time proposal writers. The guides here decode the vocabulary. The newsletter covers how this plays out in practice, issue by issue. Subscribe here.