WorkflowRegulatory Affairs

Local Label Deviation Review

Local label deviation review that reads every label against the CCDS by meaning, not by matching words

Every local label checked against the CCDS meaning by meaning, in its language.

See one case, screen by screen ↓
demo85%of the words still match in the Brazil liver warning — read for meaning, it is critical
demo6,120wordsof an 18-page Portuguese bula back-translated, 58% from translation memory
target2.1daysmedian from a label arriving to every deviation decided
target86%of meanings say the same as the CCDS, so people review only the deviations
In short

What is Local Label Deviation Review?

It is the check that every local label — SmPC, USPI, bula, package insert, IPP, monograph — says what the CCDS says, and that every difference has a reason on file. Local Label Deviation Review reads each label in its own language, back-translates it, pairs every sentence with its CCDS meaning and classifies each row as aligned, acceptable deviation or unjustified, for the medical risk assessor to decide.

How to choose AI solutions for life sciences →

Updated

The problem

Why a local label drifts from the CCDS, and why nobody sees it

Every local label must say what the CCDS says, unless a reason is on file: health-authority-mandated text, a national template rule, local data. But each local label — SmPC, USPI, bula, package insert, IPP, monograph — is written into a national template, often in another language, and meaning drifts on the way — a warning softened, a number changed in a translation round, a contraindication dropped. Checking it today means a vendor back-translation, a side-by-side in Word and a deviation tracker in a spreadsheet, label by label.

The deviations that matter are the hardest to see. A word-level check passes a sentence that keeps 85% of its words and turns “interrupt treatment” into “use with caution”. Justifications sit scattered by country and product, and one approved for another product gets applied by habit. The register lags the labels — and a softened warning in §4.3–4.4 is a patient-safety issue that can also become an inspection finding.

typical18monthsfor one manual label-deviation audit across about 100 countries
estimated32hoursof people time on one label's first pass by hand
Where a label's first-pass hours goestimated
By hand32 days
With the solution1.5 days
  • Translate the label back to English14 → 0.4 d
  • Compare it with the CCDS9 → 0.3 d
  • Classify each difference by medical risk4 → 0.6 d
  • Check the justifications on file3 → 0.1 d
  • Write the register entry2 → 0.1 d

Estimated hours of people time on one label's first pass, by hand and with the agents — the solution's own estimate.

How it works

How a local label is checked

Six agents read, back-translate, pair and classify every local label and draft each fix; the medical risk assessor decides every deviation.

What comes in
Label arrivesLocal labels · any language, any national template
Agents at work
Label Intake Readersections + version
Then
Label Translatorback-translation
Then
Meaning Alignerpairs each CCDS meaning
Then
Deviation Classifierby meaning, not words
Justification Matcher
Then
Remediation Draftercorrected local text
A person decides
Medical risk assessordecides each deviation, signs the review
What comes out
Deviation register
Fixes to each country
Ready for inspection
One case, step by step

One bula, from arrival to a correction with the affiliate

