Pick one of ten best practices, start from a ready-made use case or your own question, and choose the depth. Each document names its sources and marks what it could not find.
Head of Regulatory reviews and signsNot signed yet. The software never signs.
From an overview to an evidence review, each built for one kind of reader and decision.
Recurring questions already set up on a best practice, from HTA Decision Scan to Asset Go/No-Go.
Market access, public affairs, regulatory, corporate development, safety, innovation and more.
Counted in the product on 29 October 2026.
Ask a general assistant to recommend a route and it names one, and a decider, and a deadline. Some of it came from your notes. Some of it came from nowhere. You cannot tell which.
"Go with the 510(k) route. The board will approve it next quarter."
"Decider: [GAP: not stated]. Three routes compared on cost, time, evidence and risk. No precedent found for one of them."
The gaps stay visible, so you fill them, not the model.
You bring the question. The best practice sets the shape a careful analyst would use for it. The depth sets how widely it searches. You read the result and decide.
In your words, with your notes and sources
One of ten, or a ready-made use case
Standard, Extended or Deep sweep
Sources attached, gaps marked, nothing signed
The software never signs
A best practice sets the shape a careful analyst would use: which sections the document has, in what order, and what each one must say. Pick the one that matches what your reader has to do with it.
Descriptions and section counts as set in the product on 29 October 2026.
Pick your function to see the recurring questions already set up for it. Each card names the best practice it is built on, and you can change the question.
14 ready-made use cases for Market Access.
Use cases as set up in the product on 29 October 2026. Each one is a starting point; you can change the question.
A comparison of Deep Analysis documents against other ways of writing them has not run. When it has, the result appears here with its method and its limits.
The decision memo leaves the decider open when your request does not name one.
The scan says what it searched, not that nothing exists.
The diagnosis stops at the likely cause.
The comparison shows where the difference matters and leaves the choice to you.
Quoted from the best-practice instructions. They tell the model how to write; they are not a measured result.
Create your workspace.
Or bring your own question to any best practice.
They are what the document could not source.
The document is yours to review and sign. The software never signs.