Biotechnology AI agent · Post-approval change
Post-Approval Change & Commitment AI Agent
Carry the promises made to a regulator on one register — milestone, status word, market, the evidence behind a change — then hold it for the named regulatory lead, who decides what is filed.
- Typical delivery
- 4–6 weeks
- Deployment
- Your stack
- Lead files
- Pre-filing
- After launch
- Agent Care
What this agent does
Builds the register, not the filing decision
In
- 01
A commitment is agreed, and it enters the register with its milestone, its market and the letter it came from.
- 02
An anniversary falls, and the status pack for that application is built against the window at 21 CFR 314.81(b)(2).
Reason
- 03
An alternate date is agreed with a review division, and the register carries it beside the approval anniversary.
- 04
An accelerated approval enters, and its progress cycle under 21 U.S.C. 356b(a) is counted apart from the annual one.
- 05
A status word is put up from the set the regulation defines, with the schedule it was read against attached.
Decide
- 06
A change is raised, and the supporting data, the tiers in play and the written reason are gathered market by market.
- 07
A variation is drafted, and the register stores which Guidelines governed it: the 2013 set, or C/2025/5045.
Out
- 08
A conditional EU authorisation renews, and the date the application is due before expiry is counted, not the expiry.
- 09
A write action runs only inside the approval boundaries agreed during implementation.
Product statement
The agent assembles the register; a named regulatory affairs lead classifies, decides what is filed and signs — and the exposure that follows is the company's, not that person's.
Example workflow
One commitment, letter to filing
- 1Commitment receivedApproval letter, variation record, inspection response or register export
- 2Register assembledMilestones, markets, status words and open evidence, each with its named source
- 3Change pack draftedMilestone view, classification evidence, open items and confidence
- 4Controls appliedMilestone arithmetic, completeness tests per configured market, guideline-date checks and confidence threshold
No human action required
Stages 1 to 4 run unaided, and nothing is filed at any of them — the agent is assembling evidence, and the regulatory lead's lane opens at the confidence gate.
Goes to the regulatory lead.
Adds a CMC or labelling read first.
Regulatory lead
The pack is held with its source records, its open items and the confidence.
Approve · Amend · Send to regulatory review
Approved — released to file
- 6Commitment register updatedOnly where write access and approval policy allow it
- 7Outcome evaluatedAmendment distance, open-item outcomes, agency correspondence and post-filing corrections
Amendments
Each amendment the regulatory lead makes is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required
8 items
- Classifying a change into a reporting category.
- Determining reportability in any market.
- Filing a supplement, a variation or a status report.
- Choosing the status word an annual report states.
Automation boundary
Agent acts unaided
- ✓Assemble the register from approval letters, variations and inspection responses.
- ✓Compute each milestone and window from the dates already on file.
- ✓Gather the supporting data behind a proposed change, market by market.
- ✓Name what is missing or divergent, and hold the pack for the lead.
Writes run only inside the boundaries agreed at implementation, and never ahead of a filing.
- Assessing the effects of a change before distribution.
- Agreeing a new milestone date with a review division.
- Proposing established conditions, where a region takes them.
- Changes to milestone, market or approval rules.
Example output
One commitment, annotated
Everything the agent assembles is attached to the record it was drawn from.
Commitment register output · single application
Illustrative example- Application
- BLA, accelerated approval
- Commitment
- Confirmatory-trial milestone stated in the approval letter
- Time to milestone
- 214 days
- Source of record
- Approval letter on file
- Confidence
- 86%
- Owner of record
- Regulatory lead, named on the register
As received
Taken from the approval letter and the register on file — nothing on this side is written by the agent.
Source facts used
- Approval letter, dated
- Prior status report
- Study milestone plan
Why this is open
The status word is the lead's to choose — 21 CFR 314.81(b)(2)(vii).
What the score decides
Below the configured threshold the item picks up a CMC or labelling read before the lead sees it.
Action
ApproveAmendSend to regulatory reviewValue
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value lands
Value 01 – 04
Every application
From the approval letter
Read the promise against its milestone
Established conditions are carried per market: the EU note of 4 March 2020 and MAPP 5018.3 of 29 November 2024 do not agree.
Commitments outlive the team
A change filed in the wrong category is product distributed without the approval the regulation required, and the unwind reaches the batches released, the markets moved on the same reasoning, and the next inspection.
The sequence, and the promise
The submission helper asks whether a filing is structurally right for its region; this register asks whether every promise made to a regulator is tracked, evidenced and answerable.
Build an evidence trail
The commitment, the milestone it carries and the lead who filed stay on the register.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Regulatory information
- Veeva Vault RIM
- ArisGlobal
- Ennov RIM
Agency sources
- FDA approval letters
- EMA
- national registers
Quality systems
- Change control
- CAPA
- Veeva QualityDocs
Agent
Commitment register
- Reads the record
- Assembles the pack
- Holds for the lead
Publishing and archive
- eCTD publishing
- archive
- Document management
Observability & evaluation
- OpenTelemetry
- Langfuse
- Supported monitoring/evaluation sources
Integration availability depends on the client's existing systems and API access.
Agent controls
Six layers between the model and the register
The six tighten as you go inward. Whatever gets through them all appears in the map below.
L6 · Outermost — last line of defence
Inward → L1 · closest to the model
- L1 – L2
- Test whether the pack may stand
- L3
- Puts the release in the lead's hands
- L4 – L5
- Keep the commitment and the milestone behind it
- L6
- Holds the register at unfiled when signals degrade
How Nestack evaluates it
Evaluate the register workflow — not only the pack that gets filed.
Coverage runs the whole depth of the workflow, and every layer is cut by slice.
Surface — the status the agency is told
- E1Final-output evaluationDid every milestone trace to the letter or record behind it?
- E2Step-level evaluationDid the agent use the right dates, markets and guideline configuration?
- E3Tool evaluationDid it read and write the correct application and the correct field?
- E4Confidence calibrationDo low-confidence items actually attract more lead amendments?
- E5Slice evaluationHow does performance change across specific commitment types?
- E6Business outcomeHow many items were amended, or corrected after the filing went in?
Floor — the outcome the holder answers for
Failure modes
Where each failure originates in the agent
Seven failure modes, each set where the register first goes wrong.
Agent lifecycle
Direction of processing →
01 · Retrieval
1 mode
- EW-03
Superseded register row
The milestone read predates the date it moved to.
Stage gathers
Letters, variations, milestones and market rules
02 · Reasoning
2 modes
- EW-04
Milestone read as met
A final report submitted is taken as fulfilled.
- EW-06
One category, every market
A US tier is copied across the other rows.
Stage proposes
Milestone view, change evidence and confidence
03 · Tool / write
2 modes
- EW-02
Guideline keyed to filing
The date stored is submission, not implementation.
- EW-05
Protocol read as standing
Changes run under it with nothing filed since.
Stage writes
Only where write access and approval policy allow it
04 · Output
1 mode
- EW-01
Two clocks, one register
An accelerated approval sits on the annual cycle.
Stage returns
The pack the regulatory lead classifies and files
05 · Change / Version
1 mode
- EW-07
Silent milestone drift
A model or rule change alters which date is counted.
Stage tracks
Model, prompt, milestone rules and market config
- Sev-1 · a wrong tier reaches a signature
- Sev-2 · a wrong status reaches the agency
- Sev-3 · source degrades, item goes to review
Affected slices
A portfolio total can hide one market
A portfolio-level milestone-currency figure can read as healthy while a few markets and change types carry most of the returned items. Nestack reports the return rate by slice, not only in total.
Slice performance — reported separately, not only in aggregate
Illustrative example| Slice | Failure rate | Lift | Lift vs. threshold | Status |
|---|---|---|---|---|
| Partner and licensed markets | 7.2% | 3.6× | Review | |
| Conditional EU authorisations | 5.3% | 2.6× | Review | |
| Cross-region CMC changes | 3.6% | 1.8× | Watch | |
| Single-market annual-report changes | 2.3% | 1.1× | Normal |
Bar: return-rate lift vs. single-market baseline · scale 0–4.0× · tick marks the 2.0× review threshold
2 of 4 slices over threshold
Evidence-linked improvement
A cycle is not done until a test exists
A cycle closes when the missed milestone is a regression case. That suite is what the next status report built is measured against.
Improvement cycle · five stages
Switchback — the path turns at Improve and returns at Learn
- 01
Detect
Return rate rises for one market.
- 02
Diagnose
The milestone agreed by people who have all since left is read back until the cause narrows to one.
- 03
Improve
The change goes out with a number, and the commitments behind it travel with it.
- 04
Verify
Nothing files while one touched commitment case is still red.
- 05
Learn
It is kept for good, and the milestone rules are amended in the same commit.
Learn → Detect
The return edge. The next detection is measured against a longer suite than this one.
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, register workflow, evaluation, integration, then production validation and handover.
Workstream
Week 1Week 2Week 3Week 4Week 5Week 6
- 01Commitment workflow discovery and boundary mapping.Week 1
- 02Regulatory and quality-source assessment.Week 1, Week 2
- 03Milestone, market and classification-rule mapping.Week 1, Week 2
- 04Register ingestion and reconciliation.Week 2
- 05Pack assembly and source binding.Week 2, Week 3
- 06Confidence scoring and exception routing.Week 3
- 07Regulatory-lead review workflow.Week 3, Week 4
- 08Regulatory and quality-system integration.Week 5
- 09Milestone and classification cases.Week 4, Week 5
- 10Guardrails and filing controls.Week 4
- 11Commitment-trail instrumentation.Week 5, Week 6
- 12Deployment, documentation and Agent Care handover.Week 6
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallel
Final 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 tier | PilotOne product, one market | ProductionProduction regulatory systems | AdvancedMultiple markets / products |
|---|---|---|---|
| Introduced at Pilot | |||
| Commitment register and milestones | ✓ | ✓ | ✓ |
| Regulatory-lead approval | ✓ | ✓ | ✓ |
| Milestone-currency baseline | ✓ | ✓ | ✓ |
| Introduced at Production | |||
| Reporting by market | — | ✓ | ✓ |
| Exception workflow in your systems | — | ✓ | ✓ |
| Approved write-back | — | ✓ | ✓ |
| Regulatory-system integration | — | ✓ | ✓ |
| Introduced at Advanced | |||
| Multi-region guideline rules | — | — | ✓ |
| Multi-stage regulatory approvals | — | — | ✓ |
| High application count | — | — | ✓ |
| Multi-market variation controls | — | — | ✓ |
| Build price | From $5,000 | From $8,000 | Custom quote |
- Final build price
- Confirmed after discovery based on integrations, workflow complexity, application count, approval controls and deployment requirements.
- Separate from build
- Build 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 bring
We build with it
01Your approval letters and commitment list
→Milestone, market and classification-rule mapping
Week 102Representative prior status reports
→Register ingestion, reconciliation and the assembly baseline
Week 203Your variation history and change-control records
→Commitment-register mapping and automation-boundary definition
Week 104Access to relevant APIs, feeds or exports
→Regulatory and quality-system assessment, then integration setup
Week 205Registers you would not want reconciled
→Milestone cases and failure-mode testing
Week 406What no status report may leave open
→Confidence scoring, item routing, guardrails and filing controls
Week 307Named regulatory leads to review the pack
→Regulatory-lead review workflow, then pilot and production validation
Weeks 5–6
Nothing else is required
Deployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Bands are measured against weeks actually worked, and that measurement puts two into week five.
Phase
W1
W2
W3
W4
W5
W6
- DiscoveryW1
- BuildW2 – W3
- EvaluateW4 – W5
- Pilot & LaunchW5 – W6
Week focus
W1Commitment workflow discovery, rule mapping and the automation boundary
W2Register integration and the reconciliation baseline
W3Assembly workflow, milestone logic and review controls
W4Evaluation suite, milestone checks and failure-mode testing
W5Quality-system integration, a pilot product and targeted corrections
W6One anniversary cycle run under the regulatory lead, then Agent Care handover
- Reading the band
- A bar covers only the weeks its own work is named in. The week 5 overlap is real, not padding.
- At the end of W6
- When the status report validates, Agent Care takes the agent on.
- Duration
- Six-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Biotechnology AI agent
Build the commitment register before the next anniversary falls.
Show us your approval letters, your variation history and the lead who signs. Next step is a working session on one product: we put every commitment on one register with its milestone, its market and the evidence behind it, then show you what the pack hands your lead at the anniversary — with the classification left empty, because that determination is theirs and the exposure behind it is the company's.
- Typical delivery
- 4–6 weeks
- Deployment
- Your regulatory systems
- Lead files
- Pre-filing
- After launch
- Agent Care available
Nestack Agents · Post-approval change and commitments
AGT-BT-19 · Agent Care available after launch