HHS Sole-Source Anthropic Award Raises Contracting Questions

What happened

The US Department of Health and Human Services (HHS) has made a sole-source award to Anthropic, the AI company, to keep certain services running after its existing OneGov agreement expires. According to the agency, the award would continue services it describes as vital for six months beyond that expiry date. Contracting experts have questioned whether a sole-source approach is justified for the work, according to FedScoop, which first reported the story.

The central tension is between operational continuity and competitive procurement. The agency's position is that the services are essential and need to continue without interruption. Critics of the award are focused on the justification for not running a competitive process, a question that remains open in the reporting.

The available coverage does not set out the full scope of the services, the contract value or the detailed rationale HHS has given for the sole-source route. Those details will determine how much weight the award carries in the wider debate.

Why it matters

For leaders in government and regulated services, this case shows how quickly AI tools can move from pilot to dependency. Once a service is described as vital, the practical question becomes how to maintain it through a contract transition without locking in one provider or weakening the oversight that public bodies are expected to apply. The award also highlights a procurement gap: AI capabilities are changing quickly, but the contracting routes used to buy them are often slower and less flexible than the technology.

For digital transformation teams more broadly, the lesson is about planning for continuity. Organisations that rely on a single AI supplier need clear exit terms, documented service dependencies and a defined path to re-procure. Without these, a contract expiry can turn into an emergency decision, which is where sole-source justifications tend to attract scrutiny.

The Renascence take

The headline question here is about contracting, but the experience question sits underneath it: what happens to the people who depend on these services when the contract changes hands. Most readers will focus on the procurement debate and miss that continuity of service is itself a customer experience outcome, for citizens and for the staff who run the tools every day. A six-month bridge is a service-design decision as much as a legal one, and it should be designed with users in mind.

Treat every AI dependency as a service that customers will notice when it breaks, not just a line item in a contract. Map who relies on the tool, what fails if it stops, and how long each group can cope without it before you commit to a provider. Build your transition plan around those answers, and run your competitive process before you are forced to. The operators who avoid emergency sole-source awards are the ones who designed for the exit before they needed one.