Manage a nonconformity
A nonconformity tracks nonconforming product, from the moment it is caught to a closed, signed disposition. This guide walks through recording one, working it through evaluation and containment, and closing it once every approver has signed.
A nonconformity is nonconforming product, a part, a batch, or a device that does not meet its own requirements. A deviation is different. It is a departure from a process, not from the product itself. See Manage a deviation if that is what you are looking at.
New to Quality Events? See Key concepts for the vocabulary used across every guide.
Record a nonconformity
- Open the Nonconformities (NC) space, click the Quality Events tab, then the Nonconformities sub-tab.To see nonconformities across every Quality Events space at once, use the Jira side menu, Apps, then Quality Events.

The Nonconformities view on the Quality Events tab, with summary panels, filters, and the nonconformity table. - Click + New Nonconformity.

The button that opens the create dialog for a new nonconformity. - Set space to
Nonconformities (NC)and work type toNonconformity, then enter a summary and a description of what failed to meet requirements. Use the description to note the immediate corrective action too, if you already know it.
The create dialog, with the space, work type, initial status, summary, and description fields. - Click Create.A nonconformity is created in
Identification. You can transition it back toIdentificationfrom any other status if it needs to be reworked.
Evaluate the nonconformity
- On the Identification & Evaluation tab, select the category, one of
Product,Process,Material,System,Regulatory,Documentation,Environmental, orSafety, set market surveillance topreorpost, and set priority and due date according to impact and urgency.You can also reach a nonconformity from the space All work tab, filtered on the Nonconformity work type.
The category dropdown, open to Product, Process, Material, System, Regulatory, Documentation, Environmental, and Safety, with the evaluation and market surveillance fields below it. - Assign the nonconformity to whoever will run it.
- On the Trigger tab, link what surfaced the nonconformity: an incoming inspection, a batch item, a serialized item, a customer complaint, an audit finding, an asset or piece of equipment, or another quality event.

The Trigger tab, with link fields for test executions, defects, audit findings, and inspections. - On the Nonconforming Item tab, link the affected product, device, assembly, part, batch item, serialized item, software system, or software item.

The Nonconforming Item tab, with link fields for the batch, a serialized item, and an asset. - Once the record is documented enough, click Evaluate to move it to
Evaluation.Description is required for this transition.
The status menu on a nonconformity in Identification, with Evaluate and Cancel as the available transitions.
Take immediate corrective action
Immediate corrective action contains or fixes the nonconformity to stop further use, release, or impact, for example by segregating the affected items or moving them to temporary stock. It is not automatically a CAPA. It addresses only this specific case, with no root cause analysis, systemic correction, prevention, or effectiveness check.
- Fill in the evaluation field with your assessment, and confirm category and priority are set.
- Click Immediate action to move the nonconformity to
Immediate corrective action.Evaluation, category, and priority are all required for this transition.
The status menu on a nonconformity in Evaluation, with Immediate action and Cancel as the available transitions. - Update the description with what you contained or fixed, whether that means segregating the affected items or moving them to temporary stock.
- Choose Root cause to start a root cause investigation, or Skip to disposition when one is not needed.

The status menu on a nonconformity in Immediate corrective action, with Skip to disposition, Root cause, and Cancel as the available transitions.
Analyze the root cause
- Fill in root cause analysis summary with what you found.You can run the analysis in a controlled document instead. If you do, link it in affected documents and put the conclusion in root cause analysis summary.

The Root Cause & Escalation tab, with the root cause analysis summary field open for editing. - Choose Escalate to send the nonconformity to a CAPA, or Do not escalate to go straight to disposition.Root cause analysis summary is required for every transition out of
Root cause analysis, whichever way you go. Use it to justify the decision.
The status menu on a nonconformity in Root cause analysis, with Escalate, Do not escalate, and Cancel as the available transitions.
Escalate to a CAPA
Skip this section if you chose Do not escalate in root cause analysis.
- Use the Escalated to CAPA link field to create a new CAPA, or link an existing one.

