WorkflowMulti-Site Manufacturing

SOP Harmonization Across Sites

SOP harmonization that reads each plant's procedure against the global standard clause by clause and sorts each difference with the evidence behind it.

See one standard compared across four plants ↓
Watch with transcript →
The problem

A plant's hold time cited a study that never sampled that long

Each global standard has a local procedure at each plant, and over the years the local texts drift. One plant writes a hold time its validation never studied, another leaves portable equipment out of scope, and a third quietly builds a better control that nobody else hears about.

Aligning them is done by eye, two columns at a time. Differences are argued by email, and when a plant says it validated its number, nobody opens the report to see what the study sampled. Gaps reach the QMS one change control at a time, training is worked out by hand from reader lists, and an operator who moves between plants meets a different procedure for the same job.

Built forGlobal SOP ownersHeads of qualitySite document ownersCleaning validation leads

The Problem Today

Local procedures drift from the global standard, and the study a plant cites is rarely opened to see what it covers.

243
211.22(d) citations in FDA drug inspections, FY2025, cited most published

Compared two columns at a time

  • Global SOP
  • Local SOPs
  • Studies
  • Emails
  • A hold time no study coversThe local number cites a report that sampled less
  • Better practice stays localOne plant's stronger control never reaches the standard

The Solution

  1. Five procedures, clause by clauseEach global clause matched to its local clause despite different numbering
  2. Each difference in one of three binsJustified with evidence, a gap to close, or better than the standard
  3. Evidence opened to its resultsA justification counts only where the study covers the local claim
  4. Prepared, then approvedThe global owner signs as author, and the approver reads the packet to its end

Built-in controls

  • A card changes bins only with a reason
  • Author and approver are never one person
  • Each justification opens to its study

What You Get

Four plants work one way, and the standard improves from what the plants already do better.

  • Plant practice lifted into the standardStronger local controls become proposed edits to the global text
  • Hold times backed by their studiesA local number past its study is a gap before an inspector reads it
  • One procedure for people who moveOperators and engineers meet the same text at each plant
Features

SOP harmonization features, from clause map to approved plan

A global standard on equipment cleaning status and hold times is compared with four plants' local procedures; the global SOP owner sorts the differences, and the head of quality signs off the plan.

demoThe plants, procedures, people and numbers shown are sample data.

  1. 01Three bins

    SOP harmonization in three bins: justified, gap to close, better

    • Five procedures read in one run. The global standard and four local procedures are aligned clause by clause, so the owner works on the differences instead of rereading the matches.
    • Both passages on each card. A card holds the global text above the local text with clause numbers, the reason for its bin and a confidence.
    • Moves only with a reason code. Only the global SOP owner can move a card, with a reason code that stays in the card's history.
  2. 02Evidence

    A cited validation report opened to its results table, not its summary

    • Summary and results table together. The sentence a plant relied on sits next to the table that shows what the study actually sampled.
    • Cleaning validation confirms the reading. The cleaning validation lead opens the table and signs what the study covered before the plant can accept its change.
  3. 03Gap card

    Clean hold time gap, with past uses beyond the studied hold

    • The look back done at once. Uses after holds past the studied limit come from the equipment logbook, and a deviation goes to the plant's QA disposition lead.
    • What closes the gap, named. The card names the change control, its owner, the revision date and any client notice its quality agreement requires.
  4. 04Global draft

    Better local practice proposed into the next global standard as redlines

    • Harmonization that runs both ways. A plant's tamper-evident tag, self-expiring status or early warning becomes a proposed edit, linked to the local text it came from.
    • Accepted with a stated reason. The global SOP owner accepts or declines each edit with a reason, and reopening one is logged too.
  5. 05Challenger

    An inspector's objection that the new global wording fails at two plants

    • The agents' own sorting questioned. The challenger caught a justification read from a summary page, and that card moved to gap with the results table attached.
    • Wording chosen by a person. Where a lifted practice cannot work at each plant, the owner picks the wording, and the proposed edit changes with it.
  6. 06Plan

    Harmonization plan with a change control per gap, owner and client notice

    • One change control per gap. Each gap is drafted as a change control at its own plant, and a gap an open CAPA already covers is linked instead of raised twice.
    • Client notices where agreements ask. Gaps on lines that make a client's product carry the notice its quality agreement requires; the rest say why none is needed.
  7. 07Training

    Training impact per revision, from the learning system's reader lists

    • Readers counted once each. One read-and-understand assignment per revision reaches each reader once, with briefings added where a change needs one.
    • Nothing assigned before approval. The training coordinator confirms the plan, and no course is assigned before the plan's approval.
  8. 08Approval

    Plan approval possible once the packet has been read to its last line

    • Packet read before approve. Approve stays off until the packet is scrolled to its end, so the signature means the plan was read.
    • Author and approver kept apart. The global SOP owner cannot approve and the head of quality cannot prepare; editing the plan after a signature clears both signatures.
  9. 09Raised

    Change controls raised at each plant, waiting for their owners to accept

    • Site owners accept their own. Each plant's document owner accepts or sends back the change controls at their plant, and a send-back reopens the plan.
    • Study confirmed before acceptance. The clean hold change at the first plant waits for the cleaning validation lead's signature on what the study covered.

A plant may keep a difference that its own study proves