Veltrimab, a biologic for plaque psoriasis and Crohn's disease, has CCDS 15.0, approved Sep 2, and an audit wave of 24 local labels in 15 languages. The register is due at the Nov 20 inspection-readiness review. On Oct 7 the Brazil bula arrives. Here is what happens next, screen by screen, in the working solution.

  1. 0107:20

    The Brazil bula arrives, in Portuguese

    Dr. Maya Chen · Medical risk assessor

    Ana Ribeiro, affiliate regulatory in Brazil, sends Bula profissional v7: 18 pages, reformatted into the national bula template. On the Compare screen every row is a CCDS 15.0 meaning in English beside the Portuguese text as the label reads, with the page it sits on. A rail across the top shows all 24 markets with a status dot each. The verdict column reads “Not read yet”.

    “They compare meaning, not words: a warning that is softened in a sentence that otherwise reads the same is still caught. You decide every deviation.”

  2. 02One click

    “Read and compare” — five agents read the label

    The agents

    The Label Intake Reader finds 13 local sections across the 18 pages. The Label Translator writes a back-translation of 6,120 words, 58% from translation memory, with the labeling glossary applied. The Meaning Aligner pairs all 12 CCDS meanings and finds 1 local addition and nothing missing. The Deviation Classifier and the Justification Matcher follow, each step shown as it runs.

    The Label Translator never corrects a number or a unit, and the original text is always shown beside the reading.

  3. 03Seconds later

    The liver row turns red

    Deviation Classifier

    §4.4 Liver monitoring. The CCDS says to interrupt treatment if drug-induced liver injury is suspected; bula v7 says “usar com cautela” — use with caution. The rest of the sentence is unchanged, so 85% of the words still match, but the action to stop treatment is gone. Rule R-01, unjustified · critical, confidence 0.96. No approved justification for Brazil is on file.

    “85% of the words match the CCDS. A word-by-word check would pass this sentence. Read for meaning, it says something else.”

  4. 04Confirmed

    She confirms it critical; the correction goes to Brazil

    Dr. Maya Chen · Medical risk assessor

    The version history shows bula v6 said “Interromper o tratamento”; the wording changed when v7 was reformatted. Maya confirms critical. The Labeling Committee, chaired by Lena Ortiz, is alerted, and task REM-BR-01 goes to Ana Ribeiro with the correction due Nov 6 — and the corrected Portuguese sentence drafted by the Remediation Drafter from the CCDS and the translation memory.

    “Critical confirmed — Labeling Committee alerted, task REM-BR-01 sent to Ana Ribeiro.”

  5. 05Row by row

    Same meaning, wherever the bula puts it

    Meaning Aligner

    The national template moves sections: dosing sits under “8. Posologia”, the warnings under “5. Advertências”. Each CCDS meaning is paired with the local sentence that carries it and both pages are cited. Of 13 rows, 9 are aligned, 1 is an acceptable deviation and 3 are unjustified — the review shows “Sign review · 2 open”.

    Every pair cites both pages.

  6. 06Two more

    A near match is shown, never applied

    Justification Matcher

    §6.4 Storage: the bula allows room temperature up to 30 °C against 25 °C in the CCDS. JUS-BR-011 allows 30 °C in Brazil — but it was approved for Corventa tablets, not Veltrimab, so it is shown as a near match and a person decides whether it extends. In §4.8, tinea infections read uncommon where the CCDS says common: rule R-03, major. The pregnancy risk statement matches HA-BR-003 word for word and is accepted by rule.

    “Near match: JUS-BR-011 … Approved for Corventa only · §6.4. It is shown, never applied.”

  7. 07Elsewhere in the wave

    A number changed in a translation round

    Diego Navarro · Affiliate regulatory, Mexico

    The Mexico IPP v4 gives the contraception period after the last dose as “al menos 8 semanas”; the CCDS says at least 18 weeks. Rule R-02 makes any changed number in a dose, interval or duration critical. IPP v3 said 18 semanas — the number changed in the v4 translation round. A driving caution added without a source is a minor deviation under R-05.

  8. 08Low confidence

    When the agent is unsure, a person decides

    Deviation Classifier

    Japan's package insert v3 drops “and for at least 18 weeks after the last dose” from the live-vaccine warning. A later precaution may carry it, so confidence is 0.71 — below the 0.80 threshold. The row is marked low confidence and proposed as major under R-01b, for a person to decide between major and critical. The warning box, the percentage frequency bands and the missing driving section are acceptable deviations, each matched to HA-mandated text or a justification on file.

    Below 0.80 confidence goes to a person.

  9. 09Inspection-ready

    The deviation register, with its evidence

    Sam Patel · Labeling compliance

    After Brazil the register holds 37 entries from 21 labels: 21 acceptable with a reason on file, 11 unjustified, 5 unjustified and critical. Each names the CCDS meaning, the local wording in English, the class, the root cause, the justification or task, and its status. Sam signs and exports it before the Nov 20 inspection-readiness review.

    “If it's not in the register with its evidence, it didn't happen.”

  10. 10The wave

    Where the drift comes from

    Lena Ortiz · Global labeling lead

    The dashboard shows the Veltrimab wave: 21 labels compared, 268 meanings, 86% saying the same as the CCDS, 37 deviations. HA-mandated text is the largest root cause and all of it is justified; the drift that needs fixing comes mostly from translation errors and affiliate edits. A market-by-meaning grid opens any label from its cell.

