If you have spent any time in a proposal shop, you have heard people talk about pink team and red team as if everyone was born knowing what they mean. New teammates nod along and quietly hope to figure it out from context. Color team reviews are not mysterious, but they are widely misunderstood, and a review run badly does worse than nothing: it burns your team's time, creates false confidence, and leaves real problems undiscovered until the government finds them for you.
Color team reviews are structured proposal review gates, each with a specific job at a specific stage of writing. This guide explains why they exist, what each review checks, the order they run in, what separates a review that raises your score from one that wastes an afternoon, and the prerequisite that most teams underestimate.
Why color reviews exist
A federal proposal is written under deadline by multiple authors, often across multiple companies in a teaming arrangement. Left unchecked, that document drifts: off strategy, off compliance, off message, and out of one author's voice into five. Color reviews are scheduled checkpoints that catch those problems while there is still time to fix them. They impose discipline on a process that otherwise produces a pile of individually fine sections that do not add up to a winning proposal.
The color names are a convention, popularized by the Shipley methodology and adapted by nearly every capture organization since. Because they are a convention and not a regulation, exact definitions vary from shop to shop. The sequence and the underlying purpose, though, are remarkably consistent.
The core reviews
| Review | Stage | Primary question |
|---|---|---|
| Pink Team | Early draft, roughly 50 to 65 percent | Is the approach, structure, and win strategy on track |
| Red Team | Near-final, roughly 90 percent | How would a government evaluator score this against Section M |
| Gold Team | Final leadership review | Are the fixes made and is this ready to produce |
| White Glove | Production and quality check | Is the document we are about to submit clean and compliant |
Pink Team
Pink Team reviews an early but real draft, usually somewhere between half and two-thirds complete. The goal is direction, not polish. Reviewers ask whether the technical approach is sound, whether the structure follows Section L, whether the win themes are present and substantiated, and whether the proposal is responding to what Section M actually rewards. Pink Team is the cheapest place to course-correct, because the draft is still malleable. Catching a strategy problem here costs a rewrite of a section. Catching it at Red Team costs a scramble.
Red Team
Red Team is the most important review, and the most demanding. Reviewers score the near-final proposal exactly as a government source selection team would, against the Section M factors, using a scoring sheet rather than personal opinion. They are looking for scoring gaps, unsubstantiated claims, weak or missing proof, and any Section L noncompliance that survived. A real Red Team produces ratings and specific, actionable findings, not a list of wording preferences. For what the reviewers are simulating, see how to read Section M and the interaction with instructions in Section L vs Section M.
Gold Team
Gold Team is the final leadership review, typically after Red Team fixes are in. Senior leaders confirm that the Red Team findings were actually addressed, sign off on price and risk, and make the final go decision on the document before it goes to production. Gold Team is not the place to rewrite the technical approach. If the approach is still wrong at Gold Team, the process upstream failed.
White Glove
White Glove, sometimes called a final production or quality review, is the last pass before submission. It checks formatting, page limits, completeness, cross-references, graphics, and that the document you are about to upload exactly matches the Section L instructions. It is unglamorous and it has saved countless proposals from being rejected over a page count or a missing volume.
Other reviews you will hear about
Beyond the core four, shops use a few others. A Blue Team often reviews the capture strategy and solution before serious writing begins. A Black Hat review analyzes the competition, modeling how rivals will bid so you can counter them. A Green Team usually refers to the price-to-win and cost review. The labels matter less than the function. What matters is that someone is checking strategy, someone is checking the competition, someone is scoring against Section M, and someone is checking production.
What makes a color review actually work
The reviews that move scores share a handful of traits:
- Reviewers score against Section M with a real scoring sheet, not against personal taste. "I would word this differently" is not a finding.
- Reviewers did not write the proposal. Fresh eyes catch what authors are now blind to.
- There is time to act on the findings. A Red Team at 99 percent complete is theater, because nothing can change.
- The team walks in with a clean compliance baseline, so reviewers judge content instead of chasing missing pieces.
- Findings are written down and tracked to closure, not debated in the room and forgotten.
Scheduling the reviews
The most common scheduling failure is leaving no recovery time. Each review needs enough runway afterward to implement what it finds. A proposal schedule that puts Red Team two days before submission has effectively cancelled the review, because there is no time to fix anything substantive. Work backward from the due date and protect the gaps between reviews as fiercely as the reviews themselves.
The prerequisite everyone underestimates
A review is only as good as the requirements baseline it starts from. If your team is still arguing about what Section L requires during Red Team, the review gets spent on compliance archaeology instead of scoring. The single highest-leverage thing you can do for your reviews is walk into Pink Team with a clean requirements list and a complete compliance matrix already built, so reviewers can focus entirely on whether the proposal wins. This is also where a strong kickoff pays off; see the Proposal Kickoff Accelerator and how an Opportunity Snapshot sets the baseline. Past performance, one of the most reviewed and most commonly weak sections, deserves its own preparation; see writing past performance references.
Staffing a review
The quality of a color review depends heavily on who is in the room. The ideal reviewers know the customer and the type of work but did not write the proposal, so they bring genuine evaluator distance. Pulling in a respected outside reviewer for Red Team, someone who will score honestly rather than protect feelings, is one of the highest-return moves in proposal management. The failure mode is staffing reviews with the same people who wrote the sections, who are now too close to see the gaps a government evaluator will find immediately.
Turning findings into fixes
A review that produces findings but no closure is wasted. After Red Team in particular, the proposal manager should consolidate every finding, prioritize them by scoring impact, assign each to an owner with a deadline, and track them to completion before Gold Team. This recovery period is where the score actually improves, which is why the schedule has to protect time after each review, not just the review itself. A common and painful pattern is a Red Team that surfaces a dozen real problems two days before the deadline, leaving time to fix two of them.
Right-sizing reviews for the bid
Not every pursuit warrants the full sequence. A small task order on a vehicle you know well might justify a single combined review, while a must-win recompete deserves the complete Pink, Red, and Gold progression with outside reviewers and a Black Hat on the competition. Match the review intensity to the size and importance of the bid, decided during your bid/no-bid and kickoff. Over-reviewing a small bid wastes scarce capture capacity; under-reviewing a major one risks the whole investment.
Bottom line
Pink shapes, red scores, gold approves, white glove ships. Tie each review to Section M, staff it with people who did not write the draft, leave real time to act on findings, and start from a clean compliance baseline. Reviews do not add quality by happening on the calendar. They add it when they are run with discipline against a clean foundation.
For the surrounding pieces, see how to evaluate an RFP in under 10 minutes, build the foundation with the compliance matrix template, and pull staffing early with key personnel extraction.