Discovery
Saved views
The sidebar used to list 156+ saved queries — Overdue, Unassigned, Quiet Issues, Plan Slip and many more. They now live here: searchable, grouped by intent, and one click from any persona's workflow. Every link remains deep-link stable, so bookmarks and Compass recommendations keep working.
Steering
Headline reads — board, governance, programme health
SLA & deadlines
What's overdue, what's coming, what slipped
- Calendar BlindOpen issues with no due date on any remediation step — the defensibility gap behind every SLA report
- Coming DueStep-level deadline radar — every open remediation step past due or due in the next 14 days
- Aging BacklogOpen issues bucketed by age, ranked by severity-weighted staleness
- SLA at RiskForward-looking deadlines: past due, due in 7/14/30 days, plus open issues with no target date
- Past-Due UnassignedOpen issues already past SLA with no named owner on any remediation step — the governance vacuum behind every regulator finding
- Overdue StepsIndividual remediation steps past due and still open — the slip behind tomorrow's overdue issue
- Aged SevereOpen high/critical issues bucketed by age — the fastest read on whether the serious pile is digesting or accumulating
- Owner Overdue LoadOwners ranked by past-due open issues — SLA debt with a name on it, so leadership can rebalance before it becomes personal conduct
- Blocked AgingOpen issues formally blocked at issue- or step-level, ranked by how long the block has been sitting — paperwork blocks that won't move
- SLA MissClosed issues that landed after their target date — the late-but-landed pile, with miss rate and severity of slip
- Quick ClosesClosures landed within seven days — the healthy fast-digestion view, counterpart to SLA miss and aging
- Source AgingOpen issues grouped by originating authority and ranked by age — whose regulator backlog is going stale fastest
- Target SlipOpen issues whose target close date has already passed — broken close-date commitments at the issue level
- Step No-DueOpen issues with remediation steps that have no due date — invisible to SLA dashboards until somebody asks
- Critical No-TargetOpen high/critical issues with no issue-level target close date — severity present, commitment missing
- Closed No-TargetClosed issues with no target date on the record — counted as done with no commitment to have hit
- Step OverdueOpen remediation steps whose committed due date has passed — promises the plan made and missed
- Auto-Tagged UntriagedOpen issues still carrying the [auto:…] intake prefix — machine titles nobody has triaged
- Escalated No-TargetOpen issues escalated to leadership with no target close date — loud signal, no clock
- Issue No-TargetOpen issues with no target close date on the issue record — invisible to every SLA, aging and at-risk view
- Owner SLA DebtDays-overdue (raw + severity-weighted) attributed to every named step owner — SLA debt with a name on it, ranked by weighted debt
- Aging CohortsOpen-issue survival curve by ISO creation week — how each cohort is digesting over time
- Owner SLA PerformancePer-owner SLA hit rate over the last 365 days against severity-based targets, with currently-overdue live exposure
Ownership gaps
Unassigned, solo-owned, handoffs, owner load
- UnassignedOpen issues with no named owner on any remediation step — the silent governance gap
- Solo-Owned PlansOpen issues whose plan has owners but every owned step belongs to one person — per-issue bus factor
- Handoff RiskOpen issues whose plans spread owned steps across three or more people — the opposite failure mode to solo-owned
- Owner GapsOpen issues that look staffed but have at least one open step with no owner — the quiet single points of neglect
- Multi-Owner PlansOpen plans spanning three or more owners — highest coordination cost, easiest to stall on handovers
- Step No-OwnerOpen issues with remediation steps that have no owner — actions on the plan with nobody on the hook
- Owner Closure QualityPer-owner scorecard combining weekend, same-day, thin-note, evidence-missing and waiver-unratified rates — closure defensibility with a name on it
- Owner LoadPer-owner carrying load — open-issue count, severity-weighted total and oldest open issue, attributed to every named step owner
- Owner SilenceOwners whose attributed open issues disproportionately go quiet or stalled — silence with a name on it, ranked vs portfolio baseline
- Repeat OwnersOwner continuity across recurrences — stuck-with-one is accountability concentration; handed-around is no institutional memory
- Owner Waiver BiasPer-owner waiver vs evidence closure mix — biased owners reach for waiver as the default rather than the exception
- Owner Recurrence RateWhose closures don't stick? Per-owner share of attributed closures whose finding re-raised within 90 days
- Owner Speed BiasPer-owner median time-to-close vs portfolio — rushing owners may be rubber-stamping, dragging owners are the bottleneck, rushed+recurred is the strongest shallow-work signal
- Owner Solo Closure RatePer-owner share of closures with no co-owner anywhere in the workflow — single-point-of-failure plus un-peer-reviewed sign-off, with severe-solo as the audit callout
- Owner Severity SkewPer-owner high/critical closure share vs portfolio baseline — surfaces workload-fairness and burnout signal when one owner absorbs disproportionate severe work
- Owner Jurisdiction SpreadPer-owner jurisdiction breadth and bus-factor jurisdictions where one owner has ≥70% of closures — specialist vs generalist posture plus single-owner regimes
- Owner Weekend BiasPer-owner share of closures finalised on Saturdays/Sundays UTC — after-hours sign-off proxy, with severe-weekend as the audit callout
- Owner Reopen RatePer-owner share of attributed closures whose issue status has flipped back from resolved — closures that didn't hold, with severe-reopen as the audit callout
- Owner Evidence DisciplinePer-owner share of evidence-mode closures with no evidenceId attached — the closer-side defensibility signal, with severe-missing as the audit callout
- Owner Same-Day ClosurePer-owner share of closures finalised within 24h of issue creation — proxy for pre-baked or rubber-stamp closures, with severe same-day as the audit callout
- Owner After-Hours ClosurePer-owner share of weekday closures finalised outside 07:00–19:00 UTC — defensibility proxy for solo, after-cover sign-off, with severe after-hours as the audit callout
Plan health
Plan depth, slip, zero-progress, thin plans
- Plan DepthShape of remediation plans: empty / thin / lean / typical / deep — surfaces missing or under-scoped plans
- Zero ProgressOpen issues with a plan where not a single step is done — the quiet failure of plans that never start
- Plan SlipOpen issues whose remediation steps are scheduled past their own target close date — plans that on paper cannot meet the deadline
- Stalled StepOpen issues whose plan started but went quiet — at least one step done, none completed for 21+ days
- Closure PendingOpen issues whose remediation plan is fully done but the issue itself hasn't been signed off — the last-mile gap
- Thin PlansOpen high/critical issues whose remediation plan has at most one step — the planning gap behind every avoidable finding
- Almost ThereOpen issues with ≥75% of remediation steps done — finish-line stragglers and cheap wins for closure rate
- Heavy PlansOpen issues with six or more remediation steps — ambitious plans that mask stalled threads and resist visible progress
Escalation & blocked
Escalations, blocked work, silent critical
- BlockedIssues or active steps marked blocked — the 'what's stuck and needs unblocking' steering view
- Triple ThreatOpen issues failing two or more independent risk dimensions at once — composite emergency list
- EscalationsEscalation register: open escalations, oldest open, reactive-escalation rate, median resolution after escalation
- Silent CriticalOpen high/critical issues that have never been escalated — the 'we knew but nobody raised it' defensibility miss
- Escalation BacklogOpen issues that have been escalated but remain unresolved beyond a 7-day grace — escalation stopped producing movement
- Blocked SilentOpen issues flagged as blocked yet never escalated — the gap between 'we're stuck' and 'leadership knows'
- Escalated No-RecipientOpen issues escalated on paper but with no recipient assigned — the clock started, nobody's inbox owns them
- Escalated StaleOpen issues escalated more than 14 days ago — the loudest signal in the workflow has gone quiet
- Severity EscalationRecurring findings whose severity is trending worse on each re-raise — the issue is metastasizing, not just repeating
Defensibility
Audit trail, evidence, root cause, provenance
- Repeat Root CausesOpen issues grouped by shared root cause — each cluster is a candidate for a single structural fix
- Root Cause MissingOpen issues with no root cause recorded — the governance hygiene gap that disables pattern detection
- Audit HeavyOpen issues with a thick audit trail but no resolution — thrashing that needs adjudication or simplification
- Provenance GapsOpen issues missing origin or originating-authority metadata — the defensibility gap behind ad-hoc-looking findings
- Resolved ThinClosed issues missing a recorded root cause or evidence reference — the closures that won't survive an audit sample
- Audit-ThinIssues (open or closed) with an unusually small audit trail — where the paper would be lightest under a regulator's sample
- Regulator ReadyOpen issues passing all four defensibility checks — root cause, target date, owners, audit trail; the positive composite
- Evidence LightEvidence-mode closures with no evidence reference on the closure or any step — closed-by-evidence in name only
- Orphan IssuesIssues with no linked finding record — structurally untraceable back to source
- Closure Note MissingClosed issues whose closure record carries no rationale note — procedurally complete but undefended on a sample
- Duplicate FindingsClusters of issues raised against the same source finding — double-counted in metrics, fragmented in remediation
- Origin Link MissingOpen issues with origin and authority recorded but no link to the source record — provenance in words without a receipt
- Audit ZeroOpen issues with zero audit-trail entries — nothing recorded since they were raised, the starkest defensibility miss
- Done No-EvidenceOpen issues with done remediation steps that carry no evidence reference — completion claimed, receipt missing
- Origin MissingOpen issues with no origin tag — invisible to regulator vs internal source rollups
- Closure Evidence MissingEvidence-mode closures with no evidence reference attached — closures pointing at nothing
- Root Cause MissingOpen issues with no root cause recorded — remediation working without a documented cause
- Closure Note ThinClosed issues whose rationale note is shorter than 40 chars — present but functionally empty under a regulator sample
- Closed No-Root-CauseClosed issues with no root cause recorded — signed off without a diagnosis, invisible to root-cluster analytics
- Closed Audit-ZeroClosed issues with zero audit-trail entries — closed without a single recorded event
- Closed No-Step-EvidenceEvidence-mode closures whose remediation plan has zero step-level evidence — defensibly thin on a regulator sample
- Closure Note BoilerplateLong closure notes composed mostly of stock phrases — present, but nothing for a regulator to read
- Closure Note DuplicatesClosure rationales reused verbatim across three or more issues — copy-paste sign-off pasted across a queue
- Closure Evidence ReuseEvidence-mode closures pointing at the same evidence record across multiple issues — one artefact doing the work for a queue
- Closure Evidence StaleEvidence-mode closures whose last completed step is ≥60 days before sign-off — the evidence aged between work and close
- Root-Cause DriftSame finding, different rootCause statements over time — the diagnosis itself keeps changing
- Step Evidence ReuseSame artefact ticking off remediation steps across multiple issues — silent reuse one layer before closure
Closures & wins
Recently closed, quiet wins, closure quality
- Quiet WinsClosed issues — clean-closure rate, top closers, recent closures
- Recently Closed30-day closure register: every issue shut, with mode, days open, waiver ratification — QA / sign-off review surface
- Closure QualityEvidence vs waiver, waiver ratification rate, time-to-ratify — the defensibility view
- Closure BurstCalendar days with five or more closures — bulk-close patterns that look like cleanup rather than steady-state remediation
- Weekend ClosuresClosures stamped on Saturday or Sunday — after-hours sign-off, batch imports, or backdated closes that won't survive a regulator sample
- Same-Day ClosuresIssues closed within 24 hours of being raised — drive-by sign-off or back-dated imports made to look like remediation
- Closure Self-SignoffClosures where one person owned every remediation step and is also the issue owner — single-hand closures with no second pair of eyes
- Closure Mode FlipSame finding with closure rigor changing between occurrences — evidence→waiver is a defensibility regression; all-waiver means never proved
Cross-cutting
Jurisdiction, authority, severity, impact
- Quiet IssuesOpen plans that started progress then went silent — last step completion was 14+ days ago
- Cross-JurisdictionOpen issues touching two or more jurisdictions — per-issue coordination complexity
- UntouchedOpen issues at least a week old with at most one audit entry — nobody has actually worked on them
- New ArrivalsIssues created in the last 7 days — week-on-week delta, severity split, source mix
- Severity MixOpen pile by severity, 90-day net change and median time-to-close per severity
- Cross-JurisdictionOpen issues spanning 2+ jurisdictions — the ones most likely to be mis-owned or escalated late, and where remediation must satisfy every regulator on the list
- Authority LoadOpen issues grouped by originating authority — where regulator attention is concentrating in the open pile
- Jurisdiction LoadOpen issues bucketed by jurisdiction — where the regulator-facing load is concentrated and where overdue debt is pooling
- Impact MixOpen issues bucketed by auto-classified impact — significant, material, minor, informational, unclassified
- Impact UnclassifiedOpen issues with an origin but no impact class — provenance recorded, taxonomy mapping missing
- No JurisdictionOpen issues with no jurisdiction tag — invisible to regulator-routing, board scoping and cross-border rollups
- Severity UnknownOpen issues with no severity recorded — invisible to triage, SLA and risk-ranked queues
- Authority MissingOpen issues with no originating authority recorded — invisible to any regulator-scoped rollup
- Cross-Jurisdiction SpreadSame finding raised across multiple jurisdictions — the difference between a local incident and a systemic one
- Jurisdiction MixOpen pile split by jurisdiction with severity mix and severity-weighted exposure index
Other
Saved views not yet categorised
- My QueuePersonal worklist: open actions, escalations to me, closed by me today
- Stale WaiversWaiver-mode closures unratified beyond a 14-day grace — undocumented exceptions accumulating as governance debt
- Plan EmptyOpen issues with no remediation steps recorded — no plan, no owner, nothing to sample
- Waiver UnratifiedIssues closed under a waiver that was never ratified — unilateral closures on paper
- Classifier UnattributedOpen issues with an impact class but no classifier model recorded — labelling without provenance
- Waiver Decision MissingWaiver-mode closures with no decision reference attached — closures pointing at nothing
- Priority MismatchHigh/critical issues whose priority level lands at normal or muted — the queue is under-rating them
- Finding UnlinkedOpen issues with no findingId — remediation with no trace back to the originating finding
- Ready to CloseOpen issues whose remediation steps are all done — the work is finished, the closure hasn't been recorded
- Snap ClosesIssues closed under 24 hours after creation — fast enough to suggest no real investigation took place
- Long-Lived IssuesOpen issues older than 180 days — the perennial backlog drifting past the half-year horizon
- Waiver RushedWaiver-mode closures landed within 7 days of intake — too fast for the normal decision path
- Closed UnownedClosed issues whose remediation plan had no owner on any step — closed work no one was on the hook for
- No Finding SummaryOpen issues with no finding summary recorded — the register entry exists with no description
- Closed Pre-TargetClosures with half or more of the original SLA window unused — possible premature sign-off
- Reopen RiskClosed issues whose findingId is also on an open issue — the fix may not have taken
- Closed Plan-IncompleteClosed issues whose remediation plan still has unfinished steps — the gap between what we said and what we did
- Reopen After CloseIssues with a recorded closure whose status is no longer resolved — closures that didn't stick, the worst pattern on a regulator sample
- Waiver No-ExpiryWaiver-mode closures whose rationale mentions no expiry, sunset or review point — indefinite waivers that drift past every governance review
- Waiver ExpiredWaiver-mode closures whose rationale references an expiry that has already passed — exceptions running past their own justification
- Lone CloserOwners responsible for an outsized share of closures in the last 365 days — bus-factor risk on the closing side
- New This WeekIssues created in the last 7 days by severity and origin authority, with a delta vs the prior week
- Closed This WeekClosures landed in the last 7 days with inline defensibility flags — the weekly QA pairing for new arrivals
- Recurring FindingsFindings re-raised within 90 days of a previous closure — the strongest 'fix didn't stick' signal in the suite
- Cure Time TrendHow long fixes are holding before the same finding comes back — shrinking gaps mean each remediation wears off faster
- Decision ReuseOne waiver decision cited to close multiple issues — blanket-sign-off risk; mixed-finding groups mean unrelated risk accepted under one signature
- Finding Fan-OutOne originating finding spawning multiple issues — flagged when siblings split (some open, some closed) or scored/closed inconsistently
- Tile CatalogueEvery registered worklist, generated from route-classes.ts — single source of truth for which tiles exist, with self-audit for duplicates and missing trigger sentences
- Field CoverageEvery persisted field on Issue / Closure / RemediationStep mapped to the worklists that defend it — blind-spot audit and structural counterpart to /tile-catalogue
- Regulator SamplePick a random closed issue and see which worklists would flag it — behavioural stop-condition for the defensibility suite
- Board PackSingle-page printable roll-up: open / overdue / severe, closure mix, defensibility flag counts, top owners and jurisdictions — the quarterly board / MLRO surface
- Week-over-Week MoversInsights metrics that got worse since last week — diffed against a daily snapshot, with improvements shown underneath
- Waiver RegisterEvery waiver-mode closure with ratification status, time-to-ratify and stale flags
- Burndown ForecastProjected clear date based on 30/60/90-day net velocity
- Time to CloseClosed-issue distribution by severity with SLA hit rate
- Concentration RiskBus-factor analysis: owner share, jurisdiction share, SPOF owners
- Volume processed12-week opens vs closures with weekly net change and a pace KPI — are we keeping up?
- Source MixOpen pile by originating source — regulator vs internal, severity mix, and a severity-weighted exposure index
- Compliance MaturityDeterministic maturity self-assessment across six dimensions
- Notifications
- Operating MetricsHeadline programme metrics — throughput, SLA, closure mix, defensibility
- Value RealisedCumulative time and effort the platform has saved this tenant — defensible operational ROI