Regulatory Investigation / Legal Response Manager — Documentation

Manage regulatory investigations end to end: from receipt of a regulator request through decomposition into requirements, evidence collection, privilege review, response drafting, approval, submission, proof of receipt and closure.

In this section

• 00_OVERVIEW — what the application is for, the operating chain, and the five functional areas.
• 01_QUICK_REFERENCE — the menu map, all 16 models, the status vocabularies, and the demo data story.
• 02_SYSTEM_DIAGRAM — an interactive entity map (hub tables, per-area tabs and a curated top-level flow).

The application in one paragraph

A Regulator issues a request under an Investigation (matter). Each RegulatoryRequest is decomposed into Requirements, which are assigned to owners and reviewers. EvidenceItems are collected against requirements with custody, hash and privilege status, then legally reviewed (EvidenceReview) for relevance, privilege and redaction. ResponseDrafts are prepared and run through ReviewDecisions; deadlines can be extended (ExtensionRequest). Approved responses and evidence are bundled into a Submission — recording which requirements it covers (SubmissionRequirement) and which evidence is produced/redacted/withheld (ProductionItem) — issued to the regulator, and receipted. Communications log all correspondence and IssueExceptions track privilege, deadline and completeness risks — all under the framework's audit trail and soft-delete.