Module
NCR
The nonconformance report (NCR) as a guided sequence of steps, from containment and review through disposition, root cause and actions to verification and close-out. The report says whose turn it is and what is still missing, and every step stays in its history.
What it does
Whose turn it is
A banner at the top of the report names the next step, says whether it is yours or whose it is, and lists the fields still missing. Completing a step notifies whoever the next one waits on.
Evidence in the report
What deviated, measured, against the requirement it failed, with photos and tables placed in the description. Quantities affected and inspected, serial numbers, and the device, part or supplier it concerns.
Contained and decided
Hold the affected item and record where. Classify the nonconformance and say why, then decide its fate: use as is, rework, repair, regrade, scrap or return to supplier, with the justification.
Actions that get checked
Containment, correction, investigative, corrective and preventive actions, each with an assignee and a due date. Reminders come the day before and every day overdue, and each action is verified or sent back.
The customer in the loop
Record that the customer was informed, add their responses as they arrive and note their decision. The template runs this step always, never, or only for major nonconformances.
Your own templates
A template decides which steps run, who is responsible for each, which fields are required and whether closing needs a signature. A report keeps the template it was raised under.
How it works
Report it
Name what is wrong, when it was detected and by whom, and link the device, the part or the supplier. Keep it as a private draft, or submit it and it gets its number.
Contain and decide
Stop the item being used, classify the nonconformance and decide what happens to it. Each step is completed by the person or role the template names, and a step already behind you can still be amended, with every change logged.
Remove the cause
Find out why it happened, by whichever method you use, then assign the actions that stop it happening again. The step cannot be completed while an action is still open.
Verify and close
Check that the actions worked, sum up what was learned and sign. The closed report is read only, and reopening it takes a reason.
The record
A report that holds up in an audit
A nonconformance report is evidence, so it is kept as evidence: complete, in the order it happened, and readable by someone who was not there.
Every step in the history
Who completed each step and when, every amended field, every skipped step with its reason, and every action, comment and file.
Printed as a report
The PDF carries your logo and prints the description, the internal and customer review, verification and close-out, and the signature of whoever closed it when the template asks for one.
A hundred side by side
Export the list to a spreadsheet: one row per report, each step in a cell of its own, filtered the way the list is.
Never deleted
A closed report is a quality record and cannot be deleted. One raised in error is cancelled with a reason and stays visible.
Mesonify certifies nobody. It keeps the record an auditor asks to see, in the order it happened.
One platform
Raised from the record that showed the problem
A nonconformity rarely starts in the quality office. The report is tied to the rest of Mesonify, so it can start from the machine, the part or the delivery where the problem appeared.
Tied to what it concerns
Link the report to the device, the inventory part or the supplier it concerns, and filter the list by supplier when you review who delivers what.
Raised by an automation
A delivery rejected at goods receipt raises a supplier nonconformance on its own, linked to the order. A fault reported under your quality classification raises one linked to the event and its device. Each is submitted under the next number.
Raised by another system
A test station or an ERP reports a failed check with a webhook request, and the automation it starts opens the report in Mesonify.
Followed as it moves
An automation can act each time a report moves on to another step, such as telling the people now responsible for it.
Raising a report from an automation needs the Automations module. Raising one by hand needs nothing else.
See NCR running on your own plant.
Ask for a demo with your own devices, parts and jobs.