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.
- Trade Compliance
- Features
- Findings and remediation
Findings and remediation
Track action evidence and independent retests for failed controls.
OverviewActions awaiting verification×
Trade Compliance · Findings and remediation
New
Actions awaiting verification
Approval conditions
| Finding | Owner | Due at | Completed at | Status | |
|---|---|---|---|---|---|
| FND-8302 | 26 Oct | Submitted | |||
| FND-9244 | 15 Oct | Submitted | |||
| FND-3475 | 14 Oct | Submitted | |||
| FND-5225 | 16 Oct | Submitted | |||
| FND-8447 | 26 Oct | Submitted |
6 of 6 records
FND-8302Corrective actions · CA-30884
SubmittedDue at26 Oct
What you can do
Carry an exception to a reviewed result
A finding links an assessment to the control that failed and records severity, description, opening date and status. The corrective action links to that finding, names an owner, and carries due date, completion date, evidence and its own status. These records keep a planned response separate from a verified outcome.
An independent retest records the finding, reviewer, test date, evidence and result. A passing retest can support closing the finding and verifying the action. A failed or inconclusive retest keeps the question open for the reviewer. Action completion is therefore a handoff for assurance, not proof that the underlying control is effective.
How the work is organized
- Describe the deficiency. Link each finding to the assessment and control with its severity.
- Assign the correction. Give the action a team member, due date and evidence of work done.
- Retest separately. Record an independent result before verifying an action or closing a finding.
What to agree during setup
Agree how the Control Owner describes severity and when an action moves from planned to submitted. Name the Independent Assurance Reviewer who will perform the retest, and decide how a failed or inconclusive result goes back to the action owner. Keep the finding and action identifiers together during handoff. Confirm that a completion date alone cannot verify the action or close the finding.
Check the handoff on an actual case
Open a high severity finding against a failed control test and assign a corrective action with a due date. Have the Control Owner submit the evidence of correction, then ask the Independent Assurance Reviewer to record an inconclusive retest. The finding should remain open for further work. Repeat with a passing independent retest and inspect the finding and action statuses together. The Auditor should be able to see both retest results and the evidence behind the final closure.
What your team sees
- Open findings — Group active deficiencies by severity and assessment.
- Actions awaiting verification — Show submitted action evidence that needs independent review.
Rehearse a correction that is submitted before the due date but receives an inconclusive retest. The action owner can see that work was supplied, while the reviewer can keep the finding open pending stronger evidence. This distinction prevents an administrative completion date from being mistaken for assurance that the control now works.
For a failed retest, record the new result and evidence on the retest. The Control Owner can then revise the corrective action while the original finding remains visible to the reviewer.
Follow the work through
See the related process and the record model before agreeing the pilot.
What it keeps track of
Data model- Findings
- Deficiencies raised from failed control tests
- Corrective actions
- Remediation actions assigned against findings
- Retests
- Independent retests of remediated findings
- Controls
- Controls mitigating identified trade compliance risks
- Assessments
- Compliance assessments covering a defined period and scope
Who uses it
Permissions- Control Owner
- , Independent Assurance Reviewer, Auditor.
Set up Trade Compliance your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.