Requests and plan approval

A report goes from your request to a plan, then approval, then writing. Nothing is written until you approve the plan.

Writing a request

Say which field you want to look into: a disease, a drug target, a technology, or a modality (the kind of drug, such as small molecules, antibodies or nucleic acids). Some of the examples on the home screen, translated:

  • Obesity pipeline and the companies in it (with patient numbers in Japan and the standard of care)
  • Competition and development stages by target for ADCs (antibody–drug conjugates)
  • Design of Phase 1/2 clinical trials in pancreatic ductal adenocarcinoma (PDAC)
  • Trends in alpha-emitting radiopharmaceuticals

A request that includes something our data does not cover is not turned away as a whole. The plan is built from the parts we can answer, and a single line in the plan and in the report says what was left unanswered. Data sources and coverage lists what we hold and what we do not.

If your question starts from your own product, a slightly vaguer description is enough to work with. Do not enter the core of anything confidential; see How your input is handled.

Reading the plan

From top to bottom, the plan screen shows the following. All of it is there so you can check what will be counted before the report is written.

  • Population: what this report will count, with numbers for pipeline assets (approved drugs included), trials, companies and partnerships. When the counting needs care, a warning box appears, sometimes with buttons to drop a condition and rebuild the plan, or to reword the request.
  • Data available for this request: for each part of the request, whether our data can answer it, and what to look at instead when it cannot.
  • Views: the same population shown as a competitor table, as scope and breakdown, or as events. In the competitor table you can untick companies to leave them out of the report, and the population is recounted.
  • Not answered: the parts of the request that our data does not cover, and what is used in their place.
  • Purpose: the aim written from your request. It is read-only; if you want a different analysis, ask for it in the chat once the report exists.
  • Sections: the candidate sections for the report.

Choosing sections

Some sections are ticked to start with (the screen tells you how many it suggests starting with). Tick and untick to choose what goes in, or select all candidates at once.

  • The heading for the data at the center of your request is marked as such.
  • Unticked candidates can be added straight from under their heading. When there are many, more candidates are folded away and can be opened.
  • More sections mean more time and more cost to create the report.
  • Section titles are read-only.

Approving or declining

  • Approve to start writing the report. If you changed the ticks, the button says you are approving an edited plan.
  • To not go ahead, decline. A second confirmation deletes the project, and a deleted project cannot be restored.
  • When other plans are waiting for approval, you can go straight on to the next one.