WorkflowRegulatory Affairs

Local Label Deviation Auditor

Local label compliance against the CCDS, meaning by meaning, in every language

Every local label read in its own language and checked against the core data sheet, meaning by meaning.

See one case, screen by screen ↓
demo24labelsin 19 languages in one audit wave, each read in its own language
demo3deviationsfound in the Mexico IPP v4 on its first read — 1 critical, 1 unjustified, 1 justified by HA text
target87%of meanings match the core data sheet, so people review only the deviations
target2.1daysmedian from a label arriving to every deviation decided
The problem

Why local labels drift from the CCDS — and why nobody sees it until an inspection

A core data sheet changes once; its local labels change in many languages, each in its own national template, each at its own time. The bula numbers its sections one way, the package insert another, the IPP puts contraception under pregnancy and lactation. A shortened sentence in a reformatted version, or a number that slipped in a translation round, sits in the label until somebody reads it against the CCDS line by line.

That reading is slow work. Someone translates the label back to English, finds where each CCDS meaning landed, decides whether the difference is a health-authority requirement, a template rule or a real error, checks whether a justification is already on file, and writes the register entry. Done by hand across a whole wave, the register is never quite current — and the critical deviation is found late.

target6–8weeksfrom a label arriving to every deviation decided, by hand
estimated≈32hof people time on each label’s first pass
typical18monthsfor one manual label-deviation audit across about 100 countries
Where a label’s first-pass hours goestimated
By hand32 days
With the solution1.5 days
  • Translating back to English14 → 0.4 d
  • Comparing with the CCDS9 → 0.3 d
  • Classifying by medical risk4 → 0.6 d
  • Checking justifications3 → 0.1 d
  • Writing the register entry2 → 0.1 d

Estimated hours of people time on one label’s first pass, by hand and with the agents, as the working solution’s dashboard shows them. The person still decides every deviation.

How it works

How a label moves

Specialist agents read, translate, align and classify every local label and draft each fix; a medical risk assessor decides every deviation.

What comes in
Labels inLocal labels · any language, any template
Agents at work
Label Intake Readersections + version
Then
Label TranslatorEnglish reading
Then
Meaning Alignermeaning by meaning
Then
Deviation Classifier
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 local label, from arrived to signed

The Mexico Información para prescribir (IPP) v4 for Veltrimab arrives at 07:20 from the affiliate. Here is what happens next, screen by screen, in the working solution.

  1. 01Morning

    The whole wave, on one screen

    Dr. Maya Chen · Medical risk assessor

    Maya opens the audit for Veltrimab, CCDS 15.0: 24 local labels in 19 languages, with the inspection-ready register due Nov 20. Eight labels are signed, 13 deviations are waiting for her decision, and four critical deviations sit on the critical wall — Brazil, Argentina, Türkiye and China — each due at the Labeling Committee within 2 business days.

    “China · §4.4 Live vaccines — Local text says at least 8 weeks · CCDS: at least 18 weeks.”

  2. 0207:20

    A new label from Mexico, not read yet

    Dr. Maya Chen · Medical risk assessor

    Diego Navarro, affiliate regulatory for Mexico, has sent the IPP v4: 14 pages in Español, as a DOCX. Maya opens it. The CCDS meanings sit on the left; the local sections, still unread, on the right, in the IPP’s own order.

    “Five agents read it, write an English reading, align every meaning with CCDS 15.0, classify each deviation and check the register. You decide what they find.”

  3. 03One click

    “Run audit” — and the agents read the label

    The agents

    The Label Intake Reader finds 14 pages and 13 local sections. The Label Translator writes an English reading of 5,480 words, 64 % of it from the translation memory, with the glossary applied. The Meaning Aligner pairs all 12 CCDS meanings and finds one local addition; the Deviation Classifier finds three deviations, one of them critical.

    Every step shows what it found, and the last one says who decides: “Ready for a person — Dr. Maya Chen decides.”

  4. 04Aligned

    Meaning by meaning, even when the template moves it

    Meaning Aligner

    Threads join each CCDS meaning to the local sentence that carries it. They cross where the Mexican template reorders sections — §4.6 Contraception lands in “8. Embarazo y lactancia”, the dosing sections in “13. Dosis y vía de administración”. Same meaning in green; justified, unjustified and critical each in their own colour.

  5. 05Read in English

    The English reading, beside the original

    Label Translator

    One switch shows the agent’s English reading, another shows only the deviations. The original Spanish stays the source of truth: the reading is for comparison, and the translator never corrects a number or a unit.

  6. 06Critical

    Eight weeks where the CCDS says eighteen

    Deviation Classifier

    §4.6 Contraception, DEV-MX-08. The CCDS asks for effective contraception for at least 18 weeks after the last dose; the IPP says “al menos 8 semanas”. Rule R-02 — a changed number in a dose, interval or duration is critical — at 97 % confidence, root cause translation error. No approved justification for Mexico · Veltrimab §4.6, and no HA-mandated text in the library. The version history shows why: IPP v3 (Feb 2026) said 18 semanas; the number changed in the v4 translation round (Sep 2026).

    Click any citation to open the source page with the passage highlighted — here the IPP, page 7.

  7. 07Confirmed

    Maya confirms it — the fix is already drafted

    Dr. Maya Chen · Medical risk assessor

    Maya presses “Confirm critical”. The Labeling Committee is alerted, and task REM-MX-01 goes to Diego Navarro with a correction due Nov 6. The Remediation Drafter has written the corrected Spanish sentence from the CCDS and the translation memory, ready for the affiliate to submit.

    “Las mujeres en edad fértil deben utilizar un método anticonceptivo eficaz durante el tratamiento y durante al menos 18 semanas después de la última dosis.”

  8. 08Next open item

    A driving caution the CCDS does not support

    Dr. Maya Chen · Medical risk assessor

    §4.7: the CCDS says Veltrimab has no or negligible influence on driving; the IPP adds “se recomienda precaución al conducir u operar maquinaria”. Rule R-05 makes it a minor, unjustified deviation. Maya confirms it, and REM-MX-02 waits for the next routine update. The prescription-sale legend was accepted by rule — an exact match to HA-MX-001.

  9. 09Signed

    The Mexico review, signed

    Dr. Maya Chen · Medical risk assessor

    With every item decided, Maya signs the review. The sign-off lists the three register entries and their outcomes — task REM-MX-01, task REM-MX-02, HA-MX-001 — and records the meaning of her signature with it.

    “I confirm every deviation in this label is classified, each justified deviation has its reason on file, and each unjustified or critical deviation has a remediation task.”

  10. 10Before Nov 20

    Into the inspection-ready register

    Sam Patel · Labeling compliance

    DEV-MX-08 and DEV-MX-09 now sit in the deviation register as signed, with the CCDS meaning, the local wording, the class, the root cause and the task. Maya asks Sam Patel, who signs the register for labeling compliance, to sign it before the Nov 20 inspection-readiness review; the register exports in one step.

