A CCO's Tuesday · Step 3 of 6
The issue lands in /issues with a clock and an owner
WiredAccepting the Compass suggestion creates the issue. It shows up in /issues with an owner, a target date, and a maker–checker requirement on close. Overdue issues raise their own findings — the clock is part of the audit trail.
What this saves you
Accountability lands on a named person with a clock. Group-MLCO view rolls the same queue up across every entity.
regalign.app/issues
Open issues · 17
Sorted by SLA pressure- ISS-419Re-screen CLI-00318 against adverse-mediaA. Hendersonin 5dMaker–checker
- ISS-414Refresh source-of-funds — CLI-00671R. Mhlanga2d overdueMaker–checker
- ISS-411Update outsourcing register — Provider 14J. Powellin 12dMaker–checker
- ISS-407Quarterly EDD review — Jurisdiction XA. Hendersonin 1dMaker–checker
- 1Open issues, ranked by SLA pressure. Overdue ones surface auto-findings.
- 2Owner is a named person, not 'Compliance'. Reasonable-steps story writes itself.
- 3Maker–checker badge: closer cannot be the same person who raised it.