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.
- Compliance Management
- Features
- Findings and remediation
Findings and remediation
Assign a correction and check the result independently.
OverviewCorrections awaiting verification×
Compliance Management · Findings and remediation
New
Corrections awaiting verification
Approval conditions
| Finding | Status | Due at | Completed at | Evidence | Owner | |
|---|---|---|---|---|---|---|
| FND-6718 | Submitted | 04 Oct | EVD-121 | |||
| FND-3300 | Submitted | 21 Oct | EVD-191 | |||
| FND-9892 | Submitted | 12 Oct | EVD-219 | |||
| FND-8981 | Submitted | 16 Oct | EVD-618 | |||
| FND-8536 | Submitted | 24 Oct | EVD-652 |
6 of 6 records
EVD-121Corrective actions · CA-50209
SubmittedFindingFND-6718
Due at04 Oct
What you can do
Turn a failed check into owned work
A finding describes the issue found in an assessment and connects it to the affected control. Its severity and status let the Compliance Lead see which issues need a plan, which are awaiting retest and which are closed. A corrective action carries the assigned owner, due date, evidence and completion status. This keeps the person fixing the problem accountable for a specific response.
Imagine a failed approval sample reveals that an operating step was skipped. The Tester records the failed test, then describes the finding in terms the Control Owner and Remediation Owner can act on. The lead checks its severity. The Remediation Owner plans a correction with a due date and records evidence of completed work before asking for verification.
How the work is organized
- Finding. The team records the issue, its severity, assessment and affected control.
- Correction. The Remediation Owner moves the assigned action through planned, in progress and submitted work.
- Verification. The Independent Reviewer records a retest result and evidence against the finding.
What to agree during setup
Agree who sets severity and who can close a finding. The person who performs the corrective work should be distinct from the person who tests its effectiveness. Decide what evidence is enough for a correction to be submitted and what sample or observation is expected for the retest. A due date should reflect the real operating commitment, not merely the end of an assessment period.
The team also needs a response for a failed or inconclusive retest. Those outcomes should send the finding back for work or further examination, with the evidence retained. A submitted correction alone does not establish that the control now works. The Independent Reviewer is accountable for the follow-up result.
Check the handoff on an actual case
Open a finding from a failed control test. Confirm its description explains the observed exception and its links lead to the correct assessment and control. Assign one corrective action to a named Remediation Owner, set a due date and have that person attach the evidence reference for the completed fix. The owner submits the action for review.
Have a different person perform the retest and record the date, result and evidence. If it passes, the team can verify the corrective action and close the finding. If it fails or remains inconclusive, the lead can see that the issue still needs attention. Review the action and retest together before changing the assessment’s overall status.
What your team sees
- Findings needing action — Open, planned and retest findings by severity and assessment.
- My corrective actions — Assigned corrective work with due dates and evidence.
- Corrections awaiting verification — Submitted fixes ready for independent checking.
Follow the work through
See testing and remediation and assessment cycle.
What it keeps track of
Data model- Findings
- An issue uncovered during an assessment that the team needs to resolve.
- Corrective actions
- A fix someone owns for a finding, tracked from assignment through completion.
- Retests
- A follow-up check confirming a fixed finding actually stayed fixed.
- Assessments
- A review project for a period, tracked from planning through approval.
- Controls
- A safeguard the team relies on to keep a specific risk in check.
- Team members
- A person working in the organization, with their role and status.
Who uses it
Permissions- Compliance Lead
- , Remediation Owner, Independent Reviewer, Control Owner.
Set up Compliance Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.