We built a compliance copilot over 10 weeks, deployed as a desktop application with offline capability. Regulatory intelligence engine (weeks 1-4): the copilot monitored and processed regulatory updates from all relevant sources: FSCA (board notices, regulatory instruments, guidance notes, enforcement actions — published on the FSCA website and via email distribution), SARB (exchange control circulars, prudential communications — affecting the firm's offshore investment allocations), SARS (tax interpretation notes, binding rulings, legislative amendments — affecting fund tax treatment and investor reporting), JSE (market notices, listing requirements amendments, surveillance communications), and ASISA (standard updates, best practice guidelines, industry position papers).
For each regulatory update, the copilot: classified the update by relevance to the firm (high/medium/low — based on the firm's activities, products, and licence conditions), summarised the key changes in plain language (translating regulatory language into actionable summaries), identified specific firm obligations (what the firm needed to do — change a process, update a document, file a report, adjust an investment restriction), assessed the implementation timeline (effective date, transition period, and recommended action dates), and drafted an impact assessment memo for the CCO (a structured document suitable for board reporting). Previously, the compliance team spent approximately 15 hours per week reading and assessing regulatory updates. The copilot reduced this to 3 hours per week (reviewing the copilot's summaries and impact assessments, focusing human attention on the most significant changes).
Compliance query engine (weeks 3-7): the copilot answered ad hoc compliance queries from across the firm: portfolio managers asking: "Can we invest in this offshore ETF within our exchange control allocation?" — the copilot checked the fund's remaining offshore allocation against SARB limits, verified the ETF's eligibility under the fund's investment mandate, and provided a clear yes/no answer with regulatory references. Marketing team asking: "What disclosures are required for this new fund factsheet?" — the copilot listed the mandatory disclosures under FSCA and ASISA standards (past performance disclaimer, fees disclosure, risk rating, benchmark information, FAIS licence number), with correct current wording. Operations team asking: "When is the deadline for the FSCA annual compliance report?" — the copilot provided the deadline, the report template, previous submissions for reference, and a checklist of information needed.
The copilot answered queries with: citations to specific regulatory provisions (not general advice — specific section and paragraph references), the firm's own policy references (linking regulatory requirements to the firm's compliance manual and procedures), and confidence indicators (flagging queries where the regulatory position was ambiguous or where the copilot recommended human CCO review).
Compliance monitoring dashboard (weeks 5-9): the copilot provided a real-time compliance monitoring view: investment restriction monitoring (checking portfolio positions against: fund mandate limits (maximum asset allocation, sector exposure, single issuer limits), regulatory limits (FSCA Regulation 28 for retirement funds, exchange control limits for offshore allocation), and internal risk limits (board-approved risk parameters) — flagging breaches or near-breaches for immediate attention), reporting deadline tracking (a calendar of all regulatory reporting deadlines: FSCA returns, exchange control reports, tax submissions, JSE disclosures — with automated reminders and preparation checklists), regulatory change implementation tracker (tracking the status of required changes from regulatory updates — ensuring that identified obligations were implemented on schedule, not forgotten in the compliance team's workload), and compliance incident log (recording compliance queries, breaches, near-misses, and remediation actions — generating the compliance data needed for board reporting and FSCA regulatory returns).
Offline capability (weeks 7-10): the copilot operated in offline mode during load shedding: the complete regulatory knowledge base was cached locally (updated daily when connectivity was available), common queries were answered from local inference (without cloud round trips), and regulatory monitoring continued from cached data (with an "as of" timestamp indicating when data was last updated) — the copilot flagged when its regulatory data was more than 48 hours old, prompting the user to sync when connectivity returned.