Inside RegAlign — a working day

AR
System walkthrough

Twelve steps through the actual product.

This walkthrough links to live screens in the Saltire seed tenant — monitoring plan → test → per-item evidence → maker–checker close → finding → action → business response → validation → governance reporting. RegAlign Compass appears throughout as a suggest-only assistant; it cannot approve, decide or provide legal advice.

Pronounced Reg-align — "Reg" as in regulatory.

  1. 1

    Land on Today

    Wired

    Open Today — six curated slots that tell you what to do first this morning. This is the new day-one landing surface; the wider firm overview is one click away.

    What to look for: Tenant: Saltire seed (read-only). Notice the persona switcher in the top bar. Today replaced /overview as the post-login landing in the June 2026 release.

    Open
  2. 2

    See the obligations

    Wired

    The obligation library this firm is being held against.

    What to look for: JFSC codes ingested with SHA-256 receipts; click any obligation to see linked controls.

    Open
  3. 3

    Read the compliance risk assessment

    Wired

    The current CRA — scoring, domain overrides, framework parameters.

    What to look for: Annual board assessment lives one click away; supersession is in the audit trail.

    Open
  4. 4

    Open the monitoring programme

    Wired

    All in-flight tests, by cadence and owner. Overdue items raise auto-findings.

    What to look for: Cadence is enforced server-side; missing a test is its own audit event.

    Open
  5. 5

    Inspect the coverage matrix

    Wired

    Obligation × control × test — where is monitoring actually covering the risk?

    What to look for: Gaps are highlighted; the matrix exports into the regulator pack.

    Open
  6. 6

    Open one monitoring test

    Wired

    Pick any test to see the script version, sample selection and attribute checklist.

    What to look for: Per-item attributes, per-item evidence with SHA-256 receipts, freshness gate on the snapshot, tolerable-rate threshold locked at submission.

    Open
  7. 7

    Maker–checker close

    Wired

    Submit for review — the reviewer must be a different person than the preparer.

    What to look for: Reviewer banner shows on the test detail. Override of independence requires recorded rationale.

    Open
  8. 8

    Findings → actions

    Wired

    Item-level failures roll up into findings; findings spawn actions with owners and dates.

    What to look for: Re-tests close the chain by referencing the original failing item.

    Open
  9. 9

    Business owner picks it up

    Wired

    Action owner sees their queue and uploads evidence against the action.

    What to look for: Secure task link / digest email exists for users without a permanent seat.

    Open
  10. 10

    Validation

    Wired

    Independent validator confirms remediation; validator ≠ accepter.

    What to look for: Closure approval is a separate decision in the audit trail.

    Open
  11. 11

    Governance reporting

    Wired

    Roll-up for the compliance committee: tests, findings, actions, breaches.

    What to look for: Every figure on the board pack is traceable to a query and a snapshot id.

    Open
  12. 12

    Board pack

    Wired

    Time-aware board pack — last Thursday vs. live.

    What to look for: Compass-drafted board statement is suggest-only and clearly marked. No autonomous closure or approval.

    Open
Nothing on this walkthrough is auto-executed by AI. Every decision — close a test, raise a finding, accept evidence, validate remediation, publish a board pack — is taken by a person and recorded in the audit trail. How Compass works.
See what's wired vs scripted Narrated tour