RED in Government Contracting: What It Means and Why It Matters for Small Businesses

What a RED Rating Actually Means

Federal agencies that use color-coded evaluation schemes -- most commonly seen in Department of Defense source selections -- assign RED (or Unacceptable) to a proposal factor when it contains a material deficiency. According to DoD Source Selection Procedures (published by the Office of the Under Secretary of Defense for Acquisition and Sustainment), an Unacceptable rating means the proposal fails to meet a minimum requirement, and the deficiency is so significant that it cannot be corrected through clarification alone. A proposal factor rated RED is generally ineligible for award unless the agency opens discussions and the offeror successfully revises the response.

It is important to distinguish between the terms. Some agencies use the word RED explicitly; others use Unacceptable, Unsatisfactory, or similar language. The underlying standard is typically the same: the response does not satisfy a stated requirement in the solicitation. Contracting officers are required by FAR Part 15 to document their findings, so a RED label carries written justification that offerors can sometimes review through a debrief.

Where RED Ratings Show Up in the Evaluation Process

Most full-and-open or competitive federal solicitations using Negotiated Acquisition (FAR Part 15) include an evaluation scheme described in Section M of the solicitation. When a Source Selection Evaluation Board (SSEB) reviews submissions, each technical evaluator scores individual factors -- such as technical approach, management plan, and past performance -- against those criteria. A RED on any single factor can disqualify the entire proposal from the competitive range, meaning the offeror may not even receive an opportunity to discuss or revise their submission.

Past performance is a common area where RED equivalents appear under a separate scale. DoD often rates past performance as Substantial Confidence, Satisfactory Confidence, Limited Confidence, No Confidence, or Unknown. A No Confidence rating functions similarly to RED in that it strongly disadvantages the offeror. For past performance, agencies draw on CPARS records in the federal contractor performance database, references provided in the proposal, and publicly available information on USAspending.gov.

Common Triggers for RED and Unacceptable Ratings

RED ratings rarely come from a single careless sentence. They usually stem from a proposal that fails to address a specific requirement, contradicts the solicitation's statement of work, or relies on assumptions that the agency explicitly prohibited. Understanding the most common triggers can help your team build a compliance matrix before writing begins.

• Missing a mandatory requirement listed in the PWS or SOW (for example, failing to address a required certification or personnel qualification)
• Proposing a delivery schedule that does not meet the solicitation's minimum timeline
• Submitting page-limited volumes that exceed the stated limits, causing evaluators to stop reading
• Offering pricing that is deemed unrealistic or that fails to account for required wage determinations under the Service Contract Act
• Providing past performance references that fall outside the lookback period specified in Section L
• Leaving a factor response blank or responding with a placeholder such as 'to be determined'

A Concrete Example: How One Missing Certification Triggers RED

Consider a small IT services firm responding to a DHS solicitation for cybersecurity support. The solicitation's Section L requires that all key personnel hold an active Secret clearance at time of proposal submission. The firm's proposed Program Manager holds a clearance that lapsed 14 months ago. Even if every other section of the proposal is well-written and competitive, the evaluator reviewing personnel qualifications will likely assign an Unacceptable rating to the Staffing factor because the minimum requirement is not met.

The firm is excluded from the competitive range. During their debrief, they learn that three other small businesses with similar technical scores won evaluation points simply by satisfying the clearance requirement. The lesson: compliance with minimum requirements is not a differentiator -- it is the floor. Differentiators only matter after you clear the RED threshold on every evaluated factor.

How to Avoid RED Ratings: A Practical Checklist Approach

The most reliable defense against RED ratings is a rigorous compliance review conducted before final submission -- not the night before, but early enough to allow substantive revision. Teams that treat Section M as a scoring rubric and Section L as an instruction manual consistently outperform those that write by instinct. Here are actionable steps to build that discipline into your capture and proposal process.

1. Build a Compliance Matrix on Day OneAs soon as you download the solicitation, extract every shall, will, and must statement from Sections C, H, L, and M into a spreadsheet. Assign each requirement to a volume, section, and responsible writer. This matrix becomes your audit trail.
2. Conduct a Red Team Review Focused on Minimums FirstBefore evaluating quality or differentiation, have a reviewer -- ideally someone who did not write the proposal -- confirm that every mandatory requirement is explicitly addressed. Mark any gap as a RED risk before it reaches an evaluator.
3. Verify Personnel Qualifications EarlyConfirm clearance levels, certifications, and labor category alignment for all proposed key personnel at least 30 days before submission. Personnel gaps are the single most common avoidable RED trigger.
4. Check Page Counts and Formatting RulesVolume limits, font size, margin requirements, and file naming conventions can cause evaluators to discard or stop reading your response. Assign one person to own format compliance as a dedicated role.
5. Request a Debrief After Every LossIf you receive a RED on any factor in a prior bid, use the debrief process (FAR 15.506) to understand the specific deficiency. That institutional knowledge directly improves your next submission.

Can You Recover from a RED Rating During Discussions?

Under FAR 15.307, if a contracting officer establishes a competitive range and your proposal is included despite a RED factor, discussions give you an opportunity to address significant weaknesses and deficiencies. The agency is required to point out all deficiencies and significant weaknesses so that offerors have a fair opportunity to revise. However, inclusion in the competitive range is not guaranteed if your overall proposal is substantially weaker than competitors.

The practical limit here: even if you fix the specific deficiency during discussions, evaluators will still compare your final proposal against all other offerors' final proposals. A RED that was corrected does not reset your score to Outstanding -- it may move you to Acceptable, which may not be competitive enough if other offerors were already rated higher before discussions. Recovery is possible but not guaranteed, which is why prevention before submission is always the better strategy.

Start with the Right Opportunity to Avoid Uphill Battles

One underappreciated way to reduce RED risk is to pursue opportunities that are a strong fit for your existing qualifications and past performance -- rather than stretching for contracts where you cannot meet minimum requirements. Tools that help you monitor SAM.gov and filter opportunities by NAICS code, set-aside type, and agency history give your team more time to evaluate fit before committing proposal resources.

CaptureIQ supports this kind of early-stage decision-making by surfacing relevant opportunities and helping teams assess alignment with their capabilities. All final go/no-go decisions and proposal submissions remain with your team -- CaptureIQ provides decision-support, not automated submission.