Every regulated company has a system of record for documents, and most have one for submissions. Almost nobody has one for the conversation — the meeting requests, information requests, clarifying emails, commitments, and formal letters flowing between the company and health authorities. That correspondence is legally consequential and deadline-driven, and at most companies it lives in Outlook folders, personal drives, and the memory of whoever managed the last interaction. When that person changes roles, the institutional record of what was promised to an agency effectively resets. Health authority correspondence tracking is the unglamorous capability that fixes this, and it deserves far more attention in regulatory operations than it gets.

How Correspondence Gets Lost

The failure pattern is consistent across companies of every size:

  • Inbound arrives personally. Agency emails land in individual inboxes. Forwarding conventions (‘always cc the regulatory mailbox’) decay within months.
  • Commitments hide in prose. A response letter says ‘the applicant will provide updated stability data in the next annual report.’ That sentence is now a binding commitment — tracked, if at all, as a row someone remembered to add to a spreadsheet.
  • Threads fragment across channels. A question raised in a teleconference is answered partly in the meeting minutes, partly in a follow-up email, partly in the next sequence. Reconstructing the full exchange for an inspection takes days.
  • Status is a feeling, not a fact. Nobody can say with confidence how many open commitments exist across the portfolio, which are due this quarter, and which have actually been discharged.

Auditors and inspectors, incidentally, know all of this. ‘Show me all open commitments to the agency for this product’ is a devastating first request precisely because so few companies can answer it from a system.

What a Correspondence System of Record Requires

A structured interaction log

Every interaction — letter, email, meeting, teleconference, submission-embedded response — recorded against the application and agency it belongs to, with direction, type, date, participants, and linked documents. The unit of record is the interaction, not the attachment.

Commitments as first-class records

Commitments extracted from correspondence and tracked with owners and due dates. The critical design rule: a commitment can only be discharged by a responding correspondence. No ‘mark as done’ button. If you told the agency you would send data, the commitment closes when the interaction that sent the data is logged — which keeps the register honest and inspection-proof by construction.

Inbound capture with human confirmation

The system should meet the mail where it arrives: an ingestion pipeline that reads inbound agency email, proposes the application number, agency, and interaction type automatically, and parks everything in a triage queue as proposed until a human confirms it. Automation does the filing; a person stays accountable for the record. That split matters in a GxP context — you want the labor savings of auto-attribution without machine-created official records.

Connection to planning and intelligence

Correspondence changes plans. An information request spawns response work with a deadline; a meeting outcome changes a submission strategy. If the correspondence log lives in the same platform as submission planning and regulatory intelligence, those consequences become linked work items instead of tribal knowledge.

How DnXT Approaches It

DnXT Planner includes health authority correspondence and commitment tracking built on exactly these rules. The interaction log records every exchange against its application; commitments are structured records that can only be closed by a responding correspondence; and an inbound email pipeline auto-attributes application number, agency, and interaction type, holding everything as proposed until a person confirms it in the triage queue. Because it shares a platform with DnXT’s planning, intelligence, and eCTD publishing capabilities, an information request can flow from inbox to tracked response work to submitted sequence without leaving the system — and the full thread is reconstructable in seconds, not days.

Frequently Asked Questions

What counts as health authority correspondence?

Any documented exchange with a regulator about your applications: formal letters and information requests, meeting requests and minutes, emails with review divisions, teleconference records, and the commitments embedded in all of them. If an inspector could ask about it, it belongs in the log.

Isn’t this just document management?

No. An EDMS stores the letter as a file. A correspondence system records the interaction — who, when, about which application, requiring what by when — and maintains the commitment register that hangs off those interactions. Most companies have the former and lack the latter.

Can RIM systems do this?

Enterprise RIM suites typically include a correspondence object, and for companies fully invested in one it can work. In practice the module often goes unconfigured or unused because it requires manual data entry for every email. Capture friction is the real product problem — which is why inbound ingestion with human confirmation matters more than the data model.

What’s the fastest way to start?

Backfill is the enemy of adoption. Start the log from today with active applications only, add commitments as correspondence flows, and backfill historical records opportunistically when an interaction references them.

If ‘show me all open agency commitments’ would take your team more than five minutes to answer, talk to us — we’ll show you the correspondence workspace with a live triage queue and commitment register.