Workflow guide · Catalyst discovery and verification

Separate hard dates from company guidance

Distinguish PDUFA dates from broad clinical timing windows.

Event-Driven Biotech InvestorsUpdated 2026-07-26Practical workflow

The situation

When this workflow becomes useful

An event-driven investor sees fixed regulatory dates mixed with broad clinical timing windows in the same catalyst calendar.

Best fit

Investors and traders whose research process is organized around clinical readouts, FDA decisions, conferences, and other discrete biotech events.

The challenge

Why the obvious approach breaks down

Distinguish PDUFA dates from broad clinical timing windows. The challenge is to preserve the source, define what changed, and connect the update to a decision instead of collecting disconnected information.

How to think about the task

The reasoning behind the workflow

An event-driven investor sees fixed regulatory dates mixed with broad clinical timing windows in the same catalyst calendar. For event-driven investors, the useful response is not simply to collect more links. The task is to decide what the new information changes, which source supports it, who needs to respond, and when the question should be reviewed again.

Distinguish PDUFA dates from broad clinical timing windows. The challenge is to preserve the source, define what changed, and connect the update to a decision instead of collecting disconnected information. A repeatable process keeps the work proportional to the decision and creates a record that another investor, analyst, editor, or team member can understand later.

Start with the decision this work must support

“Separate hard dates from company guidance” becomes manageable when the user names the decision before opening more sources. The decision might be whether to escalate an event, update a thesis, change a calendar, commission deeper research, publish a story, or continue monitoring. A defined decision also makes it easier to exclude information that is interesting but not currently useful.

Build a source-linked change record

The core monitoring set for this workflow includes regulatory deadline versus company estimate, exact source wording, timing dependency, confidence level, revision history. Each material update should retain its source and previous known state. That makes timing changes, accumulating evidence, and repeated execution patterns visible instead of leaving the user with an isolated snapshot.

Turn monitoring into an owned output

A catalyst calendar that visibly distinguishes fixed, guided, inferred, conditional, and estimated timing. The output should state what changed, what remains uncertain, who owns any follow-up, and which future event will resolve the question. The investor avoids building precise trades around dates the company never formally committed to.

Illustrative example

Illustrative workflow: separate hard dates from company guidance

Begin with the specific company, program, portfolio exposure, audience, or competitive set in scope. Review the highest-confidence source first, compare the disclosure with the previous record, and then use secondary context only where it helps explain the change.

Complete the workflow by producing the defined deliverable rather than ending with a collection of tabs. Assign any unresolved question to an owner and set the next review around the most relevant clinical, regulatory, financial, strategic, or editorial event.

Questions to answer before making a decision

  • What has changed in regulatory deadline versus company estimate, and why does it matter?
  • What has changed in exact source wording, and why does it matter?
  • What has changed in timing dependency, and why does it matter?
  • What has changed in confidence level, and why does it matter?
  • What has changed in revision history, and why does it matter?

The workflow

A repeatable way to do the work

  1. 01

    Define the specific decision or research question behind “separate hard dates from company guidance.”

  2. 02

    Set the monitored scope around regulatory deadline versus company estimate and exact source wording.

  3. 03

    Collect source-linked updates for timing dependency and record what changed from the prior state.

  4. 04

    Review confidence level together with revision history before drawing a conclusion.

  5. 05

    Produce the required output, assign follow-up ownership, and set the next review point.

Monitoring checklist

Signals to keep visible

Regulatory deadline versus company estimate
Exact source wording
Timing dependency
Confidence level
Revision history

Common mistakes

  • Starting the monitoring process without a defined decision question
  • Recording the latest state without preserving its source or previous state
  • Ending with collected information but no owner, conclusion, or next review

Output and outcome

What good looks like

Deliverable

A catalyst calendar that visibly distinguishes fixed, guided, inferred, conditional, and estimated timing.

Practical outcome

The investor avoids building precise trades around dates the company never formally committed to.

Where BioPharmSignal fits

Reduce the collection work around the decision.

Use LiveFeed and company pages for source-linked monitoring, the PDUFA Calendar for upcoming FDA milestones, and watchlists or alerts to keep the relevant tickers and keywords visible. The workflow still requires independent research and judgment.

Frequently asked questions

Who is this workflow for?

It is designed for event-driven biotech investors and adjacent biotech research users who need a repeatable, source-linked way to complete this task.

What should this workflow produce?

A catalyst calendar that visibly distinguishes fixed, guided, inferred, conditional, and estimated timing.

What is the practical benefit?

The investor avoids building precise trades around dates the company never formally committed to.