A color team review is a structured proposal review where a fresh set of eyes evaluates a draft at a fixed stage, against the same criteria the client will use. The colors name the stages: pink team checks the early draft for compliance and direction, red team scores a near-final draft like a real evaluator, and gold team is the senior sign-off before submission. The point is to find the problems while there's still time to fix them.
Where the Colors Come From
Color team reviews started in federal and defense contracting, where proposals are long, scored against published criteria, and too expensive to lose on an avoidable mistake. The method spread into A/E work through firms chasing federal qualifications-based pursuits, and it applies to any competitive submittal, not just federal ones. An SOQ, a state DOT response, or an SF330 all benefit from the same idea: review the draft at planned checkpoints, with reviewers who didn't write it, against the agency's actual scoring. What separates a color team from a casual "can you look this over" is that each review happens at a set stage, has a defined job, and uses reviewers who can read the draft cold.
The Four Reviews and When They Happen
Not every firm runs all four, and smaller teams often compress them. But each review has a distinct job, and the timing is the part most firms get wrong.
| Review | Draft stage | What it checks | Who leads it |
|---|---|---|---|
| Pink team | ~50% complete | Compliance with the solicitation, structure, and win themes | Proposal manager + a fresh reviewer |
| Red team | ~90% complete | Full mock evaluation, scored against the agency's criteria | Senior staff who did not write the draft |
| Gold team | ~95% complete | Final executive read, strategy and risk, sign-off to submit | Principal or pursuit champion |
| White glove | Final, pre-submit | Page limits, required forms, formatting, broken cross-references | Coordinator or production lead |
The pink team is the cheapest and most skipped. It reads a roughly half-built draft and asks two questions: does this comply with the solicitation, and is it following the plan? Catching a missed requirement at 50 percent costs an hour. Catching it the night before submission costs the proposal. The red team is the one that earns the method its reputation: reviewers take a near-final draft and score it the way the selection panel will, using the solicitation's evaluation criteria as the rubric. They're not editing, they're grading, and the output is a ranked list of what would cost points. The gold team is the short senior read on strategy, risk, and whether the firm should still sign every commitment in the document, and the white glove pass is the final clean check of page counts, forms, and broken cross-references before the package goes out.
Who Belongs on a Red Team
The single rule that makes a red team work: the reviewers cannot be the people who wrote the proposal. Writers can't see their own gaps. They know what they meant, so they read what they meant instead of what's on the page, and the review becomes a rubber stamp.
A good red team is senior staff who can read like an evaluator, ideally including someone who has actually sat on a selection panel. They need the solicitation's evaluation criteria in hand and enough distance from the draft to score it honestly. The proposal coordinator who assembled the package is usually too close to lead the scoring, though they're essential for running the logistics of the review. The goal is an honest dress rehearsal, not encouragement.
The Failure Modes That Waste a Review
Most firms that "do color teams" still lose on the same mistakes, because the review happened in a way that couldn't help.
-
Running the red team too late. A red team three days before submission is a list of problems with no time to fix them. Schedule it with enough runway, usually five to seven days out, that the team can act on the findings. A review you can't respond to is theater.
-
Reviewers who also wrote the content. Covered above, and worth repeating because it's the most common version of the failure. If the writers are the reviewers, the review confirms what the team already believes.
-
Skipping the compliance check. Treating the review as a copy-edit and never checking the draft against the solicitation. Page limits, required forms, certifications, and SF330 Section H commitments are pass-fail gates, and they're the cheapest losses to prevent. The pink team exists largely to catch these early.
-
Reviewing on vibes instead of the rubric. Without the agency's evaluation criteria as the scoring sheet, reviewers default to personal taste. The whole value of a red team is that it scores the draft the way the client will, not the way a colleague would.
There's a quieter failure too. A red team will often flag that a featured project or a named engineer isn't the most relevant choice for the pursuit. That's the high-value finding the review exists for, but only if the team can act on it. When swapping a project means rebuilding a sheet from scratch the night before, the finding gets noted and ignored. When staff and project content is modular and retrievable, acting on a reviewer's call is a quick regenerate instead of an all-nighter, which is part of what RFPM.ai is built for. The review improves the proposal instead of just documenting its flaws.
Color team reviews aren't extra work bolted onto a tight schedule. Run on a realistic pursuit timeline, and only on pursuits that passed go/no-go, they're how a firm stops losing proposals to problems it could have caught.
Frequently Asked Questions
What is a color team review?
A color team review is a structured proposal review at a fixed draft stage, run by reviewers who didn't write the draft, against the same criteria the client will use. The colors name the stages: pink (early draft, compliance and direction), red (near-final, full mock evaluation), gold (executive sign-off), and white glove (final production check). The point is to find problems while there's still time to fix them.
What's the difference between a pink team and a red team?
A pink team reviews an early draft, around half complete, and checks that it complies with the solicitation and follows the plan. A red team reviews a near-final draft, around 90 percent complete, and scores it the way the selection panel will, using the evaluation criteria as a rubric. Pink catches direction and compliance problems cheaply; red catches what would cost points before the client does.
Who should be on a red team?
People who did not write the proposal. The best red teams are senior staff who can read like an evaluator, ideally including someone who has served on a selection panel, working from the solicitation's evaluation criteria. The proposal coordinator usually runs the logistics but is too close to the draft to lead the scoring. Writers reviewing their own work produces a rubber stamp, not a useful review.
When should you run color team reviews in a proposal schedule?
Build them into the schedule from the start. A common rhythm: pink team around the halfway point, red team five to seven days before submission, gold team a day or two out, and a white glove pass right before submitting. The most important rule is that the red team happens early enough that the team can still fix what it finds.
Do small A/E firms need color team reviews?
Yes, though usually in compressed form. A small firm may not staff four separate teams, but it still benefits from at least one honest review by someone who didn't write the draft, scored against the agency's criteria, with enough time left to act. Even a single combined pink-and-red review catches the compliance misses and relevance gaps that quietly cost shortlist points.