The artwork approval process in pharma is how a drug company reviews and approves packaging, labeling, and promotional materials before they go to print or go live.
Regulatory submission is separate from the artwork approval process; it happens earlier and produces the approved labeling text the artwork must match. The approval process also runs separately from pharmaceutical artwork management systems, which store files and route them to reviewers. Medical, legal, and regulatory (MLR) review is one stage inside this process, not a separate process.
Pharma artwork approval requires more sign-offs than other creative approval because regulators control two things: what a label or ad may say, and how the company documents its approval. Four sets of requirements drive most of the extra work.
In the US, FDA labeling rules sit in 21 CFR Part 201, and prescription drug advertising rules sit in Part 202. In the EU, Directive 2001/83/EC sets label and leaflet content, and the EMA's Quality Review of Documents (QRD) templates set the wording and order for centrally authorized products. The UK's MHRA and Health Canada set their own requirements.
A pack approved for one market can fail in another over warning placement, a missing local statement, or a translation error. Companies usually keep a separate artwork version for each market or language, so changes to shared content must reach every version.
A company must submit each prescription drug ad and piece of promotional labeling to the FDA on Form FDA 2253 when it first uses it, under 21 CFR 314.81(b)(3)(i). The version the FDA holds has to match the version the company's approvers signed off on.
The FDA's Office of Prescription Drug Promotion (OPDP) issues untitled letters, or warning letters for more serious violations, when it finds promotional claims false or misleading. A letter typically asks the company to stop using the material and list every other piece that makes the same claim. A team that can search its approved assets by claim can answer quickly. A team working from email has to rebuild the list first.
When a company signs FDA-required records electronically, such as label control records under 21 CFR Part 211, 21 CFR Part 11 applies. Each signature must show the signer's name, the date and time, and what the signature means, such as review or approval (§11.50). It must also be linked to its record so no one can copy it to another record (§11.70). The system needs audit trails that log who changed what and when (§11.10(e)).
EU GMP Annex 11 sets the equivalent rules for computerized systems used in EU manufacturing: each electronic signature must stay permanently linked to its record and include the date and time.
When a new safety warning is approved or a regulation changes, the team must find every affected asset in every market, then revise, re-approve, and reprint it. This work is called artwork change control, and it starts with knowing which version is live in each market.
In the artwork approval process in pharma, a finished promotional asset passes through four stages in a set order. Regulatory affairs can only check labeling after MLR reviewers finalize the asset's claims.
Outside pharma, the general approval process has fewer required sign-offs.
The four stages apply in full to promotional content. Packaging artwork for cartons, labels, and patient information leaflets often bypasses brand and MLR review because it derives its text from approved labeling and follows its own path to print.
Marketing and creative teams own brand review. They check that the asset follows brand and creative standards before any compliance reviewer sees it.
If they reject it, they send the file back to the design studio. Because no compliance reviewer has seen the file yet, no one has to repeat a compliance review.
Medical, legal, and regulatory reviewers decide whether every claim can stay in the asset. They check that each claim is accurate, supported by the approved label, and legally sound.
If they reject it, they send the file back with the required claim changes. Regulatory affairs only receives the asset after MLR reviewers approve those changes.
Regulatory affairs reviewers confirm that the asset meets the regulator's labeling and submission requirements, including the local rules in each market.
If the problem is a claim, they send the file back to MLR. If the problem is layout or placement, they send it back to design.
Quality Assurance (QA) performs the last check before release. QA reviewers verify that the artwork matches the approved version and confirm that the asset complies with current Good Manufacturing Practices.
Earlier reviewers should catch version mismatches during revision. If they skip that check, QA reviewers become the only people left to catch the problem, and they know the least about earlier changes.
The text on cartons, container labels, and patient information leaflets comes from the labeling the regulator approved for that product and market. Regulatory affairs keeps that approved wording as the master text, and regulatory affairs reviewers check every packaging component against it before it goes to print.
In the pharma artwork approval process, an approver formally approves or rejects the asset and records their name and a timestamp. A reviewer only comments, and a comment does not move the asset forward.
If a team lets reviewers block an asset, any reviewer with an open comment can hold up the asset, even after the approver has cleared it.
Part 11 requires each electronic signature to be linked to the record it signs, so no one can copy the signature onto another record. An approval record must therefore show which actions were binding decisions and which were comments.
Ziflow's multi-stage workflows let a team assign a different reviewer group to each stage. In the workflow template, the team also sets whether a stage advances after a single approval or only after all reviewers approve.
Teams that run pharma artwork approval through email and shared drives face three problems. Even careful people run into them because of how the process works.
A retrospective analysis of FDA recalls from 2012 to 2023 attributes about 8% of recalls to labeling problems, such as label mix-ups and cross-labeling, where a product carries another product's label.
A separate, smaller study of 195 drug recalls from 2017 to 2019 traced 14.9% of that sample to labeling issues.
When a team collects approvals by email, the approvals end up in several people's mailboxes. Some of those mailboxes belong to people who have since left the company.
Months later, an auditor or regulator may ask for that record, and the team has to piece it together from old mailboxes.
Approvals given outside email make the problem worse. When someone writes "looks good" in Slack or approves verbally on a call, no system records that approval.
A team can test this with one question. Can it produce an unambiguous, timestamped record for a disputed version in under five minutes?
Without version control, two reviewers can review different files while believing they are reviewing the same one. A reviewer might open a translated version and mistake it for the latest file.
In another case, a designer revises the file after some reviewers approve it. Those reviewers never see the change, so their approval no longer matches the printed asset.
The FDA recall classification places minor labeling errors and defective packaging as Class III. Class III covers problems unlikely to harm patients but still requiring a recall.
If a team cannot show which version its approvers signed off on, it cannot show how a labeling error reached print.
With Ziflow's FDA-compliant electronic signatures turned on, each approver re-enters their login credentials to sign an approval decision. Ziflow's activity log records every signed decision on the proof.
In Ziflow, a proof is the review copy of an asset. Ziflow enforces the stage order, so a proof cannot reach release until MLR and regulatory affairs reviewers approve it.
For teams evaluating access control, Ziflow's enterprise permissions let an administrator grant each reviewer group access only to the stages and assets covered by its role. Administrators can also separate reviewers who can only comment from decision-makers.
Ziflow's guide to the creative approval audit trail lists the six data points an auditor expects in an approval record and explains how each regulatory framework defines documentation.
For a pharma team, the approval workflow provides a fixed stage order for packaging artwork and a record of who approved which version and when.
Ziflow provides this review and approval workflow. Ziflow does not verify packaging content.
Specialists check barcodes, braille, and print specifications as a separate discipline.
They compare the final artwork against the specification character by character, using inspection software built for the task.
An approval log cannot show whether a barcode scans. A barcode scanner cannot show whether the regulatory approver signed off on the version that went to print.
Everyday Health Group publishes healthcare journalism and handles pharmaceutical advertising that needs medical, legal, and regulatory review.
Before the team adopted Ziflow, reviews ran on paper. Staff put printed materials in a folder called a job jacket and left it on a reviewer's desk.
The team now moves every asset that needs MLR review through defined review stages in Ziflow.
The team tracks its work in Asana. As a proof moves between stages, Ziflow updates and reassigns the matching Asana task, so the team can follow each asset without opening Ziflow.
Teams in other regulated categories, including consumer packaged goods, use the same staged approach.
Ogee is a certified organic brand whose packaging needs regulatory review before printing. Its team routes regulatory and formulation review separately from creative review, so each group sees only its own part.
A team can test its pharma artwork approval process with two questions:
Ziflow enforces approval-stage order and records each review decision with a timestamp.
Get a demo to see a multi-stage pharma workflow set up from brand review through final QA.