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
- Control testing
Control testing
Record sample size, exceptions, results and evidence for scoped tests.
OverviewFailed control tests×
Construction GRC · Control testing
New
Failed control tests
Assessment tests
| Id | Parent | Control | Sample size | Exception count | Result | |
|---|---|---|---|---|---|---|
| IDD-608 | ASS-24990 | CNT-2760 | 600 | 40 | Fail | |
| IDD-647 | ASS-51892 | CNT-9947 | 810 | 31 | Fail | |
| IDD-847 | ASS-17850 | CNT-8900 | 420 | 35 | Fail | |
| IDD-366 | ASS-80295 | CNT-9093 | 540 | 16 | Fail | |
| IDD-133 | ASS-14025 | CNT-6547 | 640 | 23 | Fail |
6 of 6 records
IDD-608Assessment tests · AT-94390
FailParentASS-24990
ControlCNT-2760
Sample size600
Exception count40
Evidence referenceER-720
What you can do
Record the result against the planned control
Each assessment test belongs to one assessment and one control. The Assessment Owner records when it was tested, the sample size, exception count, evidence reference and result. A result can be pending, pass, fail or inconclusive. The evidence reference makes the conclusion checkable by another person without moving the test to a different assessment or control.
The testing workflow rejects an exception count larger than the sample and refuses a passing result that has no evidence reference. It can move the parent assessment into testing or review after recording the test. A failed or inconclusive result may then be the source for a finding. A passing or pending test is not a valid source for that finding workflow.
How the work is organized
- Sample rule. Agree what makes an item eligible for the sample and when an exception is counted.
- Evidence reference. Use a stable reference that the reviewer can open in the agreed document location.
- Result meaning. Decide when an incomplete sample is inconclusive rather than passed or failed.
What to agree during setup
The Assessment 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, agree what constitutes one sample item and one exception on the selected control. Keep the evidence reference usable by the Compliance Manager. Test an oversized exception count and a pass without evidence before recording the failed result that will become a finding.
Check the handoff on an actual case
Take a scoped control test and enter a sample with an exception count within its size. Add the tested date and evidence reference, then record a failed result. Open the test from its assessment and confirm the control relationship. Next, try a pass without evidence and an exception count greater than the sample; both requests should be refused. Register a finding from the failed result and verify that it carries the same assessment and control.
From Failed control tests, open the failed result and compare its sample, exceptions and evidence reference with the linked finding. If testing times out, inspect the existing result and receipt before retrying. The second request should not replace the first observation.
What your team sees
- Failed control tests — Failed samples with exception counts and evidence references.
- Tests requiring evidence — Pending and inconclusive tests that need follow-up.
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- 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.
- Findings
- Findings raised from failed or inconclusive control testing.
Who uses it
Permissions- Assessment Owner
- , Control Owner, Compliance Manager.
Set up Construction GRC your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.