WorkflowContract Manufacturing (CDMO)

Client Change Notification

Client change notification for contract manufacturers: agents trace a plant change through equipment, utilities, recipes and cleaning to each client product, read each client's clock, and hold go-live until every required approval is in.

See one water unit change reach three clients ↓
Watch with transcript →
The problem

A water unit swap touches products the planner never names

An engineer raises a change control to replace a purified water unit, and the description is written for engineers. The QA change control specialist asks production planning which products run there, and the answer covers the recipes that call for water. Products that meet the same water only in the final rinse of a cleaning procedure are not in anyone's batch record view, so their clients are left off the list.

Then each client's quality agreement has to be found and read: one wants to approve the change before it happens, others want notice a set number of days ahead, and a due day that lands on a holiday has to move. The days are counted back by hand, each letter is written from scratch, and a condition a client attaches to its approval lives in an inbox instead of on the change.

Built forQA change control specialistsClient quality liaisonsChange ownersQA heads

The Problem Today

A plant change reaches client products through utilities and cleaning, and each client's agreement sets a different rule and clock for being told.

Worked out by hand per change

  • Products
  • Agreements
  • Deadlines
  • Letters
  • Rinse-only products missedWater that touches a product only in cleaning is left off the list
  • Conditions lost in emailA client's approval terms never reach the change record

The Solution

  1. The change traced to productsThrough the loop drawing, each master batch record and the cleaning procedures
  2. Each client's clause, each clockPrior approval or notice, counted on the plant's business calendar
  3. The client's reviewer rehearsedA challenger plays the client's QA and finds the agents' own error
  4. Go-live waits for the answersThe switch-over work order stays on hold until each approval is in

Built-in controls

  • No notice leaves before its last signature
  • Whoever edits a notice cannot approve it
  • Client free text is read by a person

What You Get

Each client hears about a change before it is made, in its own agreement's terms, and the plant's improvement still makes its shutdown window.

  • Products found through cleaning tooRinse-only products and their clients are on the list
  • Clients answer in a few choicesApproved, approved with conditions, questions or rejected
  • Conditions become tasksEach client condition gets an owner and a due point on the change
Features

Change notification features, from the product trace to the go-live gate

A plant replaces its purified water generation unit with a larger one of the same design. Here is how each client that makes product with that water hears about it, and when.

demoThe plant, the client products, the people and the dates here are sample data.

  1. 01Product trace

    Plant change traced to every client product, through recipes and cleaning

    • Each product line says how. Binder solution, coating suspension or final rinse is named on each line, with the batch record step or cleaning procedure it came from.
    • Cleaning-only contact marked apart. Two products meet the water only in a rinse, so their client is told about a change the recipes alone would have hidden.
    • Untouched plants explained. Products made on another plant's own water system are listed as not reached, with the source that shows why.
  2. 02Steer

    A product still in technology transfer added to the client's request

    • Commercial status is a person's call. The tracer filed a transfer product for the transfer team; the specialist steers it onto the client's request, because its validation batches will use the new water.
    • The plan changes in view. The steer is logged and the request redraws at once, so the specialist sees exactly what the agents now do differently.
  3. 03Agreements

    Quality agreement change control clauses read into rules and clocks

    • Prior approval, notice or summary. Each client's clause is read into the kind of answer it needs, with the clause shown as signed beside its reading.
    • Counted on the plant's calendar. A due day that falls on a holiday or weekend moves to the business day before, with the subtraction shown beside the clause.
    • The stricter reading of a vague clause. A clause that names equipment but not utilities is read to cover the water unit, since the unit makes water a product uses.
  4. 04Challenger

    The client's QA reviewer rehearsed before any notice is sent

    • The agents' own copying error. The draft said one product saw the water only in cleaning; the trace said binder solution, so the fix goes to the liaison before anyone signs.
    • Data promised with a date. Qualification data does not exist until its first phase ends, so the notice commits to a send date the agreement allows.
    • Filing left to the client. A line saying no filing is needed is flagged, because the client owns its registrations and decides its own filings.
  5. 05Notice

    Prior approval request drafted in the client's own terms and attachments

    • Attachments each client always asks for. A stability statement and a filing view ride with this client's request, learned from its answers to earlier changes.
    • The change owner signs as author. The engineer who raised the change confirms it is described accurately, and can never approve the notice that carries it.
  6. 06Approved and sent

    Client change notification approved by the QA head, then sent

    • A second person approves sending. A prior approval request goes out on the QA head's approval; a notice of change goes out on the change control specialist's.
    • Sent the moment it is signed. The approvals keeper posts the signed version to the client's portal and keeps that exact version as the one the client answers.
  7. 07Client portal

    The client's approver answers a change request in fixed fields

    • Opened before it can be answered. The answer form opens only after the client's approver has had the notice open, so a reply follows a reading.
    • Four answers the agreement names. Approved, approved with conditions, questions or rejected, and silence never counts as approval.
  8. 08Answers

    A client's approval condition turned into a task on the change

    • Conditions with owners and due points. Placing the first batches after go-live on long-term stability becomes a task for the stability coordinator, tied to the change.
    • Notes wait for the liaison. Agents leave a client's free-text comment alone; the liaison opens it and records what it asks.
  9. 09Go-live gate

    Go-live held until each client's approval and notice is in

    • Nine lines, each with an owner. Approvals, notices, answered questions, qualification phases and signed versions each show who settles them, and the approve button lists every line still open.
    • The switch-over work order held. The storage tank stays on the old unit until the QA head approves go-live, which only opens once all nine lines are met.

