1. GRC for Banking and Financial Services
  2. Features
  3. Findings and remediation
Feature · Findings and remediation

Findings and remediation

Connect testing exceptions to owned corrective work and dated evidence.

OverviewCorrective actions submitted
GRC for Banking and Financial Services · Findings and remediation

Corrective actions submitted

Approval conditions

New
IdFindingOwnerDue atCompleted atStatus
IDD-986FND-687317 OctSubmitted
IDD-794FND-246909 OctSubmitted
IDD-347FND-700110 OctSubmitted
IDD-595FND-897711 OctSubmitted
IDD-539FND-898918 OctSubmitted
6 of 6 records
IDD-986Corrective actions · CA-73044
Submitted
FindingFND-6873
Due at17 Oct
Example screen with sample data

What you can do

Keep the exception attached to its source

A finding records severity, opening date, description, assessment and control. That connection matters: a reviewer should be able to identify which control was examined and which engagement produced the exception. A failed or inconclusive test can support a finding. A passing or pending test should not be recast as one merely to create a work item.

A corrective action belongs to the finding and names an owner. It carries a due date, a target completion date, evidence and a state from Planned through Verified. The action owner explains what will change and records progress. A separate retest decides whether the change resolved the finding. This division prevents an owner marking their own work Verified from standing in for independent examination.

How the work is organized

  • Finding. Record the actual exception with severity and a specific description.
  • Action. Assign a named owner, due date, planned completion date and evidence.
  • Verification. Keep the finding open until independent retest supports closure.

What to agree during setup

Agree how Low, Medium, High and Critical are used and who can correct a misclassified finding. Set a due-date policy that the Remediation Owner and Independent Reviewer can understand. Record the intended completion date when planning the action, then distinguish it from the date work actually finishes when reporting progress.

Decide what evidence is sufficient for a submitted action. A narrative in the action can explain the change, but a reviewer may also need an assessment attachment or a source-system reference. Define who may see internal attachments. The status action planned on the finding and Submitted on its action answer different questions, so do not collapse them into one queue.

Check the handoff on an actual case

Use a failed payment approval test with two exceptions. Open a finding against the same assessment and control, choose High severity and describe the observed gap. Assign an action to a team member with a due date and evidence explaining the revised procedure. The owner moves the action into progress and submits the result for review.

Ask the owner to try closing the finding. The closure should wait for a separate reviewer and a passing retest. If the retest fails or remains inconclusive, keep the issue open and plan another response. The reviewer should be able to see the original test, the action evidence and the latest retest without relying on a verbal handoff.

What your team sees

  • Open findings — Review severity and status for issues still needing action or retest.
  • Action owner queue — Show assigned action due dates and current state.
  • Corrective actions submitted — Find work awaiting independent examination.

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.
Retests
Independent retests that decide whether a finding may be closed.
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
Remediation Owner
, Assessment Owner, Independent Reviewer, Admin.

Set up GRC for Banking and Financial Services your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started