Assembling an IND Sequence From a Client-Reviewed Plan for a Clinical-Stage Biotech
An IND Sequence Built From a Plan the Client Reviewed
A clinical-stage biotech outsourced an IND amendment sequence to DnXT publishing services. The sequence was assembled from a plan the client reviewed and annotated, every change note was resolved against the filed history, and the result was checked against the plan ahead of publishing.
Eleven change notes, several versions of the same document in force
The client’s regulatory lead reviewed the plan and returned eleven notes: rename this, replace that, add a new document here. Some were simple. Others referred to documents that existed in several versions across earlier sequences — an Investigator’s Brochure with five versions in force, two consent forms, two protocols.
Getting a replace wrong in an IND means the agency’s view of which document is current is wrong. Every note had to be resolved against what had actually been filed.
Plan, confirm, resolve, check, publish
Plan from the sequence
The documents being assembled were added to the client’s plan, each in its CTD section with a proposed lifecycle operation.
Client review
The client reviewed the plan and returned notes on every row that needed to change.
Resolve against history
Each note was matched against the filed history. Seven had exactly one answer; four referred to documents with several versions in force and were decided by a publisher.
Check before publishing
The plan was compared with the sequence, placed files were checked against their sources, and every document’s approval status was confirmed.
Judgement where it is needed, rules everywhere else
Ambiguity goes to a person
Where a note could mean more than one filed document, the publisher chose — the system did not guess.
Lifecycle comes from the filed record
Whether a document was new or replaced an earlier one was decided from what had been filed, not from file names.
Every file has a leaf, every leaf has a file
Before publishing, the sequence was checked for files without entries and entries without files, so nothing orphaned shipped.
What we did by hand became the product
The checks this sequence needed — plan-versus-sequence comparison, approval gating, validation-run comparison, bulk retitling — are now built into DnXT and run without AI.
A sequence built on the client’s own review, and a better product for every client
Every one of the client’s notes was either resolved from the filed record or decided by a publisher with the options in front of them, and the assembled sequence was checked against the plan before publishing.
The hand checks the publishing team ran on this sequence are now standard features in DnXT Publisher, available to every customer and to every sequence our publishing services team produces.
Outsource the sequence, keep the control.
Start with one application. We publish on software we built, from a plan you confirm.
