GAO Sustain Tracker

The GovCIO loss on the GSA TIS recompete is the kind of outcome that should change how mid-market IT services primes structure their next federal pursuit. The teaching moment isn't the protest itself — it's that an incumbent with active performance still got displaced when the source-selection record didn't defend the agency's evaluation against a credible challenge. If your capture playbook assumes incumbency is a moat, this decision is the counter-evidence.

Two specific traps to watch for in your next IT services recompete: past-performance relevance gaps (citing prior work the agency can't link to the SOW's actual scope is a known sustain pathway), and thin source-selection rationale (when the SSEB consensus narrative doesn't show why the offeror's proposal beat the others on the stated factors, GAO will sustain even on a generally well-run procurement). Both are fixable in your proposal — but only if you've read enough sustained decisions to know what evaluators trip on.

Why this matters for your capture timing: sustained protests at GAO are rare (historically ~10–15% of decisions). When an agency reopens an acquisition after a sustain, the do-over evaluation typically runs 60–120 days behind the original schedule, sometimes longer if the corrective action requires a re-solicit. That's your window. If you were originally a sub or a no-bid, a sustain is one of the few honest second chances the federal market gives you. Read the decision, map the agency's identified errors to your own past-performance citations, and have a revised proposal ready before the corrective-action announcement hits SAM.