Change owners sign for the description and leave the agreements to QA

QA change control decides who must hear, the liaison sends and reads what comes back, engineering describes the change, and the QA head approves requests and go-live.

QA change control specialists

Classify each change and decide which clients must be told

  • Products traced through recipes and cleaning
  • Each client's clock on one screen
  • A steer that changes the plan in view
Client quality liaisons

Apply fixes, send notices and read client notes

  • Drafts already read as the client would
  • Answers in fixed fields, conditions as tasks
  • Reminders before a client's clock runs out
Change owners

Describe the change accurately and sign as author

  • No agreement to read themselves
  • The go-live gate with what still blocks it
  • Edits that clear old signatures
QA heads

Approve prior approval requests, learned rules and go-live

  • A request already challenged
  • A gate that lists each open line
  • Rules proposed from past client answers
More screens

Two weeks of water to drain come before any go-live the rehearsal accepts

The agents' working, a go-live rehearsal, the queue of client-facing changes, the fan-out once a client answered, and the settings.

Every agent cites the records it read and names who it hands toThe change reader, impact tracer, agreement reader, drafter and challenger each list what they read, what they concluded and how sure they are.
Go-live dates rehearsed against all three clocksEach candidate go-live recomputes the client clocks and the first validation phase; a date that leaves that phase under two weeks is refused.
Open client-facing changes across four plants, nearest client clock firstEach open change with a client action shows the clients it touches, what each is owed and its status, from to trace through answered, with annual summary lines apart.
One client approved with conditions while two notices wait inside their clocksThe client that had to approve now shows approved with conditions, while the other two notices wait to be signed inside their own clocks.
A rule learned from the challenger applies only once the QA head approvesEach client's clock from its signed agreement, who signs each notice type, the plant's business calendar, and rules learned from past client answers awaiting approval.

demoSample data, from the working solution.

No product is called untouched until its cleaning procedure has been read

Change reader

Reads the change record for what changes, where, when and why.

  • Never edits the change
  • Never classifies client impact
Impact tracer

Walks equipment, utility, points of use, recipe steps and cleaning procedures to each product, citing each step.

  • Never calls a product untouched without reading its recipe and cleaning procedure
  • Never decides a product's commercial status
Agreement reader

Reads each touched client's change clause into prior approval, notice or annual summary, and a clock on the business calendar.

  • Never relaxes a clause
  • Sends an unclear clause to the change control specialist
Notice drafter

Drafts one notice per client in its terms, with the attachments that client asks for.

  • Never signs or sends
  • Never states a client's filing decision
Client challenger

Reads each draft as the client's QA would and attacks it, the agents' own facts included.

  • Never fixes anything itself
  • Never closes its own point or speaks for the client
Approvals keeper

Sends each signed notice to the client portal, reads structured answers, turns conditions into tasks and keeps the go-live gate.

  • Never sends unsigned
  • Never reads a client's free text
  • Never approves go-live
Rule keeper

Proposes a client rule from repeated answers, such as the attachments a client always asks for.

  • Nothing it proposes applies before the QA head approves

The CDMO states a view on filing, and the client makes the decision

Deciding a regulatory filingThe client owns its registrations, so each notice gives the CDMO's view and the client decides whether a supplement or annual report is needed.
Approving go-liveOnly the QA head approves the switch-over, and only once each gate line is met; the change owner never can.
Reading a client's commentFree text from a client waits for the liaison to open it; only the fixed fields change the case.
Calling a product commercialWhether a product in transfer is told through the transfer team or the client's request is the specialist's steer.
Approving an edited noticeWhoever applied a fix to a notice cannot approve it, and an edit after signing clears the signatures already on it.

What QA change control teams ask about change notification

What is change notification at a CDMO?

Change notification is how a contract manufacturer tells each client about a planned change to equipment, utilities, suppliers, processes or the site that may touch its product, in the way and on the clock its quality agreement sets. Here agents trace the change to products, read each client's clause, draft each notice and keep go-live on hold until the required approvals are in.

Which changes need the client's approval before they happen?

Whatever the client's quality agreement says. FDA's quality agreement guidance asks both parties to settle how each kind of change is reported and approved, from suppliers and major equipment to lot numbering and container closure. One client may ask prior approval for any utility change, another only notice, and the agents read each clause rather than assume.

How are products touched only through cleaning found?

The impact tracer reads the cleaning procedures as well as the master batch records, and follows the utility to each point of use. A product with no water step in its recipe still appears when its equipment is rinsed with that water, marked cleaning only, with the procedure it came from.

Who decides the regulatory filing for a change?

The client, which holds the registration. Each notice states the CDMO's view of whether registered details change, and the client decides on its own filing; the agents are barred from writing a filing decision for a client.

Can a change go live before the clients that must approve have approved?

No. The go-live gate holds the switch-over work order until each required approval, notice, answered question and validation step is in, and only the QA head can approve go-live. EU GMP's chapter on outsourced activities says a contract acceptor should make no unauthorized change, outside the terms of the contract, that may lower the quality of the outsourced work.

How is an approval with conditions handled?

The condition arrives as a fixed field and becomes a task on the change, with an owner and a due point, so it has an owner and stays on the change record for the next audit. A comment beside it is opened by the liaison before the answer counts toward go-live.

Bring a change
that touched a utility.

Send one closed change control with the quality agreements it touched, and we will trace it to each client product and its clock.