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
- Features
- Remediation and Retests
Remediation and Retests
Carry findings through corrective work and independent retesting.
OverviewCorrective Actions for Verification×
Regulatory Change Management · Remediation and Retests
New
Corrective Actions for Verification
Approval conditions
| Due at | Completed at | Status | Finding | Owner | Evidence | |
|---|---|---|---|---|---|---|
| 08 Oct | Submitted | FND-2888 | EVD-309 | |||
| 27 Oct | Submitted | FND-2413 | EVD-408 | |||
| 04 Oct | Submitted | FND-3945 | EVD-306 | |||
| 06 Oct | Submitted | FND-7784 | EVD-614 | |||
| 16 Oct | Submitted | FND-9995 | EVD-462 |
6 of 6 records
EVD-309Corrective actions 2 · CA-96284
SubmittedDue at08 Oct
FindingFND-2888
What you can do
Keep the corrective work with the finding
A finding can lead to a corrective action with an owner, due date, status, completion date and evidence. This gives the team a concrete commitment to review after a test reveals an issue. A planned action is different from work in progress; submitted work is ready for verification, while verified work has passed that step. The action remains linked to the finding throughout the sequence.
The retest is a separate record. It names a reviewer, test date, result and evidence, and links back to the finding. That separation helps the Independent Assurance Reviewer make an independent judgment about whether the corrected control now works. A failed or inconclusive retest remains visible while the team decides the next action. The retest result alone does not change the finding or action status.
How the work is organized
- Commitment. Assign a corrective action to an owner and record when it is due.
- Submission. Keep completion evidence with the action when the owner submits it.
- Verification. Record a retest result and evidence against the original finding.
What to agree during setup
Agree who may own an action and who acts as an independent reviewer. Set a standard for evidence that shows the change was completed, and a separate standard for evidence that the control now performs as intended. A due date should support practical follow-up, while a completion date records when the work actually ended. The team also needs a way to respond when a retest fails or cannot reach a conclusion.
Take a high-severity finding from an assessment. The owner proposes the corrective work and due date. When the work is complete, the owner records evidence and submits it. The reviewer then performs a retest and records the result. If the retest passes, the team can consider closing the finding. If it fails, the finding remains in the working queue with its history intact.
Check the handoff on an actual case
Open a finding with a corrective action. Confirm the action owner, due date, status and evidence correspond to the issue described in the finding. Ask the reviewer to locate the original test result and the control before recording a retest. Compare the retest evidence with the action evidence; they answer different questions. The first explains the work performed, while the second supports the independent outcome.
Check what the next owner sees if the due date has passed or the retest is inconclusive. The action and finding statuses should make the remaining work clear. The case should retain the record of the original failure even after a successful retest, allowing the team to explain how the issue was resolved.
What your team sees
- Corrective Actions for Verification — Review submitted action evidence against its finding.
- My Corrective Actions — Follow assigned work by due date and status.
- Retest Results — Compare independent outcomes and supporting evidence.
Follow the work through
See remediation and review a rule change.
What it keeps track of
Data model- Findings 2
- Control test findings raised from assessment scope
- Corrective actions 2
- Remediation actions owned against findings
- Retests 2
- Independent retests confirming remediation
- Team members 2
- Named staff with operational roles and organization membership
- Controls 2
- Controls mitigating registered risks
- Assessments 2
- Impact and control assessment periods per organization and owner
Who uses it
Permissions- Control Owner
- Prepares corrective work.
- Independent Assurance Reviewer
- Examines retest evidence and outcome.
- Auditor
- Inspects the completed trail.
Set up Regulatory Change Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.