Agents That Act — and Prove They Acted: Agentic Compliance Arrives in Atticus 2.0

Why compliance fails: clocks and consequences

Regulators rarely punish schools for wickedness. They punish them for lateness. Most of the rules that end schools are deadline rules — a withdrawal determination documented within 14 days, an SAP evaluation at the published checkpoint, a placement verified before the annual report. Each has a clock and a consequence, and each traditionally depends on a busy person noticing that the clock started. That is the single point of failure agentic software removes: the noticing.

The document-chase agent

Every registration file is watched continuously. When a required document is missing, rejected, or approaching expiration, the student receives an email listing exactly what is needed, with a portal link to upload it — three reminders, three days apart. If chasing fails, the agent stops emailing and escalates: it opens an intervention assigned to a named staff member with a due date. Files complete themselves, or they land on a human desk with the history attached. Nobody spends Friday afternoon chasing paperwork.

The withdrawal-clock agent — 34 CFR 668.22

Under the withdrawal rules effective July 2026, a school must document its withdrawal determination within 14 days. The agent watches attendance daily. Three consecutive missed sessions opens the clock: it records the last date of attendance, assembles the evidence packet — the missed-session record, the cohort context, the regulatory citation — opens an intervention for the registrar, and counts down the deadline in plain sight. If the student walks back into class, the agent closes its own case and documents why. If the deadline passes without a decision, the record turns red and stays red.

The SAP cycle agent

Satisfactory academic progress fails audits in two ways: checkpoints that never ran, and evaluations nobody signed. The SAP cycle agent runs checkpoints on the calendar — at 25, 50, and 75 percent of each cohort's dates — combining attendance from the system of record with grades from the LMS. Warning and probation letters are drafted from the student's actual numbers, with an appeal deadline tracked on every letter. Unsigned evaluations trigger a daily digest to the advisor, because an unsigned evaluation is an unfinished evaluation. Appeal windows that close without an appeal are marked, dated, and preserved.

The audit-readiness agent

Every night, the fourth agent reconciles three systems that never used to talk to each other: the LMS roster, the student records, and the money. An enrolled student with no signed agreement. Tuition never charged. Attendance recorded after a withdrawal date. A student active in the records but absent from the LMS course. Each mismatch becomes a finding — severity-ranked, dated, and linked to the file where it gets fixed. And when the record is corrected, the finding resolves itself on the next pass. The open-findings register is, quite literally, the list of what an examiner would have found — surfaced first.

The examiner binder: the whole record, one click

When the site visit comes, the binder assembles the entire institutional record on demand: every student file with document hashes, agreement status, ledger, attendance with last date of attendance, signed SAP evaluations, interventions, and policy acknowledgments — print-formatted, with open findings disclosed up front. The week of copying before a visit becomes a click.

Why the audit trail is the point

Automation without evidence is a new liability, not a solution — an examiner who asks "who sent this letter and on what basis?" is not satisfied by "the AI did it." So every agent action in Atticus writes to the same append-only audit trail as every human action: what was detected, what was done, when, and under which rule. The agents do not just act. They leave the proof that they acted, in the same file an examiner reads.

What this replaces

• The tickler spreadsheet of document deadlines someone maintains by hand.
• The term-end SAP scramble rebuilt from LMS exports and memory.
• The withdrawal that gets documented three weeks late, after the R2T4 window.
• The pre-visit reconciliation marathon between the SIS, the LMS, and the books.

See it running

The agents run every morning inside our demo school — real signatures, real payments, real LMS sync, and a live agent activity log on the overview page. There is no password: tryatticus.com/demo. Watch the register, open a student file, and read the audit trail behind any action. Agentic compliance ships in Tier 3, alongside the examiner binder — the tier where Atticus stops keeping your records and starts working them.

This article is general guidance, not legal, financial, or accreditation advice. Regulatory requirements change and vary by accreditor, state, and program. Always confirm current rules with your accreditor, your state agency, and the federal regulations and FSA Handbook before acting.