FQSMS Document Control for Dairy and Infant Formula Plants

A quality system is built by people, not by paperwork. Before you write a single procedure, put the right structure in place:

• Steering committee — senior ownership, with the authority to make decisions stick.
• Project team and team leaders — to carry the day-to-day work, area by area.
• Subject-matter experts — the operators and engineers who actually know how the plant runs. Don't write procedures without them.
• Allocated areas — divide the plant into manageable zones (intake, processing, packing, CIP, lab).

Communication skills are essential throughout — the system succeeds or fails on how well people talk to each other.

ISO 22000 addresses leadership, food safety planning and internal and external communication. A documented system still needs people who can put these requirements into practice. Use training and wider Total Quality Management (TQM) methods to strengthen:

• Leadership
• Team building
• Communication
• Customer service
• Strategic planning

A certificate or a set of procedures does not establish that these capabilities work well. Identify the training your managers, supervisors and operators need, and check its effectiveness.

A three-tier pyramid is one useful teaching model. ISO 22000:2018 does not prescribe this particular hierarchy. Choose a structure that fits your processes, risks and users:

Controlled records help show what was done, what was checked and how the result compared with its specification. They support traceability and investigation, alongside effective process controls and competent staff.

If a record, drawing, specification or instruction influences whether you accept, hold or release product — it's quality documentation, and it must be controlled.

The ISO 22000 food safety management standard (clause 7.5) is specific. Document control ensures that:

• all documents relating to the product — its design, manufacture and maintenance — are captured, controlled and properly distributed;
• personnel always have access to the latest version, and that version reflects the true state of affairs;
• any change is promptly documented, then registered, approved, distributed and implemented;
• obsolete documents are promptly removed, or clearly marked obsolete, so nobody picks one up by mistake.

Ethics and compliance

Keep records accurate, make corrections traceable and report deviations promptly. Do not conceal failed checks or change results to make them appear acceptable. Follow applicable food safety requirements, agreed product specifications and approved site procedures.

Controlled documents include: drawings; specifications; operational procedures; inspection, testing and other work instructions; the Quality Manual and its procedures; inspection and test reports and data; and the visual aids on the plant floor. If a decision rests on it, it's on this list.

Terminology — words matter here:

• Procedure — describes the process.
• Work instruction — tells you how to perform the process.
• Attachment — information attached to a procedure for clarification.

Determine what to control: procedures, work instructions, forms, attachments, external documentation, prints and drawings.

Decentralised

• each function looks after its own documents;
• common in product-oriented systems;
• tends to produce a multitude of control schemes and inconsistent formats.

Centralised

• a functional area retains control over content;
• the common strategy of process-oriented systems;
• one scheme across the organisation — common format, style and look.

Keep the system as simple and manageable as possible — that simplicity is critical to success.

Build effective documents

• Clear, concise, user-friendly.
• Short sentences starting with a command verb.
• Present tense; make it clear who performs the task.
• Format for reading — headings and white space.

Have the right amount

Avoid too much (no overlap; don't put one process in more than one instruction) and avoid too little (the goal is consistency).

Plan the infrastructure before you commit: use the ISO standards and specifications, prepare a blueprint, then choose your system — a word-processing setup, an existing database, packaged document-control software, or (today) a cloud-based electronic document management system with version control and audit trails.

What's best for your company? Consider company size, computer setup and availability, the number of processes, and the rate of change. You may need more than one system — e.g. one for quality-system documents and a separate one for engineering documents.

A good code tells you everything at a glance. Reading across the row: which manual, which area, the document type, the sequence number, the revision, and any references.

Originator (W = Watson Dairy Consulting) · manual · plant area · document type · SOP / sequence number · revision · reference code.

Now the same idea as a worked example — each character carries meaning:

Reads, in plain English: a Watson Dairy Consulting document, Technology & Production Manual, Evaporator area, form 019, revision A — with its reference document alongside. One string, and you know exactly what you're holding.

That's the essence of getting started with ISO — and of building documentation you can stand behind. For assistance with ISO 22000 (the Food Safety Quality Management System standard), with Total Quality Management, or with infant formula and milk powder manufacturing, Watson Dairy Consulting is here to help.

Talk to us Infant formula & milk powder