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.
- GRC for Banking and Financial Services
- Features
- Assurance review
Assurance review
Record independent decisions against an assessment revision with a reason.
OverviewPrudential review inbox×
GRC for Banking and Financial Services · Assurance review
New
Prudential review inbox
Approval conditions
| Id | Parent | Organization | Control area | Regulator reference | Revision | |
|---|---|---|---|---|---|---|
| IDD-135 | ASS-52525 | ORG-2198 | CA-283 | RR-553 | 910 | |
| IDD-790 | ASS-29135 | ORG-2534 | CA-243 | RR-212 | 880 | |
| IDD-421 | ASS-76075 | ORG-4124 | CA-314 | RR-552 | 770 | |
| IDD-492 | ASS-36930 | ORG-8201 | CA-872 | RR-868 | 470 | |
| IDD-824 | ASS-44316 | ORG-2451 | CA-458 | RR-132 | 230 |
6 of 6 records
IDD-135Prudential control reviews · PCR-45040
SubmittedParentASS-52525
OrganizationORG-2198
Control areaCA-283
Regulator referenceRR-553
Revision910
What you can do
Keep judgment tied to the reviewed version
A review decision points to an assessment and records its source revision, reviewer, date, decision and reason. Approve, Reject and Return are distinct responses. The reviewer can approve the examined submission, reject it or send it back for work. The decision concerns that revision; a later edit to the assessment should not silently inherit the earlier approval.
Prudential control reviews add control-area and regulator-reference context under an assessment and organization. Their statuses include Draft, Submitted, Approved, Rejected and Completed. The organization can compare review decisions with test evidence and findings, while keeping the reviewer’s judgment separate from the outcome of the parent assessment.
How the work is organized
- Submission. Place the relevant assessment revision and evidence before the reviewer.
- Decision. Record a named reviewer, substantive reason and decision for that revision.
- Context. Keep prudential control area, reference and exceptions with the review record.
What to agree during setup
Agree who may submit an assurance review and who may decide it. A reviewer should be independent of preparing the work being judged. Define what a Return means for revisions and whether a Reject requires a new submission. Keep decision reasons specific enough that the preparer can respond and a later reader can understand what was examined.
Agree how the regulator reference is named and maintained for each organization, and which control area the review covers. The reviewer should be able to locate the referenced material and identify the assessment under review. Agree whether exceptions are counted at review level or read from individual control tests; those numbers should have a documented interpretation before they appear in a report.
Check the handoff on an actual case
Submit a prudential control review for a chosen assessment revision. Include its organization, control area and regulator reference, then have an Independent Reviewer examine the linked tests and findings. Record a Return with a reason asking for clearer evidence. Revise the material and submit again, retaining the earlier decision.
Try an approval against a source revision that no longer matches the submission. The reviewer should examine the current version rather than silently approving the change. Also confirm that an Approved prudential review or an Approve decision does not move the parent assessment by itself. An assessment can still have open findings or remediation work after a review decision.
What your team sees
- Prudential review inbox — Find submitted review records with their control area and source revision.
- Assessments in review — See assessments whose current work is awaiting review.
Follow the work through
What it keeps track of
Data model- Prudential control reviews
- Prudential control reviews covering regulator references and control areas.
- Review decisions
- Independent reviewer decisions recorded against an assessment revision.
- Assessments
- Scoped assessment engagements driven through a status lifecycle.
- Assessment tests
- Individual control tests executed under an assessment.
- Findings
- Findings raised from failed or inconclusive control testing.
Who uses it
Permissions- Independent Reviewer
- , Assessment Owner, Risk Manager, 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.