Platform · Issue management and remediation tracking
Findings run to a deadline, and closed only on evidence.
Issue management takes the findings you accept, puts each on a deadline, orders the work by dollar exposure, and closes an issue only when cited, signed evidence shows the fix works. When your examiner or your sponsor bank asks about an MRA, you show them the trail, not a spreadsheet.
The problem it removes
"Done" in a spreadsheet is not closed
- Issues sit in a spreadsheet, and an item closes when someone types "done", not when evidence shows the control works.
- Every finding looks equally urgent, so the team works the easy ones first.
- Deadlines slip quietly, and you learn about it when the examiner asks.
What you see
One queue, ordered by exposure
Each issue shows its state, its owner, its due date and its expected cost. A finding the engine inferred waits as "proposed" until you accept or dismiss it, and its clock starts only when you accept.
| Issue | State | Owner | Due | Middle cost |
|---|---|---|---|---|
| SAR filing timeliness | In progress | BSA Officer | 2026-10-31 | $640K |
| Beneficial ownership at opening | Re-test | Onboarding lead | 2026-10-15 | $310K |
| Monitoring thresholds untuned | Remediation planned | Monitoring lead | 2026-12-15 | $220K |
| High-risk review cadence | Proposed | n/a | clock not started | $140K |
| Wire recordkeeping fields | Closed, verified | Operations | 2026-09-01 | $85K |
Illustrative example with invented issues and figures. Each closed issue links to the evidence and the signature it closed on.
How it works
Accept, plan, fix, re-test, close
- Accept. A control that failed on your records can enter the queue directly. A finding the engine inferred is proposed, and you accept or dismiss it with a reason.
- Plan. Each accepted issue gets an owner and a deadline counted from acceptance, and the roadmap is ordered by its dollar exposure.
- Fix. The issue moves through seven defined states, and every move is recorded with who made it and when. AI may draft the remediation notes; it never moves an issue.
- Re-test and close. An issue closes only against cited evidence that a practitioner has reviewed and signed. The closure stays on the trail.
The team that fixes your program never performs the independent test of that same program.
Guardrails
What it will never do
- It doesn't close an issue on someone's word. Without evidence, the issue stays open.
- It doesn't let the team that remediated your program also test it.
Where it shows up
The work this part does for you
Plain English
What this is, and how anyone does it
Reference articles from our library, cited to the published rules and standards. No sales copy.
- ReferenceCompliance Remediation and Issue Management: From Finding to Validated ClosureHow findings, MRAs and MRIAs are managed to closure: root cause, corrective action plans with owners and deadlines, independent validation, and the separation of remediation from testing.
- Consulting PracticeHow to Write a Corrective Action Plan After an Audit FindingThe field-by-field format for a corrective action plan after an audit or exam finding, a worked example, when to escalate to a team CAPA, and what makes examiners reject a CAP.
Connected parts
What it works with
Talk to a practitioner
Book a 15-minute chat with our founder.
A real conversation with a senior compliance leader, to see if there's a fit. Not a sales call, not a demo, no pressure.