For SAP committees & appeal reviewers

Every SAP appeal, committee-ready by 9 a.m.

NineSweep runs your progress standards overnight — read-only — pulls each student's GPA, pace, and timeframe, checks the appeal packet for the statement and academic plan your policy requires, and hands the committee a table it can work from. The decision stays with the committee.

Book a 20-minute demo

Not ready to share access? Send your SAP policy — no student records — and see the playbook it would run.

We do the legwork. You make the call.

How a Tuesday goes

Assign the queue at close. Read verdicts with your coffee.

5:41 PM

You hand over the stack

Term-end evaluation for the whole population, or just the appeals waiting on Thursday's committee.

2:17 AM

It reads every packet against your standard

Signs in read-only, pulls GPA, pace, and attempted credits, opens each appeal statement and academic plan, and measures them against the standard your policy actually sets.

8:47 AM

Verdicts, with receipts

Committee-ready, missing a document, or human review — each row citing the transcript, the statement, and the plan behind it.

9:00 AMYour counselors make the determinations.

Built for offices that get audited

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.

“But our policy reads it differently.”

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:

Thursday's committee · after your rulePlaybook v3
StudentGPA / paceAppeal packetVerdict
T. Nguyen · UGstatement + advisor plan1.72 / 58%CompleteCommittee-ready
S. Patel · UGdeath in family documented · no plan1.94 / 71%Missing planNotice drafted
D. Reyes · GR3rd appeal · 2 prior approvals2.10 / 66%CompleteHuman review

See it on your SAP policy first — no student data

Send your published SAP standard and your appeal form. You'll get back the playbook NineSweep would run against them, worked on synthetic appeal packets. No system access, no student records, no FERPA paperwork.

Send your SAP policy
From the founder
“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