Who it’s for

Built for everyone who answers for a local label.

The same wave, seen by the five people who carry it — in their own words, and what their work looks like now.

MC
Dr. Maya ChenMedical risk assessor · Global Labeling
Medical risk assessor
Before
“Show me the sentence that changed meaning, not the forty that only changed words.” Works from a vendor back-translation and a side-by-side in Word.
Now
Opens a label already read, back-translated, paired and classified, decides each deviation with the rule and both pages in front of her, and signs the review.
LO
Lena OrtizGlobal labeling lead · chairs the Labeling Committee
Global labeling lead
Before
“A justification for one product is not a justification for another.” Runs the audit waves, approves new justifications and chairs Labeling Committee escalations.
Now
Keeps one list of HA-mandated text and justifications by market, product and section; approves any extension, and sees every critical escalation.
SP
Sam PatelLabeling compliance · signs the deviation register
Labeling compliance
Before
“If it's not in the register with its evidence, it didn't happen.” Chases a spreadsheet tracker that lags the labels.
Now
Signs and exports a register where every entry cites both pages and names who decided.
AR
Ana RibeiroAffiliate regulatory · Brazil · owns the bula
Affiliate regulatory
Before
“Send me the corrected Portuguese, and the reason.”
Now
Receives a task with the corrected Portuguese sentence, the reason and the due date for its risk class, and submits the correction to the agency.
DN
Diego NavarroAffiliate regulatory · Mexico · owns the IPP
Affiliate regulatory
Before
“Our template moves sections — compare the meaning, not the order.”
Now
Sees his IPP compared meaning by meaning wherever the national template puts each sentence, and gets a task only for a deviation a person has confirmed.
Built on the engine

6 agents. Each with one job, and hard limits.

Six agents read, back-translate, pair and classify every local label and draft each fix; the medical risk assessor decides every deviation.

Label Intake Reader

Reads each local label where it lives — document type, language, version, sections and pages — and links it to the CCDS version it should follow.

  • Read only — the label file never changes
  • An unknown template goes to a person
Label Translator

Writes an English reading of the label sentence by sentence, using the translation memory and the labeling glossary; the original stays the source of truth.

  • Never corrects a number or a unit
  • The original text is always shown beside the reading
Meaning Aligner

Splits the CCDS and the local label into meaning units and pairs them, even when the local template reorders or merges sections; reports missing meanings and local additions.

  • Every pair cites both pages
Deviation Classifier

Reads each pair for meaning, not word overlap, and proposes aligned, acceptable deviation or unjustified — critical, major or minor — with the rule that fired, the reason and a confidence.

  • Below 0.80 confidence goes to a person
  • Never closes a critical item on its own
Justification Matcher

Checks each deviation against the justification register and the HA-mandated text library for the same market, product and section; exact matches are accepted by rule.

  • A near match — another product or section — is shown, never applied
Remediation Drafter

When a person confirms a deviation, drafts the corrected local sentence in the label language and opens a task for the affiliate with the clock its risk class sets.

  • Drafts only — the affiliate submits
Medical risk assessor

Decides and signs. The agents propose; a named person decides.

Ask in plain words

Ask about any label, in plain words

Ask about a market, a CCDS section, a deviation or the register — or say which rule to add. Every answer cites its sources.

Why is the Brazil liver warning critical?

The CCDS says to interrupt treatment if drug-induced liver injury is suspected. The Brazil bula v7 says “usar com cautela” — use with caution. 85% of the words still match, so a word-by-word check passes it; read for meaning, the instruction to stop treatment is gone. Rule R-01 makes a weakened warning critical. Bula v6 said “interromper o tratamento”. No justification is on file.

