How do I run the Monday regulatory sweep?

The trigger

Monday morning, first block of the week. Regulator output does not arrive on a schedule that suits your team: a letter to industry, an updated starter kit or a guidance consultation can land any day, and a program document a version behind the regulator's is exactly the drift a weekly sweep exists to catch. The sweep runs every Monday. A nil result is still a record.

The inputs

• The news or media-release pages for APRA, ASIC, OAIC and AUSTRAC, opened directly (primary sources, not a newsletter digest)
• The current version of your regulatory change impact-assessment skill file, loaded into your AI workspace
• Your organisation context file: business lines, licence types, obligation register categories, control framework names
• Last week's sweep record, so the window picks up where it left off
• Read access to the obligations register

The steps

1. Open each of the four regulators' release pages and list every item published since the last sweep, with its title, date and link.
2. Triage the list against your organisation context file: mark each item in scope, out of scope, or unclear, and treat unclear as in scope.
3. Read every in-scope release on the regulator's own page. The AI structures the analysis; it never substitutes for reading the release itself.
4. Run each in-scope release through the impact-assessment skill file, pasting the full release text and the context file, and collect the draft assessments.
5. Hand each draft to the obligation owner for validation of every classification and draft action against the release text.
6. Record the sweep: date, items found, items assessed, items dismissed and why, and file the validated assessments with their draft stamps.

The prompts

The skill file carries the method; this prompt invokes it per release.

Run the Regulatory Change Impact Assessment skill on the following
release.

Release name and date: [RELEASE_NAME], [RELEASE_DATE]
Release text, pasted in full: [RELEASE_TEXT]
Organisation context: [ORG_CONTEXT]
Date of this assessment: [DATE_CHECKED]

Follow the skill file exactly: classify each affected area as no
impact, monitor, or change required, cite the release section or
page for every claim, mark all action owners TBD, and stamp the
output DRAFT requiring human validation. If the release text
appears incomplete or superseded, say so and stop.

The checks

• Open the release beside the draft and confirm every citation points to a real section, paragraph or page
• Confirm dates and deadlines in the change summary match the release verbatim
• Check the draft stamp carries the release name, release date and date checked
• Delete any claim that rests on general knowledge of the regulator rather than the release text
• Confirm the sweep record lists every item found, including dismissals

Governance controls

• A named obligation owner validates every classification and impact rating before anything enters the obligations register or reaches a business owner. The AI drafts; existing licensee obligations still apply to whatever the draft becomes.
• The skill file is a controlled document: versioned, with a named owner and approver, and the sweep always runs the current approved version.
• Only the public release text and the organisation context file go into the tool. No confidential assessments, register extracts or customer information are pasted.
• Retain the validated assessments and the sweep record. Automated processes that shape decisions are increasingly disclosure territory, and the sweep record is your evidence of a working change process.

The output

A dated sweep record covering all four regulators, plus a validated, citation-stamped draft impact assessment for every in-scope release, filed and ready for register entry by the obligation owner.

Time it takes

Around 45 minutes the first run, while the context file and skill file settle. A practised run on a quiet week is 15 minutes; a week with one substantive release fits inside 30.