Every withdrawal, calculated by 9 a.m.
NineSweep works your withdrawal list overnight — read-only — finds the date your records actually support, runs the Return of Title IV calculation against it, and flags the ones where the date doesn't hold up. Every row cites its evidence, and the 45-day clock is on the table.
Not ready to share access? Send your R2T4 procedure — no student records — and see the playbook it would run.
We do the legwork. You make the call.
Assign the queue at close. Read verdicts with your coffee.
You hand over the withdrawals
This week's official withdrawals, the all-F list at term end, and the ones already sitting on the 45-day clock.
It finds the date and runs the numbers
Signs in read-only, reads the registrar's record, the course activity, and the grade roster, then calculates earned aid against the period your records support.
Verdicts, with receipts
Calculated, no return due, or date conflict — each row citing the withdrawal record, the activity log, and the calculation behind it.
9:00 AMYour counselors make the determinations.
Trust is the product.
Read-only by design
Nothing in your student system changes. NineSweep never packages, never disburses, never releases a hold. It gathers and judges; anything outgoing — a missing-document notice, a decision letter — is drafted for your counselor's signature, never sent.
Verdicts a reviewer can follow
No chatbot prose. Every recommendation is a row in a table, and every row cites the ISIR transaction and field, the document page, and the screen it was read from — the same trail a program review would ask you for.
Your policy, not ours
Your verification tolerance, your appeal standard, what your office counts as conflicting information. Say it once in plain English: NineSweep revises its playbook, re-decides the affected files, and versions the change.
Good. Teach it yours — in a sentence.
Your tolerances, your carve-outs, your definition of “worth a second look” — typed as feedback, kept forever, applied to every run after, and versioned so you can show an auditor when the rule changed. No tickets, no retraining projects. Watch:
| Student | Withdrawal | % earned | Return | Verdict |
|---|---|---|---|---|
| K. Boateng · UGgraded assignment submitted 10/02 | 10/02 | 41.8% | $2,318 | Calculated |
| M. Duarte · UG10/14 login · last graded work 09/22 | 10/14 | 56.0% | $1,140 | Calculated |
| L. Marin · UGpast the 60% point | 11/07 | 100% | $0 | No return due |
See it on your R2T4 procedure first — no student data
Send your withdrawal procedure and what your office accepts as academically related activity. You'll get back the playbook NineSweep would run against them, worked on synthetic withdrawals. No system access, no student records, no FERPA paperwork.
“NineSweep grew out of production agent automation inside a large public university's student-services operation — the same read-every-screen, judge-by-the-policy work an aid office does every packaging cycle. I build it, I run your pilot personally, and every verdict shows its work. If it can't earn your trust on your own files, it shouldn't have it.”
Apoorv Agarwal · Founder, NineSweep · Phoenix, AZ