In examination practice, a walkthrough is how an examiner traces a control end to end to see if it actually works. This guide walks the RegTwin platform the same way: every section of the sidebar, in the order the work actually happens. Build the twin, run the analysis, monitor it live, and hand the results to your board and your examiners.
§ 1 · Overview
The Compliance Command Center.
The Overview is your real-time compliance posture at a glance. Four journey cards track the phases of the work: Build Compliance, Run Analysis, Live Monitoring, and Board & Examiners, each with a completion percentage and the counts that drive it. Amber and red alerts under each card link directly to the item that needs attention, so the dashboard tells you where to go instead of making you hunt.
1Read the journey cards left to right. The phase with the lowest percentage is usually where your next hour belongs.
2Click any alert, for example "22 regulations need mapping," to jump straight to the queue behind it.
3Check the Health Score and KPI cards below, then the Gap Coverage chart showing mapping status across every regulation-control pair.
regtwinai.com/dashboard
The Command Center: journey cards, health score, KPIs, and gap coverage.
What to noticeThe health score is honest. If it says 61% and "Needs attention," that is the platform telling you the truth about your posture rather than decorating it. Everything below the score explains why the number is what it is.
§ 2 · Build Compliance
Construct the twin: regulations, controls, and the map between them.
Regulations is the inventory of every obligation you track, and Controls is the inventory of every mechanism you rely on to meet them. Neither is useful alone. The Reg → Control Map is where the twin becomes real: every regulation-control pair is assessed as fully mapped, partially mapped, gap identified, or not assessed.
1Start in Regulations and confirm the inventory matches your actual footprint before anything else. The twin can only be as honest as this list.
2Do the same in Controls, then open the Map and work the unmapped queue. The Overview alert tracks how many pairs remain.
3Use Import Data to bring in existing registers and inventories instead of rekeying them.
regtwinai.com/regulations
The regulation inventory: every tracked obligation.
regtwinai.com/mappings
The Reg → Control Map: where coverage and gaps become visible.
What to noticeA "gap identified" status in the map is not a failure of the platform. It is the platform doing its job: a named gap with a location is fixable, while an unmapped pair is a surprise waiting for an examiner to find it first.
§ 3 · Run Analysis
Find the gaps, plan the fixes, and rehearse the exam.
This is the working core of the platform, five tools that turn the twin from a picture into a practice. Gap Analysis runs AI analysis across the map and surfaces where coverage fails. Remediation Plans turns each finding into corrective actions with owners and dates. Then three tools rehearse the examination itself. The Exam Simulator runs a full mock examination, an OCC Safety and Soundness for example, and returns a preliminary examination report: an overall rating, a domain scorecard, findings, observations, and Matters Requiring Attention. Exam Defense then builds your defense of those MRAs (there is a Defend button on each finding), and the Document Exam has the system read your own policies the way an examiner would, before a regulator does.
1Run Gap Analysis after any material change to the map. Every gap it finds should end the day owned by a remediation plan.
2Work Remediation Plans until nothing on the Overview says "gaps need remediation plans."
3Before an exam cycle, run the simulator, read the report the way your board will, and click Defend on every MRA it issues. That output is your prep list.
regtwinai.com/ai
Gap Analysis: AI-surfaced coverage failures across the twin.
regtwinai.com/remediation
Remediation Plans: findings converted to owned, dated corrective actions.
regtwinai.com/exam
The Exam Simulator: your framework tested before a regulator tests it.
What to noticeThe order matters: analyse, remediate, then simulate. Running the simulator against unremediated gaps just documents problems you already know about. Running it after remediation tests whether the fixes would actually survive scrutiny.
§ 4 · Live Monitoring
The twin stays current so you don't fall behind quietly.
Compliance decays silently: regulators publish, controls drift, review dates pass. Compliance Health is the live score with its drivers. Reg Change Alerts is the Regulatory Watchdog: it scans the Federal Register and agency publications (OCC, FRB, FDIC, CFPB, FinCEN, SEC), classifies each item, auto-adds critical ones to your regulation tracker, and shows its reasoning step by step in the Agent Activity panel as it works. Risk Predictions looks forward at where posture is heading rather than where it is, and the Calendar holds the deadlines: reviews, attestations, response dates.
1Run a scan (pick a period, click Scan Now) or read the latest one. Every critical item arrives already summarized, tagged with affected areas, and added to the tracker; your job is the review it asks for.
2When the health score moves, click into it. The drivers tell you which controls or mappings moved it.
3Work from the Calendar during exam season. Missed internal dates become external findings.
regtwinai.com/health
Compliance Health: the live score and what is driving it.
regtwinai.com/watchdog
Reg Change Alerts: new regulatory activity, triaged against your inventory.§ 5 · Board & Examiners
The two audiences that read your work.
Board Reports generates the same underlying data for three audiences: a Board Report for directors, a Committee Report for the risk committee, and a Management Report for senior management, each with a written executive summary and PDF export. The Audit Trail is the platform's memory: a complete record of every agent decision with its reasoning, confidence level, timing, and output, exportable in full. It is what an examiner reads to verify that your process is real and not reconstructed.
1Generate a board report on a fixed cadence, not just when asked. A report trail is itself evidence of governance.
2Before any exam, review the Audit Trail the way an examiner will: chronologically, looking for gaps in the record.
regtwinai.com/reports
Board Reports: the governance view, generated from the live twin.
regtwinai.com/audit
The Audit Trail: every action, attributed and timestamped.
What to noticeThese two pages are the payoff for everything above them. The report and the trail are only as good as the twin behind them, which is why the journey starts at Build and ends here.
§ 6 · Program Governance
The RAID log: running the program like a program.
Compliance transformation is a program, and programs have Risks, Assumptions, Issues, and Dependencies. The RAID Log tracks all of them in one register with severity filters, program status, and a natural-language Ask AI bar ("Show me all BSA/AML gaps", "What's overdue?") that answers from the live twin. Critical counts surface in the top bar itself, so they stay visible from anywhere in the platform.
1Review critical RAID items weekly. The sidebar count is a standing reminder, not decoration.
regtwinai.com/programs
The RAID Log: risks, assumptions, issues, and dependencies with criticality.§ 7 · System
Performance, Admin, and Settings.
The system section holds the platform's own governance. Admin is platform-wide intelligence: active alerts, agent status, success rates, the database, and, most importantly, the Approval Queue, where AI-assisted analyses wait for human sign-off. Performance and Settings cover system health and configuration. Watch the queue: pending approvals are unresolved governance decisions, and letting them age is itself a finding waiting to happen.
regtwinai.com/admin
Admin: users, roles, and access aligned to real authority.
