Get started
Change Management
CG-09

Approve emergency changes within one day and notify the bank within one

How Leela would run itEvent-driven · each emergency change; approval within one business day, bank notice within one business day of implementation
From the policy library
The requirement
Where a security incident, a critical system failure, or a regulatory mandate with an immediate deadline requires an urgent change, the process may be accelerated with the approval of the Compliance Officer and the CEO. The Compliance Officer reviews the compliance implications immediately, the approval decision is made within one business day, the sponsor bank is notified within one business day of implementation with full documentation, the change is validated and monitored after implementation, and a root cause analysis and process review follow once the situation is resolved. A regulatory deadline that cannot be met on the routine timeline uses this procedure.
Applies
Tell Leela about your company to see whether this applies.
Status
Setup needed

Tell Leela how you handle it today, or hand it over: see what’s next.

The work

Record the emergency and its justification, obtain the two approvals inside the day, send the bank the full documentation within a business day of implementation, schedule the validation, and complete the root cause review once the emergency is over.

What Leela keepsThe evidence this obligation leaves, as the work happens
Listed from the policy library
Contents
  1. 01
    Emergency change record
    Trigger, justification, Compliance Officer and CEO approvals with times
  2. 02
    Emergency bank notice
    Full documentation and root cause explanation, date sent, hours after implementation
  3. 03
    Root cause analysis
    Cause, process changes, date completed
Evidence
Emergency change record
Change Management §9, §10
3
of 3 records

The work and the records come from this obligation in the policy library.

What’s next?