Walk into any regulatory operations team preparing a major submission and you will find it: the tracker. A sprawling spreadsheet — often several — listing every document in the dossier, who is writing it, which review round it is in, whether QC has seen it, and when publishing needs it. It is the true operational nerve center of the submission, and it lives in Excel.

Before building the document tracking capability in DnXT Planner, we studied 14 real NDA-program tracking spreadsheets in depth. That analysis shaped everything that followed — including a genuine respect for what those spreadsheets get right. This post is about what we learned: why Excel wins, where it breaks, and what a purpose-built replacement has to do to earn the switch.

What the Spreadsheet Gets Right

Tracking spreadsheets persist because they encode real operational wisdom:

  • The document is the unit of work. Every tracker we studied converged on the same insight: submissions are managed document-by-document, not section-by-section or milestone-by-milestone.
  • The lifecycle is richer than “in progress.” Real trackers distinguish authoring, multiple review rounds, QC, QA, and publishing readiness as separate stages with separate owners.
  • Everyone can see it. A grid that the whole team reads at standup beats a sophisticated system only the PM understands.

Any replacement that loses these properties fails, no matter how much technology it adds. The grid view had to stay a grid.

Where the Spreadsheet Breaks

The same analysis showed exactly where Excel-based tracking collapses under load:

  • Version chaos. The tracker is emailed, copied, and merged by hand. By week six there are three “current” versions and reconciliation is a standing meeting.
  • No structure awareness. The spreadsheet does not know what an eCTD section is. Documents get orphaned from the dossier structure they are destined for, and completeness questions (“what is still missing for Module 3?”) require manual cross-referencing.
  • Dates without dependencies. Columns hold dates, but nothing connects them. When the clinical study report slips two weeks, no downstream date moves — a human has to notice and re-plan by hand.
  • Issues live elsewhere. QC findings end up in email threads or a second spreadsheet, disconnected from the documents they concern.
  • History evaporates. Overwritten cells have no memory. Who changed the QC status, when, and why is unanswerable — a real problem in an environment where process evidence matters.

The Replacement: A Document-Level Operations Grid

DnXT Planner’s tracking grid keeps the spreadsheet’s form and fixes its physics. Each submission gets a document-level grid tracking 13 lifecycle fields per document — authoring status and owner, review rounds with named reviewers, QC status, QA status, publishing readiness, and the dates that govern each stage. It reads like the spreadsheet your team already uses, because that layout is the thing the 14 trackers proved works.

Underneath, it behaves differently:

  • One live grid. Everyone sees the same state; there is nothing to email and no versions to reconcile. Every change is attributed and timestamped.
  • Structure-aware rows. Documents link to their planned eCTD sections, so completeness rolls up automatically — the plan knows Module 3 is missing four documents without anyone cross-referencing.
  • A real timeline behind the dates. Tasks form a hierarchical Gantt with predecessor relationships and percent-complete. When an upstream date moves, dependent dates visibly move with it — re-planning becomes review-and-confirm instead of archaeology.
  • One-click standard phases. For any document, the platform generates the standard authoring lifecycle — the eight phases a regulatory document conventionally moves through, from draft through reviews to publish-ready — as linked tasks. Coordinators stop hand-typing the same task ladder hundreds of times per submission.
  • QC findings attached to documents. The issue log lives in the same system, with dual-graded severity (how bad, how urgent) and routing — including to external vendors — and closure that can be gated behind an audited e-signature rather than a cell edit.
  • A milestone register connecting document-level reality to the program-level dates leadership actually reports on.

The Migration Question, Honestly

Nobody switches tracking systems mid-submission for fun, so two honest notes. First, the switching cost is real: your team has muscle memory in its spreadsheet, and the right moment to change is at program start, not week nine of dossier assembly. Second, a tracking system is only as good as the discipline of the people updating it — DnXT reduces the update burden (statuses roll up, phases generate themselves, dependencies propagate) but does not eliminate it. What it eliminates is the reconciliation burden: the hours spent figuring out which copy is true and whether the dates still hold together.

The payoff compounds at exactly the moments spreadsheets fail hardest — the six weeks before submission, when change velocity peaks and the cost of a stale tracker is measured in missed documents. And because the tracker lives in the same platform as eCTD publishing, “publishing-ready” in the grid is adjacent to publishing itself, not a status in one tool describing work in another. It is part of the same operational spine as DnXT’s workflow automation and the broader platform.

Frequently Asked Questions

Can we import our existing tracker?

The grid’s field model was derived from real NDA trackers, so conventional tracker columns map naturally onto its 13 lifecycle fields. Bringing an in-flight program across is a structured mapping exercise, not a retyping project.

Does it handle multiple submissions per program?

Yes — grids are per-submission, and submissions roll up to programs and portfolio views, so document-level detail and leadership-level status come from the same data.

What about the people who love Excel?

The grid deliberately preserves the spreadsheet’s reading experience — dense rows, scannable columns. What changes is what is underneath: one live version, attributed history, structure awareness, and dates that move together.

Retire the Reconciliation Meeting

If your team spends part of every week reconciling tracker copies, that time is recoverable. Book a demo and bring your current tracker — we will map it onto the grid together and show you what your submission looks like with dependencies that actually connect.