The Court of Federal Claims has confirmed that a contractor who paraphrases a required certification, rather than submitting the signed form the solicitation demands, has no path to award. In Revelations Counseling & Consulting, LLC v. United States, 180 Fed. Cl. 721 (2026), the court denied the protester's motion for judgment on the administrative record and granted the government's cross-motion, sustaining the Department of Veterans Affairs' decision to reject a proposal that lacked the signed VAAR 852.219-75 Certificate of Compliance for limitations on subcontracting. The ruling, reported by SmallGovCon on June 30, 2026, is a sharp reminder that mandatory certification language is not a box to be summarized in the contractor's own words.
Background
The VA issued its solicitation for call-center staffing on August 27, 2025, setting the work aside for service-disabled veteran-owned small businesses. Among the solicitation's requirements, offerors had to complete and sign the VAAR 852.219-75 Certificate of Compliance, the VA's mechanism for enforcing the limitation on subcontracting on set-aside services work.
That clause carries real substance. For services set-asides, VAAR 852.219-75 requires the awardee to certify that it will not pay more than 50 percent of the amount it receives from the government to firms that are not listed as verified SDVOSBs or veteran-owned small businesses in the VA's VIP database. In other words, at least half of the government's payment must stay with the veteran-owned prime and similarly qualified veteran-owned subcontractors. The certificate is how the VA locks that commitment in at proposal time rather than discovering a violation during performance.
Revelations Counseling & Consulting submitted its proposal on September 15, 2025. Instead of completing and signing the required certificate, the company inserted its own paraphrased language stating that it would comply with the limitation on subcontracting. The proposal omitted the authorization clause and the signature the form called for. The VA rejected the proposal as non-compliant and declined to evaluate it any further.
Key Details
Before the Court of Federal Claims, Revelations argued that its substitute language conveyed the same commitment the certificate would have, and that a signature appearing elsewhere in its proposal should be read to cover the certification. The court was unpersuaded on both points.
The court held that mandatory minimum requirements are "per se material," meaning a solicitation term phrased as a hard requirement does not become optional simply because a contractor believes it has satisfied the underlying intent another way. The certificate was a pass/fail submission requirement, and the failure to provide it in the required form was enough, on its own, to render the proposal ineligible.
The court also rejected the argument that the solicitation was ambiguous about what offerors had to submit. As SmallGovCon reported, the court found the solicitation "could [not] have made it any clearer" that offerors had to submit the formal certification. There was no gap for the contractor to fill with its own interpretation.
Finally, the court dismissed the idea that a signature located elsewhere in the proposal cured the defect. A signature attached to a different document does not authenticate a certificate that was never completed. Because the certificate itself was absent, there was nothing for the stray signature to validate. With the submission requirement unmet, the VA's rejection without further evaluation was reasonable, and the protest failed.
What It Means for Contractors
The lesson here is narrow but unforgiving: when a solicitation directs offerors to complete and sign a specific certificate, submit that certificate, filled out and signed, exactly as written. Do not translate it into your own compliance narrative. Contracting officers are entitled to treat a missing mandatory certificate as a fatal omission, and the Court of Federal Claims will back them when the requirement is clearly stated.
For SDVOSBs and VOSBs pursuing VA set-asides, VAAR 852.219-75 deserves particular attention because it ties directly to the limitation on subcontracting, one of the most heavily policed rules in the veteran-owned program. Building a proposal checklist that flags every required certificate, representation, and authorization clause, and confirming each is present and signed before submission, is cheap insurance against losing an otherwise competitive bid on a paperwork gap.
The reasoning is not unique to the VA. Across agencies, the Court of Federal Claims and GAO have repeatedly treated clearly worded, mandatory submission requirements as material terms that cannot be waived for one offeror without treating others unfairly. A strong technical approach and sharp pricing carry no weight if the proposal never clears the pass/fail gate. Contractors should also resist the temptation to assume that a signature block on the cover letter, the price schedule, or the SF 1449 stretches to cover every attestation buried in the solicitation. Each required certification stands on its own, and the safest practice is to sign each one where the form provides for it.
Small businesses without dedicated proposal compliance staff are the most exposed to this failure mode, because the substantive commitment, keeping at least half the contract value with qualified veteran-owned firms, may be one the company fully intends to honor. Intent is not the issue. The court drew a bright line between meaning to comply and documenting compliance in the required form, and only the second one keeps a proposal alive. A final read of the solicitation's instructions and evaluation criteria, cross-checked against every submitted attachment, is the step that would have saved this bid.
