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.
- Construction GRC
- Features
- Findings and corrective actions
Findings and corrective actions
Turn failed tests into owned correction work with due dates and evidence.
OverviewCorrective actions awaiting retest×
Construction GRC · Findings and corrective actions
New
Corrective actions awaiting retest
Verified waits for the independent reviewer
| Id | Finding | Owner | Due at | Status | Evidence | |
|---|---|---|---|---|---|---|
| IDD-349 | FND-3528 | 07 Oct | Submitted | EVD-980 | ||
| IDD-590 | FND-8622 | 27 Oct | Submitted | EVD-358 | ||
| IDD-132 | FND-1349 | 03 Oct | Submitted | EVD-109 | ||
| IDD-157 | FND-8231 | 09 Oct | Submitted | EVD-891 | ||
| IDD-723 | FND-3134 | 03 Oct | Submitted | EVD-605 |
6 of 6 records
IDD-349Corrective actions · CA-55375
SubmittedFindingFND-3528
Due at07 Oct
EvidenceEVD-980
What you can do
Keep the exception attached to the test
A failed or inconclusive control test can lead to a finding. The finding records severity, opening date, description, assessment and control. The source test remains available for the reviewer to inspect. The correction belongs in a separate corrective action with its own owner, due date, evidence and status. This separation keeps the observed problem distinct from the work proposed to resolve it.
The finding workflow refuses a pass or pending test. The remediation workflow assigns an action and places the finding in action planned. The action owner may move the action through planned, in progress and submitted. Their update cannot mark the action verified or close the finding. Closure belongs to a later independent retest.
How the work is organized
- Severity. Agree how the team applies low, medium, high and critical to construction compliance issues.
- Due date. Set a correction deadline the owner can act on and the manager can monitor.
- Evidence. Decide what completion evidence must be submitted before a reviewer retests.
What to agree during setup
The Finding Owner and Compliance Manager should rehearse how this work is assigned and reviewed. Agree which organization and business unit own the first case, who may update it, and where its supporting evidence lives. Set a clear handoff when the person preparing the record is different from the person checking its outcome. Use the same rule for routine work and exceptions so an urgent item does not lose its owner or history.
For the pilot, use a failed test whose assessment and control are clear. Agree how its severity is chosen, who owns correction and when the action is due. The owner should submit evidence without changing the finding to closed; the Independent Reviewer needs that original test when retesting.
Check the handoff on an actual case
Use a failed control test with a clear exception description. Register the finding, then assign a corrective action with an owner and due date. Have that owner submit evidence of completed work. The action should appear in the reviewer’s queue while the finding remains open for independent checking. Try to close the finding through an owner status update; it must not work. A second request using the same operation key should resolve to the original finding or action.
Open Open findings and check that the severity, assessment and control match the failed test. In Corrective actions awaiting retest, confirm that the submitted action has an owner, due date and evidence. The finding should stay open until the independent reviewer records a passing retest.
What your team sees
- Open findings — Unresolved findings grouped by assessment, control and severity.
- Corrective actions awaiting retest — Submitted corrections ready for a separate reviewer.
Follow the work through
See the related process for the stage-by-stage handoff. Use the data model to inspect the record relationships and implementation to plan the first rehearsal.
What it keeps track of
Data model- Findings
- Findings raised from failed or inconclusive control testing.
- Corrective actions
- Remediation actions assigned to a finding owner with due dates and evidence.
- Assessment tests
- Individual control tests executed under an assessment.
- Assessments
- Scoped assessment engagements driven through a status lifecycle.
- Controls
- Controls that mitigate a risk and are executed by a named owner.
Who uses it
Permissions- Finding Owner
- , Assessment Owner, Compliance Manager, Independent Reviewer.
Set up Construction GRC your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.