From the State Government edition of October 7, 2026
Indiana's workforce agency has run about half its documents through a Gemini-based plain-language tool, with 58 rewritten documents now public and human review of every draft
Indiana Department of Workforce Development (DWD), Office of Gov. Mike Braun; tool built with Resultant · State unemployment insurance (UI) claimant communications · Indiana statewide
- Publisher
- Indiana Department of Workforce Development
- Original publication
- 2026-10-07
- Source retrieved
- 2026-10-08
- Event date
- 2026-10-07
What happened
On Oct 7 DWD said its AI plain-language tool, built on Google's Gemini model and configured for DWD over several rounds of testing, has processed about 50% of its documents, and 58 rewritten documents are now in public use. Staff generate a first revision with the tool and every document goes through human review for accuracy, meaning and compliance before publication. The first phase covers high-volume UI materials, including notices generated by the Uplink system, some of which have more than 100 versions depending on a claimant's situation. DWD is also moving decisions, benefit amounts, deadlines and next steps to more prominent places and adding plain question headings such as 'What if I disagree?' for appeals. DWD says the changes are expected to reduce avoidable calls, filing errors and unnecessary appeals and that it plans to track those outcomes, but it reports no results yet. An April 2026 DWD post said the tool was developed with Resultant, that DWD has 750 distinct documents, and estimated manual conversion at 13 years versus about two years with AI.
Why it matters
A concrete, narrow state use of generative AI on a high-stakes public channel: legal notices that tell residents about benefits decisions and appeal rights. It shows the drafting-plus-human-review model at production scale and gives a baseline (750 documents, 13-year manual estimate) against which progress can be checked.
Evidence and measured results
Opened DWD's Oct 7 newsroom post (article:published_time 2026-10-07) and its April 6, 2026 post on the same tool (curl, BeautifulSoup). WBIW republished the Oct 7 release text. Compared with an archived Nevada Taxation NASCIO entry on AI plain-language notices for context only.
Limitations and uncertainty
Agency press release with no independent check. '50% of its documents' has no stated denominator; if it refers to the 750 documents in the April post, most processed documents haven't been published yet (58 are public). The 13-year versus two-year estimate is a projection, not a measurement. No readability scores, call volumes, error rates or appeal data are given.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-07; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Benefits notices written in legal language drive confusion, calls and avoidable appeals, and rewriting hundreds of templates by hand would take years.
- Stakeholders
- UI operations chief
- Agency general counsel
- Agency communications and content staff
- State CIO or IT office for the UI system
- Governor's efficiency office
- Discovery questions
- How many distinct notice templates and variants do you have?
- Who must approve rewritten legal notices?
- Do you have baseline call, filing-error and appeal data by notice type?
- Can rewritten text be loaded into your UI system's templates without code changes?
- Value hypothesis
- AI-drafted plain-language templates with legal review could shorten a multi-year rewrite, if review capacity keeps up.
- Potential engagement
- A pilot rewriting one notice family with baseline and follow-up measures of calls and appeals.
- Unsupported claims
- That Indiana's rewrites reduced calls, errors or appeals: none reported yet
- That the 13-year to two-year estimate has been achieved
- That AI output is accurate without human review
Pre-sales engineering
Role takeaway
- Fit
- Fits agencies with large libraries of templated legal notices and a separate review step.
- Architecture and integration
- Generate drafts outside the case system, then load approved text into the UI system's conditional templates with version control.
- Prerequisites
- Inventory of templates and their conditional variants
- Plain-language style guide
- Legal review capacity
- Constraints
- Notices carry legal rights and deadlines, so wording must stay legally accurate
- Template systems may need changes to support new layouts
- Translation depends on separate services
- Security
- Keep claimant records out of the drafting step and confirm model data terms.
- Proof of value
- Readability scores before and after for a sample of notices
- Reviewer correction rate on AI drafts
- Call and appeal counts for a rewritten notice versus its old version
Delivery
Role takeaway
- Work
- Run a phased rewrite of notice families with AI drafting, human review and template loading.
- Dependencies
- Legal and policy reviewers
- UI system template access
- Baseline service data
- Ownership
- UI operations, with general counsel approving legal content.
- Skills and adoption
- Content staff need plain-language and prompt skills; reviewers need a shared checklist.
- Governance checkpoints
- Legal sign-off for each document family
- Accessibility check before publication
- Outcome review after each phase
- Acceptance criteria
- Proposed: each published notice has a recorded reviewer approval
- Proposed: readability target met for each rewritten notice
- Proposed: calls and appeals tracked for six months after release
- Risks
- AI rewording changes legal meaning
- Review becomes the bottleneck
- Outcome tracking never gets set up
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
A configured Gemini model produces draft rewrites outside the case system; reviewed text is then loaded back as templates, including templates generated by the Uplink UI system. Because a single notice can have 100+ variants, the template logic (which paragraphs appear for which claimant) matters as much as the rewritten wording.
Governance
Who approves, reviews and stays accountable for outcomes?
Every rewritten document gets human review for accuracy, meaning and compliance before release, which matters because UI notices carry legal rights and appeal deadlines. DWD doesn't say who reviews (legal staff, UI policy staff), how disagreements are resolved, or whether review findings are recorded. Outcome tracking is planned, not reported.
Security and privacy
What data, permissions and controls need testing?
Limited relevance: the tool rewrites document templates, not individual claimant files, per the release. DWD doesn't say whether any claimant data reaches the model or what data terms apply to the Gemini configuration.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Plain language and clearer layout aim to make UI decisions easier to understand, and DWD says simpler English text could support future Spanish and other translations. The work keeps staff as editors and reviewers rather than replacing them; staffing effects aren't discussed.
Procurement
What should contracts, pricing and exit terms secure?
The tool was built with a consulting firm (Resultant) on a commercial model (Gemini). Agencies buying similar work should expect to pay for configuration and testing rounds, and should require the vendor to support measurement of downstream outcomes, which DWD hasn't yet reported.
Operating model
Which teams own the service once it runs?
The UI operations team owns the rewrite-and-review cycle in phases: UI determinations first, then the claimant handbook, employer materials and web content. That phased, document-family approach is easy to copy but needs a content owner for each family.
Publication history
- 2026-10-07State Government · Issue 322 resources
Stable resource ID: indiana-dwd-gemini-plain-language-ui-notices-20261007