Teardown #2: when the solicitation is a moving target

The submission due date was wrong as originally posted — corrected by amendment

The government itself had to amend the solicitation to fix the posted due date. The governing deadline therefore lives in an amendment attachment, not in the notice text a bidder first read. Two versions of the most unforgiving number in any pursuit were in circulation.

“ClaimsCore Combined Synopsis/Solicitation Amendment 0002- The purpose of this amendment is to correct the Phase 1 RFP submission due date as stated in Amendment 2 - Attachment 3, ClaimsCore Instructions to Offerors.”chars 242–457

What a bidder should do: Track deadlines from the latest amendment attachment, never the original notice; confirm the operative date in writing if any doubt remains.

Relative importance of evaluation factors: not stated in the notice text

The posted text names an award approach but defines no evaluation factors and no relative weights — the factor definitions live in an instructions attachment that is not part of the posted description. CiteTrac marks this NEEDS SOURCE rather than guessing: the honest answer is that the posted text does not contain it.

No quote — this flag reports information absent from the notice text, so it carries the NEEDS SOURCE marker instead of a citation. CiteTrac never fills a gap with a guess.

What a bidder should do: Pull the instructions attachment and shred the evaluation section before anything else — it defines the game you are playing.

3 amendments — the day-1 documents are no longer the documents of record

Every artifact a bidder shredded on day 1 was superseded while the pursuit was live: the Statement of Objectives was amended; the Instructions to Offerors were amended; an attachment was renamed mid-pursuit; a submission due date was corrected. A compliance matrix built from the original package silently drifts out of date unless the process re-shreds on every amendment — by hand, that means re-reading everything and diffing by eyeball.

“ClaimsCore Combined Synopsis/Solicitation Amendment 0003- The purpose of this amendment is to request offerors provide a copy of any CTA, as applicable in Phase 2 as stated in Amendment 3 - Attachment 3, ClaimsCore Instructions to Offerors.”chars 0–240

“ClaimsCore Combined Synopsis/Solicitation Amendment 0002- The purpose of this amendment is to correct the Phase 1 RFP submission due date as stated in Amendment 2 - Attachment 3, ClaimsCore Instructions to Offerors.”chars 242–457

“ClaimsCore Combined Synopsis/Solicitation Amendment 0001 - The purpose of this amendment is to 1) provide responses to RFP questions, 2) provide an Amended Solicitation - 75FCMC26R0022, 3) provide an amended Attachment 1 - ClaimsCore SOO, 4) provide an Amended Attachment 3 - ClaimsCore Instructions to Offerors, and 5) rename and provide an amended Attachment 6 - Beneficiary Quantities Claims and Unit Pricing.”chars 459–871

What a bidder should do: Re-shred on every amendment and diff requirement-by-requirement; version-stamp the matrix against the amendment number it reflects.

The actual requirements live outside the posted text

The posted description is an index, not a solicitation: 4 pointer statements route the reader to attachments for the requirements (Statement of Objectives), the instructions, the CLIN structure, and the clause list. Each attachment is a separately versioned document — and the amendment history shows several were revised or renamed mid-pursuit. Shredding the notice alone yields a matrix of pointers, not requirements.

“See Attached Soliciation-75FCMC26R0022 for a full breakdown of the CLIN structure, items, quantities, and units of measure (including option(s)).”chars 2010–2155

“See Attachment 1 ClaimsCore Statement of Objectives for full description of the requirements being acquired.”chars 2310–2418

“See the attached Solicitation - 75FCMC26R0022 and Attachment 5 - FAR 52.212-5 to find the full list of solicitation provisions and contract clauses”chars 2420–2567

“See Attachment 3 - ClaimsCore Instructions to Offerors for full instructions.”chars 2569–2646

What a bidder should do: Shred the attachments, not the notice — and re-pull every attachment on every amendment before trusting an existing shred.

Material change introduced after the question window closed

Per the notice metadata, questions closed March 6, 2026 and the final amendment posted March 11, 2026 — adding a new submission element after bidders could no longer ask about it. Whatever the amendment changed had to be absorbed on a compressed clock with no Q&A recourse.

“ClaimsCore Combined Synopsis/Solicitation Amendment 0003- The purpose of this amendment is to request offerors provide a copy of any CTA, as applicable in Phase 2 as stated in Amendment 3 - Attachment 3, ClaimsCore Instructions to Offerors.”chars 0–240

What a bidder should do: Treat every post-Q&A amendment as a compliance emergency: re-shred it the day it posts and log a stated assumption for anything unclear.

Two different performance standards for the same capability: 'sub-second' vs. 'near real-time'

One clause requires 'sub-second' performance — measurable, testable — while another promises 'near real-time', which has no acceptance criterion. A vendor sizing infrastructure against the looser reading underbids the one engineering to the stricter one; at acceptance-test time only one standard can govern.

“Develop and implement a configurable, interoperable claims processing platform capable of sub-second adjudication.”chars 1666–1780

“CMS intends to procure a Software as a Services (SaaS) Commercially-Available-Off-The-Shelf (COTS) product and complimentary configuration and integration services that will provide CMS with near real-time adjudication and claims status, policy agility, industry leading enterprise tools, improved fraud prevention capabilities, and tighter integration across CMS, Medicare Administrative Contractor (MACs), providers, and partners.”chars 1232–1664

What a bidder should do: Engineer and price to 'sub-second' (the measurable standard) and state that interpretation in the technical response.