---
title: "Manage deficiencies, exceptions and risk acceptance"
description: "Work the deficiencies that failed control tests raise, move them through remediation to a passing retest, or accept the risk with a justification and a review date."
url: https://helpcenter.complytrain.net/en/articles/216-manage-deficiencies-exceptions-and-risk-acceptance
collection: "Operate and test"
updated: 2026-09-22
language: en
---

# Manage deficiencies, exceptions and risk acceptance

Work the deficiencies that failed control tests raise, move them through remediation to a passing retest, or accept the risk with a justification and a review date.

Work the deficiencies that failed control tests raise, move them through remediation to a passing retest, or accept the risk with a justification and a review date.

A deficiency is the record that a control test failed and what was done about it. The product also calls it an exception: the failure policy **Open an exception** creates one, and a control's **Exceptions** tab shows its **Deficiency history**. Deficiencies are never created by hand. Each one ends in one of two ways: a passing retest closes it, or someone accepts the risk instead of fixing the control.

A deficiency is different from a segregation exception, which lets someone test a control they also operate. For those, see [govern control definitions and versions](https://help.complytrain.net/en/controls/control-governance/).

## Who can do this

Product location: `/qms/controls/deficiencies`. Open Deficiencies in Controls.

<table style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Task</p></th><th colspan="1" rowspan="1"><p>What you need</p></th></tr><tr><td colspan="1" rowspan="1"><p>See the <strong>Deficiency register</strong> and a control's deficiency history</p></td><td colspan="1" rowspan="1"><p><strong>View controls</strong> (<code>controls:view_controls</code>)</p></td></tr><tr><td colspan="1" rowspan="1"><p>Record the cause, change severity, owner or due date, move a deficiency between stages, and record the retest</p></td><td colspan="1" rowspan="1"><p><strong>Manage controls</strong> (<code>controls:manage_controls</code>)</p></td></tr><tr><td colspan="1" rowspan="1"><p>Accept the risk</p></td><td colspan="1" rowspan="1"><p><strong>Accept control risk</strong> (<code>controls:accept_control_risk</code>)</p></td></tr></tbody></table>

Admins can do all of these. Buttons you cannot use are not shown.

## How a deficiency is raised

Product location: `/qms/controls/deficiencies`. Open Deficiencies in Controls.

A failing test raises a deficiency when the failure policy that applies is **Open an exception**, **Exception, then CAPA** or **Create an action item**. It is raised when the result counts: as soon as the test is saved, or, if the control needs a second approver, when the result is approved. A rejected result raises nothing. **Log only** raises nothing, and **CAPA directly** opens a CAPA without a register entry. See [test a control and get it signed off](https://help.complytrain.net/en/controls/test-signoff-deficiencies/#preview-a-failing-verdict).

The new deficiency gets a reference number, a title naming the control and what failed, and:

<table style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Setting</p></th><th colspan="1" rowspan="1"><p>How it is set</p></th></tr><tr><td colspan="1" rowspan="1"><p>Severity</p></td><td colspan="1" rowspan="1"><p><strong>Critical</strong> when the design has gaps and the control did not run as designed. <strong>High</strong> when the design has gaps, or the control did not run as designed. <strong>Medium</strong> when it only ran with gaps. <strong>Low</strong> is available when you reassess a deficiency.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Due date</p></td><td colspan="1" rowspan="1"><p>By default 7 days after the deficiency is raised for <strong>Critical</strong>, 14 for <strong>High</strong>, 30 for <strong>Medium</strong> and 60 for <strong>Low</strong>.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Owner</p></td><td colspan="1" rowspan="1"><p>The implementation's owner, or the control's owner if the implementation has none.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Status</p></td><td colspan="1" rowspan="1"><p><strong>Open</strong></p></td></tr></tbody></table>

The owner receives **Control Deficiency Raised**. Under **Exception, then CAPA**, a corrective CAPA with the source **Control Test Failure** is also opened, linked to the control and the deficiency, with the CAPA severity critical for a critical deficiency, major for high, and minor for medium or low. Work it in QMS; see [manage corrective and preventive actions](https://help.complytrain.net/en/qms/create-and-progress-capa/). Under **Create an action item**, an action item is assigned to the owner with the same due date.

## Read the deficiency register

Product location: `/qms/controls/deficiencies`. Open Deficiencies in Controls.

Open **Controls**, then **Deficiencies**. The **Deficiency register** starts with figures for the whole organisation:

<table style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Figure</p></th><th colspan="1" rowspan="1"><p>What it counts</p></th></tr><tr><td colspan="1" rowspan="1"><p><strong>Still outstanding</strong></p></td><td colspan="1" rowspan="1"><p>Deficiencies that are <strong>Open</strong>, <strong>Being fixed</strong> or <strong>Awaiting retest</strong>.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>High or critical</strong></p></td><td colspan="1" rowspan="1"><p>Outstanding deficiencies of those severities.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Past their date</strong></p></td><td colspan="1" rowspan="1"><p>Outstanding deficiencies whose due date has passed.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Risk accepted</strong></p></td><td colspan="1" rowspan="1"><p>Deficiencies settled by accepting the risk.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Escalated to CAPA</strong></p></td><td colspan="1" rowspan="1"><p>Deficiencies with a CAPA.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Closed by retest</strong></p></td><td colspan="1" rowspan="1"><p>Deficiencies closed by a passing retest.</p></td></tr></tbody></table>

Filter with **Any status**, **Any severity**, **Any owner**, **Outstanding only** and **Overdue only**; **Clear filters** resets them. The table shows **Reference**, **Control**, **Severity**, **Owner**, **Due** (with, for example, **5 days overdue**, or for an accepted risk **Until** a date or **No expiry**), **Status** and **Escalated to** (the CAPA number, or **Action item**).

## Work a deficiency

Product location: `/qms/controls/deficiencies`. Open Deficiencies in Controls.

Select a row to open it. The top of the dialog shows the **Control**, **Implementation**, **Where**, **Period tested**, **Design** and **Operation** verdicts, the **Policy applied** and where it came from, and any **CAPA** with its status.

Under **Work this deficiency**:

1.  Enter **Why did the control fail?** This is the field most often left blank and the one a reviewer needs most.
    
2.  Adjust **Severity**, **Owner** or **Due** if your assessment differs, and choose **Save**.
    
3.  Move the deficiency on as work progresses:
    

<table style="min-width: 75px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Status</p></th><th colspan="1" rowspan="1"><p>Button to reach it</p></th><th colspan="1" rowspan="1"><p>Allowed from</p></th></tr><tr><td colspan="1" rowspan="1"><p><strong>Being fixed</strong></p></td><td colspan="1" rowspan="1"><p><strong>Start fixing it</strong></p></td><td colspan="1" rowspan="1"><p><strong>Open</strong>, <strong>Awaiting retest</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Awaiting retest</strong></p></td><td colspan="1" rowspan="1"><p><strong>Ready to retest</strong></p></td><td colspan="1" rowspan="1"><p><strong>Open</strong>, <strong>Being fixed</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Open</strong></p></td><td colspan="1" rowspan="1"><p><strong>Back to open</strong></p></td><td colspan="1" rowspan="1"><p><strong>Being fixed</strong></p></td></tr></tbody></table>

There is no button to close a deficiency. The panel **How this closes** explains why and offers **Open the control**.

## Close it with a passing retest

Product location: `/qms/controls/{controlId}` (fallback: `/qms/controls/deficiencies`). Open the deficiency and choose Open the control, then select the Tests tab.

1.  Choose **Open the control**, then **Tests**, then **Record a test**.
    
2.  Under **Does this answer an open deficiency?**, choose the deficiency.
    
3.  Record the retest as usual and choose **Save**.
    

If the retest passes, the deficiency closes when the result counts: as soon as the retest is saved, or, if the control needs a second approver, when the retest is approved. It then shows **How it closed**; the register counts it under **Closed by retest**, and the control's **Exceptions** tab shows **Retest passed** with the date. If the retest fails, the original deficiency stays open and the retest raises a new one, so the register shows both attempts. Move the original back to **Being fixed** and continue.

A closed deficiency can no longer be edited, because what it looked like when it was settled is part of the record.

## Accept the risk instead

Product location: `/qms/controls/deficiencies`. Open Deficiencies in Controls.

Accepting the risk settles a deficiency without the control being fixed: your organisation decides to live with the exposure. It is permanent in the record. The section **Accept the risk instead** is available while the deficiency is not closed or already accepted.

1.  Open the deficiency and go to **Accept the risk instead**.
    
2.  Enter **Why is this acceptable?**, for example "Compensating control CTL-9 covers the same failure mode until the platform migration lands in Q1." It is required.
    
3.  Enter **Review it again on**. It cannot be in the past. Leave it empty only if the acceptance is genuinely permanent.
    
4.  Choose **Accept the risk**.
    

The acceptance is recorded in your name, as the person with **Accept control risk** who accepted it, together with the date and your justification. The status becomes **Risk accepted**, and the dialog shows **Accepted by** and **Justification**, which stay readable after any expiry.

From 14 days before the review date, the deficiency owner is reminded with **Risk Acceptance Expiring**. Once the review date has passed, the deficiency returns to **Open** by itself and must be remediated or accepted again with a fresh justification. An accepted deficiency cannot be reopened by hand.

## Reminders and escalation

Product location: `/qms/controls/deficiencies`. Open Deficiencies in Controls.

Once an outstanding deficiency is more than three days past its due date, the owner's manager receives **Control Deficiency Overdue**. If the owner has no manager recorded, nobody is escalated to. Managers are set on each person's user record; see [link people to their managers](https://help.complytrain.net/en/settings/import-users/#link-people-to-their-managers).

## See a control's deficiency history

Product location: `/qms/controls/{controlId}` (fallback: `/qms/controls`). Open the control from the Library and select the Exceptions tab.

Open the control and select **Exceptions**. **Deficiency history** starts with **If a test fails, this control will:** and the policy in force, with its source: **Set on the implementation.**, **Inherited from the control.** or **The organisation default, because nothing more specific is set.** The table lists each deficiency's **Reference**, **Severity**, **Raised by**, **Status** and **Outcome**: **Retest passed** with the date, or the CAPA number. Open the deficiency register to work any of them.

## Where deficiencies show elsewhere

Product location: `/qms/controls/deficiencies`. Open Deficiencies in Controls.

-   **Controls overview:** the **Open exceptions** figure links to the register. See [framework coverage and the Controls overview](https://help.complytrain.net/en/controls/framework-coverage-dashboard/).
    
-   **QMS:** CAPAs opened by **Exception, then CAPA** or **CAPA directly**.
    
-   **Risk register:** the failing test lowers the control's effectiveness, which feeds residual checks on the risks it is linked to. See [controls and residual challenges](https://help.complytrain.net/en/rms/controls-residual-challenges/).
    
-   **Reporting:** the **Control Exception Register** report.
    

## Example: three leavers still had access

Product location: `/qms/controls/deficiencies`. Open Deficiencies in Controls.

The second-quarter test of **AC-07 Quarterly access review** on the production AWS account found three leavers with access: **Ran, with gaps**. The implementation's policy is **Open an exception**, and AC-07 requires a second approver.

1.  When the quality manager approves the result, a **Medium** deficiency is raised, owned by the cloud platform lead and due 30 days later. They receive **Control Deficiency Raised**.
    
2.  The cloud platform lead opens it and enters the cause: "The leaver process did not notify the AWS administrator." They choose **Start fixing it**, remove the three accounts and add the AWS administrator to the leaver checklist.
    
3.  They choose **Ready to retest**.
    
4.  The internal auditor records a test for July to September, chooses the deficiency under **Does this answer an open deficiency?**, samples 25 accounts with all satisfactory, and records **Well designed** and **Ran as designed**.
    
5.  The quality manager approves the retest in **Awaiting my approval**, which closes the deficiency. It shows **Closed by retest**, and AC-07's **Exceptions** tab shows **Retest passed**.
    

Had the fix been months away, the quality manager could instead have accepted the risk with a justification naming the compensating monthly check, and a review date at the end of the quarter.
