Indiquez vos coordonnées pour télécharger le document.
Le fichier s’ouvre dans Google Drive : vous pouvez le télécharger ou l’imprimer.
The essential fields, a template to copy and the workflow from opening to closure: a non-conformity report that stands up at audit, for a deviation on a material, a product or a test report.
A non-conformity report is the record that captures a deviation found, the requirement it contradicts, the evidence that establishes it, the decision taken and the actions launched. This page deals with the document itself and its workflow - essential fields, standard template, steps from opening to closure, monitoring indicators - for food manufacturers who need to trace a deviation on a raw material, a product, an analysis result or a supplier document. It does not concern the testing laboratory, whose internal deviations are documented in its own management system, following a different logic and different requirements.
The report is a document: a unique reference, a date, an object, a deviation, evidence, a decision. Non-conformity management is the process that encompasses it: the procedure that says who opens, who qualifies and who closes, the register that lists all reports, handling times, trend analysis, periodic review. The first is filled in, the second is organised.
This distinction has a practical consequence. A company can fill in reports correctly and still manage its deviations badly: without a register, the same causes recur without anyone measuring it. Conversely, a well-written procedure that lets each department improvise its own form produces records that cannot be compared and cannot be consolidated in a review.
Three points on scope:
Nine blocks are enough to cover what an auditor, a supplier or a colleague arriving two years later must be able to reconstruct. Each field answers a precise question.
| Block | What goes in it | What an auditor looks for |
|---|---|---|
| Identification | Unique reference (e.g. NCR-YYYY-NNN), date and time of detection, name and department of the person detecting, location, workshop or step | Who found the deviation, when and where: the chronology comes before the handling |
| Object concerned | Product and internal reference, batch number, quantity concerned, supplier or customer, related documents (technical data sheet, certificate of analysis, delivery note) | The link to the batch and the supplier file, which defines the extent |
| Deviation found | Fact observed, measured and located, without interpretation: “moisture 15.2% for a specification of 14% maximum” | Wording that a third party can verify, independent of whoever wrote it |
| Reference requirement | Document cited with its version and date: internal specification, customer or supplier specification, maximum residue level, regulatory requirement | Evidence that the deviation is assessed against a written requirement, not against habit |
| Evidence | Numbered attachment: photo, analysis result, certificate of analysis, delivery note, record extract, extract from the supplier file | The item itself, without which the report remains a statement |
| Root cause analysis | Method used (5 Whys, 5M), cause or causes retained, causes ruled out and why | Dated reasoning, not the words “human error” |
| Immediate actions | Block, quarantine, sorting, line stop, re-analysis, return to supplier, with quantities and time carried out | Control of the product before any root cause analysis |
| Corrective actions | One action per cause retained, a named owner, a deadline, the expected evidence and the verification criterion | A dated, named and verifiable plan |
| Decision and closure | What happens to the product or the supplier relationship, who decided, date, result of the effectiveness check, closure date | The decision owned by the quality team, and evidence that the action worked |
Two service fields complete the setup: a status (open, in progress, closed) to filter the register, and an index of attachments to find evidence without searching an inbox. The retention period for reports depends on your customer standard and internal procedure. Set it in writing, at least equal to the shelf life of the product concerned, and apply it to all reports.
The “reference requirement” block assumes the requirement is written, quantified and dated. To build these parameters, thresholds and check frequencies, our page quality control plan: method and examples in the food industry details the method.
Downloading a non-conformity report template does not spare you from adapting it to your requirements: a document taken as is produces empty boxes and useless headings, which teams end up working around. The template below sets out the nine blocks in the order in which they are filled in.
Non-conformity report - template to copy
Reference: NCR-2026-014 Status: open Date and time of detection: … Detected by (name, department): … Location / line / step: … 1. OBJECT Product / reference: … Batch(es): … Quantity concerned: … Supplier / customer: … Related documents: technical data sheet, certificate of analysis, delivery note… 2. DEVIATION FOUND Fact observed, measured, located: … Extent (other batches, other lines, finished products concerned): … 3. REFERENCE REQUIREMENT Document and version: … Expected value or criterion: … Type: regulatory / specification / internal specification 4. EVIDENCE Attachment no. …: photo / analysis result / certificate of analysis / delivery note / extract from supplier file 5. IMMEDIATE ACTIONS Block, quarantine, sorting, re-analysis, return: … Quantity contained: … Done by / on: … 6. ROOT CAUSE ANALYSIS Method: 5 Whys / 5M Causes ruled out: … Cause(s) retained: … 7. CORRECTIVE ACTIONS Action | Owner | Deadline | Expected evidence | Verification criterion … 8. DECISION Decision taken on the product or the supplier relationship: … Decided by (name, function) / on: … 9. VERIFICATION AND CLOSURE Effectiveness checked on: … Result: … Closed by (name, function) / on: …
Four writing rules make most of the difference between a template and a usable record:
The nine blocks in the order in which they are filled in, ready to adapt to your procedure.
Five steps, one lead per step, and one underlying rule: each step signs off the previous one. A workflow without sign-off turns into a form filled in after the event.
Whoever detects the deviation opens the report: at goods-in, in production, on a laboratory result, during an audit or on a complaint. Two fields are never postponed: the time stamp and the factual description. A deviation noted in a notebook then entered the following week loses its chronology - and the chronology is the first thing an auditor reads.
Raw material goods-in remains the most frequent point of detection. What must be checked and recorded at this stage is described on our page raw material incoming inspection: a 5-step method. The analysis result is another: a parameter above the blocking threshold of your specification, or a regulatory limit, triggers the opening of the report.
Qualification crosses three criteria: the potential impact on product safety, the deviation from a regulatory requirement (maximum residue levels, contaminants, allergens, labelling) and the deviation from the customer specification. It produces two outputs: the level of urgency and the extent to contain (batches, quantities, finished products already made).
Regulation (EC) No 178/2002, Article 19, requires an operator who considers that a food does not meet safety requirements, and which has left its immediate control, to immediately initiate procedures to withdraw it, inform the competent authorities and, if the product may have reached the consumer, inform consumers and recall it. The report records this reasoning, not just its conclusion.
Qualification states the urgency; it does not decide what happens to the product. That decision belongs to the quality teams and is recorded in block 8, with a name and a date.
The 5 Whys follow the causal chain until an answer changes something in the organisation. The 5M (material, machine, method, environment, manpower) sweep through the families of causes when the first method gets bogged down. In both cases, writing down the causes ruled out is as valuable as the cause retained: it shows that an analysis took place.
A cause worded as “human error” does not describe a cause: it describes an end point. The next question - why was this error possible at this step? - almost always leads to a cause in method, training or workstation design, and therefore to a possible corrective action.
ISO 22000:2018 (§8.9.3) requires evaluating the need for action in response to a non-conformity, determining its causes, implementing actions, reviewing their effectiveness and retaining the corresponding documented information.
Two distinct questions, often confused: was the action carried out, and has the cause disappeared? The first is checked by a document (updated procedure, training delivered, supplier chased). The second is checked on a later result, with a criterion set at opening - three consecutive batches, a re-analysis, zero deviation over the monitoring period. The verification deadline is set according to criticality (example: 30 days for a major non-conformity, 90 days for a minor one), according to your procedure.
A monthly review of deadlines, kept by a single person, avoids the pile-up of unclosed actions that characterises non-conformity registers at year end.
Closure requires four elements together: decision recorded, actions completed, effectiveness criterion filled in, name and date. As long as the effectiveness criterion is empty, the report stays open - it is the simplest rule to keep and the easiest to check.
A closed report must remain retrievable: single register, stable naming, link to the supplier file and to the batch concerned, periodic review of open reports and recurring causes, at a frequency set in writing (example: monthly).
The workflow of a report, from opening to closure
Each step signs off the previous one. As long as the effectiveness criterion is empty, the report stays open.
Four elements distinguish a supplier non-conformity report from an internal one: it involves a third party, it depends on that party's responsiveness, it often concerns a document or an analysis result rather than a product, and it feeds a commercial relationship. Each of these points changes the way it is written.
The message to the supplier must allow the deviation to be handled without prior exchange. It contains:
The record of the exchange matters as much as its content. Sending through tracked messaging or the supplier portal, with date and attachments, avoids reconstructions from memory three months later. A verbal answer is restated in writing and attached to the report.
Keeping it separate from the commercial dispute avoids deadlock. The report documents a deviation and a quality action; the penalty, credit note or formal notice belong to purchasing and another channel. A report used to negotiate a price loses its documentary value: it becomes an argument, no longer a record.
The state of the document file is the question forgotten at the time of the deviation: not just “is the batch compliant?”, but “did we have the document that makes it possible to check?”. A missing certificate of analysis, a technical sheet whose version has changed, a declaration of compliance not sent: the report must refer to an identified document, not a search through emails.
History, finally, feeds decisions: the number and nature of reports opened over twelve months weigh in the periodic supplier assessment and the purchasing review. Without this link, the same non-conformity recurs with the same supplier with no visible consequences.
An auditor is not looking for a perfect report: they are looking for a report that makes it possible to understand what happened. The flaws that prevent this recur.
Six to eight indicators are enough. Beyond that, the dashboard is no longer read. All are calculated from the register, provided the fields are filled in consistently.
| Indicator | Definition | Decision it informs |
|---|---|---|
| Number of reports opened per month and by origin | Number of reports opened, broken down by detection source (goods-in, production, laboratory, audit, complaint) | Where to focus prevention effort |
| Closure time (median, in days) | Time between opening and closure, calculated as a median to limit the effect of extreme cases | The real capacity to handle deviations |
| Share of reports with a documented root cause analysis | Reports with an identified cause and an explicit method, out of all closed reports | The quality of handling, not just its speed |
| Share of reports with effectiveness checked | Reports whose effectiveness criterion is filled in, out of all closed reports | Exposure to undetected recurrence |
| Recurrence rate by cause | Share of reports linked to a cause already handled in the previous period | The real effect of corrective actions |
| Breakdown by supplier | Number of reports per supplier over a rolling period | Material for discussion in the purchasing review and supplier assessment |
| Share of documentary deviations | Reports where the deviation concerns a missing, expired or incomplete document | The need to make the supplier file more reliable upstream |
Two reading precautions. A falling volume can signal an improvement as well as under-reporting: cross-check with the number of checks carried out. And a flattering average time can hide a few very old reports: also track the age of the oldest report still open. These indicators are reviewed at a frequency set in writing (example: quarterly), with the quality, purchasing and laboratory teams.
For analysis results, Tracklab comes in upstream of the report: at the point where the deviation appears.
What the platform does not do calls for the same clarity: it does not decide what happens to a batch, does not rule on a non-conformity and does not replace the quality, purchasing and laboratory teams. The report, its workflow and its actions remain in your procedure; Tracklab provides the analysis result, its calculated status, the trace of the threshold applied and the history of status changes with their reasons. For details, see Tracklab's LIMS software page.
To see how Tracklab calculates and traces the compliance status of your test reports, book a meeting with the Tracklab team.
The texts below underpin the requirements cited on this page; always consult their current consolidated version on EUR-Lex.
Sources consulted on 12 November 2026.
An auditor is not looking for a perfect report: they are looking for a report that makes it possible to understand what happened.
Unusable report: “Material too moist”, “unreliable supplier”
Usable report: “Moisture 15.2% for a specification of 14% maximum”
Unusable report: No requirement cited, no attachment
Usable report: Requirement cited with its version, numbered evidence
Unusable report: Closed on the day of the meeting, with no check
Usable report: Correction and corrective action separate, effectiveness checked
No regulation imposes a named form. What is required is the record: food safety management standards require documented information on the non-conformity, corrections and corrective actions (ISO 22000:2018, §8.9.2 and §8.9.3), and IFS Food or BRCGS audits examine these records. Where a food does not comply with safety requirements, Article 19 of Regulation (EC) No 178/2002 also imposes obligations to withdraw, inform and, where necessary, recall. The report is the simplest way to keep this record; its form remains an organisational choice.
The most robust rule is one report per event. If the same deviation affects several batches, a main report and an annex listing the batches concerned avoid fragmentation. If two deviations of different kinds appear on the same batch, two reports are justified: the causes and corrective actions will probably not be the same. The choice must be written in the procedure so that all departments apply it in the same way.
Correction acts on the product: block, sort, return, downgrade, destroy. Corrective action acts on the cause, so that the deviation does not recur: change a goods-in parameter, add a check, change supplier, revise a specification. A report containing only a correction deals with the incident; it does not deal with the risk of recurrence.
The quality teams, depending on criticality and the organisation in place, together with purchasing and production. This decision relies on the risk assessment, the applicable regulatory obligations and the customer specification; it is recorded with a name, a function and a date. Software can calculate the status of a result and date the decision, not take it.
The period depends on your customer standard, your audit commitments and your internal procedure, and it covers at least the shelf life of the product concerned. What matters is to write a single rule, apply it to all reports and check it during internal reviews, rather than keeping files indefinitely whose status nobody knows any more.
Tracklab calculates the compliance status of each parameter in your test reports and keeps the threshold, regulation and date applied: the requirement and evidence for your non-conformity report are already brought together. The decision stays with your quality teams.
0.02 mg/kgCompliant0.09 mg/kgAlert0.015 mg/kgNon-compliantAbsent /25 gTo be determinedIllustration, fictitious data.
Their quality and purchasing teams collect, control and leverage their supplier data with Tracklab.
companies supported
suppliers referenced
products and ingredients
“Tracklab has eliminated the blind spots that existed in our document monitoring. Every document is analysed, every change is detected and every decision is traceable. This has enabled us to take a real step forward in terms of professionalism and credibility, particularly with auditors and customers.”

Independent assessment of our cybersecurity framework and of the protection of the data entrusted to Tracklab.
They use Tracklab







Platform
Resources