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 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 ↓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
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
Built-in controls
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.
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.
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.
Classify each change and decide which clients must be told
Apply fixes, send notices and read client notes
Describe the change accurately and sign as author
Approve prior approval requests, learned rules and go-live
The agents' working, a go-live rehearsal, the queue of client-facing changes, the fan-out once a client answered, and the settings.
demoSample data, from the working solution.
Reads the change record for what changes, where, when and why.
Walks equipment, utility, points of use, recipe steps and cleaning procedures to each product, citing each step.
Reads each touched client's change clause into prior approval, notice or annual summary, and a clock on the business calendar.
Drafts one notice per client in its terms, with the attachments that client asks for.
Reads each draft as the client's QA would and attacks it, the agents' own facts included.
Sends each signed notice to the client portal, reads structured answers, turns conditions into tasks and keeps the go-live gate.
Proposes a client rule from repeated answers, such as the attachments a client always asks for.
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.
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.
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.
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.
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.
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.
Quotes a client can trace to every assumption, checked against real capacity.
1-min demoCapacity Planning & Scheduling ScenariosSay yes to a client's pull-in with a plan the plant can run, and dates the client can trust.
1-min demoMulti-Market Post-Approval Change FilingOne approved plant change filed in every client market, and no line supplies a market before its approval.
1-min demoSend one closed change control with the quality agreements it touched, and we will trace it to each client product and its clock.