Client Collaboration — Submission Plans Your Client Confirms, Submissions You Deliver Securely
Your Client Confirms the Plan. Not an Email Thread.
Build the submission plan from the sequence you are assembling, send it to your client by secure link, see their progress, turn their feedback into the change — and deliver the published submission the same way.
The plan lives in your system. The answers live in their inbox.
Every outsourced sequence depends on the sponsor confirming what goes into it: which documents, which sections, which replace what. Usually that confirmation happens in an email thread with an attached spreadsheet, and the publisher re-keys the answers.
Nobody can say whether the client has opened it, how far they have got, or which of their comments has been acted on. And when the sequence is finally published, it leaves by file transfer with no record of who downloaded what.
DnXT gives the client a secure view of the plan itself, and turns what they say back into the plan.
Built for the people who own the outcome
Publishing service providers
Run each client sequence from one plan the client signs off, instead of chasing confirmations by email.
CROs and consultancies
Show sponsors exactly what is going into their submission, and keep an audited record of every confirmation and change.
Sponsor regulatory teams
Review your own plan in a clear view, confirm or flag each document with a note, and check the application details on file are right.
One plan, from assembly to delivery
Build from the sequence
One action adds the sequence’s documents to the plan, each in its section, with the operation proposed from the filed lifecycle.
Send a secure link
The client signs in with a one-time code. You see when it was sent, whether it was opened, and how far they have got.
Client confirms or flags
Each row is confirmed, or flagged with a note. The client also confirms the application details you have on file.
Apply and deliver
Feedback becomes the change, the plan is checked against the sequence, and the published submission is delivered through the same portal.
Built for the hand-off between publisher and sponsor
Plan built from the sequence
Documents you have already placed become plan rows automatically, linked to their source documents, so the plan and the sequence start in agreement.
Status you can see
Who has the plan, when it was sent, whether it was opened, when the client was last active, and how many rows are confirmed — beside the plan, at a glance.
Told when they finish
When every row is confirmed or flagged, you get one email and an in-app notice listing what was confirmed, what was flagged and the client’s notes.
What we have on file
The client sees the application number and type, applicant, products, substances, indications and contacts you hold, and marks each correct or wrong.
Feedback becomes the change
A note such as “replace the earlier protocol” is matched against the filed history. When the history gives exactly one answer it is applied; when it does not, the options go to your team.
Secure delivery
The published sequence is delivered as a download through the portal — the same package Publisher produces, with every download recorded.
Rules that keep the record trustworthy
Nothing is written from outside
A client’s correction to the details on file becomes a proposed answer for your team. Only your team changes the dossier.
Ambiguity goes to a person
When a comment could mean more than one thing — several versions of a document in force, for example — the system offers the candidates rather than choosing.
Plan and sequence are checked against each other
Before publishing, every plan row is compared with the sequence: placed, in the wrong section, with the wrong operation, or not placed yet — plus anything in the sequence the plan does not account for.
Every change is audited
Sending, confirmation, feedback applied and documents linked are all recorded in the audit trail.
Frequently asked
Does the client need a DnXT account?
No. The client opens a secure link and signs in with a one-time code sent to their email address.
How is the plan applied to the sequence?
From the plan, the publisher sees what each outstanding row will do — place as new, or replace a specific in-force document — and applies them after a preview. Anything that needs a judgement is left for a person, with the reason.
How is the published submission delivered?
From a published sequence, Publisher sends the client a portal link. The download is the same package as Publisher’s own export, nothing is copied, and each download is recorded.
Can we use this for our own publishing services clients?
Yes. DnXT’s own publishing services run on exactly this workflow.
Stop re-keying your client’s answers.
Bring a recent outsourced sequence and we will show you the same hand-off as one confirmed plan.
