These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Regulatory Change Management
- Process
- Test a control and raise a finding
Test a control and raise a finding
Capture test evidence and turn an exception into an owned finding.
Step by step
-
Open the assessment Control Owner
The Control Owner selects the current testing record and its scoped business unit.
- Establish test context
- Updates Assessments 2
-
Identify the control Control Owner
The test line points to the control being examined and records its code.
- Link the test to a control
- Updates Controls 2, Assessment tests 2
-
Perform the test Control Owner
The owner records the test date, sample size, exception count and evidence reference.
- Record sample and evidence
- Updates Assessment tests 2
-
Choose the result Control Owner
The owner marks the line pending, passed, failed or inconclusive according to the evidence.
- Record the test outcome
- Updates Assessment tests 2
-
Raise a finding Control Owner
A failed result can lead to a finding with severity and a description tied to the control.
- Describe the issue and severity
- Updates Findings 2
-
Hand off for action Control Owner
The team assigns corrective work against the finding.
- Assign follow-up work
- Updates Corrective actions 2, Findings 2
Who does what
Roles and permissions- Control Owner
- Records the test and finding; Independent Assurance Reviewer examines the evidence; Auditor reads the final test history.
Set up Regulatory Change Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.