Financial-aid work is federal work: every decision has a rule, a citation, and an auditor who may ask. Eli takes on the workflows your office already runs, FAFSA fraud and identity review, SAP, professional judgment, R2T4, and verification, and prepares each one the way an aid office needs: cited, logged, and routed to your staff when judgment is required. Eli resolves more of the repeatable work and keeps institutional decisions with the office.
Exception work is the bottleneck offices can't hire their way out of.
The FUTURE Act IRS data exchange (FA-DDX, live 2024–25) now imports most FAFSA tax data and treats it as verified, so the bulk of routine income verification is gone. What remains is stubbornly manual, and it is the work Eli takes on:
Incumbents (Ellucian/StudentForms, Inceptia, ProVerify) mostly collect & route documents to humans. Eli works the whole exception queue, with a person on every judgment call.
Supported compliance calculations rest on unit-tested engines keyed to versioned rules: the $25 correction trigger and all-or-nothing submission, IRS "Per Computer" precedence, the Student Aid Index recomputation, the SAP standards (34 CFR 668.34), the R2T4 return order (668.22), and loan proration and caps. The demo labels directional SAI/Pell previews separately from final federal-table results and stops unsupported cases for review.
Models handle bounded extraction, classification, summaries, explanations, and drafts within typed tasks. Every extracted value carries a source and confidence; supported compliance calculations remain in tested, versioned code, with staff review where policy or judgment is required.
Identity rejects, V4/V5 outcomes, conflicts, SAP and PJ decisions, R2T4, and anything low-confidence route to a reviewer with a full, replayable audit trail. Eli does the legwork and drafts the decision; a person owns the judgment. The current demo only stages simulated or file-based action. Any production SIS or federal-system write requires a scoped integration and named authorization.
Workflow and reviewer actions land in a replayable record: what Eli read, why it recommended what it did, the governing rule, and the person who made the call. Here is one case, start to finish.
Every aid workflow runs the same ten stages, and the calculation sits in the middle. A calculated answer is only the midpoint; a case closes when the posting is acknowledged, the student is told, and the money ties out. Eli tracks each case across the whole spine.
Calculate is stage five of ten. The five stages after it are why a case stays open.
A professional-judgment case: Eli reads the documents, recomputes the Student Aid Index, shows its confidence and its reasoning, then waits for an administrator to decide.
Recompute SAI with documented income loss, then route for a professional-judgment decision.
Eli grades itself against a labeled corpus of known-truth documents. Most recent run (2026-06-09, 21 synthetic fixtures, 52 fields):
The live demo runs on 100% synthetic data across three institution types. Sign in as "Eli Operations" to see the full cross-institution picture.
Try a demo100% synthetic data. No real student, IRS, or FAFSA records. FERPA role, FTI scope, and Title IV third-party-servicer status depend on the contracted work and require institution and counsel review.