Regulatory reporting draft responses

Identifies pre-submission draft responses, reports, and submissions prepared for a regulator or supervisory authority. Topic phrases are retained for discovery; enforcement requires reporting-period, event, proposed-disclosure, affected-record, data-quality, control, corrective-action, legal-review, or outstanding-evidence content, and high confidence also requires approval, submission, clearance, comment, deadline, or regulator-reference workflow evidence.

Type: regex
Engine: boost_regex
Confidence: medium
Confidence justification: Medium confidence requires substantive reporting content rather than draft or regulator vocabulary alone. High confidence adds explicit pre-submission workflow or regulator-reference evidence.
Detection quality: Topic false positive
Jurisdictions: global
Regulations: GDPR
Data categories: government
Scope: wide
Risk rating: 8
Platform compatibility: Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?is)\b(?:regulatory\s+reporting\s+draft\s+(?:response|submission|report)|draft\s+(?:response|submission|report)\s+(?:to|for)\s+(?:the\s+)?(?:regulator|regulatory\s+authority|supervisory\s+authority)|draft\s+response\s+to\s+(?:a\s+)?(?:regulatory|statutory)\s+(?:request|notice|reporting\s+obligation))\b

Corroborative evidence keywords

regulatory reporting draft responses, regulatory, reporting, draft, responses, privacy, compliance, risk

Proximity: 300 characters

Should match

regulatory reporting draft response — Low-tier probe - draft regulatory-response topic without substantive content
Regulatory reporting draft response: reporting period, reportable event, proposed disclosure, affected records, data quality issue, control weakness, corrective action, legal review, and evidence outstanding — Medium-tier probe - substantive draft response without workflow evidence
Regulatory reporting draft response to the regulator: reporting period, reportable event, proposed disclosure, affected records, control weakness, and legal review; status not approved, regulator reference: RRN-2026-77, response due 30 August 2026 — High-tier probe - substantive draft with approval, reference, and deadline evidence

Should not match

unrelated generic text without domain phrases — No relevant topic phrases present
The regulator publishes annual regulatory reporting guidance. — Public reporting guidance without a draft response
Draft response to the customer complaint — Non-regulatory draft response
Training example: regulatory reporting draft response with proposed disclosure, status not approved, and regulator reference RRN-2026-77 — Explicit training content must not enforce

Known false positives

Public reporting guidance, published statutory reports, and ordinary customer-response drafts can contain reporting, compliance, response, and deadline language. Mitigation: Require an explicitly draft regulator-facing response, submission, or report before considering substantive reporting evidence.
Training drafts can contain realistic proposed disclosures, approval states, regulator references, deadlines, and legal-review notes. Mitigation: Reject explicit template, demo, tutorial, sample-data, and training-example framing from enforcing tiers.

References

https://www.austrac.gov.au/business/core-guidance/reporting
https://asic.gov.au/regulatory-resources/find-a-document/regulatory-guides/