The Government Accountability Office has dismissed a protest from ProSource360 Consulting Services, Inc. after the Washington, D.C., small business argued that a blank set-aside field on SAM.gov hid an Army opportunity it wanted to bid. In a decision dated June 4, 2026, and publicly released July 21, GAO ruled in ProSource360 Consulting Services, Inc., B-424386 that the company was charged with constructive notice of the solicitation the moment the Army posted it — regardless of an admitted clerical mistake in the online synopsis — and that its objections arrived far too late to matter.
Background
The dispute grew out of Army RFP W911QY-26-R-A007, a solicitation for materiel fielding and medical liaison support services. The Army posted the requirement on February 18, 2026, and set a proposal deadline of March 23, 2026. The work carried a total small business set-aside, and the RFP itself incorporated FAR clauses 52.219-6 and 52.219-8, leaving no doubt on the face of the document about the competition's restricted scope. ProSource360 had a direct stake in the outcome: the incumbent contract was performed by ERProSource360, a joint venture of Enterprise Resource Planning International, LLC (ERP) and ProSource360. The follow-on was, in other words, work the company already knew intimately.
Key Details
The problem, ProSource360 said, was discovery. When the company filtered SAM.gov for small business opportunities, the Army posting never surfaced. The reason, GAO recounted, was a data-entry slip: the Army contract specialist "inadvertently failed [to] make a selection from the 'Original/Updated Set Aside' drop-down menu," leaving the set-aside classification blank on the synopsis. Because ProSource360 screened for set-aside work, the empty field meant the opportunity fell outside its search results. The company said it did not learn of the solicitation until its joint venture partner, ERP, told it about the requirement — by which point the March 23 proposal deadline had already passed.
The sequence underscored how close the miss was. ERP itself submitted a proposal on March 21, 2026, two days before the deadline, but the Army notified the firm on March 27 that its bid was non-responsive because ERP, standing alone, did not qualify as the small business the set-aside required. Only after that rejection did the restricted character of the follow-on crystallize for the wider ProSource360 team, well past the point when a timely proposal or a pre-deadline protest was still possible.
ProSource360 raised two grounds. First, it argued that the blank set-aside field effectively concealed the small business opportunity from the very firms it was meant to reach. Second, it contended the Army used an improper solicitation form, arguing the agency should have issued the requirement on Standard Form 1449, the form prescribed for commercial products and services, rather than the form it actually used.
GAO rejected both as untimely. Under its bid-protest regulations, challenges to alleged improprieties that are apparent on the face of a solicitation must be filed before the deadline for receipt of proposals, per 4 C.F.R. § 21.2(a)(1). Both of ProSource360's arguments — the set-aside coding and the choice of solicitation form — were apparent from the posted RFP itself. A protester who waits until after the closing date to raise them has waited too long.
The blank drop-down did not rescue the timeliness problem. GAO invoked the constructive-notice doctrine, holding that "protesters are charged with constructive notice of procurement actions published on the [Government Point of Entry]." Once the Army posted the full RFP on SAM.gov — the governmentwide point of entry — the law treated every prospective offeror as on notice of its contents. The missing menu selection, GAO reasoned, created "ambiguity rather than misrepresentation." The synopsis field was empty, not affirmatively wrong, and a diligent contractor could have opened the posted solicitation and read the FAR set-aside clauses spelling out the competition's terms. ProSource360's reliance on a filtered search, rather than the underlying document, did not excuse the late filing.
What It Means for Contractors
The decision is a pointed reminder that SAM.gov's search filters are a convenience, not a safe harbor. Contractors that build capture pipelines around keyword or set-aside filters can miss opportunities when an agency miscodes a posting — and GAO will not shift the consequences of that gap onto the government. Constructive notice runs from the moment a solicitation hits the Government Point of Entry, so the posted document, not the metadata wrapped around it, defines what a contractor is presumed to know. GAO has applied that principle for years, and the ProSource360 decision extends it squarely to the failure of a search filter: the tool a contractor picks to find work does not narrow the universe of what the law says it should have found.
That lesson lands hardest on incumbents and their teaming partners. ProSource360 had every incentive to track the follow-on to work its joint venture was already performing, yet it still relied on a filtered search that a single blank field defeated. Companies chasing recompetes should monitor the specific solicitation number, the contracting office, and the underlying requirement directly, rather than trusting that a set-aside filter will always catch a known follow-on.
The timing rule is equally unforgiving. Anything wrong or ambiguous on the face of a solicitation — a coding error, a questionable form choice, a defective evaluation scheme — must be protested before proposals are due. Waiting until after award, or until a partner flags the opportunity, forfeits the argument no matter how meritorious. Here, ProSource360's complaint about the solicitation form may have had substance, but GAO never reached it because the clock had already run out.
Finally, the ruling draws a sharp line between an agency error and a viable protest ground. The Army's contract specialist did make a mistake, and GAO said as much. But an internal slip that produces ambiguity, rather than an affirmative misrepresentation that actively misdirects offerors, does not toll GAO's deadlines. Contractors that spot a blank or inconsistent SAM.gov field should treat it as a prompt to open and read the full solicitation at once — and, if something in that document looks improper, to protest before the proposal deadline rather than after. The filter that fails you will not stop the clock; only a timely filing does that.
