DnXT Labeling — CCDS Compliance, Deviation Control & Submission Due Dates
Your CCDS Is the Standard.
Prove Every Label Still Meets It.
DnXT Labeling compares local labels against the CCDS, classifies what changed, puts a defensible due date on every market, and refuses to let artwork through without an approved change control. Built around how labeling actually works — content, artifact, and execution — not around a text diff.
Stages
Columns
Approvals
Who This Is Built For
Labeling failures are rarely failures of knowledge. They are failures of tracking — and they land on three desks.
You own the Company Core Data Sheet, and every market label is supposed to be consistent with it. In practice you find out about deviations when someone raises them — usually late, usually informally, and usually without the impact assessment that should have accompanied them. When an inspector asks how you know all forty markets are aligned, the honest answer is a spreadsheet somebody maintains by hand.
- Every local label compared against the current CCDS, with a graded verdict per difference
- Deviations as typed records — safety or non-safety, with mandatory rationale and escalation state
- Per-market due dates that update themselves when the CCDS is approved
- An on-time submission rate you can quote without qualifying it
You are told a CCDS change is coming and that your market has a deadline, but the deadline depends on a basis label that has not been approved yet — so the date you have been given is fiction. Meanwhile a change that was deferred for a good reason six months ago now looks like a missed commitment, because the deferral was recorded in an email thread nobody can find.
- Markets blocked on an unapproved basis label report as blocked — never a fabricated date
- Deferrals are first-class records with rationale, approver, and a revised date
- Health-authority-mandated dates override the calculated clock and say so
- The binding constraint is named, so you know which rule is driving your date
Artwork is where labeling stops being a document problem and becomes a physical one. The label text was approved, but the artwork moved ahead of — or entirely outside — the change control that was supposed to authorise it. The failures here are expensive, and the ones that reach the market start as a missing check nobody was assigned.
- Artwork cannot be approved until its CMC change control is approved for implementation
- Artwork under a closed change control is blocked — it is running outside any authorisation
- Required signature authority scales with change magnitude, and a new market escalates it
- Scannable-element verification is enforced, not assumed
How It Works
The chain of custody most systems never model: CCDS text → local label section → artwork → change control → approved component.
The comparison engine extracts document structure — including tables, which is where most naive comparisons fail — and grades each difference on four tiers: verified match, equivalent match, near match, and true difference. Equivalent match explicitly means a formatting-only difference with no change in content, because the standard that matters is consistency in tone, meaning, and placement in an equivalent section — not word-by-word identity. A reformatted paragraph should not generate work.
Each true difference is classified by impact — safety, efficacy, administrative, or formatting. Safety-related deviations carry a hard definition: differences that materially affect safety messaging or benefit-risk, such as new safety messaging, a change in safety hierarchy, a restricted patient population, or altered contraindications, warnings, or precautions. That classification is what determines everything downstream.
Differences are adjudicated one by one — is a deviation, is not a deviation — with a comment required whenever something is called a deviation. The comparison report cannot be generated until every difference has a decision, which removes the most common quiet failure in label review: a difference nobody looked at, in a report that reads as complete. Dispositions and their audit history are retained.
A detected difference can be proposed as a labeling concept, with a suggested change class and the reasoning behind it. The system proposes; it never decides. Nothing is persisted without a named endorser, no proposal arrives pre-classified, and formatting-only differences are never proposed at all because they carry no submission obligation. Classification of core safety information is a governed human judgement, and the software is built to stay on the correct side of that line.
Once a concept has a class and a set of markets, the clock computes each market's due date from the configured classification offsets. Where a class carries two constraints, the earlier one binds — and the system tells you which. Markets waiting on an unapproved basis label report as blocked rather than receiving an invented date. Health-authority-mandated dates override the calculation. Deferrals are recorded with rationale and approver. And a class whose obligation is a tracking-system update rather than a filing deadline never raises a quality event when it lapses.
Before artwork can be approved, the gate resolves its CMC change control by number and checks it is approved for implementation. Missing, unapproved, or closed change controls all block — a closed one because artwork moving under it is running outside any authorisation. Required signature authority scales with the magnitude of the change, and any new market escalates it. Unverified scannable elements block. Missing information never opens the gate, and every blocker is reported at once rather than one per round trip.
Six Labeling Capabilities That Survive an Inspection
Labeling tools demo well on a clean diff. These are the capabilities that matter when the question is why a market was late.
Structural Document Comparison
Structure-aware extraction of PDF and document content, including table-level comparison, graded on four verdict tiers rather than reduced to a text diff. Formatting-only differences are identified as equivalent rather than raised as findings, so reviewers spend their attention on changes that actually carry an obligation.
Deviation Adjudication & Audit
Every difference is adjudicated with a recorded decision and a mandatory comment on anything called a deviation, and the report is withheld until the queue is empty. Dispositions carry a full audit history, which turns a review into evidence rather than a conversation someone remembers differently.
Class-Driven Submission Clock
Configurable change classes drive per-market due dates, with the binding constraint named explicitly, basis-label dependency modelled as a blocking state, health-authority overrides, deferral with rationale, and an on-time rate that excludes markets where no deadline was ever computable — so the metric cannot flatter you.
Eleven-Stage Milestone Chain
Track a labeling change from concept through approval, local implementation, and artwork, with a selectable definition of what counts as the end. Stages whose dates come from outside the system report as unknown rather than pending — an honest distinction that stops a reporting gap from looking like an execution failure.
Artwork Change-Control Gate
Artwork approval is gated on a resolved, currently-approved CMC change control, with signature authority scaled to change magnitude and escalated for any new market. Closed change controls and unverified scannable elements both block. The gate reports every blocker in one pass and never opens on absent information.
Thirty-Column Inspection Extract
A one-command extract of the labeling record in the shape an inspector asks for, with cardinality expansion across markets and a coverage figure so you know what is missing before anyone else does. Blank fields stay blank rather than being padded, and multi-value identifiers remain in a single cell rather than silently splitting a row.
DnXT Labeling vs The Alternatives
Most labeling teams run one of three things today. Each is good at something, and each leaves the same gap.
| Capability | DnXT Labeling | Spreadsheet + RIM | Precedent Search Tools |
|---|---|---|---|
| CCDS-to-local comparison | ✓ Structural, table-aware, 4 verdict tiers | ✗ Manual read-through | ✗ Not a comparison tool |
| Deviation workflow with forced adjudication | ✓ Report blocked until every difference is decided | ● Only as disciplined as the owner | ✗ No system of record |
| Per-market due dates from change class | ✓ Computed, with the binding rule named | ✗ Hand-maintained, silently stale | ✗ Out of scope |
| Basis-label dependency modelled | ✓ Blocked state, never an invented date | ✗ Usually a guessed date | ✗ Out of scope |
| Artwork gated on change control | ✓ Enforced, with authority levels | ✗ A checklist someone owns | ✗ Out of scope |
| Connected to the submission itself | ✓ Same platform as EDMS and publishing | ● RIM stores it; nothing computes | ✗ A lookup tool alongside your systems |
Design Decisions That Matter in a Regulated Process
- No auto-classification — proposals never arrive with a class already applied
- Endorser required — creating a concept with no named endorser is refused, and saves nothing
- Conservative suggestions — the highest-severity class is suggested only on strong signal, and even then asks for confirmation
- Formatting never proposed — no obligation, no record
- Blocked, not guessed — an unapproved basis label yields a blocked state
- Two constraints, earlier binds — and the binding one is named on screen
- Tracking obligations are not deadlines — a class whose duty is a system update never raises a quality event
- Null, not zero — on-time rate is undefined when nothing has been submitted
- Resolved by number — the change control is looked up, not taken on the caller's word
- Closed blocks too — artwork under a closed change control has no live authorisation
- Authority scales — larger changes need higher signature authority; a new market escalates it
- All blockers at once — not one discovery per round trip
- Runs inside DnXT EDMS — the same controlled documents, versions and audit trail
- Part 11 signatures — endorsements and approvals use the platform signature model
- Publishing-connected — approved label content flows toward eCTD publishing
- SPL and artwork generation — structured product labeling output and artwork generation are built in
Know Every Market's Date. Before Anyone Asks.
See the comparison engine, the class clock, and the artwork gate run against your own CCDS and a real local label.
