Checking Required Disclosures
Check a closed file for the disclosures it should contain, their timing and their signatures, against your own disclosure matrix.
About this use case
Disclosure findings are the most avoidable kind of exam finding, because the requirement is written down and the check is mechanical. It is also the check most likely to be sampled rather than performed on every file, which is how a systematic gap survives a year.
This use case runs the matrix against a file: which disclosures the product and circumstances require, whether each is present, whether it was delivered in time, and whether it is signed and dated.
For a single file that means every disclosure the matrix requires marked present or absent, with timing and signatures checked; a disclosure dated after the event that triggers it is reported with both dates and the interval; a batch from one channel gives the exception rate by disclosure type.
Documents to consider
- Your disclosure matrix by product and circumstance
- The complete closed file with all documents
- Timing requirements and how delivery is evidenced
- Signature and dating standards
- Prior audit and exam findings on disclosures
The prompt
Written to be pasted straight into your AI assistant, with the documents it asks for attached. Request access below and we’ll send it over.
Files
Nothing to download here. This prompt runs against your own institution’s material — the documents it lists above.
More in Risk & Compliance
Triaging Customer Complaints
Classify an incoming complaint against regulation and internal procedure, route each issue it raises, and flag anything that needs priority escalation.
Audit Response Drafting
Draft an auditor or client response from your own control descriptions, evidence logs and prior answers, with every statement traced to an artifact.
Compliance Operations
Answer an obligation or interpretation question from approved regulatory and internal content, surfacing the exact clause that drives the answer.
