Unofficial satire. Not government guidance. Memes are not legal review.
CMCoEContracting Memes Center of Excellence

Daily acquisition brief // October 23, 2026

CMCoE Meme Intel: There Go My 200 Points

A spotless record, a bespoke requirement, surprise specifications, and an attachment from another timeline.

4 storiesRSS feed
Air Force / Experience credit

A clean record leaves 200 corrective-action points on the table.

AFRL's latest Q&A confirms that offerors without qualifying corrective-action experience cannot claim that line item.

Bad Luck Brian meme: NEVER NEEDED A CORRECTIVE ACTION PLAN / THERE GO MY 200 POINTS
NEVER NEEDED A CORRECTIVE ACTION PLAN / THERE GO MY 200 POINTS

What happened

The October 21 amendment to AFRL's 711th Human Performance Wing mission-support solicitation includes a 200-point item for government-approved corrective actions addressing employee performance or professionalism. Question 47 confirms that firms without qualifying historical experience must forgo those points.

The rule rewards demonstrated recovery: Section M requires concerns to have been addressed and fixed. A document need not be titled Corrective Action Plan, but the government must have identified a concern and accepted or approved the response. The current proposal deadline is October 30.

Why CMCoE cares

A spotless history does not supply evidence of fixing a documented problem. That creates an awkward experience-credit gap even though both outcomes can reflect capable management.

Regulatory fine print

This is an ongoing solicitation first issued August 21, not a new award or a claim that the criterion first appeared October 21. The minimum is 1,740 validated points; all qualifying offerors may receive awards, and extra points above the threshold earn no greater consideration. A firm can qualify without this 200-point item. Unresolved poor performance earns no credit. The caption is hypothetical satire, not a statement about a named bidder.

Sources

  1. AFRL Amendment 0006 Q&A, October 21: question 47, page 27 (Air Force Research Laboratory, )
  2. Attachment 5: technical ID 5(c), 200-point worksheet (Air Force Research Laboratory, )
  3. Section M, Amendment 0006: threshold and corrected performance (Air Force Research Laboratory, )
  4. SAM FA239626RB008: current amendment and deadline (SAM.gov, )
DHS / Sole-source justification

The requirement fits Carahsoft because DHS tailored it that way.

A newly posted justification says its action to address competition barriers was to include only OEMs solely distributed by Carahsoft.

Roll Safe meme: ONLY CARAHSOFT FITS THE REQUIREMENT / I HAD IT TAILORED
ONLY CARAHSOFT FITS THE REQUIREMENT / I HAD IT TAILORED

What happened

DHS posted sole-source justification FY26-0119 on October 20. In the section asking how it might overcome barriers to future competition, DHS says it tailored the original requirement to OEMs solely distributed by Carahsoft. The document describes an enterprise software BPA with an estimated five-year value of $2.657 billion.

DHS says the products must be obtained through Carahsoft, including by other resellers, and cites schedule pricing, volume discounts, administrative savings and standardization. Although SAM labels the posting presolicitation, USAspending records this BPA as signed July 15, with performance starting July 20; a September call order is already recorded.

Why CMCoE cares

The competition-barriers answer describes narrowing the product portfolio around one distributor. That makes the definition of the requirement central to the sole-source rationale.

Regulatory fine print

October 20 is the posting date, not the award date. The justification was approved June 5. Its $2.657 billion estimate is not an obligation or a finding of overpayment. The BPA itself obligates no funds; individual orders do. This story reports the documented rationale and date mismatch, not a finding that the arrangement is unlawful or that all software vendors must sell through Carahsoft.

Sources

  1. DHS FY26-0119: estimated value, rationale and competition-barriers section (Department of Homeland Security, )
  2. SAM: October 20 publication of Carahsoft BPA justification (SAM.gov, )
  3. USAspending: BPA 70RTAC26A00000011, July signature and performance dates (USAspending.gov, )
  4. USAspending: September ServiceNow call under the BPA (USAspending.gov, )
Defense Health Agency / Technical baselines

Guarantee a smooth transition. The system details may come later.

DHA's revised data-exchange solicitation asks for a measurable operational plan while withholding current SLAs and interface details during Phase I.

Condescending Wonka meme: GUARANTEE ZERO DISRUPTION / SPECIFICATIONS WOULD SPOIL THE SURPRISE
GUARANTEE ZERO DISRUPTION / SPECIFICATIONS WOULD SPOIL THE SURPRISE

What happened

On October 22, DHA revised its Data Exchange Platform solicitation and posted a workbook containing 608 question-and-answer entries. The revised AOI asks vendors for a credible strategy guaranteeing continuous legacy support and no unplanned, partner-impacting outages during modernization.

Question 2 says current SLAs, interface inventories and architecture diagrams are not being provided and may come in later phases. The AOI acknowledges the gap, directs firms to use comparable experience and allows explicit assumptions. Vendors must propose an integrated approach and a draft measurable work statement; submissions remain due October 28.

Why CMCoE cares

A transition plan is harder to test when offerors cannot see the actual service targets or interface inventory. The government will compare proposed approaches while important sizing assumptions remain unsettled.

Regulatory fine print

Phase I is a technical screening, not a binding priced offer. Preliminary commercial pricing may be requested in Phase II and detailed pricing in Phase III; final terms are not fixed here. Planned, coordinated maintenance is excluded from zero disruption. The workbook supplies qualitative operational guidance in question 541, so the claim is missing specific baselines, not a total absence of information. It has 608 entries numbered through 609, with 128 absent.

Sources

  1. DHA revised AOI: Phase I criteria, missing specifications and later pricing (Defense Health Agency, )
  2. DHA Q&A workbook: questions 2, 10, 139 and 541 (Defense Health Agency, )
  3. SAM HT003826SC005-AOI0002: October 22 amendment and attachments (SAM.gov, )
GAO / Replacement proposals

The Navy had April's attachment. July's proposal still needed it.

GAO upheld Hatalom's exclusion after a complete replacement proposal omitted a material attachment submitted months earlier.

Thanos — I Don't Even Know Who You Are meme: YOU HAVE MY APRIL ATTACHMENT / THAT WAS A DIFFERENT TIMELINE
YOU HAVE MY APRIL ATTACHMENT / THAT WAS A DIFFERENT TIMELINE

What happened

GAO's October 16 Hatalom decision appeared on its October 21 recent-decisions list. Hatalom had submitted required contract-reference attachment L-1 in April, but left it out of its July replacement proposal for Navy courseware services.

Hatalom argued the Navy already possessed the missing information. GAO denied the protest: the amendment expressly required a complete replacement and warned of exclusion, and L-1 was essential to the technical and past-performance evaluation.

Why CMCoE cares

A complete-replacement instruction makes the new submission the operative proposal. An attachment in the agency's older files does not automatically become part of it.

Regulatory fine print

GAO found the rejection reasonable; this was not a lost-file or late-email case. The Navy conceded its initial statement that FAR 52.215-1 did not apply was mistaken, but the material omission remained a valid basis for exclusion. The timeline caption is fictional film satire about superseding submissions, not a claim that the Navy erased records.

Sources

  1. GAO B-424681: full Hatalom decision and agency response (U.S. Government Accountability Office, )
  2. GAO recent decisions: October 21 public listing (U.S. Government Accountability Office, )