What did the Mexico leaflet get wrong?

Three findings in the Mexico IPP v4. The critical one: contraception after the last dose is “al menos 8 semanas” where the CCDS says at least 18 weeks — the number changed in the v4 translation round. A driving caution was added without a source (minor), and the prescription legend is justified by HA-MX-001.

Is the Brazil 30 °C storage justified?

Not yet. The bula allows up to 30 °C; the CCDS says up to 25 °C for 21 days. India and Egypt are justified at 30 °C under JUS-IN-002 and JUS-EG-001. For Brazil, JUS-BR-011 covers Corventa only, so it is a near match. You can extend JUS-BR-011 to Veltrimab with the climate-zone stability report SR-VLT-118.

Add a rule: a dropped anaphylaxis term is always critical

Done. Rule R-08 is on: when §4.8 no longer names anaphylaxis, the deviation is critical and goes to the Labeling Committee. It reclassified the open items that drop the term, such as France. The rule is in Settings and on the audit trail.

Every screen

The working solution, as it ships.

13 screens from the working solution, on its sample data. Pick one to see it large.

CompareThe CCDS, the local label in its own language, the back-translation and the verdict, row by row, with the decision panel on the right.
A label arrivesThe market rail, the new label with its pages and owner, and every CCDS meaning waiting to be read.
Agents at workThe label read, back-translated and paired in view, with what each agent found.
A softened warning“Interrupt treatment” has become “use with caution”: 85% of the words match, and the row is critical under R-01.
Confirmed, with the correction draftedThe decision on the record, the Labeling Committee alerted, and the affiliate task with the corrected Portuguese text.
A near matchA justification approved for another product is shown with its scope, never applied; a person decides whether it extends.
A changed numberEight weeks where the CCDS says eighteen — critical under R-02, with the version where the number changed.
Low confidenceA classification below the threshold is marked low confidence and left for a person to decide.
Local labelsEvery label in the wave: document, language, meaning-by-meaning mix, rows to decide, stage, affiliate owner and due date.
Deviation registerEvery deviation with its class, root cause, reason or task and status — ready to sign and export.
Justifications and HA-mandated textWhat a local label may say differently from the CCDS, and why, by market, product and section.
DashboardLabels and meanings compared, deviations by root cause and by CCDS section, and first-pass review time per label.
Your rulesClassification rules R-01 to R-07, exact-match acceptance and the confidence threshold — all settings.
Governance

Built for inspection: cited, decided by a person, on the record.

Label files are read in placeEach local label is read where it lives, in the labeling repository, read only. The file never changes, and an unknown template goes to a person.
Every deviation cites both pagesEach row names the CCDS page and the local label page it came from, and the register entry carries the same evidence and the person who decided.
Translation never corrects a numberBack-translations keep numbers, units and frequencies exactly as written, and the original-language text is always on screen beside the reading.
A person closes every critical deviationThe agents propose. The medical risk assessor confirms, downgrades or accepts each deviation, and any classification below the confidence threshold is marked low confidence and goes to a person.
Near matches are shown, never appliedOnly exact matches for the same market, product and section are accepted by rule. Extending a justification to another product needs evidence and the global labeling lead's approval.
Every step on the audit trailEvery decision, task, rule change and signature is kept in the audit trail, and the label sign-off records the meaning of the signature.
Configuration

Your labeling rules, not ours

The rules every label is classified by, who approves what and the correction clocks are settings, on the audit trail.

SettingDefaultChoose from
R-01 · a contraindication, warning or monitoring step in §4.3–4.4 missing or weakenedCritical, escalated to the Labeling CommitteeOn · Off
R-02 · a number changed in a dose, interval or durationCritical — the number must match exactlyOn · Off
Accept exact matches to the register by ruleOnOn · Off
Send to a person below this confidence0.800.75 · 0.80 · 0.85 · 0.90
Confirm a critical deviationMedical risk assessor · Dr. Maya ChenDr. Maya Chen · Lena Ortiz · Sam Patel · Omar Haddad · Dana Okafor
Escalate a critical deviation to the Labeling Committee2 business days1 · 2 · 3 business days
Submit the correction — critical30 days14 · 30 · 60 days
Submit the correction — major90 days60 days · 90 days · Next routine update
Connections