The global SOP owner sorts and prepares, site owners own the fixes at their plants, and the plan goes to the head of quality for approval.

Global SOP owners

Own the global standards, sort each difference and prepare the plan

  • Both passages on one card
  • Plant practice offered as redlines
  • Gaps drafted as change controls
Heads of quality

Approve harmonization plans, global revisions, rules and protected settings

  • A packet read in full before signing
  • Program status across the standards
  • Rules drawn from earlier rulings
Site document owners

Own their plant's local procedures and accept or return its change controls

  • Only their own plant's gaps
  • The exact clause to change
  • A way to disagree before approval
Cleaning validation leads

Confirm what each cleaning study covered

  • The results table, not the summary
  • Past uses beyond the studied hold
  • Sign-off before the plant accepts

A summary sentence passed as coverage until the challenger opened the table

Each agent cites the passage it read; people move cards, decide points and sign.

Clause aligner

Maps each global clause to its local clauses across different numbering and wording.

  • Calls no clause missing before reading the whole local text
Difference sorter

Sorts each difference into a bin with a reason and a confidence.

  • Moves no card a person has placed
Evidence checker

Opens each justification's report and checks the hours, equipment, runs and scope it studied.

  • Takes no summary sentence as coverage
Challenger

Raises what an inspector would say about the sorting, the agents' own included.

  • Settles no point itself
Change drafter

Drafts a change control per gap and a redline per better local practice.

  • Edits no procedure
  • Raises nothing before the plan is approved
Training impact reader

Reads the learning system's reader lists and drafts the course for each revision.

  • Assigns no training
Justification memory

Proposes rules from past rulings, such as a stricter local value that equals its study.

  • Applies no rule still awaiting approval

A clean hold of 72 hours cited a study whose swabs stopped at 48

Four differences a side-by-side reading would have passed, each found with its source.

A summary taken as coverage

The report's summary said acceptable; its results table sampled the clean hold to 48 hours, not the 72 the plant allowed.

Portable equipment with no limit

One plant's scope named its tanks only, so nothing limited how long transfer hoses, portable pumps and homogenizer heads could wait dirty.

A cleaner checking their own clean

At packaging changeover, the operator who cleaned could sign the pre-use check the standard gives to a second person.

A fix that would have been counted twice

One plant's hold time was already being changed under an open CAPA, so the plan links that CAPA instead of raising a new change control.

demoSample data, from the working solution.

More screens

Fifty global standards still wait for their first comparison across plants

Around the bins: where each clause sits, where the program stands, and how its rules and settings are governed.

Clause map across four plantsEach global clause against each plant's clause: the same, a difference with its bin, or not stated, each cell opening its card.
A scope that left equipment outThe global scope covers portable equipment; one plant's procedure covers its tanks only, and the card names the change control that brings hoses and pumps in.
Where the program standsEach global standard by plant, harmonized, in review, with gaps open or not compared, beside the reviews in progress and their due dates.
Rules proposed from rulingsEach rule shows which ruling produced it and which reviews used it; a declined rule stays visible with its reason.
The review, step by stepEach move, decision and signature, whether an agent or a person made it, with its reason and stated meaning, plus the plan packet as a download.
Settings only quality can changeThe confidence threshold, the evidence rule and the plan's service level need a signature from the head of quality to change; the administrator decides no quality item.

demoSample data, from the working solution.

Reader lists in the learning system decide who retrains on each revision

A procedure changes only through its own plant's change control, after the site document owner accepts it.

Document managementGlobal standards, local procedures and each revision in force or in draft
Validation reportsCleaning and hold-time studies, read to their results tables
MES and electronic logbooksEquipment status, hold-time clocks and each use after a clean
QMSChange controls, CAPAs and deviations already open against a procedure
Learning systemWho reads each local procedure, by role and plant

What global SOP owners ask before a harmonization review

What is SOP harmonization?

SOP harmonization is the work of bringing each plant's local procedures into line with the company's global standard, keeping only the differences a plant can justify. Here agents compare the clauses, sort each difference with its evidence, and the plan that closes the gaps carries the head of quality's approval.

How does a global SOP differ from a local SOP?

A global SOP sets the company's standard for a GMP topic; a local SOP says how one plant does it with its own equipment and systems. A local procedure may differ where its own process or study requires it, and the difference should point to that evidence.

How do you run an SOP gap analysis across sites?

Align the clauses first, then read each difference against the standard and against the evidence the plant cites. A gap becomes a change control at its plant with its training impact, and a local practice stronger than the standard becomes a proposed edit to it.

Can one plant keep a different clean hold time?

Yes, when its own validation studied that hold for that equipment. The standard here asks each plant to state its validated value; a local hold longer than its study sampled is a gap, and past uses beyond it go to QA as a deviation.

Is the client told when its product's procedure changes?

If its quality agreement requires notice, the plan drafts it alongside the change control, and the gap's line names the client affected. Gaps that change nothing about how a client's product is made say no notice is needed.

What happens to a local practice that is better than the standard?

It becomes a proposed edit to the next global revision, linked to the plant text it came from. The global SOP owner accepts or declines each edit with a reason. The challenger asks whether every plant could follow the new wording, and where some plants cannot, the owner picks wording that works at each.

Send us one standard
and its local versions.

Share one global SOP with two plants' local procedures and the studies they cite, and we can sort each difference with the evidence behind it.