Change Notification for API Supply: Whose Clock Is Running

An email arrives from a customer's quality team. The certificate of analysis for the latest batch shows an impurity at 0.06 per cent where the previous four batches sat at 0.03. Every value is inside the limit. The customer asks one question: has anything changed?

The honest answer is yes. A purification step was added eight months ago to improve yield. The specification was not touched, the material still passes, and nobody thought of it as a change because nothing failed.

That answer, given late, is more expensive than the change itself.

Two clocks, and only one of them is visible

A supplier experiences a change as an internal event: a process modification, a validation batch, a revised batch record. The clock that governs it is the production schedule.

A customer experiences the same change as a regulatory event. Their marketing authorisation, their CEP, their customer's technical file, and in some cases a filed variation describe a process. When the process moves, the description has to move with it, and that filing has a queue, a fee and a reviewer.

This is why "we gave thirty days' notice" can be true and useless at the same time. Thirty days is enough to update a specification annex. It is not enough to prepare and file a variation, and the customer who discovers the change after implementation has lost the option to plan the filing around their own supply continuity.

A workable classification

Category	Examples	Timing
Prior approval	Site change, route change, new starting-material source, specification limit change	Agreement before implementation
Notify before	New purification step, new solvent, changed drying or milling, pack change	Before implementation, with comparability data
Notify after	Minor equipment like-for-like replacement, organisational changes with no quality impact	Within an agreed period after
No notification	Documentation edits with no effect on the product or the file	Recorded internally

The table is not a regulation. It is a starting point for the annex of a quality agreement, and its value is that it forces the two parties to agree on which category each kind of change belongs to before a change occurs.

Same specification, different material

The intuition that a passing specification means an unchanged product is the root of most late notifications. A specification is a set of limits. A process is a distribution within those limits, and the distribution is what the customer's method, their formulation and their stability data were built around.

Consider a change from one recrystallisation solvent to another. Assay is unaffected. Total impurities may even improve. But the relative proportions of the individual impurities can shift, and one of them can move from a level that was never detected to a level that is consistently present.

Three consequences follow, none of which shows up on the certificate.

• The customer's related-substances method may have been validated with a resolution that no longer separates the new profile cleanly.
• Their stability data were generated on material with the old profile, and a new degradant can behave differently.
• Their own customer, one step further downstream, may have a specification for an impurity that was previously absent.

A notification with comparability data addresses all three. A notification without it creates three open questions and a customer who now has to re-qualify material they had already qualified.

What good comparability data looks like

At least three batches before and three after, tested on the same methods, with the results presented side by side rather than as summary statistics. Full impurity profile, not only total. Assay, loss on drying, and any attribute the process change could plausibly touch. A statement of what was looked for and not found, because the absence of a new peak is itself a result.

If the change is a scale-up rather than a route change, the relevant comparison is between scales, and the question is whether the larger vessel reproduces the mixing and cooling profile of the smaller one. That is a chemical engineering question with a quality consequence, and it is the one most often left out of a notification.

Upstream changes are still your changes

One step back in the chain, a supplier of a starting material changes its own process. Your site sees material that meets the incoming specification. Nothing on your side has changed, so nothing is notified.

Except that the customer's file describes the starting material and often its source. A change of source is a change in the described chain. Even where the source is unchanged, a process change at that source can alter the impurity profile that arrives at your first step, and your own process may or may not remove it.

The practical answer is a supplier qualification clause that requires your own suppliers to notify you, and a notification duty that passes the information downstream. It is unglamorous and it is the difference between a controlled chain and a chain that merely looks controlled from the outside.

What to put in the agreement

Five lines do most of the work: the categories, the notice periods for each, the data package that must accompany a notification, the named contact on each side, and the consequence of implementing without notification. The last one is the only line that changes behaviour, and it is usually the one left out because it is uncomfortable to draft.

A workable consequence is not a penalty. It is that the batch is treated as unapproved for that customer until the change is reviewed, which converts a commercial risk into an operational one and makes the conversation happen before the shipment rather than after.

Where this leaves a supply-chain partner

