Good Software Makes You More Capable: What That Means for Regulatory Teams

A tool earns its place only if it makes the person using it more capable — able to do something that was out of reach before, or do it markedly better. It is a demanding test, and most features fail it. Here is where that test lands across a regulatory team’s whole job — planning, documents, review, publishing, readiness and quality — and the capabilities we built because they pass.

I came across a line recently that has stayed with me: good software makes a person more capable. Read it the other way and it is sharper still — without the tool, there are things you cannot do at all, and things you do in a slower, more fragile way than you should.

That is a useful test, because it is demanding. Most software does not make you more capable. It saves a click, or does a little faster what you were already doing. That is convenience, and convenience is fine, but it is not the same thing. A capability lets you do the whole job yourself, or opens work that was closed to you before, or changes what your team can realistically take on.

We hold DnXT to that test deliberately. There is a long list of things the platform does; this is not that list. What follows is organised the way a regulatory team actually works — from planning a filing through to running quality around it — and in each part, the one capability we think genuinely makes someone more capable, framed by what it lets you do that you could not, or could not do well, before.

Plan a filing you can actually see

Long before a document is written, a filing is a plan: who owns what, when it is due, and what is holding it back. For years that plan lived in a spreadsheet that went stale the moment it was shared, and readiness was whatever the last status email said.

DnXT Planner is a content plan that understands eCTD structure — global core plus market variants — with owners, due dates and a document-level grid that shows exactly which item is holding a filing back, across every application in the portfolio rather than one at a time. The capability is that you can run the filing from live readiness instead of chasing people for status.

Manage regulated content as regulated content

A regulated document is not an ordinary file. It has a version that matters, a lifecycle, a signer and an audit trail — and a general-purpose file share gives you folders and hope.

DnXT EDMS gives regulated content what it needs: versioning and check-in/check-out, controlled lifecycles from Draft to Effective, Part 11 electronic signatures, AI classification into the right CTD section, and proof of who was trained on the document they had to read. Configurable document QC — with auto-fix and approval gates — runs before anything is assembled. The capability is that an inspection stops being a scramble: you can hand an inspector a complete, controlled record on demand, and every document is where it should be.

Publish it yourself — and know it will be accepted

Assembling a valid eCTD sequence has always needed a specialist who knows the backbone, the lifecycle operations and each region’s Module 1, working in a tool most of the team never touches. And the worst place to learn that a submission is wrong is the agency gateway.

DnXT lets a regulatory associate build, publish and validate a sequence from a single dossier across 16 eCTD regions, with the region-specific rules applied for you — then check it against more than 2,000 validation criteria before it leaves your hands. When the next market comes, clone the approved dossier and build only the variant instead of rebuilding it. Three things you could not do alone before, now in one pair of hands: file a region you have never filed, prove it clean before you send it, and reuse your own work.

You find out while you can still fix it quietly.

Review the way the agency reads

Agencies read a dossier a particular way — cumulatively, following each document’s lifecycle across sequences — and they expect the dynamic FDA forms to render. Desktop viewers and downloaded copies make that hard, and often show those forms as empty boxes.

DnXT Reviewer opens any sequence in the browser — no install, no local copy — with cumulative and current lifecycle views and native rendering of the dynamic FDA forms such as the 1571, 356h and 2253. The capability is that anyone who needs to read the dossier the way the agency will can do it, from wherever they are.

Find anything you have ever filed, in seconds

A regulatory team is asked, constantly, to remember: where did we commit to that stability protocol, what did we tell the agency about that impurity, which sequence carried the last label change. The honest answer has usually been to open old submissions one at a time, or to trust a spreadsheet someone kept.

Unified search looks across the whole dossier library — full text and metadata together — not one submission at a time. The question that used to mean an afternoon of opening sequences becomes a search box. Institutional memory stops living in people’s heads and becomes something you can query.

Stay ahead of the agency and the label

Two of the hardest things to do under pressure are answering a health authority well and keeping every local label true to the company core data sheet. Both reward preparation that is almost impossible to assemble in the moment.

Regulatory Intelligence builds question readiness from more than 1,000 real health-authority questions, tracks correspondence and commitments, and keeps a clinical development history in which each agency request sits beside the response that answered it. Labeling tracks every local label against the core data sheet, controls and justifies deviations, and compares submitted against approved section by section with evidence-backed status. The capability is preparation that used to depend on one person’s memory, held instead by the system.

Run quality where the filing lives

Quality events — change control, CAPA, deviations, audits, risk — have almost always lived in a different system from the submissions they affect, so the link between a change and the filing it changes was a person remembering to make it.

DnXT runs those processes on the same platform, with every market’s filing tied to the regulatory record and carried on the same audit trail. The capability is simple and overdue: a change control and the sequence it changes are finally in the same place.

Let AI take the first pass, and keep the judgment

There is a wrong way to put AI into regulatory work: let it decide, and hope. We built it the other way. AI takes the mechanical first pass — a review pass that only comments and never changes the record, cross-reference detection, document classification — and the judgment, the sign-off and the responsibility stay with the person.

Every AI call runs through one governed path, with the model, the prompt and the result recorded. The capability is a careful one: you get the lift of a tireless first reader without giving up the accountability an inspector will expect you to hold.

What we decided not to count

The discipline in this piece is as much in what it leaves out. A button that saves a step is welcome, but it is not why you would choose a platform. We did not count the conveniences, because convenience is not capability — and a regulatory team evaluating a tool deserves to know which is which.

The test we kept coming back to is simple: after this, can the team do something it genuinely could not do before, or do it well enough that it stops being a risk? Everything above clears that bar. That is the only list worth publishing.

Why it adds up

Put together, these are not a feature list. They are a shift in what one regulatory team can carry across its whole job: plan a filing from live readiness, manage content that is inspection-ready by default, publish and prove a sequence yourself in a region you have never filed, review it the way the agency will, answer any question about anything you have ever filed, keep labels true, run quality in the same place as the submission — and lean on AI without handing it the pen. You can even hand a client a secure link to their own plan and turn their feedback into the next change. That is what we mean when we say software should make you more capable, and it is the only standard we think is worth building to.