Separate the direction from the finished requirement
Executive Order N-5-26 directs DGS and CDT to submit recommendations within 120 days for certifications that may be incorporated into contracting, consistent with existing procurement law. It addresses safeguards concerning illegal content, harmful bias and civil rights. It also directs related work on contractor responsibility and watermarking guidance for certain AI-generated or significantly manipulated media.
The signed order is dated March 30. A department summary page lists March 20; the signed instrument is the source used here. A recommendation deadline is not proof that a completed certification took effect on that date. A vendor must read the applicable solicitation, contract and issued guidance to determine its actual obligations.
Understand what purchasing power can—and cannot—do
A state can use its purchasing process to specify what it needs from a service and what evidence a contractor must provide within its legal authority. That makes procurement an important route for operational AI governance even while broader regulation remains debated.
It does not follow that procurement conditions are immune from federal preemption or other legal challenges. The distinction between government as a buyer and government as a regulator can matter, but outcomes depend on the specific law and measure. Counsel needs to assess the actual condition, not just the procurement label attached to it.
The practical point does not require that legal prediction: officials already writing specifications can make permitted requirements clearer and more testable. They should do so with counsel and technical reviewers, rather than assume a label such as certification settles the legal or operational question.
Build one evidence base and map it to each buyer
For vendors, differing state terms can create repeated evidence work. A reusable internal record should identify the product and version, intended uses, evaluation methods, known limitations, security controls, incident handling and relevant provenance capabilities. Map those records to each actual solicitation rather than assuming all fifty states use the same definitions—or all have adopted different AI regimes.
An evidence base should also make gaps visible. If an evaluation does not cover the buyer's population or workflow, do not present it as though it does. If a product depends on another provider's model, identify which claims the supplier can substantiate and which changes require reassessment.
This turns compliance planning into product governance. Sales, engineering and legal teams need the same account of what the system does and what the company is promising. An attestation that cannot be supported consistently across those teams is a delivery risk, not merely a paperwork problem.
Give the state capacity to evaluate the claim
A certification regime needs people who can distinguish a relevant test from a persuasive document. That capability can come from trained agency staff, shared technical resources or qualified independent support. The agency still needs an official responsible for deciding whether the evidence is sufficient for its use.
Review should continue after award. A model update, new data source or changed workflow can alter the basis for an earlier assurance. Contract terms should identify notification, access to evidence, revalidation and corrective action. The order itself does not establish the precise terms for every contract; these are implementation considerations for buyers developing them.
A sequence for a useful AI solicitation
- Define the use and affected decisions. Explain the task, users, data and actions the system may support. Avoid requesting generic responsible AI without operational context.
- Specify the evidence. Identify representative testing, security documentation, accessibility, privacy and error analysis appropriate to that use.
- Name the reviewer and acceptance decision. Establish who evaluates each category and how unresolved concerns reach an accountable official.
- Control material changes. Require notification and reassessment when model, data, permissions or delivery conditions change.
- Make remedies practical. Define correction, suspension, transition assistance and access to necessary records within applicable procurement law.
Purchasing language matters because it survives beyond a policy announcement. Its value depends on whether the agency can use it to decide, verify and respond throughout the service's life.
Sources and further reading
- Signed California Executive Order N-5-26 — controlling source for the order's date and directions.
- CDT executive-order index — department overview; its date differs from the signed document.
Spartan X connects AI consulting with engineering and program execution, helping turn a policy intention into requirements a team can evaluate, deliver and maintain. A stronger purchase order starts with that understanding of the work.
