CCDS label change management that finds every local label on day one and puts every market on its own clock
Every local label a CCDS change touches found, with every market on a clock
See one case, screen by screen ↓When the labelling committee approves a new Company Core Data Sheet, every local label has to follow: the USPI and Medication Guide, the EU SmPC and package leaflet, the Canadian Product Monograph, the Brazilian bula, the Japanese package insert and more. Each has its own template, language, procedure and deadline. Working out which markets, which documents, which sections and which registered deviations a change touches is done by hand, in spreadsheets, over the first days after approval.
Every market is then tracked against the company deadline — 30 days for a safety-critical change — but some markets close earlier. Japan's PMDA consultation cycle can shut before the company clock runs out, and that is found only when it is missed, so the new warning reaches Japanese patients a revision cycle later. Meanwhile head office overwrites wording ANVISA asked Brazil to add, and an affiliate's shortened leaflet quietly drops a safety sentence.
Estimated split of the change and impact assessment for one safety change across about 16 markets, by hand and with the solution, in working days.
Six agents compare, classify, map, draft and forecast every change; the labelling lead decides deviations and pull-forwards.
Northwind Bio is a fictional company in the working solution. Today is October 7. Veltrimab CCDS 15.0 is already cascading through 16 markets, and at 08:10 the labelling committee approves Talmirex CCDS 23.0 with a new warning for severe skin reactions. Here is what happens next, screen by screen.
Maya opens the cascade for Veltrimab CCDS 15.0, approved Oct 2 after the final report of study VLT-305 on drug-induced liver injury. The change sits at the root — a new §4.4 warning, §4.8, §4.6, §4.2 and §5.2 — and branches to 26 local labels in 16 markets. The forecast line reads 11 on time, 2 tight, 1 will miss, 2 submitted. Japan is red: its PMDA window closes Oct 23, and at today's pace it files Oct 27.
“Forecast against each market’s own deadline.”
Talmirex CCDS 23.0 adds a §4.4 warning for Stevens-Johnson syndrome and toxic epidermal necrolysis, SJS/TEN as rare in §4.8, and an editorial §4.2 change. No market is on a clock yet. Maya runs the cascade: the CCDS Comparer aligns 22.0 and 23.0 section by section and finds 3 changes; the Safety Change Classifier marks 1 safety-critical, 1 safety, 1 editorial with reasons cited; the Label Impact Mapper finds 26 local labels and 2 registered deviations touched; the Local Text Drafter drafts 12 markets from translation memory and sends 4 to the vendor.
Every agent step runs in view, with its result and how long it took — about a second each.
Sixteen country tasks are open, the company deadline is Nov 6, and the forecast reads 14 on time, 1 tight, 1 will miss. Japan's PMDA consultation must be filed by Oct 28. With Japanese back from the vendor Oct 16 and affiliate review by Kenji Mori to Oct 24, the consultation pack would be filed Nov 2. China is tight: Nov 3 against Nov 6.
“Will miss by 5 days · deadline Oct 28 · forecast filing Nov 2.”
The Deadline Planner has found a way back: express vendor return on Oct 13, not Oct 16, for USD 2,100, and Kenji Mori reviews each section as it lands. Maya clicks “Pull Japan forward”. The row turns amber, Japan now files Oct 27 — one day before its window — and the vendor and Kenji are notified. The planner proposed it; it spends nothing until she clicks.
“Pulled forward by Dr. Maya Chen · vendor and Kenji Mori notified.”
Brazil's bula profissional draft opens as an English master, each sentence marked as approved CCDS wording or registered local deviation, to be translated into Portuguese from memory once Maya decides. DEV-BR-009 — an ANVISA letter requiring a patient alert for severe skin reactions with antiepileptics — covers the new §4.4 warning. The drafter kept it and asks Maya: keep the local wording (recommended) or align to the CCDS. She keeps it in one click, and the register re-confirms it today.
The Local Text Drafter never overwrites a registered deviation.
Maya approves the Brazil draft for Talmirex CCDS 23.0 — bula profissional and bula paciente — and sends it to Rafael Souza for affiliate review. The dialog shows the changes, her decision (C1 deviation kept), the meaning “Approved by the global labeling lead” and the signer.
“Your signature, its meaning and the time are stored with the record.”
Opening the Veltrimab change shows each section as a redline against 14.2, the markets it lands in and how many need checking. The summary reads 5 changes, 1 safety-critical, 16 markets, 26 local labels, 68 sections to update, 5 deviations or edits to check and 5 already aligned. Omar Haddad, the global medical lead, confirmed the safety-critical class.
The classifier never settles a safety-critical class without the global medical lead's confirmation.
Each cell says what the local text needs: Update, Aligned, Deviation, Diverging or Vendor. Brazil's §4.4 meets registered deviation DEV-BR-004 — liver tests every 3 months, from an ANVISA letter. Switzerland's §4.8 and Turkey's §4.6 have their own deviations. Mexico's §4.4 is marked Diverging.
The mapper never marks a passage aligned without a cited local sentence.
Ana Torres shortened the Mexico IPP on Oct 6 and removed “y periódicamente después” from the monitoring sentence. The Meaning Checker back-translated it: without it, patients are tested only once, before treatment — weaker than CCDS 15.0, and no registered deviation covers it. Maya can send it back with the CCDS sentence, escalate it to Carlos Mendes, the Americas head, or accept it with a justification that needs Safety sign-off.
“The affiliate’s edit changes the meaning.”
The Countries tab lists every market's local labels, procedure, stage and forecast against its own deadline, with the affiliate owner: Mexico in affiliate review with a diverging edit, Japan filing Oct 27 against Oct 23, Brazil drafted and filing Oct 20. Late markets escalate to the regional head, with the task and sources.
The planner escalates only to named people, and its dates follow the clock rules in Settings.
The same change, seen by the people who own it globally, file it locally and sign off its safety text.
Six agents compare, classify, map, draft and forecast every change; the labelling lead decides deviations and pull-forwards.
Aligns the previous and the new CCDS by section number and heading and lists every real change with its old and new text and the page in both versions.
Classifies each change as safety-critical, safety or editorial, with the reason and the study report, agency request or committee minutes it rests on — and so sets the clock that follows.
Uses the registration data and the CCDS-to-local section map to find every market's documents and sections, comparing meaning, not words: Update, Already aligned, Not in this label, or Deviation.
Drafts local wording sentence by sentence in each market's language and template: approved translation memory first, then local template wording, then new translation marked for a linguist.
Opens a country task per market with its procedure, submission date and affiliate owner, forecasts each filing against the market's own deadline, proposes pull-forward plans and escalates late markets every morning.
Back-translates each affiliate edit and compares its meaning with the CCDS, checking the deviation register for a justification before it flags anything.
Decides deviations and pull-forwards. The agents propose; a named person decides.
Ask in plain words — or tell it what to change. Every answer points to its source.
Which markets are at risk on the Veltrimab safety deadline?
Each market is forecast against its own deadline, not just the company's Nov 1. Japan will miss: its PMDA consultation window closes first. Mexico is tight with a diverging edit to re-review, and China is tight with Chinese back from the vendor Oct 14.
What changed between CCDS 14.2 and 15.0?
Five changes: a new §4.4 warning for drug-induced liver injury, with liver tests before and during treatment (safety-critical); §4.8 liver injury added as uncommon and urticaria now common; §4.6 pregnancy outcomes data from 318 pregnancies; and editorial changes to §4.2 and §5.2.
Why is Brazil keeping “every 3 months”?
Because ANVISA asked for it in 2024 (deviation DEV-BR-004). CCDS 15.0 says “periodically”; the stricter local wording still meets the core safety information, so the drafter kept it and asked the global labelling lead.
Add a rule: never overwrite a health-authority deviation
Done. Every deviation in the “Health-authority mandated” category is now locked — like Brazil's every-3-months liver tests and Turkey's pregnancy category. Only a new health-authority letter can retire one. The rule is on in Settings and recorded in the audit trail.
13 screens from the working solution, on its sample data. Pick one to see it large.
The clocks every market is measured against, the drafting rules and who approves what are settings.
| Setting | Default | Choose from |
|---|---|---|
| Safety-critical changes — submit within | 30 days | 15 days · 30 days · 45 days, counted from labelling committee approval |
| Safety-critical changes — implement within | 90 days | 60 days · 90 days · 120 days |
| Other safety changes — submit within | 90 days | 60 days · 90 days · 180 days |
| Use translation memory at or above | 85% | 75% · 85% · 95% — lower matches go to a linguist or the vendor |
| Global drafts and deviations decided by | Dr. Maya Chen | Dr. Maya Chen · Lena Ortiz · Dana Okafor |
| Safety-critical wording signed off by | Omar Haddad | Omar Haddad · Dr. Maya Chen |
| Local text approved by | Affiliate regulatory manager | Affiliate regulatory manager · Affiliate head |
| Escalate a late market after | 3 days | 1 day · 3 days · 5 days — to the regional head, with the task and sources |
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
“demo” = seen in the working solution, on its sample data · “target” = the design goal, measured in the live solution · “estimated” = our estimate · “typical” = published labelling benchmarks (30 products × 15 markets × 4 updates ≈ 1,800 local revisions a year; change and impact assessment by hand takes days 1–10) and typical company clocks (safety-critical changes submitted within 30 days). Northwind Bio, its products, studies and the people named on this page are fictional — characters and sample data in the working solution.
It is the work of carrying a change to the Company Core Data Sheet into every local label it touches — finding the markets, documents and sections, drafting the local text, filing the right procedure in each market and tracking each one to submission. CCDS Label Change Management does the comparison, mapping, drafting and forecasting with six agents, and the global labelling lead decides.
The CCDS Comparer lists each change between the old and new versions. The Label Impact Mapper then uses the registration data and the CCDS-to-local section map to find each market's documents and sections, and compares meaning, not words, to mark each one Update, Already aligned, Not in this label or Deviation.
The Deadline Planner forecasts each market's filing date from the steps still ahead — vendor return, affiliate review, filing pack — and compares it with that market's own deadline, not only the company one. A market that will miss turns red on the first day, with a costed way back that the lead accepts in one click.
No. The Local Text Drafter never overwrites a registered deviation; it keeps it and shows the global labelling lead both versions to decide. A setting can lock every health-authority-mandated deviation so only a new health-authority letter retires it.
The Meaning Checker back-translates the edited sentence, compares it with the CCDS and checks the deviation register. Removed or weakened safety information is always flagged, in plain words, before submission; the lead can send it back, escalate it to the regional head or accept it with a justification.
Yes. It drafts sentence by sentence from approved translation memory first, then local template wording, and marks every sentence with its source. Languages below the memory threshold — 85% by default — go to the translation vendor automatically.
Yes. Agents draft and forecast; a person approves every local text. The global labelling lead decides deviations and pull-forwards and e-signs each draft, the global medical lead signs off safety-critical wording, affiliates approve their local text, and the planner spends or notifies nothing without the lead's click.
The Agentic Solution Engine builds and deploys it from your requirements and documents — your CCDS versions, local labels, translation memory, registration data and deviation register — and it goes live once every quality gate has passed. We will walk you through it on one of your own past CCDS changes first.
Every agency change reaches the right team within hours, with what changed marked.
1-min demoCTD Module 2 AuthoringModule 2 summaries drafted in weeks, every statement cited to its source.
1-min demoHealth Authority Query ResponseCited first drafts within hours, consistent with every past answer to every agency.
1-min demoWe'll run CCDS Label Change Management on one of your own past CCDS versions and its local labels.