Skip to content
RegAlign LimitedTechnology and professional services

How it fits together

Follow a regulatory change through five areas of work

A fictional example showing the questions a regulatory change can raise for compliance, risk, governance, client relationships and assurance. Each product keeps its own records and decisions.

Worked example

A regulatory change with implications beyond compliance

Worked example · Illustrative

A regulatory change can affect more than compliance

Five separate areas may need attention. Each retains its own evidence, responsibilities and decisions.

Requirement changes

Source, effective date and applicability assessed.

  1. RegAlign®

    Applicability, obligations and control response

  2. RiskAlign®

    Risk exposure, appetite and indicators

  3. GovernAlign™

    Mandates, governance decisions and actions

  4. ClientAlign™

    Relationship criteria and review triggers

  5. AssureAlign™

    Assurance coverage, findings and validation

Illustrative relationships only. Each product maintains its own records and accountable decisions. This is not a representation of live cross-product integration or automated write-back.
  1. 01RegAlign®

    A regulatory change is identified

    The change is captured against its source, assessed for applicability, and translated into obligations with named owners. Rationale and evidence are recorded alongside the assessment.

  2. 02RiskAlign®

    Enterprise risk implications are considered

    The change may alter exposure, appetite thresholds or the relevance of existing indicators. Risk owners consider whether the enterprise risk position needs to be revisited.

  3. 03GovernAlign™

    A governance decision is required

    Where the change exceeds delegated authority, it is routed to the appropriate board or committee with the supporting context. The decision, its rationale and resulting actions are recorded.

  4. 04ClientAlign™

    Relationship handling may be affected

    Acceptance criteria, diligence expectations or review triggers for affected relationships may need to change, with the reason for the change traceable to the original requirement.

  5. 05AssureAlign™

    Assurance responds to the new picture

    Assurance planning can reflect the new obligation and control coverage, test whether the response is operating, and validate remediation where it is not.

This fictional example illustrates the design. It does not show a live customer integration. Each product keeps its own records; authorised people confirm decisions.

What stays separate

  • Each product's records and history
  • Named owners and responsibilities
  • Decisions, which remain with the authorised person or forum

What can be shared

  • Context and references, where permitted
  • Evidence links supporting a decision elsewhere
  • Signals of possible implications or coverage gaps
Read about Compass and Bridge