Eli
What we solveHow it worksWhy EliSecurityTrust center
Log in
Open the demo
Eli

The Financial Operations Desk for financial aid offices. Software, or our team working it with you. Staff keep every sign-off.

The front door

  • Forms and guided intake
  • The hotline
  • Chat
  • Front desk assistant

Casework & judgment

  • Professional judgment
  • SAP appeals
  • Verification of income
  • FAFSA fraud & V4/V5 identity

Money movement

  • R2T4 returns
  • Schedule of Reductions
  • Fiscal close

Reporting & assurance

  • Annual reporting
  • Assurance
  • Aid dashboard
What we solveHow it worksWhy EliSecurityTrust centerThe 5-minute proofThe 90-day pilotLog in to the demo
Email pat@tryeli.comSynthetic-data demo. No real student, IRS, or FAFSA records. © 2026 Eli.
90-day pilot

The 90-day pilot

Before any live pilot, Eli replays a school's historical cases with no live effect and compares its disposition to the office's. Every product gate has to pass. Procurement, security, contract, identity, and data access are separate gates. This run covers 183 synthetic cases (modeled pilot volume: 400).

It starts with a 45-minute workflow interview

Bring one workflow and one de-identified case. No data leaves your office for this meeting.

We walk the workflow the way your office runs it: seven questions in 45 minutes. By the end we reproduce a result you already know and show the defense file behind it. That earns data access.

  1. 1Trigger5 min

    What exact event, file, or report tells you there is work? Who notices first? What can be missed?

  2. 2Population and clock5 min

    How do you find every affected record? Which date starts which deadline? What report proves completeness?

  3. 3Tools5 min

    The real SIS screens, portals, spreadsheets, and federal sites. Which one is authoritative at each stage?

  4. 4Happy path10 min

    One real de-identified case, first event to final close: every click, handoff, wait, calculation, and message.

  5. 5Exceptions8 min

    The three cases that consume disproportionate time. What missing or conflicting fact stops the work? Who decides?

  6. 6Execution and reconciliation7 min

    What is posted or transmitted? How do you know it was accepted? Which financial and system records must tie?

  7. 7Audit test5 min

    A different staff member reconstructs the case. What evidence is hard to find? What relies on memory?

Shadow validation, historical
Synthetic product gates pass. External pilot gates remain.
92%
disposition agreement
Disposition agreement
Eli's disposition matches the office's historical decision
Pass
92%target ≥ 90%
Audit-packet completeness
Each case produces a program-review-ready package
Pass
97%target ≥ 95%
Critical compliance misses
A wrong dollar determination or a missed required action
Pass
0target 0
Staff-touch reduction
Share Eli cleared straight-through without a human touch
Pass
36%target ≥ 25%

What the shadow run found

Modeled on the cohort's per-case economics, no live effect

61h
staff-hours saved on the cohort
97%
cases with a complete audit packet
0
critical compliance misses
36%
cleared straight-through
The 90-day path
Phase 1
Week 0
Trust packet

Security review starts with the model card, data-handling controls, RLS, retention schedule, and the mode-boundary memo. The artifacts procurement and IT ask for.

Phase 2
Weeks 1-2
Data extract

A de-identified historical cohort (300 to 500 cases) loads into a scoped tenant. Identifiers are masked. The distribution that makes the queue realistic is kept.

Phase 3
Weeks 2-5
Historical shadow

Eli replays the cohort with no live effect. Every disposition is compared to the office's own decision. The gates below decide whether to advance.

Phase 4
Weeks 5-10
Live-assist (gated)

Starts only after the gates pass. Eli prepares real cases and your staff approve every call. Straight-through clearing stays off until the office says so.

Phase 5
Weeks 10+

What the pilot has to prove

Seven dimensions, agreed before any data moves and measured at exit

Population
Agreed up front

Inclusion and exclusion rules, with control totals

Evidence at exit

Your report counts and dollars match Eli's import

Correctness
Agreed up front

Golden cases and the acceptable tolerance

Evidence at exit

Every intermediate value and final result agree

Exceptions
Agreed up front

Named unsupported and ambiguous scenarios

Evidence at exit

Each routes to the right owner, with no false confidence

Workflow
Agreed up front

Required human gates and downstream states

Evidence at exit

Approval, exported action, response, and reconciliation on record

Efficiency
Agreed up front

Baseline touches and cycle time, with a target

Evidence at exit

Measured before and after on the same cohort

Defense

Shadow results, sample

Eli's disposition vs the office's historical decision (183 cases replayed)

CaseOffice didEli wouldAgreementAudit packet
Olivia LimRequest docsRoute to humandocumented diffcomplete
Dmitri CostaRoute to humanRoute to humanmatchcomplete
Kofi HernándezRoute to humanRoute to humanmatchcomplete
Fatima NoorRoute to humanRoute to humanmatchcomplete
Rosa Martinez
The pilot deliverable kit
MODEL-CARDModel cardWhat the AI does and does not decide; measured accuracy.›RETENTIONData handling & retentionFERPA, IRS Pub. 1075, RLS, the records-retention schedule.›AUDIT.PDFAudit package sampleThe program-review artifact, per case.›TRACE.JSONReasoning trace sampleEvery step Eli took, replayable.›INTEGRATIONSIntegration specThe SIS connector contract and de-identified roster path.›
The 5-minute proofSecurity & compliance
Managed ops

Optional. Eli's team works the queue on the same software. Your office keeps the sign-off.

Agreed up front

Required audit-packet contents

Evidence at exit

A blind reviewer reproduces the decision

Data boundary
Agreed up front

De-identification, retention, access, and deletion

Evidence at exit

A signed handling protocol and a purge report

DimensionAgreed up frontEvidence at exit
PopulationInclusion and exclusion rules, with control totalsYour report counts and dollars match Eli's import
CorrectnessGolden cases and the acceptable toleranceEvery intermediate value and final result agree
ExceptionsNamed unsupported and ambiguous scenariosEach routes to the right owner, with no false confidence
WorkflowRequired human gates and downstream statesApproval, exported action, response, and reconciliation on record
EfficiencyBaseline touches and cycle time, with a targetMeasured before and after on the same cohort
DefenseRequired audit-packet contentsA blind reviewer reproduces the decision
Data boundaryDe-identification, retention, access, and deletionA signed handling protocol and a purge report
Route to human
Route to human
match
complete
Marcus LeeCorrectRoute to humandocumented diffcomplete
Liang RomanoRoute to humanRoute to humanmatchcomplete
Bryce WhitakerClearRoute to humandocumented diffcomplete
Tyrone WilliamsRoute to humanRoute to humanmatchcomplete
Aisha BelloRoute to humanRoute to humanmatchcomplete
Nadia WashingtonRoute to humanRoute to humanmatchcomplete
Andrés CohenRoute to humanRoute to humanmatchcomplete
SOWDraft SOW & HECVAT response kitPrepared per school: scope, gates, mode-boundary memo, and security-questionnaire evidence.