Change Management Notification and Approval Requirements in Pakistan

1. Key takeaways

Change management in Pakistan follows a fixed order of judgement: first determine which object the change falls on — the product or the institutional licence; then determine whether it belongs to the approval type or the notification type; and finally pay the fee according to the corresponding entry in Schedule C. General changes are charged at 50 per cent of the relevant fee. The two errors that occur most often in practice are treating a notification-type change as if no action were needed at all, and treating an approval-type change as something that can be done first and declared later. Both errors have the same root: a change that looks commercially small can still be legally significant, and the classification under the rules does not track the commercial size of the edit. A notification-type change still requires a submission within its category, and an approval-type change implemented before approval leaves the marketed product inconsistent with the authorised file. Building the classification step into the internal change process, before implementation rather than after, is what keeps the certificate and the market reality aligned. The order matters as much as the content: an object misidentified at step one produces a wrong classification at step two and a wrong fee at step three, so the first question — product or institutional licence — deserves the most careful answer.

2. Legal basis

The provisions that govern changes are set out below: the fee basis in Schedule C reached through Rule 63, the annotation governing the 50 per cent charge for general changes, the five-year validity against which changes must be coordinated, the label consistency rule, and the online submission channel that all change applications now use.

3. Expert insights

Insight one: Rule 14(6) turns label changes into a high-risk category. Any adjustment to the label must be checked back against the approved version in the country of origin or the reference country. This means a label change cannot be decided locally in Pakistan alone; it requires synchronisation on the source side. The Pakistani artwork is legally a derivative of the approved master, so a local edit that has no counterpart at the origin creates a document that matches nothing. The operational consequence is that marketing teams in Pakistan and regulatory teams at the origin need a shared trigger: whenever either side contemplates a label edit, both sides review it. A change process that treats the label as a local marketing asset rather than a regulated derivative will generate inconsistencies that surface later, usually during a patrol or a renewal review.

Insight two: changes to the institutional licence and changes to the product certificate are two separate lines. The institutional licence is the foundation of the applicant’s qualification (Rule 14(1)(b)). Once institutional information changes, the associated information on the product certificates must follow, otherwise the certificate and the system data become inconsistent. The two lines move at different speeds and through different forms, which is why they are easy to leave half-finished: the licence update is granted, everyone congratulates themselves, and the product certificates still show the old importer details. An inconsistency of that kind is not cosmetic — it is the kind of mismatch that complicates customs clearance, renewal and any later deficiency response, because each of those proceedings starts by reading the certificate and the system record as if they described the same entity.

Insight three: stacking a change on top of a renewal is a timing trap. Within the five-year cycle, changes submitted close to the renewal date cross paths with the renewal process itself. GRZAN recommends handling them within the same round, avoiding duplicate submissions of the same materials and inconsistent review standards between the two proceedings. A change filed three months before renewal may be examined against one version of the file while the renewal is examined against another; merging them into one proceeding removes that ambiguity and saves one round of fees and correspondence. It also shortens the total calendar, because the materials supporting the change and the materials supporting the renewal overlap far more than either filing admits on its own.

4. Practical recommendations

GRZAN requires clients to maintain a change ledger recording: the content of each change, the date it was raised, its classification (approval or notification), the fee, the submission channel, the date of approval, and whether the change triggers a label or system data update. The ledger is reviewed in full once before every renewal, which prevents the situation of holding a certificate whose underlying information has gone stale. The ledger also disciplines decision-making at the moment a change is proposed: writing down the classification and the fee before implementation forces the team to confront the legal category of the change rather than its commercial convenience. Over a five-year certificate life the ledger becomes, in effect, the audit trail of the product’s evolution in Pakistan, and it materially shortens the renewal preparation because every historical change has already been documented once, at the moment it happened, by the people who handled it. Where a client inherits a product from a previous distributor without such a ledger, reconstructing the change history from correspondence is slow and error-prone, which is precisely why GRZAN insists the ledger start on day one.

5. Verification checklist

• □ A change ledger has been established with classification (approval / notification)
• □ Fees have been checked against the corresponding Schedule C entry (general changes at 50 per cent)
• □ Label changes have been checked against the source-side approved version (Rule 14(6))
• □ Institutional information changes have been synchronised to the product enlistment / registration records
• □ Changes have been submitted through the e-Services portal with approvals retained

Regulatory information verified as of October 28, 2026.

How GRZAN can help. GRZAN provides medical device and IVD registration, quality system, authorised representative and local testing support across South Asia, including Pakistan. Our team prepares dossiers to DRAP expectations, manages eCTD-format submissions and deficiency responses, and supports post-market vigilance obligations. Business enquiries: info@grzanglobal.com