Cognatum

Life sciences

Common technical document: no module for an answer

The CTD gives every claim about a medicine a named place, down to whether a section may hold one file or several. An AI answer about the same medicine has no section, no sequence and no operation. It sits outside the structure.

Cognatum Team · Nov 10, 2026 · 5 min read

Two reviewers on opposite sides of the world can open the same drug dossier and find the same fact in the same place. That is not luck. Someone decided, years earlier, where every claim about that medicine would live.

Served to one approved entry
AI assistants & agents
Proposal tools
Internal search & chat
Customer portals
Compliance & audit

Cognatum governs the entry

source · version · approver · permissions

The format that makes this work is older than many of the people who use it. It gives a place to each thing a company asserts about a product. Not a folder. A place, named and numbered, down to the level of a single file.

Then a scientist on that same team asks the company assistant what the shelf life is. The reply comes back in four sentences. It lives nowhere.

Five modules, and then the real work

The dossier is split into five modules. The first one changes by country. The other four are the same everywhere, which is the point of agreeing on a format at all.

Most explanations stop there. The five modules are the part everyone draws as a triangle. They are also the least useful part, because a module only tells you which of five buckets a document belongs in.

The decisions that matter sit underneath, and they are published on their own, in a document about granularity.

What the granularity document rules on

That document goes section by section and settles two questions. May this content be one file, or several? And may content be filed at this level at all?

Some headings now carry a flat prohibition. Documents may not be submitted at that level, full stop. Others were opened up, so one file or several are both fine. For one optional section the guidance says all the information “could be in one document or multiple documents and within one or multiple” sections of that type.

A rule against joining things

There is also a rule against joining things. A sponsor may file a high level document at the top of a quality section, but may not pour all of that section’s documents into it. The granular versions still go where they go.

So the format holds a considered view on combining separate pieces of content into one piece. An answer is that combination, performed on demand, by software, with nobody asked.

The unit of control is the file

In the electronic version, an XML backbone carries metadata about each content file plus lifecycle instructions for the receiving system.

Every submission is one sequence. A dossier is a stack of sequences, and what you see when you open it is worked out from all of them together.

Each file in each sequence declares what it is doing. It is new, or it replaces something, or it adds to something, or it withdraws something. The old version drops out of the current view and stays in the history.

Three facts therefore travel with every document in a regulated dossier. Where it sits. Which sequence brought it. What it did to what was there before.

An answer carries none of the three

It has no section, because it was built across several of them. A number from the quality module, a sentence from the summary above it, a line from a study report below it.

It has no sequence, because it was never a submission.

It has no operation, because it replaced nothing. And nothing can replace it. No specification anywhere contains an instruction that withdraws a paragraph somebody has already read.

Why this is not a filing complaint

None of this is about tidiness. The granularity rules exist so that one change touches one file, and so that a reviewer looking for one fact goes to one place and finds one answer.

That service is built for the regulator. It is not built for the people who work on the product every day. They ask in plain words and get prose back.

Their question usually has a module number sitting behind it. The reply almost never mentions it.

One fact, four homes

A specification limit lives in the quality module. It is summarized in the module above. It turns up again on a slide from a conference. It is quoted in a standing procedure that nobody has touched in two years.

The granularity rules settle which of those is the record. Retrieval software has never read the granularity rules. It ranks by likeness, and a slide can read more like the question than the specification does.

When two of those sources disagree, the dossier has a rule for that. An assistant has a ranking.

What would have to be true instead

One useful definition calls provenance the chronology of the origin, development, ownership, location and changes to data, and adds the people and processes that touched it. A dossier has all of that. An answer, as normally served, has none of it.

Eight steps, and one gate

Cognatum works off its own framework, the Cognatum Knowledge Loop. Eight steps, four phases, one gate. AI runs seven of the eight. It finds the material, structures it, clears the duplicates, enriches it and routes it. It does not decide what is true.

The step it does not run is Approve. The item goes to a person, who can rework the wording and then signs it. After that the entry carries a named approver, a date and a source, and it can say where the knowledge stood on the day an answer was given.

Conflict, and notice

Where two documents contradict each other, it shows both and points at the disagreement rather than choosing a winner. Two divisions with two policies is a real conflict to link, not an error to retire.

When a source document changes, it tells you, and it tells you which answers now rest on an old version. It does not quietly rewrite anything, and it is not always current. The notice is the product.

Nothing has to move

None of this asks you to move the dossier. The submission archive stays where it is. So does the quality system. Cognatum flows to and from those places instead of becoming one more place to put things.

Your company’s knowledge isn’t missing. It’s unusable. Cognatum changes that.

The eight steps and the one human gate are set out at the Cognatum Knowledge Loop.

Common questions

Questions this raises.

What is the Common Technical Document?

It is an internationally agreed format for the dossier a company submits to register a medicine. It was developed by the European, American and Japanese authorities and is maintained by the International Council for Harmonisation. It has five modules. The first is regional, and the other four are common across regions.

What does the CTD granularity document do?

It states, section by section, whether content may be filed as one document or several, and whether documents may be filed at a given level at all. It also limits combining. A sponsor cannot merge all the documents of a quality section into a single higher level file.

Does an eCTD submission cover answers from an AI assistant?

No. The electronic format's unit of control is the file. Each file sits in a section, arrives in a numbered sequence, and declares whether it is new, replaces, appends or withdraws. An answer assembled on demand has no section, no sequence and no operation, so there is nothing for the format to track.

Can a knowledge platform make our AI answers compliant?

No software confers compliance, with the EU AI Act, with the NIST AI Risk Management Framework, or with any submission requirement. What software can do is supply the evidence a reviewer asks for: who approved an entry, when, from which source, and what it said on the day it was used.

How is this different from document control?

Document control governs the document, through version, approval, access and withdrawal of obsolete copies. The granularity rules are document control at a very fine grain. Neither one reaches the answer a person or a system derives from the document, and that is where a governed knowledge layer has to sit.

Knowledge governed. Intelligence everywhere.

See it on your own content, in your own environment.