The Escalated to CAPA link field, with a search box and a button to create a new CAPA. - Click Proceed to disposition to move on.
The CAPA then runs its own independent lifecycle. This nonconformity carries on with its own, through disposition, closure, and closed. See Manage a CAPA for that lifecycle.
Decide the disposition
- On the Disposition tab, set disposition strategy, for example
Use as is,Rework, orReject or scrap, describe what was actually done in disposition, and give your reasoning in justification.
The disposition tab, with the disposition strategy, disposition, and justification fields filled in.
Choosing Use as is as the disposition strategy requires a concession, created from the link field on the record. See Manage a concession.
- Set closure approvers to whoever will sign off on the closure.

The closure approvers field on a nonconformity, with an approver added. - For a rework or repair disposition, create tasks to track the implementation. See Track the work with tasks, further down this guide. They must be completed before the nonconformity can be closed.
- Link any related records that need the connection: concessions, deviations, CAPAs, affected documents, products, or change requests.
- Once disposition strategy, disposition, justification, and closure approvers are all set, click Close to move the nonconformity to
Closure.
The status menu on a nonconformity in Disposition, with Close and Cancel as the available transitions.
Close the nonconformity
- Fill in effectiveness check with how you confirmed the corrective actions worked.

The Closure tab, with the effectiveness check, closure remarks, and overdue justification fields, all empty. - Fill in closure remarks with anything else worth recording, such as lessons learned or an accepted residual risk.

The Closure tab, with the effectiveness check and closure remarks fields filled in. - Every closure approver gets an email, then approves individually. Click Reject or Approve, add a comment if you want to, then enter the one-time password sent to your email.The password is what records the signature, not the click.

The approvals field, showing an approval required lozenge, a comment box, and Reject and Approve buttons. 
The signature dialog, prompting for the passcode sent by email. - When every approval is in, the nonconformity moves to
Closedon its own.
The closure tab on a closed nonconformity, with the effectiveness check and the closure remarks recorded, and no overdue justification needed.
Once closed, the nonconformity can no longer be edited. If it has to be reopened, the only route is back to Identification.
If any approver rejects, the nonconformity moves to Closure reject on its own, then back to Identification to be revised and re-routed. A closure is typically rejected when QA finds the content thin or tasks still open.
Resume an overdue closure
If the closure approval runs past the configured period, an automated Closure overdue transition moves the nonconformity from Closure to Closure overdue, and notifies whoever is configured to hear about it. The period and the recipients are set in Set up Quality Events.
- Open the nonconformity and find out why the approval stalled, such as an approver being unavailable or more information being needed.
- Fill in overdue justification with the reason for the delay.

The overdue justification field, filled in with the reason a closure was delayed. - Check the due date. It resets automatically, so change it if the new one is not right.
- Click Justify & resume to return the nonconformity to
Closureand restart the approval cycle.Overdue justification is required for this transition.
The status menu on a nonconformity in Closure overdue, with Justify & resume and Cancel as the available transitions.
Cancel a nonconformity
- Open the nonconformity. It can be canceled from any status between
IdentificationandClosure overdue. - Click Cancel.

The status menu on a nonconformity in Closure overdue, with Cancel selected.
Only a user with the Quality Events Administrator role can cancel a nonconformity. A canceled nonconformity cannot be edited. The only route back is to Identification.
Track the work with tasks
A rework or repair disposition needs its own record of the work, tracked and signed separately from the nonconformity itself.
- From the nonconformity, open the Disposition actions link field and create a task, or link an existing one. It links back to the nonconformity automatically.

The Disposition actions link field on a nonconformity, with a linked task. - Assign the task and set a due date.
- Set type to
Corrective actionorDisposition.
The task’s type field, open to Corrective action and Disposition, with the Implements field below it. - Fill in description with the scope and the acceptance criteria, and set approvers to whoever will review it.
- The assignee clicks Start to move the task from
To dotoIn progress. - Fill in verification with the work performed and the outcome, then click Review to move it to
In review.Type and approvers are both required for this transition.
The status menu on a task in In progress, with Review and Cancel as the available transitions. - Each reviewer signs the same way: click Approve or Reject, then enter the one-time password.
- If a reviewer clicks Reject, the task moves to
Reopened. Click Restart to return it toIn progressand address the feedback. - If the review sits too long, an automated transition moves the task to
Overdueon its own. Fill in overdue justification and click Justify & resume to return it toIn review.
Done cannot be edited. A task can be canceled from any status, but only by a user with the Quality Events Administrator role.
