Is AI deciding your VA claim? Here is what the public record shows so far.
- By Alec Morgan
- The Veteran Benefit Desk
- Published August 8, 2026
- ISSN 3144-0835
- https://doi.org/10.68077/vbd.ai-va-claims
Independent research; not peer reviewed. Corrections and version notes are published under our Corrections Policy.
VA's 2025 AI use case inventory, published in January 2026 and updated in April 2026, lists 367 individual AI use cases, several of which sit inside the disability claims pipeline. VA also states, on the record and under congressional questioning, that no automation makes or denies a disability compensation claim decision. This page assembles what is documented: the claims-related systems we identified in VA's published records, VA's own statements, the accuracy debate, the oversight proposals, and the records fights already underway. Every claim on this page links to a primary source or named reporting, and we will keep it current as the record grows.
Where automation sits in a claim's path
Compiled from the systems documented on this page. Automation works the front and back of the pipeline; under VA's stated policy, the decision itself belongs to a person.
Documents are digitized, classified, and routed to the right queue.
Federal records pulled, evidence assembled, summary documents generated for the processor.
Assesses whether records already on file can support a rating (ACE DBQ) instead of a new C&P exam.
A human claims processor decides. VA on the record: automation will not make or deny a disability compensation claim.
Error and fraud flags route files to further human review, not automatic cuts. VA says the DBQ fraud tool does not use AI.
What the record shows
VA discloses hundreds of AI systems, and a subset touches benefits claims
Federal agencies must publish an annual inventory of their AI use cases. VA's 2025 inventory, released in January 2026 and updated in April 2026, lists 367 individual AI use cases across health care, benefits, and operations. Inventory entries tied to claims work include Smart Claim Check, described as helping Veterans Service Representatives identify and resolve issues in extensive claim documentation before they become errors, and an earlier inventory described Claims Profile, which builds computable profiles from historical disability data so adjudicators can compare a new claim against prior decisions faster. These are decision support tools by VA's own description: they organize and flag, and a person acts on what they surface.
Automation runs the front of the pipeline: intake, sorting, evidence, and summaries
VA's claims modernization materials describe automated decision support that pulls federal records, assembles evidence, and generates summary documents for claims processors, and state plainly that it does not replace the need for claims processors to review and make decisions. VA points to this front-end work when it reports speed gains: the agency completed a record volume of claims in fiscal year 2025 and announced on April 15, 2026 that average completion time had fallen to 80.7 days, a 43 percent drop from 141.5 days, crediting automation, workflow changes, and records-access improvements as contributors. The same front-end automation was part of PACT Act processing: VA said in 2024 that automation tooling helped it approve its first million PACT Act claims.
VA's position on the record: automation will not make or deny a decision
In April 2026, VBA's Principal Deputy Under Secretary for Benefits told Congress that claims automation, quote, will not make any decisions and will not deny a claim, and that, quote, our people are making the decisions. That is the clearest on-record statement the agency has made, and it matches the written descriptions in the use case inventory and the claims modernization pages. It is a policy position, not a statutory requirement, which is exactly the gap lawmakers have started trying to close.
One boundary is already documented: in April 2026 the VA inspector general reported that a separate rules based automation for certain survivor benefit claims had processed some claims from start to finish with no human involvement. From a statistical sample of 160 automated decisions, projected to about 8,100 eligible decisions, OIG estimated that at least 8,000 decisions or notification letters had at least one legal or procedural deficiency, such as omitted favorable findings or incomplete evidence summaries, and that at least 2 percent contained errors with monetary impact, at least 2.7 million dollars in improper payments; the evidence supported the grant in most cases. OIG's public tracker shows recommendations 2 and 3 closed as implemented on July 8, 2026 and recommendation 1 still open. That system is not one of the AI tools described on this page, but it shows the line between assistance and adjudication is drawn by policy and program design, not by a technical barrier.
Two systems arrived in 2026 that veterans should know by name: AICES and the DBQ fraud tool
The Artificial Intelligence Claims Evaluation System, AICES, appears in a privacy impact assessment VA signed in April 2026. Per the assessment, AICES evaluates whether a disability claim is suitable for an Acceptable Clinical Evidence, or ACE, DBQ, meaning whether the claim can be rated from records already in the file instead of scheduling a new in-person C&P exam, and it uses AI, natural language processing, and OCR to fill out DBQs for qualifying cases and upload them into VA's benefits system. The assessment states the system processes personally identifiable information including name, Social Security number, and date of birth, and retains data in AWS GovCloud for up to one year after processing. One wording tension in the document is worth knowing: the assessment says AICES analyzes claims data, quote, to make benefit decisions, while also stating that the DBQs it produces, quote, enable the government employee to make benefit decisions. VA's broader position that people make final claims decisions comes from its testimony and policy statements, not from this assessment. What the assessment itself establishes is that the tool can materially shape the evidence placed before the human who decides, including whether an in-person exam happens at all.
Separately, VA is building a fraud screening tool for newly submitted Disability Benefits Questionnaires. The two systems should not be conflated: AICES is an AI system by VA's own description, while VA says the DBQ fraud tool is not. Initial reporting on March 9, 2026 described an automated screening tool; VA clarified the following week that the tool does not use artificial intelligence, relies on manual data entry and analysis, is forward-looking, flags new submissions for further human review rather than automatically reducing or denying benefits, and is not revisiting finalized claims. Disabled American Veterans publicly raised concerns about the plan, and private DBQ providers have tracked it closely.
The accuracy debate turns on one distinction: issue-level versus claim-level
While discussing claims automation at an April 2026 hearing, VBA cited a 93.95 percent 12-month issue-based accuracy rate. VA's published issue-level accuracy metric is a national claims-quality measure covering the individual medical issues inside compensation claims; it is not a separate measure of claims processed with AI or automation, and VA has not published a distinct accuracy rate for automation-assisted claims. Lawmakers pressed a second distinction at the same hearing: issue-level accuracy is not claim-level accuracy. A claim contains many issues, so a small per-issue error rate can still leave a meaningful share of claims with at least one error, and VA's published claim-level accuracy runs well below the issue-level figure.
In May 2026, two House lawmakers proposed amendments to the FY2027 VA funding bill that would add AI guardrails, including a proposal by Rep. Paul Gosar to bar AI from making a final disability claim determination. The proposals show congressional concern about preserving human decision making, though they had not been enacted as of this report's latest update. On the health care side, the VA inspector general's final national review, issued in June 2026, found limited coordination with VA's patient safety office and no AI-specific mechanism for identifying safety events involving generative AI clinical documentation, a caution that shapes how the benefits-side rollout is being watched.
Inside VA, generative AI is allowed, but only on authorized tools
VA's generative AI guidance turns on authorization: tools VA has authorized for sensitive data, such as VA GPT and Microsoft Copilot Chat, may be used with that data, and entering VA-sensitive data, including personally identifiable information, into AI services without the appropriate VA authorization, including public web-based chatbots, is prohibited. Staff remain responsible for verifying AI output before relying on it. That rule cuts both ways: it confirms generative AI is in day-to-day use inside the agency, and it sets a data-handling standard that veterans would be wise to apply to their own records.
What we found in VA's own FOIA logs
We review VA's monthly Freedom of Information Act logs as part of our records program. Two entries this year show the scrutiny building around automation and decision quality.
The watchdog probe. VA's May 2026 FOIA log records request 26-14634-F from American Oversight, a nonprofit government watchdog. It seeks VBA internal emails and Teams messages from June 2025 through March 2026 that pair a claims term such as benefits claim, appeal, error, quota, backlog, higher-level review, or wait time with an AI term such as artificial intelligence, AI, or LLM. A request's terms show what the requester sought; they do not establish that the conduct described occurred or that responsive records exist. The log entry lists FOIA exemptions (b)(5), which covers certain privileged inter- and intra-agency material, including deliberative process material, and (b)(6), which protects personal privacy; both could limit what is eventually disclosed. American Oversight typically posts released records in its public documents database, so if VA produces records, what those emails show about how AI is discussed inside claims processing is likely to become public. We are tracking the request and will analyze any release when it lands.
The quality-review request. The April 2026 log records a media request for the internal protocol VBA's quality and oversight staff use to review Higher-Level Review decision letters. It is not an AI request, but it points at the same underlying question: how the agency checks its own decisions during the fastest processing push in its history.
The documented timeline
If you have a claim pending
A person decides your compensation claim. Under VA's stated policy for disability compensation claims, automation prepares the file and a human claims processor makes the final call. Your rating decision identifies the office that decided it, and the decision carries the same weight and the same appeal rights however the file was assembled.
Automation can influence whether you get an exam. AICES is intended to assess whether your claim can be rated from existing records without a new C&P exam. If you believe the record understates your condition, submitting current medical evidence is one important way to strengthen it, alongside lay statements, service records, and nexus evidence, because that record is what any tool and any human reviewer will read.
Errors are appealable no matter what produced them. A decision that misstates your evidence can be challenged through a Higher-Level Review, a Supplemental Claim, or a Board appeal under VA's modernized review system. Automation changes none of those rights. Filing periods vary by review option, so follow the deadline stated in your decision letter.
Keep your records out of public chatbots. VA prohibits its own staff from putting sensitive data into public AI tools. Apply the same rule to your C-file, medical records, and Social Security number. If you use AI to help organize your thoughts or draft a lay statement, strip out the identifying details first.
Questions veterans are asking
Does AI decide VA disability claims?
Not for disability compensation claims, per VA's stated policy. VA states on the record that people, not automation, make final disability compensation claim decisions. In April 2026 testimony, VBA's Principal Deputy Under Secretary for Benefits said automation will not make any decisions and will not deny a claim. AI and automation are used to sort mail, classify claims, gather records, flag possible errors, and summarize evidence before a human claims processor decides. One documented boundary: a separate rules based automation for certain survivor benefit claims did process some decisions with no human involvement, which the VA inspector general reviewed in April 2026.
Can AI deny my VA claim?
VA says no: its stated policy is that automation will not deny a claim. That position is agency policy rather than a statutory requirement, which is why lawmakers proposed language in the FY2027 VA funding process to bar AI from making final disability determinations. Every decision carries the same appeal rights regardless of what tools touched the file.
What is AICES?
AICES is the Artificial Intelligence Claims Evaluation System. According to the privacy impact assessment VA signed in April 2026, it evaluates whether a disability claim is suitable for an Acceptable Clinical Evidence, or ACE, DBQ, meaning whether a claim can be rated from records already in the file instead of scheduling a new in-person exam, and it uses AI, natural language processing, and OCR to fill out DBQs for qualifying cases. The assessment states it processes claim information including name, Social Security number, and date of birth, and retains data in AWS GovCloud for up to one year after processing. VA's position that human employees make final claims decisions comes from its testimony and policy statements; the assessment itself describes a tool that shapes the evidence those employees decide on.
Is VA using AI to scan DBQs for fraud?
VA is building a fraud screening tool for newly submitted Disability Benefits Questionnaires, but VA says the tool does not use artificial intelligence. Initial reporting on March 9, 2026 described an automated screening tool; VA clarified the following week that the tool relies on manual data entry and analysis rather than AI, is forward-looking, flags new submissions for further human review rather than automatically reducing or denying benefits, and is not revisiting finalized claims. Disabled American Veterans publicly raised concerns about the plan.
Is it safe to put my claim documents into a public AI chatbot?
Treat that with the same caution VA applies to its own staff. VA's generative AI guidance turns on authorization: employees may use tools VA has authorized for sensitive data, such as VA GPT and Microsoft Copilot Chat, and may not enter VA-sensitive data, including personally identifiable information, into AI services that lack that authorization, which includes public consumer chatbots. A veteran's C-file, medical records, and Social Security number deserve the same protection. If you use AI to help draft a statement, keep identifying details out of the prompt.
Method, limits, and sources
Method. This page reports only what appears in primary VA documents, named congressional testimony, VA's published FOIA logs, and attributed journalism. Where VA's characterization is the only source, we say so. We reviewed VA's monthly FOIA logs for January through June 2026 directly as part of our records program.
Limits. The public record describes what these systems are supposed to do, not independent audits of what they do in production. Claim-level accuracy for automation-assisted decisions has not been published. The American Oversight records, the FY2027 guardrail language, and future inventory updates will each move this record, and this page will be updated when they do.
Request for comment. On August 9, 2026 we sent VA's Office of Public Affairs a written request for comment on the questions this page raises, with a response date of August 14. We followed up on August 19 and extended the response date to August 28. VA did not respond. The desk will add VA's response here if one arrives, and will note the date it came in.
Version history. Version 1.3, September 11, 2026: added the record of the desk's request for comment to VA public affairs and the fact that no response was received. Version 1.2, corrected September 10, 2026: the OIG survivor-automation passage now states that the findings come from a statistical sample of 160 decisions projected to about 8,100, and gives the recommendation status as recorded on the OIG tracker (recommendations 2 and 3 closed July 8, 2026; recommendation 1 open). Version 1.1, corrected and updated August 13, 2026, following an independent external review: the DBQ fraud tool answer now reflects VA's March 16, 2026 clarification that the tool does not use AI; the 93.95 percent figure is now described as VA's national issue-based accuracy measure rather than an automation-specific rate; statements about human decision making are scoped to disability compensation claims; the OIG survivor-automation description now includes the full deficiency findings and remediation status; and the congressional guardrail and health care oversight passages were updated to the current record. Version 1.0 published August 8, 2026.
Primary sources. VA AI use case inventory, VA generative AI guidance, AICES privacy impact assessment (PDF), VA OIG report 25-00153-47 on automated death benefit decisions (PDF), VA OIG final review of generative AI chat tools in clinical care (June 2026), VA press release on benefits processing (April 15, 2026), VA on modernizing the disability claims process, VA FOIA library and logs.
Reporting cited. GovCIO on the April 2026 testimony, Nextgov on the accuracy debate, Nextgov on the FY2027 guardrails, Stars and Stripes on the DBQ fraud tool (March 9), Stars and Stripes on VA's clarification (March 16), the DAV statement, Nextgov on PACT Act automation (2024). For how our own research program works, see the public FOIA log and data methodology.
Claim-by-claim source ledger
| Claim | Source | Accessed |
|---|---|---|
| AICES function, data handling, and the assessment's benefit-decisions wording | VA AICES privacy impact assessment (PDF) | August 2026 |
| VA position that people make claim decisions | April 2026 House VBA testimony, via GovCIO and Nextgov | August 2026 |
| AI use case count (367) and claims system descriptions | VA 2025 AI use case inventory, published January 2026 | August 2026 |
| DBQ fraud screening tool, VA's clarification that it does not use AI, and VA response | Stars and Stripes, March 9 and March 16, 2026; DAV statement | August 2026 |
| FOIA request 26-14634-F terms and listed exemptions | VA FOIA log, May 2026 | August 2026 |
| FY2027 AI guardrail amendments (Reps. Gosar and Walkinshaw) | House Rules Committee filings; Nextgov, May 2026 | August 2026 |
| FY2025 claims volume and the 80.7-day average completion time | VA press release, April 15, 2026 | August 2026 |
| Automation's role in the first million PACT Act approvals | Nextgov, May 2024 | August 2026 |
| Generative AI oversight gaps in clinical care | VA OIG final national review, June 2026 | August 2026 |
| HLR quality-review protocol FOIA request | VA FOIA log, April 2026 | August 2026 |
| Automated survivor benefit decisions without human involvement, error estimate | VA OIG report 25-00153-47, April 2026 (PDF) | August 2026 |
| Generative AI rules for VA staff | VA generative AI guidance | August 2026 |
This review is free to reference. Copy the citation below and link back so your readers can check every source themselves.