Internal Production Control: Keeping Production Married to the Assessed Design

Internal production control is the system that makes the declaration true of the millionth unit, not only of the assessed sample. Its elements are the standard quality repertoire aimed at the conformity file: controlled specifications (the assessed version is the production version, under change control), incoming-goods verification against the substance and content specifications, process monitoring at the points conformity is made or lost (cure, seal, mix ratios, print), finished-goods checks proportionate to risk, and a nonconformity loop that can stop, correct and - where placed goods are affected - trigger the corrective-action duties.

The system's outputs feed the file continuously. A quality system that cannot show its records to a surveillance authority as conformity evidence is running two systems where one would do.

Map the production process against the file and mark where each requirement is physically decided. Composition requirements are decided at goods-in and at formulation: supplier identity, certificate validity, batch identity. Recycled content is decided at mix and allocation: the records the content station prescribed. Grades are decided at converting: layer structures, adhesives and finishes applied as specified. Labelling is decided at artwork and print release. Substances are decided by input control, because nothing downstream removes them. The map, with the check at each point and its record, is the production-control plan - a page or two per line, owned by production, audited by the challenge function.

Nonconformities sort into three legal classes. Contained: caught before placing, corrected, recorded - the system's ordinary virtue. Placed but immaterial: a deviation that does not affect conformity (a cosmetic print variation) - recorded, dispositioned, no external duty. Placed and material: production that does not conform to the declaration is on the market - the corrective-action machinery of the roles station engages (inform, correct, withdraw or recall proportionately), and the loop's speed and honesty in this class is what authorities judge the whole system by. Pre-agree the materiality criteria and the escalation path, in writing, in calm times: the business that debates definitions during an incident has already lost the incident's first week.

Where production is contracted, production control is exercised through the contract's machinery: specification ownership retained by the declarant, change notification enforced (the unannounced reformulation is the classic contract-manufacture conformity failure), audit and sampling rights exercised on a rhythm, and records flowing to the declarant's file rather than residing in the contractor's. The roles station's manufacturer-conversion rule decides who declares; this guide's point is that whoever declares must control, and distance is not a defence the file can plead. Contract reviews should sample the control evidence physically - pull a batch record, test a certificate's scope - because paper rights unexercised read, after an incident, as paper only.

The practical integration that saves the duplication: every production-control record the system generates (goods-in checks, batch records, print releases, nonconformity dispositions) carries the specification and packaging identifiers the technical file uses, and the file's evidence index points to the record series rather than to copies. The file then stays current by reference - the index is stable while the records accumulate - and a surveillance production request is answered by extracting the series, not by assembling a story. Businesses with mature ERP and QMS tooling can automate the extraction; businesses without can achieve the same join with disciplined identifiers in a spreadsheet world. The join is a naming convention before it is a software project.

Production control, summarised for the wall of the quality office: the assessed specification is the only specification; inputs are verified, not trusted; conformity is decided at named points by named checks; nonconformity has three classes and three speeds; and every record carries the identifiers the file speaks. Five sentences, each auditable. The system's sophistication can grow from there indefinitely, but a line that cannot pass those five sentences is not controlled in the sense the declaration asserts - whatever its certificates say.