Development pipeline

What is a development pipeline?

A development pipeline is the collection of pharmaceutical research and development projects progressing from early discovery towards market approval. It may describe one company’s potential new drugs and therapies, a particular disease area, or the combined activity of the wider industry at a given point in time.

A pipeline includes projects at different stages and may cover new molecular entities, biologics, vaccines, devices used with medicines, new indications and other development programmes. Inclusion does not mean that a candidate will reach the market: projects can be delayed, redesigned, partnered, deprioritised or discontinued as evidence develops.

Why does a development pipeline matter in medical affairs?

The pipeline gives medical affairs teams advance notice of the scientific, clinical and stakeholder needs that may arise if an asset progresses. It informs evidence planning, expert engagement, publication priorities, disease education, capability building and the timing of field medical activity.

It also helps teams direct limited resources. A crowded or fast-moving therapy area may require earlier scientific monitoring, while an asset approaching a key decision point may need more detailed evidence-gap analysis. Pipeline visibility supports coordination with clinical development, regulatory, commercial and market access colleagues without treating uncertain candidates as confirmed products.

How is a development pipeline built and maintained?

A pipeline view is usually assembled from internal project records and governance decisions. An industry or competitor pipeline may also draw on public trial registries, company disclosures, scientific congresses, publications and regulatory information.

Each project should have a consistent set of fields, such as:

• Asset or programme name and mechanism of action.
• Indication, target population and intended place in therapy.
• Current development stage and important upcoming decision points.
• Study status, design and expected evidence outputs.
• Ownership, partnerships and territorial rights.
• Regulatory status and anticipated submission or approval pathway.
• Known risks, dependencies and reasons for any change in status.

The pipeline should be updated when evidence or governance decisions change, rather than only for periodic presentations. Clear source dates and status definitions prevent old assumptions from being repeated as current facts.

What stages are included in a development pipeline?

Stage labels vary between organisations, but a pipeline commonly moves through discovery, preclinical research, clinical development and regulatory review before approval. Clinical programmes may be divided into phases, although not every therapy follows a simple linear route.

The asset and the indication should be tracked separately. The same medicine can be approved in one indication while remaining in development for another population, formulation or combination. A useful pipeline therefore records individual development programmes, not just a single overall status for each molecule.

Who owns the development pipeline?

No single function owns every aspect. Research and development teams usually own scientific progression and study delivery, while portfolio governance bodies make investment and prioritisation decisions. Regulatory, medical, commercial and access teams contribute assessments relevant to their responsibilities.

Good governance distinguishes verified facts from forecasts. Expected milestones, approval timing and commercial potential are estimates and should be labelled as such. Teams often go wrong by presenting optimistic target dates as commitments, retaining discontinued projects, or comparing competitors whose stage definitions are not equivalent.

How is a development pipeline different from a portfolio, launch plan or access evidence plan?

A development pipeline is the subset of research and development projects moving towards possible approval. A company portfolio is broader and can include marketed products, mature brands, partnerships and other investments alongside pipeline assets.

A launch plan concerns the coordinated preparation for introducing a selected product or indication, usually once there is enough confidence to plan specific activities. An access evidence plan addresses the clinical, economic and value evidence needed for health technology assessment and reimbursement decisions. Both may be informed by the pipeline, but they are more focused and do not replace it.