Non-Conformities
A register for recording the moments your organisation did not meet one of its own rules, and for working each one through containment, root cause, corrective action and verification until it can be closed with proof.
A non-conformity is any instance where the organisation did not meet a requirement it has committed to — a procedure that was not followed, a supplier delivery that failed its check, a customer complaint that turned out to be justified, or an audit finding. The word comes from ISO 9001 (the international quality-management standard, clause 10.2), but the idea is everyday: something went wrong, and the organisation must show it fixed both the instance and the underlying cause. The fix-the-cause part is called CAPA (corrective and preventive action). This register is where each non-conformity lives from the moment it is raised to the moment it is closed.
Who uses it
-
Contributor — can raise a
non-conformity, edit it, move it through its lifecycle, and use
Draft CAPA with AI. - Manager — everything a Contributor can do, plus deleting a record.
- Admin — everything, as always.
-
Viewer — can open the register
and read every record, but sees no
New non-conformitybutton, noLifecycle statuscontrol and no action buttons, and cannot change anything.
The Owner picker in the form is offered only to people who may list
users; anyone else can still raise a record and leave the owner to be set later.
What's on this screen
The register is a card grid rather than a table: each card is one
non-conformity, showing its title, a source badge, a status badge, its owner and
any due date. The page header carries the title, a one-line reminder of the CAPA
stages, and the primary action on the right. Above the grid sit a search box and
two filters; below it, the page count (Page 1 of …) with
Previous and Next. The register shows 20 cards per
page. Find the working parts first — they are numbered on the figure below.
-
The
New non-conformitybutton sits top right, beside the page title. It opens the create form described in the next section. A Viewer does not see it. -
The search box (
Search non-conformities...) filters the register by title and description as you type — useful once the register grows past a page. Changing the search or a filter returns you to the first page. -
The source filter (
All sources) narrows the grid to one origin: customer complaint, internal audit, management review, process, supplier, BCM exercise, or other. -
The status filter (
All statuses) narrows the grid to one lifecycle stage — for example everything still atOpen, or everything awaitingVerification. -
The card grid itself. Each card shows the source badge (for
example
SupplierorInternal audit), the status badge, the owner (orNo owner) and the due date when one is set. Selecting a card opens that non-conformity's detail page, where the lifecycle is worked. When filters match nothing, the grid is replaced byNo non-conformities match the current filters.
The captured screen shows the demo register with cards at every stage from
Open to Closed, raised from processes, internal
audits, customer complaints, suppliers, a BCM exercise and other sources. A card
shows a due date only when one has been set — the closed record in the capture
has none.
Before anything has been raised, the grid is replaced by
No non-conformities yet
with a short explanation and, for anyone allowed to create, a
New non-conformity button of its own. If the register cannot be
loaded, a message appears with a Retry link.
Raise a non-conformity
-
Select
New non-conformity. TheCreate non-conformityform opens asking for aTitle(a short summary, up to 200 characters), aDescription(what went wrong and how it was detected), and aSource. All three are required; the form marks any that are missing. -
Assign an
Owner— the person responsible for driving it to closure — and set aDue dateif the fix has a deadline. Both are optional. -
Select
New non-conformityat the foot of the form to save. A confirmation appears, and the record joins the grid at statusOpen— a new record always starts there. The evidence fields — correction, root cause analysis, corrective action, effectiveness verification — sit on the same form and can be filled in now or later; the lifecycle will insist on them at the right moments.
A Raise non-conformity button appears on a mock audit, on a
vendor's detail page, on a BCM exercise (and its follow-up actions), and in
the corrective-action part of a compliance-obligation evaluation. Raising
one there opens the same form with the source and, where available, a title
and description already filled in — all still editable — and links the new
record back to the audit, supplier, exercise or framework control it came
from, so the register stays connected to its evidence.
Work it to closure
Open a card to reach the detail page. Its Lifecycle status control
advances the record one stage at a time — and each forward step is gated: Aegis
refuses the move until the matching evidence text has been recorded on the
record. That gating is what makes the register auditable: a closed
non-conformity always carries its whole story.
The header shows the title with its source and status badges, the description
beneath it, and a line with the owner (Unassigned when there is
none), the due date, and — once the record is closed — the date it closed. A
Back to non-conformities link above the title returns you to the
register.
-
Check the status badge beside the title — it shows the
stage the record has reached, here
Root cause analysison the captured screen. -
Use the action row —
Draft CAPA with AI,EditandDelete(the last only for a Manager or Admin, so it is absent from the Contributor capture).Editopens theEdit non-conformityform, where you record the correction, root cause, corrective-action and verification text.Deleteasks for confirmation, then removes the record from the register and returns you to it. -
Advance the
Lifecycle statuscontrol. It lists only the current stage and the stages one step away — you cannot skip ahead. Moving toContainedrequires a correction; toRoot cause analysis, a root-cause text; toCorrective action, the action itself; and closing requires the effectiveness verification. You can also step backwards if a stage has to be redone — for example when a verification fails. A successful move showsStatus updated.; a refused one shows the reason beneath the control, where it stays until your next attempt. - Read the correction block — the immediate containment action that was taken.
- Read the root cause analysis block, and below it the corrective action and the effectiveness verification once they are recorded. These four texts are the record's proof; the lifecycle above merely confirms they exist. A block appears only once its text has been recorded.
-
Check
Related recordsat the foot of the page. A non-conformity raised from elsewhere shows what it is anchored to — a framework control, a mock audit, a vendor, or a BCM exercise (the last as a link that opens the exercise in Business Continuity). The captured screen shows a supplier record linked to its vendor.
The Edit non-conformity form also carries a
Status field with the same one-step choices. When you pick a
forward stage there, the form reminds you which evidence the move needs. Because
the check runs against the record as it will be after saving, you can type the
evidence and advance the stage in one save.
When your organisation has a Jira connection, a Jira issue panel
also appears on the detail page, for linking the non-conformity to an existing
Jira issue or creating one — see Jira.
Without a connection the panel is hidden, as it is on the captured screen.
| Status | What it means | Required before entering it |
|---|---|---|
Open |
Raised and acknowledged; nothing proven yet. | — |
Contained |
The immediate damage is stopped. | A correction (the containment action taken). |
Root cause analysis |
The underlying cause has been investigated. | A root cause analysis text. |
Corrective action |
A fix that prevents recurrence is in progress. | A corrective action text. |
Verification |
The fix is being checked for effectiveness. | — |
Closed |
Proven fixed; the record is complete. | An effectiveness verification. |
Stepping backwards to an earlier stage never requires anything.
The AI assist
Draft CAPA with AI on the detail page asks Aegis to read the
non-conformity and its linked records, then draft a root-cause analysis and a
corrective action for you. Select Draft with AI in the panel to
start; progress messages show while it reads the record, analyses the likely
root cause and drafts the action. The drafts appear in an editable panel —
nothing is written to the record until you review, adjust and select
Apply & save. Draft again asks for a fresh draft.
If the record already carries CAPA text, the panel warns you that applying will
replace it. The AI proposes; a person decides.
Drafting uses your organisation's AI credits, and the button appears only for
people allowed both to edit the record and to run AI actions. Text that came
from the draft is labelled on the detail page: AI-generated while
it is the AI's wording, or AI-assisted, human-edited after a light
edit. Once a person has rewritten it substantially, the label disappears.
Tips and limits
- A non-conformity is not an incident. A security incident (a breach, outage or attack) belongs in Incidents, with its own regulatory deadlines. Use this register for quality failures — the two can describe the same event from different angles.
- Do not fear the word. An auditor expects to see non-conformities being found and closed; an empty register at a mature organisation looks less credible, not more.
-
The gates are the point. If a forward step is refused, the
message tells you which evidence text is missing — record it via
Editand try again. -
One step at a time. The lifecycle never jumps stages. To
close an
Openrecord you pass through every stage in turn, recording each piece of evidence on the way.
Where this connects
- Management Reviews — the open non-conformity register is a standing input to every review.
- Mock Audit — findings there can be raised straight into this register.
- Vendors — supplier failures raised from a vendor's page land here with the link preserved.
- Business Continuity — a BCM exercise that fell short can raise a non-conformity, which links back to the exercise.
- Jira — track a non-conformity's fix as a Jira issue.
- Incidents — the security-incident lifecycle, for events that are attacks or outages rather than quality failures.