What Is GMP Documentation?

What it is

GMP documentation is the complete body of written material that controls how your operation runs and proves that it ran correctly. It divides into two distinct categories that must never be confused:

• Documents are instructions. They tell people what to do, how to do it, and to what standard. A cleaning procedure, a product formula, a specification — these are all documents.
• Records are evidence. They capture what actually happened, when, and by whom. A completed cleaning log, a signed batch sheet, a calibration certificate — these are all records.

The simplest test: if you are reading it to know what to do, it is a document. If you are filling it in to show that you did it, it is a record.

Why it matters

Regulators — whether a national authority inspecting your facility or a retail buyer auditing your supply chain — cannot watch every batch being made. What they can do is inspect your paperwork. Your documentation is, in practice, your operation as far as an auditor is concerned.

The governing principle of GMP inspections worldwide is:

If it is not written down, it did not happen.

This is not a technicality. It has direct commercial and legal consequences:

• Without a batch record, you cannot prove what went into a product, who made it, or that it passed quality checks. If that product is later linked to a consumer complaint or regulatory recall, you have no defence and no way to identify which other batches are affected.
• Without training records, you cannot demonstrate that your staff knew the hygiene or safety rules they were required to follow. A regulator will assume they did not know.
• Without approved specifications, there is no agreed definition of what a "good" batch looks like — which means your quality control testing has no pass/fail line to test against.

Documentation is also the mechanism by which your operation stays consistent as it grows. A verbal instruction passed from one person to the next drifts over time. A controlled, written procedure does not.

What you must do

Work through this in order. Do not try to write every document at once — start with the minimum needed to make your first compliant batch.

1. Learn the two categories. Be able to say, for any piece of paper or file in your operation, whether it is a document (instruction) or a record (evidence).

2. List the documents your operation requires. At a minimum, a small cosmetics or supplement operation needs:

Document type	Examples
Specifications	Raw material spec, finished product spec, packaging spec
Formulas	Master formula / Master Manufacturing Record
Procedures (SOPs)	Cleaning, weighing, batch manufacture, labelling, hygiene
Labels	Artwork files at approved version
Contracts	Supplier agreements, contract-lab agreements

1. List the records your operation generates. For the same small operation:

Record type	Examples
Batch records	Batch Manufacturing Record (BMR) — one per batch produced
Testing records	Raw material CoA, in-process checks, finished product results
Equipment records	Calibration certificates, cleaning logs, maintenance log
Personnel records	Training records, health declarations, visitor log
Facility records	Temperature logs, pest control reports, cleaning schedules
Quality records	Non-conformance reports, complaint files, CAPA log

1. Do not rely on memory, verbal communication, or informal notes. WhatsApp messages, sticky notes, and mental records do not exist in a GMP audit. If something matters, it belongs in a controlled document or a signed record.

2. Decide on a basic filing system before your first batch. Decide where documents are stored, how records are filed, and who is responsible for each. Even a simple labelled folder system or a shared drive with a clear structure is a valid starting point — what matters is that it is consistent and accessible.

What "good" looks like

Follow one activity — cleaning a mixing vessel — through both a document and a record.

The document (instruction):

SOP-EQ-003 — Cleaning of Mixing Vessel MV-01 Version 2.0, approved 2026-03-15 by [QA Lead] "After each batch, rinse with 60°C potable water for 5 minutes. Apply 1% citric acid solution, scrub all surfaces, rinse twice with potable water. Allow to air-dry with lid open. Sign the equipment logbook on completion."

The record (evidence):

Equipment Logbook — MV-01, page 14 Date: 2026-05-14 | Batch cleaned after: B-2026-047 Cleaned by: J. Waweru | Start: 14:30 | Finish: 15:10 Visual inspection pass: ✓ | Signature: [signed]

The document tells the operator exactly what to do. The record proves that a specific person did it on a specific date after a specific batch, and that the result was acceptable. Together, they form a complete, auditable trail for that activity.

A regulator reviewing these two items can confirm: the procedure exists, it was followed, and someone took responsibility by signing. Any one of those elements missing — no procedure, unsigned record, or no record at all — is a finding.

Common mistakes

• Conflating documents and records. Treating a completed SOP as a record, or trying to use a training record as a procedure. They serve different functions and must be managed differently: documents are version-controlled and approved before use; records are unique, contemporaneous entries that must never be changed after the fact.

• Mental records. "We always do it this way" is not a document. "I cleaned it" is not a record. The information has to exist on paper or in an approved electronic system, not in someone's head.

• Informal capture. Logging temperatures on scrap paper, recording batches in a personal notebook, storing results in an email thread. These cannot be easily reviewed, may be lost, and will not satisfy an auditor. Start with a proper form or logbook from the first batch.

• Backdating and reconstruction. Writing up records the day after (or week after) an activity because "it was all fine." This is a data integrity violation — one of the most serious findings a regulator can make. Records must be created at the time the activity occurs, not reconstructed later.

• Over-engineering before starting. Spending three months writing 40-page SOPs before making a single product. A one-page procedure that is followed consistently is better than a 40-page procedure that nobody reads. Start simple, then improve.

Templates & checklists

• [[document-record-inventory]] — [to be created] — A worksheet for listing all the documents and records your operation needs, mapped to the activities that generate them.
• [[document-control-checklist]] — [to be created] — Verification checklist confirming your document system meets the minimum GDocP requirements.