Unwritten
The standard lives in one inspector's head
Without a tolerance recorded against the parameter, two people on two shifts pass two different batches and both are certain they were right.
Parameters with written ranges, inspections raised against the goods receipt or the work order that caused them, rejections classified so they add up, and a supplier quality record you can open before the next order.
The same range applies on every shift.
Results attach to the receipt or the run.
Classified, so the pattern surfaces.
Rejection rate ready before you reorder.
None of them is about how carefully people inspect. They are all about what the inspection is written against and what happens to it afterwards.
Unwritten
Without a tolerance recorded against the parameter, two people on two shifts pass two different batches and both are certain they were right.
Detached
A check filed separately from the goods receipt or the work order cannot answer what a specific batch was inspected against.
Unaggregated
Rejections logged as incidents never become a pattern, so the supplier and the line that cause most of them stay invisible.
Neome fixes all three by recording the tolerance, attaching the result to the batch, and classifying the defect.
Checklists
Inspection parameters are configured per item with the tolerance range that decides a pass. That turns the check from a judgement into a measurement, and makes the same standard apply on the night shift and at the second plant.
Inspections
Inspections are raised against a goods receipt or against production, so a result always belongs to a specific batch. Pass and fail are recorded with the inspector's name and their remarks, which is what makes a result defensible six months later when a customer asks.
Rejections
Rejections are logged against the batch with a defect class and a quantity, and routed for a decision between return and rework. Classifying at the point of rejection is what allows the aggregate to mean something, rather than producing a pile of free text nobody can count.
Supplier quality
Because inspections are tied to receipts, a supplier's rejection rate is a by-product rather than a project. The number is worth having at the moment the next purchase order is placed, which is the only point where it can change anything.
Reporting
Set a date range and every figure below it is bounded by those dates.
How much are we losing?
Rejected against inspected, broken down by item, by line and by period, so a rise is visible before it is a quarter's worth.
Who keeps sending trouble?
Rejection rate per supplier across deliveries, with the defects behind it, which is the record to have open in a price negotiation.
Is it getting better?
Defect classes over time, so an improvement can be attributed to something rather than hoped for.
Configured per item.
Written down, not recalled.
Raised on the goods receipt.
Against the work order.
Recorded per parameter.
Every result is attributable.
Evidence with the result.
So rejections can be counted.
A decision, not a pile.
Raised when rejection climbs.
Made mandatory where it matters.
Inspect at the bay, not at a desk.
The questions quality and purchase teams ask before the first check is recorded in Neome.
What it costs
₹299/ user / month$9.99/ user / month
There is no separate charge for this module. The same per-user price covers Quality Control and the other 25+ modules, so adding a second or third one costs nothing extra.
Version-controlled bills of materials, work orders planned against real capacity, material deducted as output is recorded, and variance raised during the run.
Learn moreTrigger maintenance by calendar or running hours, record breakdowns with a root cause, consume spares against the job, and see what each machine really costs.
Learn moreKnow what you hold, where you hold it and what it is worth, with a stock ledger that updates as goods are received, issued, transferred and adjusted.
Learn moreTalk to our team and get a rollout plan aligned to your business process.