An occurrence describes a fact; a nonconformity depends on a requirement
An occurrence is a record of something that happened and deserves follow-up, review, or consultation. It may be an observation, interruption, unexpected situation, or event the operation needs to preserve.
A nonconformity is a classification connected to failing to meet a defined requirement within the applicable quality process. The requirement may come from an internal rule, specification, contract, or another criterion adopted by the organization. The classification should not be assumed simply because an event is undesirable.
An occurrence may not become a nonconformity
Imagine a field observation that requires a supervisor to follow a condition, but no missed requirement has been identified. It may remain an operational occurrence until the team has enough information to decide its treatment.
In another case, an occurrence may record an observed failure, gather evidence, and later be assessed against a requirement. If the responsible process concludes that the requirement was not met, the organization may formally classify it and route it through the applicable workflow.
The initial record does not need to predict that outcome. It needs to preserve what was observed and done.
The common mistake is classifying too early
Calling every event a nonconformity mixes fact with conclusion. It may start a formal treatment without enough basis or make an operational observation look like a quality decision that has already been made.
This caution does not mean ignoring risk. It means allowing the people and process with the relevant authority and information to classify it while keeping the original context available.
Three questions before using the term
Ask:
- Which applicable requirement was not met?
- Who has the authority or process to classify it?
- What formal treatment does the organization require after that decision?
If the team cannot answer, record the occurrence without pre-labeling it. The question can be routed to the quality process without losing the operational context.
The occurrence record may come first
An operational record can preserve date, location, description, participants, evidence, and initial actions while the responsible process decides whether a nonconformity exists. This protects both kinds of information: the fact is not rewritten to fit a category, and the category is not applied without criteria.
When classification occurs, keep the relationship between records according to the organization’s process. This article does not define how every company should run quality management. The industrial context for this distinction appears in occurrence records in industry, while sample preparation is discussed in preparing occurrence records for an internal audit.
When specialist quality controls are required
If the situation requires a QMS, CAPA, or another formal control, use the process and tool defined for that domain. An occurrence record does not replace approvals, root-cause analysis, corrective actions, effectiveness evidence, or other controls the organization has established.
End with conceptual clarity
Not every occurrence is a nonconformity. An occurrence preserves what happened and may support later review; a nonconformity depends on a requirement and classification within the applicable process. Keeping that distinction clear avoids both minimizing a problem and announcing a conclusion that has not been made.
