A pink team review checks the plan, not the prose. What to read in a half-written proposal, which gaps are still cheap, and when to call the gate. A pink team review tests the plan behind a proposal rather than the writing in it. Here is what to check when half the draft is still an outline, and which gaps are still cheap to close. A pink team review tests the plan behind a proposal, not the prose inside it. The reviewers read the outline, the compliance matrix and each section's plan against Section L and Section M. Then they answer one question. Does the document the government asked for exist yet, even as a skeleton? Word choice does not belong in this gate. Half the draft is still an outline, so there is nothing to polish. What there is to check is coverage, placement and the claim each section intends to prove. Those three things cost almost nothing to change today. They cost nights in two weeks, and they cost the bid after submission. Our guide to the four review gates (/blog/color-team-review-proposal) sets out what each one can still change. This post covers the first gate alone. What A Pink Team Review Tests Shipley defines the gate narrowly. Its glossary says the pink team "reviews storyboards, outline, discriminators, and features/benefits before the first draft is written" (https://www.shipleywins.com/glossary/pink-team). Its course description puts the same gate against the solicitation, checking the whole planned proposal in the form of content plans against the customer's proposal instructions and evaluation factors. Shipley also makes a blunt claim about skipping it. "More proposals fail because of poorly executed or nonexistent Pink Teams than any other cause," says its guidance on who to invite (https://www.shipleywins.com/blogs/color-team-reviews-who-to-invite-and-why). Treat that as a practitioner's judgment rather than a measured finding, because no agency publishes a number on it. The underlying point still holds. A plan nobody tested becomes a draft nobody can save. The Outline Belongs To Them The outline under review is not yours to design. FAR 15.204-5(b) tells the contracting officer to put proposal instructions in Section L. The paragraph says offerors "may be instructed to submit proposals or information in a specific format or severable parts". It adds that the instructions "may specify further organization of proposal or response parts". The examples it lists are administrative, management, technical, past performance and cost data. Section M then carries every significant factor and subfactor "and their relative importance", under FAR 15.204-5(c) (https://www.acquisition.gov/far/15.204-5). So a pink team works from an answer key. Put Section L beside the draft outline and most of the review becomes mechanical. Every part the instruction names needs a he
A pink team review tests the plan behind a proposal rather than the writing in it. Here is what to check when half the draft is still an outline, and which gaps are still cheap to close.
A pink team review tests the plan behind a proposal, not the prose inside it. The reviewers read the outline, the compliance matrix and each section's plan against Section L and Section M. Then they answer one question. Does the document the government asked for exist yet, even as a skeleton? Word choice does not belong in this gate. Half the draft is still an outline, so there is nothing to polish. What there is to check is coverage, placement and the claim each section intends to prove. Those three things cost almost nothing to change today. They cost nights in two weeks, and they cost the bid after submission. Our guide to the four review gates (/blog/color-team-review-proposal) sets out what each one can still change. This post covers the first gate alone. What A Pink Team Review Tests Shipley defines the gate narrowly. Its glossary says the pink team "reviews storyboards, outline, discriminators, and features/benefits before the first draft is written" (https://www.shipleywins.com/glossary/pink-team). Its course description puts the same gate against the solicitation, checking the whole planned proposal in the form of content plans against the customer's proposal instructions and evaluation factors. Shipley also makes a blunt claim about skipping it. "More proposals fail because of poorly executed or nonexistent Pink Teams than any other cause," says its guidance on who to invite (https://www.shipleywins.com/blogs/color-team-reviews-who-to-invite-and-why). Treat that as a practitioner's judgment rather than a measured finding, because no agency publishes a number on it. The underlying point still holds. A plan nobody tested becomes a draft nobody can save. The Outline Belongs To Them The outline under review is not yours to design. FAR 15.204-5(b) tells the contracting officer to put proposal instructions in Section L. The paragraph says offerors "may be instructed to submit proposals or information in a specific format or severable parts". It adds that the instructions "may specify further organization of proposal or response parts". The examples it lists are administrative, management, technical, past performance and cost data. Section M then carries every significant factor and subfactor "and their relative importance", under FAR 15.204-5(c) (https://www.acquisition.gov/far/15.204-5). So a pink team works from an answer key. Put Section L beside the draft outline and most of the review becomes mechanical. Every part the instruction names needs a he
Contact Shaavir · View services · Read the blog · Careers · Case studies · Privacy policy · Terms