MSL role

What is a Medical Science Liaison?

RocketMSL5 min read
A smiling medical science liaison in a white coat with a stethoscope, standing in a bright clinic

A Medical Science Liaison, or MSL, is a field-based scientific role inside a pharmaceutical or biotechnology company's Medical Affairs function. The job is peer-to-peer scientific exchange with healthcare professionals, and in most markets it is separated from commercial activity by both regulation and company policy.

The role is widely misunderstood outside the industry, and not always well understood inside it. Ask someone in a different function what an MSL does and the answer is often a version of "scientific sales", which is close enough to be plausible and wrong in the way that matters most.

This is the explanation rather than the job description. If you want the shorter version, the MSL entry sits in our glossary alongside twenty-four terms defined plainly.

Key takeaways

  • A Medical Science Liaison is a field-based scientific role within Medical Affairs, responsible for scientific exchange with healthcare professionals (HCPs)
  • The role is non-promotional. In most markets that separation is maintained by regulation as well as by internal policy, and it is the defining feature of the job
  • MSLs typically hold an advanced scientific or clinical qualification, because the conversations are peer-to-peer with specialists
  • A typical week combines scientific meetings, preparation, evidence follow-up, congress attendance and internal reporting
  • The boundary between scientific exchange and promotion is what makes the role credible to clinicians, and it is the reason the function is measured differently from commercial teams

What does a Medical Science Liaison do?

An MSL holds scientific conversations with healthcare professionals about a company's therapeutic area, its data, and the evidence base around it.

In practice that breaks into four activities.

Scientific exchange. Discussing clinical data with specialists — trial design, endpoints, subgroup findings, safety profile, mechanism of action. These are peer-level conversations, which is why the role requires genuine scientific depth rather than product familiarity.

Responding to clinical questions. Clinicians raise questions the published literature does not answer. The MSL either addresses them from approved material or routes them to Medical Information, depending on the nature of the question.

Capturing what comes back. Unmet needs described from practice, gaps in the evidence base, barriers to guideline-concordant care. This is the part that feeds evidence generation planning, and it is the part most often lost, because it depends on what the organisation learns and loses between one conversation and the next.

Supporting scientific activity. Advisory boards, investigator engagement, congress presence, and internal input into medical strategy.

What an MSL does not do is sell. That is not a matter of emphasis.

How is an MSL different from a sales representative?

The two roles both involve visiting clinicians, and there the similarity ends.

Purpose. A sales representative's objective is to influence prescribing behaviour in favour of a product. An MSL's objective is scientific exchange — which includes, legitimately, a clinician concluding that a therapy is not appropriate for her patients.

Content. A representative works from promotional material approved for that purpose. An MSL works from scientific material approved through medical, legal and regulatory review, which is a different process with different constraints.

Direction. Sales conversations run outward — a message is delivered. Scientific exchange runs both ways, and the information coming back is often worth more to the company than the information going out.

Reporting line. MSLs report through Medical Affairs, structurally separated from commercial. In most companies this separation extends to objectives, incentives and, increasingly, to systems.

Measurement. A representative can be measured against prescribing movement. An MSL cannot, without redefining the role — which is a large part of why Medical Affairs has no owned outcome metric in the way other functions do.

That last difference is the one that causes the most trouble internally, because it is easy to assume a field role should be measured like a field role.

What does an MSL's week actually look like?

Less uniform than a job description suggests, and more fragmented.

Meetings, usually a handful rather than dozens. Scientific conversations with specialists take preparation and run long. Volume is not the objective, which is why counting them tells you very little.

Preparation, which takes considerably longer than people expect. Assembling what a specific clinician has previously asked, what the current evidence says, which publications are relevant to her patient population, and which questions remain open from the last conversation. Much of this lives across several systems, or in the MSL's own notes.

Documentation, afterwards. Capturing what was discussed, what the clinician raised, and what needs following up. Frequently done at the end of a long day from memory, which is why detail is lost — and why what a scoring model should and should not measure matters to the people doing the work, not only to those reporting on it.

Follow-up. Evidence requests, publication references, connecting a clinician with a medical information team or an investigator programme.

Congresses and internal work. Scientific meetings, advisory boards, and input into medical plans and content development.

Travel is a substantial part of the role in most territories, and the administrative load at the end of the day is the part MSLs consistently describe as the worst.

What qualifications does the role require?

There is no single standard, and requirements vary by company, therapeutic area and market. Some common patterns are worth describing.

An advanced scientific or clinical qualification is usual — a PharmD, PhD, MD, or equivalent. The reason is structural rather than credentialist: the conversations are peer-to-peer with specialists who will not engage seriously with someone unable to discuss trial design at their level.

Therapeutic-area depth matters more than pharmaceutical industry experience. Companies hire from clinical practice, academia and research reasonably often.

Communication ability in a specific sense — the capacity to hold a scientific discussion with someone more expert than you in their own subfield, without either deferring entirely or overclaiming.

Comfort with ambiguity. The role has no script. What to raise, when to stop, and what a particular clinician actually needs is judgement exercised in real time.

What is rarely required, and sometimes actively unhelpful, is a sales background. The habits transfer badly.

Why does the non-promotional boundary matter so much?

Because it is the only reason the conversations work.

A specialist agrees to meet an MSL on the understanding that the discussion is scientific. She will raise genuine objections, describe where the evidence is inadequate, and say things she would not say to someone whose objective is to increase prescribing. That candour is the entire value of the interaction, and it depends on her belief that the boundary is real.

If the boundary erodes — if MSLs are given commercial targets, or measured on prescribing movement, or used to deliver messages that could not clear medical review — the clinician's behaviour changes before anyone notices. The meetings continue. The candour does not. And the company loses the information it valued most, without any visible signal that it has happened.

This is also why the function is measured differently. A measurement framework built on commercial outcomes does not merely report on the function; it redefines it. Which makes measuring Medical Affairs honestly a harder problem than it first appears, and an important one to get right.

RocketMSL is built for Medical Affairs teams measuring scientific engagement without borrowing commercial metrics. See how the platform works →