Works with the sources a label review already runs on

CCDS libraryapproved Company Core Data Sheets with their version history
Labeling repositorylocal labels and versions, read only — SmPC, USPI, bula, package insert, IPP, monograph, leaflet
Translation memory27 languages · 1.24 M segments
Labeling glossary4,180 terms, MedDRA-aligned
Justifications and HA-mandated textapproved reasons and required national text, by market, product and section
Deviation registerclass, root cause, reason or task, and who decided — exported for inspection
What it changes

The difference, in numbers.

Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
2.1days
median from a label arriving to every deviation decided
By hand6–8 weeks
With agents≈ 2 days
target
86%
of meanings say the same as the CCDS, so people review only the deviations
meanings that match
estimated
1.5h
of people time on each label’s first pass, down from about 32 hours

“demo” = seen in the working solution, on its sample labels · “target” = the design goal, measured in the live solution · “estimated” = the solution's own estimate before deployment · “typical” = published figures (Acolad, identifying local label deviations — a manual audit of about 100 countries that took 18 months). Products and people named on this page — Veltrimab, Corventa, Dr. Maya Chen, Lena Ortiz, Sam Patel, Ana Ribeiro, Diego Navarro — are fictional: characters and sample data in the working solution.

Questions

What labeling teams ask us.

What is local label deviation review?

It is the check that every local label — SmPC, USPI, bula, package insert, IPP, monograph — says what the CCDS says, and that every difference has a reason on file. Local Label Deviation Review reads each label in its own language, back-translates it, pairs every sentence with its CCDS meaning and classifies each row as aligned, acceptable deviation or unjustified, for the medical risk assessor to decide.

How does it compare a local label with the CCDS?

By meaning, not by matching words. The Meaning Aligner pairs each CCDS meaning with the local sentence that carries it, wherever the national template puts it, and the Deviation Classifier reads each pair against the medical-risk rules. A sentence that keeps 85% of its words but turns “interrupt treatment” into “use with caution” is caught as critical.

Does it work in the label's own language?

Yes. Each label is read in its own language, and the Label Translator writes an English back-translation sentence by sentence with the translation memory and the labeling glossary. Numbers and units are never corrected, and the original text is always shown beside the reading. The sample wave covers 15 languages.

How does it handle HA-mandated text and justified deviations?

The Justification Matcher checks every deviation against the justification register and the HA-mandated text library for the same market, product and section. Exact matches are accepted by rule and cited. A justification approved for another product or section is shown as a near match and never applied; extending it needs evidence and the global labeling lead's approval.

What happens when a deviation is confirmed?

The Remediation Drafter drafts the corrected sentence in the label language and opens a task for the affiliate owner with the clock its risk class sets — 30 days for a critical correction and 90 days for a major one by default. A critical deviation is escalated to the Labeling Committee. The deviation register records the class, root cause and who decided.

Do people stay in control?

Yes. The agents propose and never close a critical deviation. The medical risk assessor confirms, downgrades or accepts every deviation and signs each label review; anything below the confidence threshold goes to a person; the affiliate submits the correction; and labeling compliance signs the register.

Can we set our own classification rules and clocks?

Yes. The classification rules, exact-match acceptance, the confidence threshold, who confirms, approves and signs, and the escalation and correction clocks are all settings, kept on the audit trail. New rules can be added in plain words.

How long does it take to go live?

The Agentic Solution Engine builds and deploys it from your requirements and documents — your CCDS, your local labels, your justification register and labeling rules — and it goes live once every quality gate has passed. We will walk you through it on your own labels first.

See it on
your labels.

We'll run Local Label Deviation Review on your CCDS and a sample of your own local labels.