SaFi Bank Space : Change Management Guidelines

Principles:

  1. Each change in process, system, control, scorecard is documented

    1. all changes are subject to 4-eyes check

    2. Major changes (based on severity/impact) are subject to layered approval process

    3. All changes are subject to “User Acceptance Testing” and result is part of documentation for approval

    4. Major changes (based on BIA of affected processes) may require review from business continuity management perspective

  2. There is always up-to-date documentation of actual state

    1. such as Credit risk policy, Scorecard documentation, Fraud rules

  3. There is a clear changelog describing differences between versions

    1. with Date, Author, Approver if needed and description of the change

    2. if the change is major, copy the change-compare page as reference

    3. changelog is propagated upstream (change of policy control must be reflected also in strategy changelog)

  4. Despite all versions are saved in Confluence history, Major changes as created as new version (copy) of the document and previous version goes to “Archive folder”

Changelog implementation

Each important documentation holds a “_changelog page” and “_archive page”

The documentation changelog holds a table that summarize the changes and changes of child pages (if applicable)

Original Page includes link to Changelog and Archive for better navigation

Approval Process Principles

Process/Change

Levels of Approval

Levels of testing

Change to UW parameter

Change to Collections strategy parameter

Addition to Slacker OR early warning system parameters with expected low impact to hit rate

Head of relevant department

Fast-Track type of testing

Change to UW parameter with impact:

  • approval rate > +-2% relative

  • risk > +-5% relative

  • any other significant impact to UW flow or operational capacity

Change to collections parameters with impact:

  • capacity or technical capacity (lines) > +-5% relative

Update to Antifraud strategy

Any new model or update to existing model

Head of Relevant department

CRO

Fast-track type of testing

case by case individual UATs (targeting the change)