Who it’s for

Built for everyone who owns a local label.

The same Mexico IPP, seen by the four people who carry it — from the assessor who decides to the affiliate who files the fix.

MC
Dr. Maya ChenMedical risk assessor · Global Labeling
Medical risk assessor
Before
Reads each label against the CCDS herself, through a back-translation, before she can judge the risk.
Now
Starts from the aligned label with each deviation classified, the rule that fired and both pages cited; decides and signs.
LO
Lena OrtizGlobal labeling lead
Global labeling lead
Before
Learns of a critical deviation when it is already late for the Labeling Committee.
Now
Runs the audit wave from one screen, with every critical deviation on the critical wall and its committee clock beside it; approves each new justification.
SP
Sam PatelLabeling compliance
Register signer
Before
Assembles the deviation register by hand before an inspection, chasing who decided what.
Now
Signs and exports a register where every entry carries the reason, the evidence and the person who decided.
DN
Diego NavarroAffiliate regulatory · Mexico
Affiliate
Before
Gets a finding and has to work out the corrected local wording himself.
Now
Gets a remediation task with the corrected Spanish sentence already drafted and the due date the risk class sets.
Built on the engine

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

Specialist agents read, translate, align and classify every local label and draft each fix; a 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
  • Unknown template goes to a person
Label Translator

Writes an English reading of the label using the translation memory and the labeling glossary, sentence by sentence; 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 aligns them, even when the local template reorders or merges sections; reports missing meanings and local additions.

  • Every pair cites both pages
Deviation Classifier

Classifies each aligned pair as aligned, justified, unjustified or critical with the medical-risk rules, and says which rule fired.

  • 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; exact matches are accepted by rule, near matches are shown to a person.

  • A near match is never applied automatically
Remediation Drafter

Drafts the corrected local sentence in the label language and opens a remediation task for the affiliate with the clock that the 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 it about any label, in plain words

Ask about any local label, deviation or justification — or tell it what to change. Answers cite the CCDS and the local page.

Which critical deviations are still open?

Four are waiting for you: Brazil §4.4 liver monitoring, Argentina §4.3 contraindications, Türkiye §4.2 Crohn’s dosing and China §4.4 live vaccines. The China clock ends today.

Why is the Brazil liver-test sentence critical?

The CCDS asks for liver enzymes and bilirubin at baseline and monthly up to week 12, and to interrupt treatment if liver injury is suspected. The Brazil bula v7 keeps only “no início do tratamento” — at the start of treatment. Two safety steps are missing, so rule R-01 makes it critical. Bula v6 still had the full sentence; it was shortened when v7 was reformatted. 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.

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 where the term is missing, France among them. The rule is in Settings and in 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.

