Quality runs on files. The inspector writes readings on a sheet, the sheet goes into a folder, and the batch moves on while the folder is still being completed. When a customer complains months later, the plant has paperwork — but the paperwork was never in the path of the batch.
The quality problem nobody solves with a thicker file
The usual response is more forms and a stricter sign-off. That adds work for the inspector and still leaves the real gaps open:
- The batch moves before the check. Material reaches finished goods or dispatch while the inspection is pending.
- The reading has no instrument. Nobody can say which gauge measured it, or whether it was in calibration.
- Failures are discussed, not fixed. A problem is raised in a meeting, and the action is forgotten by next month.
- The sample is missing. A complaint arrives, and there is no retained material to test against.
The gap is not discipline. It is that the quality record sits beside the work, not in its path.
What changes when the check sits on the order
The specification is set once
Each QC parameter carries its specification, tolerance, method and the instrument it is measured with. An inspection plan decides which parameters are checked, at which stage, on what sample size. Nobody decides the limits again on the floor.
Pass or fail is computed, not judged
The reading is captured against the batch, the order and the instrument that took it. Because the specification travels with the reading, pass or fail is worked out by the system rather than by opinion.
The order waits for the check
QC checks sit on the manufacturing order and on the operation. The order will not close while an inspection on it is open. Incoming material waits in QC stock, which is visible but not saleable, and rejected stock stays out of the usable pool.
A failure opens a record that must close properly
A failed reading opens a nonconformance with the quantity affected, the severity and who raised it. From it, a corrective action is raised with a root cause, an owner and a due date. The nonconformance closes only after the action is verified — without verification, the close is refused.
What this looks like in practice
Consider a component manufacturer with a bore diameter specified at 40.00 mm, +0.03.
During in-process inspection, the inspector records a reading of 40.05 against the batch, the manufacturing order and the bore gauge. The system marks it as a fail, and a nonconformance opens:
- The affected quantity is recorded, and the batch cannot move to finished goods.
- The QA head raises a corrective action — a worn tool at one station — with an owner and a due date.
- The tool is changed, the next readings pass, and QA verifies the action.
- Only then does the nonconformance close, and the order can complete.
Six months later, a customer asks about that batch. Specification, reading, instrument, inspector and corrective action are on one screen, and the retained sample is held against the same batch.
Nothing here makes the machine more accurate. What it does is put the check in the path of the batch — which is where most quality failures quietly slip past.
Instruments you can prove were in date
A reading is only worth what the instrument is worth. Calibration plans set the due date for each instrument, and calibration events record what was done, by whom and against what standard. The due date is visible before it passes. Keeping an overdue instrument out of use is a decision your quality process makes; Unnati makes sure nobody can say they did not know it was due.
Where this meets the rest of the business
Quality is not a separate database in Unnati. It uses the same records as stock, production and sales.
- Stock: QC stock and rejected stock are stock states, so held material cannot be picked for sale.
- Production: MO QC sits on the manufacturing order and gates its close.
- Purchase: incoming material waits in QC stock after the GRN until it clears.
- Sales: the batch on the invoice is the same batch the retained sample is held against.
That is the practical argument for quality sitting inside the same system as production and stock rather than in a folder beside them.
A note on regulated plants
Unnati is built with pharma, chemical and engineering work in mind: parameter-level checks, calibrated instruments, retained samples, nonconformance, corrective action and QC-gated completion. Whether it satisfies your particular regulatory scope is a question for your quality head, and we are happy to walk through the module with them before you decide.
Unnati's quality module covers QC parameters and instruments, inspection plans, MO QC, calibration, nonconformance, corrective action, QC and rejected stock, and retained samples. The quality control feature page shows the screens, and the production page covers how QC gates the manufacturing order.
Key takeaways
- A quality file kept beside the work cannot stop a batch; a check on the order can.
- Pass or fail should come from the specification, not from opinion on the floor.
- Every reading needs the batch, the order and the instrument that took it.
- A nonconformance should close only after its corrective action is verified.
- Calibration due dates must be visible before they pass, not found in an audit.
- Retained samples tied to the batch make a late complaint answerable with material.