Principles:
Each change in process, system, control, scorecard is documented
all changes are subject to 4-eyes check
Major changes (based on severity/impact) are subject to layered approval process
All changes are subject to “User Acceptance Testing” and result is part of documentation for approval
Major changes (based on BIA of affected processes) may require review from business continuity management perspective
There is always up-to-date documentation of actual state
such as Credit risk policy, Scorecard documentation, Fraud rules
There is a clear changelog describing differences between versions
with Date, Author, Approver if needed and description of the change
if the change is major, copy the change-compare page as reference
changelog is propagated upstream (change of policy control must be reflected also in strategy changelog)
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:
Change to collections parameters with impact:
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) |
Attachments:
image-20220529-064658.png (image/png)
image-20220529-064905.png (image/png)
image-20220529-064936.png (image/png)