We notify before implementation, with the comparability package, and we treat a new purification step as a notifiable change even when the specification is untouched. That costs us a conversation in a quiet month. The alternative costs the customer a variation filed in a hurry against material already in their warehouse, and it costs the relationship more than the change did.

If your supplier's quality agreement has no change-notification annex, the annex is worth more than the discount you negotiated for it.

The comparability package, item by item

What separates a notification from an announcement is the data attached to it. Four items do most of the work.

Before and after, batch by batch. At least three batches on each side, tested on the same methods, presented as a table rather than as a summary statistic. A mean and a standard deviation hide exactly the shift the customer is looking for.

The full impurity profile, not the total. Individual named impurities and unspecified ones, at their actual values. A total that stays at 0.2 per cent can conceal one impurity falling from 0.15 to 0.02 while another rises from 0.01 to 0.12.

What was looked for and not found. If a new solvent was introduced, the statement that its residue was tested and was below the limit is a result. Silence is not, because the customer cannot tell whether the test was done.

The impact statement. A short paragraph naming what the change could plausibly affect: the customer's method, their stability data, their own downstream specification. The supplier knows more about the process than the customer does, and this is the one place where that knowledge has to be volunteered rather than requested.

The ICH Q10 framework treats change management as part of the pharmaceutical quality system rather than as an administrative step, and the European Medicines Agency pages on variations describe what the customer will have to file. Reading the second is the fastest way to understand why the notice period in a contract is usually too short.

How the customer actually uses the notification

The notification enters a process the supplier never sees. It goes to the customer's quality unit, which decides whether the change is reportable under their own licence. It may go to their regulatory affairs group, which decides whether a variation is needed. It may go to their customer, one step further downstream, who has their own file and their own timeline.

Three consequences follow, and none of them is obvious from the supplier's side.

First, the clock that matters is the longest of the three, not the shortest. A thirty-day notice satisfies the quality unit and leaves regulatory affairs with nothing.

Second, a change that is not reportable still has to be assessed, and the assessment takes time. A notification that arrives with a complete package can be assessed in a week. One that arrives with a sentence generates a request for information, and the request sits in a queue.

Third, the customer may say no. That is a legitimate outcome and it is much cheaper to hear before implementation. A supplier who notifies before and accepts a delay keeps the account. One who notifies after keeps the batch and loses the argument.

The connection to method transfer is direct, because a process change is often followed by a method question, and the connection to pharmacopoeia revisions runs the other way: an external revision can force a specification change that then has to be notified on the same terms. Both are easier to manage when the specification gap between the two parties is already documented, and the notification duty itself is set out in the EudraLex volume 4 requirements on quality agreements for the EU market.

Frequently asked questions

What counts as a change that must be notified?

Any change to the site, the process, the specification, an analytical method, the packaging, or the source of a critical starting material. The test is not whether the specification still passes. It is whether anything that a customer's regulatory file describes has moved. A new purification step moves the process description even when every result stays inside limits.

How much notice is normal?

Quality agreements commonly distinguish changes requiring prior approval from changes requiring notification before implementation and changes notified after the fact. The periods are negotiated, and the number matters less than the category. A thirty-day clause applied to a change that requires the customer to file a variation is thirty days of nothing, because the customer's filing takes longer than that.

Why does a purity-neutral change matter?

Because the impurity profile is part of what was approved, not only the total. A new solvent or a new resin can remove one impurity and introduce another at a level that is still within the limit but outside the profile the customer's method was validated against. The specification passes and the validated method's specificity claim quietly weakens.

Do we need to notify if the change is at a supplier of a starting material?

Yes, if that material is critical. The customer's file names the starting material and often its source. A change one step upstream is still a change in the chain the customer described, and the fact that it happened outside your site does not make it outside your notification duty.

What should a notification contain?

What changed, why, when, the batches affected, the comparability data before and after, the impact assessment on the specification and on the customer's methods, and the proposed implementation date. Six items. A notification that says only what changed forces the customer to ask for the other five, which consumes the notice period it was supposed to provide.

What if the customer says no?

Then the change does not proceed for that customer, or it proceeds and the supply relationship ends. This is why the commercial conversation belongs at the start rather than at the end. A supplier who implements first and notifies second has removed the customer's option, and customers tend to remember that at the next tender.