If Edgar Allan Poe had been a federal contractor, he might have written a very different story. In this version, the quiet thumping under the floorboards is not a guilty conscience, but the sound of yet another contract vehicle going sideways. With the official announcement of the collapse of CIO-SP4, we find ourselves once again pondering what the future of governmentwide and multi-agency vehicles will look like. CIO-SP4 is now a confirmed failure. We have talked before about systemic flaws that haunt overall contract evaluation, and CIO-SP4 was unfortunately a highlight of those flaws. A number circulating within industry suggests that the combined investment from government and bidders reached roughly $1.6 billion dollars. When the financial stakes climb that high, nobody is walking away from a potential award without a fight.
There is another striking figure. More than 80% of the original small business CIO-SP3 incumbents did not make it onto CIO-SP4, which created the perfect conditions for a protest superstorm. Meanwhile, OASIS+ kept moving forward, and POLARIS appears to be sailing through the waves even while fending off its own set of challenges. At the same time, everyone is watching whether T4NG2 will actually move forward, as promised, in March 2026.
The Army’s ACC-APG appears determined to keep marching ahead with MAPS – a consolidation of the existing RS3 and ITES-3S contracts. They held a well-attended Industry Day event on January 28th. The enthusiasm did little to hide the problems already visible in the drafts. Inconsistencies, unclear parameters, visible errors, and a self-scoring framework that gives every offeror far too much interpretive freedom. These are the exact ingredients that have kept T4NG2 stuck in limbo for over two years. On the bright side, the Army did take an important first step by delaying the release of the final solicitation, which was originally planned for February 2nd, so they could sort through the tidal wave of questions generated by the Industry Day.
Even so, the current award plan paints a worrisome picture. Each domain plans to award to a total of 15 large businesses and five SBs, four WOSB firms, three SDVOSB firms, three HUBZones, five 8(a) firms, and five SDB firms. The math becomes more troubling when compared to more than 80 task order winning incumbents on RS3 and more than 110 on ITES-3S. This recipe sets up the same problem that sank CIO-SP4 long after “award day” arrived. A very high number of incumbents will be excluded before the race even starts because the award ceiling is too narrow. Layer on top of that a scoring sheet that leaves far too much space for subjective interpretation, and you have a familiar sinking feeling. Unless major adjustments are made, MAPS looks like it is tiptoeing toward the gallows before the solicitation even fully hits the street.
When you compare MAPS to vehicles that survived their launch cycles, a few lessons become painfully obvious. MAPS will need resilience, modularity, and transparency woven into its structure. This is not optional. It is essential.
OASIS+ succeeded because its design encourages stability. It uses continuous on ramps and domain-based scorecards which let the program keep moving even as GAO picked through a handful of focused challenges including questions involving women owned small business status timing and joint venture qualifying projects. The structure absorbed the turbulence because the turbulence was never allowed to freeze the entire program. [pubkgroup.com], [acquisition.gov], [nextgov.com]
POLARIS provides another lesson in survival. Instead of waiting for every dispute across every pool to resolve, GSA kept moving forward with the pools that were clear including HUBZone and SDVOSB. This approach preserved buyer confidence and kept spending activity alive. [iquasar.com]
Unfortunately, when you look closely at the way CIO-SP4 imploded, and the long list of hurdles that T4NG2 continues to face, the MAPS scoring criteria begin to look eerily familiar.
A. The “100% domain coverage” mystery, also known as CIO SP4 déjà vu -CIO-SP4’s downfall began with fuzzy definitions. The rules never made it clear what counted as a qualifying project. Offerors struggled to tell whether their projects met domain requirements. Scoring was inconsistent, and the documentation was uneven across the board. GAO and the Court of Federal Claims came down hard on NIH for this ambiguity because unclear instructions lead directly to arbitrary scoring and arbitrary scoring leads directly to sustained protests. These problems eventually caused CIO- SP4 to collapse entirely. [federalnew…etwork.com], [bakertilly.com]
MAPS is now potentially walking that same path. The draft RFP does not show a consistent standard for determining full domain coverage. Offerors and evaluators are left to figure it out on their own. This ambiguity almost guarantees protests once preliminary scores appear. [washington…nology.com]
B. Attrition and vacancy scoring, the T4NG2 ghost returns – T4NG2 ran aground because vendors were allowed to self-report internal HR metrics. Offerors inflated numbers. The government had no way to audit any of it. The scoring model rewarded unverifiable claims which evaluators could not defend. Protests followed in predictable waves.
MAPS is echoing that pattern. The scoring model now includes employee retention and staffing stability as major point categories, yet the draft RFP includes no instructions about verification, no rules for validating data, and no audit methodology. Everything rests on the honor system which becomes a disaster the moment competitors file pre-award protests alleging uneven treatment or false reporting. [govconwire.com]
C. When HR scoring outweighs actual capability – MAPS places so much weight on HR stability that it risks skewing the entire evaluation. Staffing stability often reflects the size and maturity of a company, not its capability to perform a specific domain mission. Attrition varies sharply depending on region and industry. Small businesses usually have higher turnover and fewer resources, which means they enter the competition at a structural disadvantage. This creates a bias that is not mission aligned, not verifiable, and not defensible in court. These same issues forced redesigns on POLARIS scorecards and ultimately contributed to the unraveling of CIO-SP4.
At this point, it is worth sending an early plea to the contracting teams working on MAPS. Please take lessons from the vehicles that came before. Talk to your peers. Study failures. Make corrections now before the protest slide begins. Industry will continue to protest every time a scoring system is ambiguous, and every time they feel boxed out by unclear or unverifiable rules. If those protests keep coming, delays will keep compounding, and cancellations will continue to follow. That is a waste of resources for everyone involved. We can do much better. Let us strengthen the structure on the front end and build something that stands.