Executive Order 14426 gives the Secretary of War and the Secretary of Veterans Affairs 180 days to create and deploy artificial intelligence digital tools that carry veterans' benefit applications through a single source

What the order actually says about artificial intelligence

One subparagraph carries the whole of it. Section 2(a)(ii) directs the Secretary of War and the Secretary of Veterans Affairs, within 180 days of the date of the order, to "create and deploy new digital tools using artificial intelligence and other emerging capabilities to streamline veterans' applications for and access to benefits earned through military service in a comprehensive single source that includes job training and opportunities offered by the Department of Labor".

Two verbs are doing the work: create and deploy. The order does not ask for a pilot, a strategy or an assessment. It also does not describe the tools, name a model class, set an accuracy standard, require human review of any output, or say what the tools may decide as against what they may only assist with.

That silence is worth naming precisely, because it is the sort of gap a reader fills in without noticing. The order is binding on the two secretaries as of 8 September 2026, and on its face it fixes a delivery date and a scope, not a control regime.

Where the statutory guardrails actually sit

Section 2(a)(i), the records sharing subparagraph, ends with an express consistency clause. The updated information technology systems, policy guidance and memoranda are to be established "consistent with 38 U.S.C. 5103A, 38 U.S.C. 8111, 38 U.S.C. 7332(e), 5 U.S.C. 552a, and any other applicable statutes". The order does not say what those provisions contain, and we did not open them.

Section 2(a)(ii), the artificial intelligence subparagraph, carries no such list. It ends at the Department of Labor clause and stops.

We are not saying the four statutes stop applying to the tools. They apply because they are statutes, and section 4(b) separately provides that the order "shall be implemented consistent with applicable law". What we are pointing at is a drafting fact with a practical consequence: the specific naming of the sensitive records regimes is attached to the systems build, not to the artificial intelligence build, even though both subparagraphs run on the same 180 day clock and the second one plainly reaches the same category of data.

For anyone drafting the implementation memoranda, that is the sentence to write rather than assume. The order will not supply it.

Three clocks, and only one of them is about AI

Section 2(a)(iii) is the fastest. Within 30 days, and at all times thereafter, all current service member Official Military Personnel Files, health records and Service Treatment Records are to be shared by the Department of War with the Department of Veterans Affairs immediately when a service member is discharged or released.

Section 2(b) runs 120 days. Within that period the two secretaries, in consultation with HHS including its Office of the National Coordinator for Health Information Technology and with OMB including the Federal Chief Information Officer and the Administrator for Federal Procurement Policy, are to review and modify existing information technology contracts, to the extent consistent with law and federal procurement policy, including by adding an interoperability requirement. The same subparagraph directs that all future contracts for medical and personnel IT systems and software include that requirement.

Section 2(a)(i), section 2(a)(ii) and section 3 all run 180 days. The order states its deadlines only in days from the date of the order. Counting forward from 8 September 2026 puts the 30 day date on or about 8 October 2026, the 120 day date on or about 6 January 2027, and the 180 day date on or about 7 March 2027. That arithmetic is ours; the order gives no calendar dates and we do not attribute these to it.

What this means for contractors, and what it does not

The interoperability duty at section 2(b) runs on the secretaries, not on suppliers. It tells the agencies to review and modify their own contracts and to include the requirement in future ones. A vendor acquires nothing from the order itself; it acquires a contract term if and when a contracting officer writes one.

Section 4(c) closes the door on the other reading. The order "is not intended to, and does not, create any right or benefit, substantive or procedural, enforceable at law or in equity by any party against the United States, its departments, agencies, or entities, its officers, employees, or agents, or any other person". A veteran, a veterans service organisation and a losing bidder are all on the wrong side of that clause.

Section 4(b) adds the funding caveat that turns a deadline into a conditional one. Implementation is subject to the availability of appropriations. The order also assigns its own publication costs to the Department of Veterans Affairs, at section 4(d), which is a small detail that tells you which agency the drafters treated as the owner.

The practical exposure for suppliers is therefore forward looking and contractual. If you hold or are bidding on a Department of War or Department of Veterans Affairs medical or personnel records system, the question to put to your contracting officer now is whether an interoperability clause is coming and in what words.

What we did not verify

What we opened: the full text of Executive Order 14426 as published in the Federal Register, retrieved from the Government Publishing Office at the FR-2026-09-11 package and read end to end, including sections 1 through 4 and the signature and filing block. The document caption reads "Executive Order 14426 of September 8, 2026" and the filing line reads "Filed 9-10-26; 11:15 am".

What we did not open: 38 U.S.C. 5103A, 38 U.S.C. 8111, 38 U.S.C. 7332(e), 5 U.S.C. 552a, 10 U.S.C. 1142 to 1144 and 38 U.S.C. 4113 and 4215, the America's Talent Strategy document, the Department of War's Project Patriot Pipeline, any implementing memorandum, and Executive Order 14427 published in the same Federal Register part. We therefore describe those statutes only as the order cites them, and we state nothing about what any of them require.

What we refuse to claim: we do not say the order imposes any duty on a private party, because section 4(c) forecloses it. We do not say the order regulates artificial intelligence, because it sets no standard, no accuracy threshold, no human review requirement and no transparency duty. We do not say the statutory consistency clause was deliberately omitted from section 2(a)(ii); we report only that it is present in one subparagraph and absent from the other, and the reading we draw from that is marked as ours. We do not treat the 180 day date as fixed, because section 4(b) conditions implementation on appropriations.

Informational analysis for working professionals, not legal advice. Confirm how any rule applies to your situation with qualified counsel.

Related briefings

• The GSA AI clause and OMB M-25-22 flowdowns for federal contractors
• OMB M-26-04 on unbiased AI in federal procurement
• Executive Order 14421 on the bulk power system and AI data centre demand
• North America AI regulation tracker
• AI Regulation News hub