How one desk carries the work from a student's first question to the audit file, read over the demo queue. Every link opens the live product.
You are reading over the full synthetic demo caseload, no sign-in needed. Links into the product offer a one-click demo desk first.
Every queue shares the same rules engine, audit log, and approval gate. Each piece of work has a rule behind it and an auditor who may ask, so Eli works it to the decision, cites the rule, and a person signs.
The demo desk holds 118 open cases across 6 kinds of work right now.
A synthetic case from the demo queue, worked from the first document to the exported record. Every queue above runs the same way.
Simone BarrowProfessional Judgment · Whitmore College · day 103Open the case →Every figure Eli uses carries its source and a confidence. It reconciles what a document says against what was reported and names any disagreement, whether the work is a verification, a withdrawal, an appeal, or a loan adjustment. Every recommendation cites the FSA Handbook or CFR section behind it. Open the case for the full trace.
The model never decides a dollar figure or a determination. Identity, conflicts, SAP and PJ decisions, R2T4, and anything low-confidence go to a person, who approves or overrides on the same screen. Nothing reaches your SIS or FPS without a name on it.
The case history logs what Eli extracted and why, every reconciliation, every reviewer decision, and the regulatory basis. Each case exports as an audit package with citations and the retention date. The demo's FPS tracker is simulated; pilot output is file-based and submits no federal correction.
Scenario estimates: configured baseline minutes and loaded hourly rates applied to 174 synthetic exception cases in scope. Modeled. No customer has measured them yet.
The demo runs on synthetic data. The security page separates implemented controls from production gaps: no raw FTI, the intended FERPA role, scope-dependent TPS status, and the independent assurance still to come. A pilot starts with validated file exchange. Live connectors are separate work.
Can a financial aid office take a real de-identified case or population, let Eli do the routine work, make the required human decision, complete the authoritative downstream action, and hand an auditor the case record, without relying on the memory of the one person who knows the process?
If yes, the module fits how the office works. Every Eli surface has to answer yes.
Bring the work that hurts most this term, and we'll walk it through the desk with you.