What the Reader Outside Regulatory Affairs Does Not See

Most people outside regulatory affairs do not realise how the hyperlinks in a regulatory submission actually get there. The clinical study report, the periodic safety update, the clinical evaluation — every one of them is dense with cross-references: see Table 14.3.1.2, as discussed in §11.4.1, per Figure 1. In the final eCTD package, each of those must resolve to a clickable, navigable link, or the submission is at risk.

Today those links are not in the document the writer produced. They are added later, by different software, by different people, often weeks after the draft is locked. That separation is the source of an enormous amount of friction in regulatory writing, and it is the thing we just closed.

What the Regulators Actually Require

The FDA's Providing Regulatory Submissions in Electronic Format guidance, together with the Technical Conformance Guide, requires that PDFs in a submission have a working table of contents and resolved hyperlinks for every internal cross-reference. The European eCTD validation criteria treat broken intra-document hyperlinks as a B21 critical error — the kind that gets a sequence kicked back. The EMA's two-click rule sets a navigation depth expectation, ICH M8 codifies it, and PMDA's Appendix 2 mirrors it. Hyperlinks are not a nice-to-have. They are a publishing gate.

How the Prevailing Workflow Handles It

The writer drafts in Word. The draft is full of plain-text references. The document then moves to a specialised eCTD publishing tool, where a publishing specialist — often a separate function, sometimes a separate vendor — runs a dynamic-linking pass. The pass tries to detect cross-references in the prose and wire them to bookmarks. It misses often. The writer's exact phrasing matters: see Table 1, Table 1 (above), and see Tables 1 and 2 all look different to a parser. Sections get reordered late, numbers drift, the parser fails silently, and specialists fix it by hand. This entire loop sits between the writer and the regulator, takes weeks, and is where Refuse-to-File risk lives.

What We Built

Asthra's drafting agent now treats hyperlinking as a first-class property of the draft, not a post-process.

Every table, figure, listing, and appendix is assigned a structural anchor at the moment its caption is written. Anchor identifiers are derived deterministically from the caption text and section number, so the same caption in the same section yields the same anchor every time. Every cross-reference is declared structurally alongside the prose: the agent does not just write "see Table 1," it pins that phrase to the anchor it points to. A numbering pass runs over the inventory and assigns display numbers from current document state. When sections move, the numbers re-derive. References stay correct because the link is to a stable identifier, not to a number that might shift.

The Word add-in then writes the real artefacts into the document — a Word bookmark at each anchor's position, a hyperlink wrapping each cross-reference — using the same deterministic names the backend resolved. By the time the draft leaves the writer, the hyperlinks are already there.

What Changes for Each Function

For the writer, the publishing-phase fixup loop shortens dramatically. Writers see real, navigable hyperlinks in their own draft. When they reorder a section or rename a table, the linkage stays correct.

For the publishing function, the eCTD publishing tool inherits a document where intra-document linking is already in place. The dynamic-linking pass becomes a verification step rather than a rebuild. Fewer last-mile defects, less manual reconciliation, lower B21 risk.

For the regulatory function as a whole, this is the first observable instance of Asthra's broader thesis: a regulatory document is a view over structured state, not a container of strings. Anchors and cross-references are state. Numbers are derived. Layout is rendered. The harder problems waiting downstream — persona reviewers, surgical edits, cross-document consistency — all become tractable once the document carries its structure with it.

This is the same principle that drives the skill registry that gives every regulatory edit an audit trail by construction and the literature search that now lives inside the chat alongside the draft. One idea, three layers of the stack.

What Is Next

This release covers intra-document linking, references within a single output document. Inter-document linking across CTD modules — a Module 2 narrative pointing at a Module 5 study report — is the obvious next layer. We will feed our anchor inventory upward so the rest of the publishing chain can consume it directly, rather than re-detecting cross-references from prose.

The submission is the regulator's view of the work. The work itself lives in state.