The audit waveLabels signed, critical deviations open, decisions waiting, where the deviations come from, and the critical wall with its committee clocks.
A label arrivesThe Mexico IPP v4, not read yet: the CCDS meanings on the left, the local sections on the right, ready to audit.
Agents at workRead, English reading, meanings aligned, deviations classified, the register checked — each step with what it found.
Meaning by meaningThreads join each CCDS meaning to its local sentence, crossing where the local template reorders sections.
The English readingThe agent’s English reading beside the original, filtered to the deviations only.
The source passageEvery citation opens the source page with the passage highlighted — here IPP v4, page 7.
Confirmed, with the fix draftedA confirmed critical deviation alerts the Labeling Committee and sends the affiliate a task with the corrected local text.
The next open itemA driving caution added without a source: unjustified and minor under rule R-05, with no justification on file.
Sign the label reviewEvery entry and its outcome, and the meaning of the signature, recorded with the assessor’s sign-off.
The deviation registerEvery place a local label differs from the CCDS — the reason, the evidence and the person who decided. Inspection-ready.
Justifications and HA-mandated textWhat a local label may say differently from the CCDS, and why, by market, product and section.
The labeling dashboardLabels audited, meanings compared per week, root causes, deviations by CCDS section and first-pass time per label.
Your rulesClassification rules R-01 to R-07, accepting exact matches by rule, and the confidence below which a person decides.
Governance

Built for labeling compliance: cited, decided, signed.

Label files are read, never changedLocal labels are read in place from the labeling repository, read only. Corrections are drafted as tasks; the affiliate submits the variation.
Both pages cited on every deviationEvery deviation cites the CCDS page and the local label page. Click a citation to open the source passage, highlighted.
Numbers are never translated awayThe English reading never corrects a number or a unit, and the original text is always shown beside it — so an 8 that should be an 18 stays visible.
A person closes every critical deviationThe agents propose; a named medical risk assessor confirms, downgrades or accepts. Classifications below the confidence threshold go to a person, marked low confidence.
Near matches are shown, never appliedOnly an exact match to the register — same market, product and section — is accepted by rule. A justification for another product is shown as a near match, and extending it needs evidence and the global labeling lead’s approval.
Every decision on the audit trailEach decision, task and signature is kept in the audit trail. Each label review is signed with the meaning of the signature recorded, and the register is signed by labeling compliance.
Configuration

Your labeling rules, not ours

The classification rules, approvers and clocks are settings your team owns.

SettingDefaultChoose from
Classification rules8 rules, R-01 to R-07 and R-01b, all onTurn each on or off · add a rule by asking the assistant
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 deviationDr. Maya Chen, medical risk assessorDr. Maya Chen · Lena Ortiz · Sam Patel · Omar Haddad · Dana Okafor
Approve a new justificationLena Ortiz, global labeling leadDr. Maya Chen · Lena Ortiz · Sam Patel · Omar Haddad · Dana Okafor
Sign the deviation registerSam Patel, labeling complianceDr. 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
Connections

Works with the labeling systems you already run

Labeling repositorylocal labels and versions, read only
CCDS librarycore data sheets with their version history
Translation memory27 languages, 1.24 M segments
Labeling glossary4,180 terms, MedDRA-aligned
Justification registerapproved reasons a label may differ
HA-mandated text libraryrequired national text, by market
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
87%
of meanings match the core data sheet, 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 for a fictional product · “target” = the design goal, measured in the live solution · “estimated” = the solution’s own estimate of people time · “typical” = published figures (a published label-deviation audit case study: about 100 countries, 18 months). People, companies and products named on this page are fictional — characters and sample data in the working solution.

Questions

What labeling teams ask us.

What is a local label deviation audit?

A check of each country’s label — SmPC, prescribing information, bula, package insert, monograph or leaflet — against the Company Core Data Sheet (CCDS), recording every place the local text says something different, why, and what will be done about it. The result is a deviation register you can show an inspector.

How does it compare labels written in other languages?

The Label Translator writes an English reading sentence by sentence, using your translation memory and labeling glossary, and the Meaning Aligner pairs each CCDS meaning with the local sentence that carries it, wherever the local template puts it. The original text stays the source of truth and is always shown beside the reading.

How are deviations classified?

The Deviation Classifier applies your medical-risk rules — for example, a missing contraindication, warning or monitoring step in §4.3–4.4, or a changed number in a dose, interval or duration, is critical — and says which rule fired, with a confidence. The Justification Matcher then checks the justification register and the HA-mandated text library, so required national text is recognised as justified.

Does a person stay in control?

Yes. The agents propose; a named medical risk assessor confirms, downgrades or accepts each deviation, and no critical item is closed by an agent. Anything below the confidence threshold goes to a person, near matches to the register are never applied automatically, and the label review and the register are each signed.

Does it change our labels?

No. Labels are read in place from the labeling repository, read only. The Remediation Drafter drafts the corrected local sentence and opens a task for the affiliate, who submits the correction.

What happens when a critical deviation is confirmed?

The Labeling Committee is alerted, the affiliate owner gets a remediation task with the corrected local text drafted, and the correction is due on the clock the risk class sets. Both the escalation window and the correction clocks are settings.

Which systems does it connect to?

Your labeling repository, CCDS library, translation memory and labeling glossary, plus the justification register and the HA-mandated text library. It produces the deviation register, cited side-by-side comparisons, remediation tasks and a compliance dashboard.

How long does it take to go live?

The Agentic Solution Engine builds and deploys it from your requirements — your CCDS, a sample of local labels, your justification register and your classification 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 local labels.

We’ll run the Local Label Deviation Auditor on a sample of your own local labels and your CCDS.