All work

Case studyUniversity of Washington2026

Every Budget, Built Once: Human-in-the-Loop AI for Grant Budgeting

TL;DR

In UW's research budgeting system, the AI does the copying and a grant manager confirms every value.

  • Put AI only on the in-between work inside UW's research admin system, gated by an explicit AI vs. Human boundary
  • Redesigned the workflow: embedded the budget worksheet where grant managers already work
  • Projected 75–150 hrs per grant manager per year (3,000+ org-wide), a 25–33% workload cut
  • Every AI-filled value carries its confidence and source; rates and math run on fixed rules, not AI guesses
  • Transferable to teams shipping AI into high-stakes expert workflows where errors are expensive
Role
Product manager and UX research lead
Team
4 people: me, a UX researcher and 2 designers
Timeline
6 months, January to June 2026
Sponsor
UW Office of Research Information Services, which owns SAGE, through my master's capstone
Research
6 contextual inquiries across 6 departments
Tested
Moderated usability sessions with grant managers
Projected
25 to 33% less workload, or 75 to 150 hours a year per grant manager

01The problem

Grant managers built every budget twice.

A UW grant manager carries about 50 active awards, and 75 or more at peak. Each budget is built once in Excel and again by hand in SAGE, across 8 or more disconnected systems: about 2 to 3 hours of copying per award before the judgment work begins.

I ran 6 contextual inquiries with grant managers in 6 departments and watched the real work: which systems they opened, how many tabs stayed up, where they copied and pasted. All 6 used Excel as a scratch space, and 5 looked up rates by hand across scattered sources.

The scattered sources a grant manager juggles per award: file folders, an Excel budget, the Notice of Award PDF, and UW rate websites
8 or more surfaces per award: folders, the Excel budget, the award letter and UW rate sites, each re-keyed by hand.

02What I decided

SAGE became the place the budget is built.

UW treated SAGE as a system of record, where finished budgets are stored and checked. We made it a system of work: the worksheet moved inside SAGE, in the Excel layout grant managers already knew, and the AI took only the work in between. Then I set where the AI leads, assists and refuses.

  1. 1

    AI leads the routine work

    It reads the award letter and the rate sites, fills budget lines into SAGE and flags mismatches, each linked to its source.

  2. 2

    AI assists, and the grant manager decides

    Every AI-filled value is reviewed, then accepted or edited, before it counts.

  3. 3

    AI refuses anything that carries accountability

    The final submission, conflict-of-interest sign-off and effort certification stay with a person, always.

03How it works

Built, checked and submitted in one workspace.

The AI fills each line with its source and its confidence. Rates and the dollar and percent math run on fixed rules, never on the AI. Mismatches with the award are resolved in a separate reconciliation step, and every fix is previewed before it saves.

INSIDE SAGEone workspace, in the Excel layout grant managers knowSOURCESAward letterthe funder's PDFUW rate sites5 to 6 sourcesWorkdaysalaries and effortAI fills budget linessource and confidence on eachFixed rules do the mathrates, dollars and percentsGrant manager reviewsaccepts or edits each valueAI flags mismatchesand suggests each fixGrant manager confirmsevery fix previewed firstSubmit and sign-offa person only, alwaysthen reconcile against the award

Microsoft HAX, Google PAIR and the University of Idaho's AI4RA framework became concrete parts of the screen: a confidence chip and a source on every value, math that opens on a click, and a preview before anything saves.

The prototype's reconciliation view: a budget worksheet with a rounding mismatch explained in a side panel, and a suggested fix to apply or adjust by hand
Reconciliation in the prototype: a mismatch explained, with a suggested fix to preview and confirm.

04Looking back

Define where AI belongs before designing where it goes.

I took the sponsor's mandate, automate award setup, as the starting point and narrowed it afterwards, through the six inquiries, to the finding that grant managers build every budget twice. The narrowing was right, and the order was not. Next time I would first map where AI fits the existing workflow and why it adds value there, then decide what to build.

More work

Sign-in and authorization for 60+ financial institutions, a palm-vein ID for 14 airports, and the builds in between.

All work