1. Trade Compliance
  2. Features
  3. Control testing
Feature · Control testing

Control testing

Tie each test result to a control and its supporting evidence.

OverviewTests awaiting result
Trade Compliance · Control testing

Tests awaiting result

Approval conditions

New
ParentControlControl codeResultEvidence reference
ASS-15000CNT-9624CC-233PendingER-663
ASS-68177CNT-1069CC-735PendingER-967
ASS-27898CNT-8073CC-129PendingER-400
ASS-77259CNT-8565CC-529PendingER-143
ASS-40885CNT-2051CC-444PendingER-237
6 of 6 records
CC-233Assessment tests · AT-46709
Pending
ParentASS-15000
ControlCNT-9624
Evidence referenceER-663
Example screen with sample data

What you can do

Make a result inspectable

Each test belongs to an assessment and a named control. The test can carry its line number, revision, date, sample size and exception count. The result distinguishes pending, passed, failed and inconclusive work. An evidence reference gives the reviewer a path to the material behind that result; a blank or inconclusive result should not be treated as a pass.

For a failed test, the Control Owner can inspect the linked control and raise a finding describing the deficiency. The reviewer looks at the test result alongside the exception count and evidence before accepting the assessment outcome. If the team changes a test record, preserve the revision context so the earlier reviewer decision remains explainable.

How the work is organized

  • Select the control. Use the control linked to the assessment test and check its effective date.
  • Record the sample. Keep the test date, sample size, exception count and result together.
  • Explain an exception. Supply an evidence reference and raise a finding when a failed result needs correction.

What to agree during setup

Set a rule for choosing the control that applies to the assessment period. Agree how testers record an inconclusive result and what evidence reference the Independent Assurance Reviewer needs to inspect a failure. Decide who compares exception count with sample size before the assessment moves into review. Keep the test revision and parent assessment visible when a result changes.

Check the handoff on an actual case

Have the Control Owner enter a test against a named control with a sample size, exception count and evidence reference. Record a failed result and open a finding against the same assessment and control. Ask the Independent Assurance Reviewer to follow the reference to the evidence and confirm that missing material is never treated as a pass. Repeat with an inconclusive result and ask the owner to explain what further work is needed before the assessment can be reviewed.

What your team sees

  • Tests awaiting result — Find tests that still need a recorded result and evidence.
  • Failed control tests — Inspect exceptions and the supporting control before remediation.

During rehearsal, use one passed test and one failed test against different controls. Ask the reviewer to find the sample size, exception count and evidence reference for each. An inconclusive result deserves an explanation and a next action; it should remain distinct from both a pass and a failure in the review queue.

Follow the work through

See the related process and the record model before agreeing the pilot.

What it keeps track of

Data model
Assessment tests
Individual control tests executed within an assessment
Assessments
Compliance assessments covering a defined period and scope
Controls
Controls mitigating identified trade compliance risks
Findings
Deficiencies raised from failed control tests
Record attachments
Evidence files attached to assessment records

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.

How to get started