Keep the labelling change as one record: the order clock that fires a few times a year, and the core-sheet cascade that fills the rest of it, held for the named signatory.
An order arrives, and the notification, the evidence behind it and the applications it touches enter one record.
02
A clock starts at receipt, and the response, discussion and action dates are re-derived whenever one of them moves.
Reason
03
A change is proposed, and the evidence it would rest on is gathered before a supplement or a rebuttal is drafted.
04
A pathway is picked per change as a written determination against 21 CFR 314.70 or 601.12, not the last one used.
05
A leaflet change is split from an SmPC change: Article 61(3) and the variations framework run different clocks.
Decide
06
A core sheet version is approved, and the markets it obliges are listed with the framework in force on filing day.
07
A local label is read section by section, and each divergence is held open until it carries a reason and an owner.
Out
08
An approval lands, and submission, approval, implementation, artwork version and effectivity stay on the label file.
09
A write action runs only inside the approval boundaries agreed during implementation.
→Product statement
The agent assembles the change record; a named regulatory and safety signatory approves the text and files it — and a change filed wrong travels on into artwork, promotional copy and periodic reports.
Example workflow
One change, order to effectivity
AgentHuman
1Order or change receivedOrder notification, signal outcome, core-sheet proposal or partner request
2Record assembledClocks, affected markets, evidence and current label text, each with its source
3Pack draftedPathways, divergences, open items and confidence
4Controls appliedReconciliation tests, clock checks, pathway determinations and confidence threshold
No human action required
Stages 1 to 4 run unaided, and nothing is filed at any of them — the agent is building the record, and the signatory lane opens at the confidence gate.
5DecisionBranches at the confidence threshold
High confidence
Goes to the regulatory signatory.
Low confidence
Adds a labelling committee read first.
Signatory approval
The pack is held with its sources, its open divergences and the confidence.
Approve · Amend · Send to labelling review
Approved — released to file▼
6Label record updatedOnly where write access and approval policy allow it
7Outcome evaluatedAmendment distance, divergence outcomes, agency questions and implementation gaps found later
Amendments
Every signatory amendment is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Approving the wording that goes on the label.
Deciding a labelling change is or is not required.
Assessing whether new safety information exists.
Signing a supplement, variation or notification.
Automation boundaryAgent acts unaided
✓Compute the order clock and re-derive it when a date moves.
✓Compare the core sheet to each local label, section by section.
✓Gather the evidence a proposed change or rebuttal would rest on.
✓Name each divergence, its owner and what is still open, and hold.
Writes run only inside the boundaries agreed at implementation, never ahead of a signature.
Concluding that a rebuttal position is defensible.
Agreeing a divergence with a national agency.
Choosing what a translated label should say.
Changes to mapping, clock or approval rules.
Example output
One market label, annotated
Everything the agent compiles is set beside the document it was read from.
Labelling change output · single marketIllustrative example
Market
Section compared
Since approval
Source of record
Confidence
Signer of record
Partner-held market
Warnings and precautions, two core-sheet versions behind
142 days
Core data sheet, dated
84%
Regulatory signatory files
As receivedTaken from the core data sheet and the local label on file — nothing on this side is written by the agent.
Source facts usedCore sheet, datedApproved local labelFiling and approval log
Why this is openThe change cleared in this market and has not reached the artwork in the channel.
ActionApproveAmendSend to labelling review
What the score decidesBelow the configured threshold the divergence picks up a labelling committee read before the signatory sees it.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Each marketFrom the core-sheet change
03Reconciliation
Read the sheet against the label
The core data sheet has no legal existence — GVP Module VII, Rev 1 calls it a practical option — and it still drives the work.
01Approved path
The signatory owns the words
The agent never approves label text, never decides that a change is required, and never assesses whether new safety information exists.
02Human review
Signal, report, label
Signal detection works a hypothesis, aggregate reporting works a calendar, promotional review reads claims against the approved label. This page changes the label.
04Build an evidence trail
The change, the source it rests on and the signatory who approved stay on the label file.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Regulatory informationVeeva Vault RIM ArisGlobal · Ennov RIM
Label content and artworkLabelling content systems Artwork and packaging management
Safety and signal sourcesArgus · signal register Aggregate and RMP records
Agent
Safety labelling change
Reads the sources Reconciles the labels Holds for the signatory
Submission and archiveeCTD publishing systems Document and QMS systems
A portfolio-wide reconciliation-coverage figure is published by no regulator we found, and no rule requires the register it would come from. Nestack reports the divergence rate by label section, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Partner-held markets
8.9%
3.6×
Review
Warnings and precautions
6.2%
2.5×
Review
Leaflet-only changes
4.5%
1.8×
Watch
Core EU and US labels
1.8%
0.7×
Normal
Bar: divergence-rate lift vs. core-label baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
A cycle ends by leaving a test behind
A cycle is done when the unreconciled label has become a case the next release must pass. That suite is what the next change tracked is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Divergence rate rises for one label section.
02Diagnose
The market still carrying a sentence the core sheet dropped last year is read back through its filings until the cause narrows to one.
03Improve
Stamp the change; the labels behind it are filed against that number.
04Verify
Each touched label case runs once more, and one red holds it.
05Learn
It stays as a standing test, and the mapping rules move with it.
Learn → DetectThe return edge. The next change runs against a suite one case longer.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, reconciliation workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Labelling workflow discovery and boundary mapping.
02Label and regulatory source assessment.
03Core-sheet, market and reportability rule mapping.
04Label and core-sheet ingestion.
05Reconciliation logic and source binding.
06Confidence scoring and exception routing.
07Signatory approval workflow.
08Regulatory and artwork system integration.
09Reconciliation and clock cases.
10Guardrails and signature controls.
11Label-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne product, one marketProductionProduction label systemsAdvancedMultiple products / markets
Introduced at Pilot
Reconciliation and clocks✓✓✓
Held for the named signatory✓✓✓
Reconciliation-coverage baseline✓✓✓
Introduced at Production
Reporting by label section—✓✓
Exception workflow in your systems—✓✓
Approved write-back—✓✓
Label-repository integration—✓✓
Introduced at Advanced
Many-market cascades——✓
Multi-stage signatory routing——✓
High label count——✓
Multi-market labelling controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your product list and the markets they sit in→Core-sheet, market and reportability rule mappingWeek 1
02Your current core data sheet and local labels→Ingestion, section alignment and the reconciliation baselineWeek 2
03Your divergence history and the reasons behind it→Divergence register and automation-boundary definitionWeek 1
04Access to relevant APIs, feeds or exports→Label and regulatory source assessment, then integration setupWeek 2
05Labels you would not want compared→Order cases and failure-mode testingWeek 4
06What no label change may skip→Confidence scoring, exception routing, guardrails and approval controlsWeek 3
07Named regulatory and safety signatories→Signatory approval workflow, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
The schedule reflects the weeks the work really fills, which is why one band in week five doubles.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Labelling workflow discovery, rule mapping and the automation boundaryW2Source integration and the reconciliation baselineW3Reconciliation workflow, confidence logic and approval controlsW4Evaluation suite, clock checks and failure-mode testingW5Label-system integration, a pilot change and targeted correctionsW6One labelling cycle run under the regulatory signatory, then Agent Care handover
Reading the bandA bar covers only the weeks its own work is named in. The week 5 overlap is real, not padding.
At the end of W6The final checks clear on live labels and monitoring moves to Agent Care.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Biotechnology AI agent
Build the labelling change record before the next order lands.
Show us one core data sheet, the markets it feeds and who signs. You get the clock computed in calendar days, the reconciliation section by section, the pathway written down per change, and the implementation and artwork trail afterwards. We date what we build against: FDA reopened its section 505(o)(4) guidance as a draft on 19 September 2025, and the Commission Variations Guidelines apply from 15 January 2026 — the label text stays with your signatory.
