Lesson 09 · Activity 03

Compliance Routine Audit

Speed isn't safety. Here you'll run the "Should I automate this?" aid on a proposed compliance automation, find what makes it unsafe, and redesign it.

Work through it

0 of 4 done

Read the proposed automation.
Answer the four decision-aid questions.
List what’s missing or unsafe.
Write a safe redesign, then compare to the model.

The proposed automation

"An agentic browser logs into the SIS each month, reads every student’s records, fills in the state compliance report (including names and IDs), and submits it automatically — no review, so it’s never late."

Run the decision aid

Answer each, then list the flaws. Saved on this device.

Repetitive & rule-based (not judgment-heavy)?
Student data handled safely (de-identified / approved tool)?
Output verified before it goes out?
Audit trail of what it did?

What’s unsafe, and how would you redesign it?

Saved automatically on this device.

Reveal model answer

Decision aid: only Q1 is a clear "yes." Q2 fails (full records incl. names/IDs into the tool), Q3 fails (no verification), Q4 fails (no audit trail). Flaws: auto-submits a consequential report with no review; sends student PII through the agent; no log to defend it.

Safe redesign: extract only the de-identified fields the report needs; verify a sample against the source; assemble into the report template; require your sign-off before submission; and log each run (audit trail). "Never late" is not worth filing an error or a FERPA violation automatically.

Takeaway: the fix isn’t "don’t automate" — it’s automate the gathering and drafting, de-identify early, and keep the human at the irreversible step.