Skip to content
Pharma GXPGlobal Consulting

QMS Design & Implementation

Building a Quality Management System from the ground up — Quality Manual through SOPs — aligned to GMP, ICH Q10, and ISO 9001:2015.

In short

A pharmaceutical Quality Management System (QMS) is the documented framework — Quality Manual, Site Master File, procedures, records and the governance around them — that defines how a manufacturing site controls quality and demonstrates GMP compliance to a regulator.

A Quality Management System is only as strong as the architecture underneath it. I design QMS frameworks that connect the Quality Manual to the Site Master File, and the Site Master File to every SOP, BMR, and BPR beneath it — so nothing is left as an orphaned document waiting to be found by an auditor.

This is ground-up work: for a new facility, a new product line, or an organization formalizing quality for the first time. Having built and operated these systems from inside manufacturing — not only advised on them from outside — I design for what holds up under daily production pressure and periodic regulatory inspection, not just what looks complete in a binder.

How QMS Design & Implementation engagements work

  1. 1

    Current-state assessment

    Review existing practices, facility scope, and the applicable regulatory pathway to define the target QMS.

  2. 2

    System architecture & document hierarchy

    Design the Tier I–III document structure and map every required procedure to it.

  3. 3

    Procedure authoring

    Write and cross-reference SOPs, forms, and records so they operate as one coherent system, not isolated documents.

  4. 4

    Roll-out & training

    Train process owners and staff, and pressure-test procedures against real operating scenarios.

  5. 5

    Audit & management review cadence

    Establish the internal audit schedule and management review rhythm that keeps the system alive after handover.

FAQ

QMS Design & Implementation — frequently asked questions

What documents make up a pharmaceutical QMS?

A pharmaceutical QMS is normally structured in three tiers. Tier I is the apex policy layer — the Quality Policy, Quality Manual and Site Master File — which states what the site commits to and how it is organised. Tier II is the procedural layer: SOPs covering CAPA, deviations, change control, out-of-specification results, self-inspection, training, documentation and supplier management. Tier III is the execution layer: work instructions, forms, logbooks, batch manufacturing records (BMR) and batch packaging records (BPR) that generate the evidence. Each tier must trace to the one above it, or documents become orphaned and an auditor will find them.

How long does it take to build a QMS from scratch?

It depends almost entirely on scope, not on effort. A single product line at an existing site with some procedures already in place is a materially different job from a greenfield facility seeking first licensure, which needs the full Tier I–III architecture plus training and a demonstrated operating history before an inspection is credible. The realistic driver is rarely authoring speed — it is how quickly the site's own process owners can review, approve and then actually operate the procedures being written.

What is the difference between ICH Q10 and ISO 9001:2015?

ICH Q10 is a pharmaceutical quality system model that applies across the product lifecycle, built alongside ICH Q8 (Pharmaceutical Development) and ICH Q9 (Quality Risk Management). It is a regulatory guideline, not a certifiable standard. ISO 9001:2015 is a general, sector-agnostic quality management standard that a site can be certified against by an accredited body. They overlap heavily on process approach, management review and continual improvement, and most pharmaceutical sites end up satisfying both — but only ISO 9001 produces a certificate, and only ICH Q10 speaks directly to product lifecycle and regulatory expectations.

Do you write the SOPs, or only the framework?

Both, and they are designed together. A document hierarchy with no procedures beneath it is an org chart, and SOPs written without an architecture become a library of contradictions. The usual pattern is to design the Tier I–III map first, author the procedures that carry the most regulatory and operational risk, and hand over templates and conventions so the site's own team can extend the system consistently after the engagement ends.

What is a Site Master File?

A Site Master File (SMF) is a single document prepared by the manufacturer that describes its GMP-related activities at a given site — the company and site, personnel and quality system, premises and equipment, documentation, production, quality control, contract activities, distribution, complaints and recalls, and self-inspection. Inspectors frequently read it before they arrive, which makes it one of the highest-leverage documents on site: it sets the tone of the inspection before the first question is asked.

Let’s talk

Ready to talk about QMS Design & Implementation?

Share a little about your site and timeline — I'll follow up within one to two business days with next steps.