Scenario-Based Compliance Training
Biotech & Pharma Compliance Scenarios
Seven realistic situations covering the compliance decisions most likely to surface in pharmaceutical and biotech organizations — from FDA submission integrity and off-label promotion to Anti-Kickback concerns, research data integrity, patient privacy, insider trading, and investigator financial disclosure.
Quick Answer
Why do biotech and pharma organizations need specialized compliance scenarios?
Generic compliance training addresses Code of Conduct fundamentals. Biotech and pharma employees face a distinct set of compliance situations — commercial pressure to submit before safety data is complete, conversations with physicians about off-label use, speaker bureau patterns that attract Anti-Kickback scrutiny, and MNPI obligations that extend to family members asking about stock. Generic scenarios don’t build the recognition skills these situations require.
Three Ways to Use These Scenarios
|
Embed in a Course Add to a pharma-specific compliance course or Code of Conduct program adapted for clinical, commercial, and regulatory teams. |
Deploy as Reinforcement Push targeted scenarios to clinical operations, sales, regulatory affairs, and research teams at the moments of highest risk — before NDA submissions, during speaker bureau seasons, and approaching trial data readouts. |
Add to Existing Training Layer onto any existing pharma compliance program as a reinforcement layer — regardless of which platform your organization uses. |
Regulatory Integrity
Pressure to Submit a Drug Before Safety Studies Are Complete. The Head of Commercial Says the Missing Data Is Unlikely to Change the Profile.
The commercial team is pushing to submit an NDA before two safety studies are complete. The Head of Commercial argues that the missing data is unlikely to affect the safety profile, and the competitive window won’t stay open. The regulatory team is being asked to submit a package it knows is incomplete.
Why it’s harder than it looks: The commercial argument sounds reasonable — the data probably won’t change anything, and the window matters. But assessing what the missing data would reveal belongs to the regulatory process, not the commercial team. Submitting a known-incomplete safety package is a regulatory integrity violation, regardless of the competitive rationale.
Right call: Refuse and escalate to the CMO and Compliance. Commercial pressure does not change the regulatory obligation.
FDA Compliance — Off-Label Promotion
A Physician Asks a Sales Rep About Using an Approved Drug for an Unapproved Indication. The Rep Knows the Phase 2 Trial Data Looks Promising. Can They Share It?
A physician initiates a question about an off-label use. The sales rep has seen encouraging Phase 2 data from an ongoing trial. Sharing it feels like helpful, patient-focused information sharing. The rep didn’t bring it up — the physician asked.
Why it’s harder than it looks: The physician who initiates the question is what makes this scenario genuinely difficult. But off-label promotion is illegal regardless of who initiates the conversation, how accurate the data is, or how patient-focused the intent seems. The rep’s job is to decline and refer to Medical Affairs — not to evaluate whether the information is accurate enough to share.
Right call: Decline and refer to Medical Affairs. The initiation doesn’t change the legal analysis.
Research Integrity
A Senior Scientist Wants to De-Emphasize Disappointing Secondary Endpoint Data in a Publication. Is That Acceptable?
A Phase 3 trial shows strong primary endpoint results, but a pre-specified secondary endpoint shows no benefit. A senior scientist suggests that the secondary results be de-emphasized in the publication because “the primary endpoint is what regulators care about.”
Why it’s harder than it looks: The primary endpoint framing is accurate — regulators do weight primary endpoints more heavily. But selectively de-emphasizing pre-specified secondary endpoints is publication bias, a research integrity violation, whether or not any data is technically falsified. The pre-specification creates the reporting obligation.
Right call: Insist that all prespecified endpoints be reported with equal transparency. Refer to the publication committee.
Anti-Kickback — Speaker Bureau
A Physician Is Paid to Speak at 14 Events This Year. The Peer Average Is Three. Their Prescription Volume Surged. Is That a Red Flag?
A top-prescribing physician speaks at 14 company-sponsored events this year. The peer average is three to four. Their prescription volume increased 40% after joining the speaker bureau. A manager says that’s how the program works.
Why it’s harder than it looks: The physician is qualified. The events are legitimate. The manager’s defense — “that’s how the program works” — reflects a pattern that has been at the center of multiple OIG enforcement actions. A significant correlation between speaker bureau participation and prescription volume growth is a textbook Anti-Kickback Statute red flag that requires a formal compliance review, regardless of the commercial team’s comfort with it.
Right call: Flag the pattern to Compliance immediately. Do not reduce speaking engagements without reporting — that addresses the symptom without documenting the concern.
Patient Data Privacy
A Colleague Wants to Share Clinical Trial Participant Data With a Vendor Not Listed in the Consent Documents. Is That Allowed?
A colleague wants to share the clinical trial participant list with a third-party survey vendor not covered by the consent documents. “The IRB will never know — it’s just a survey.” The intent is to improve participant experience.
Why it’s harder than it looks: The survey serves a legitimate purpose, and the intent is patient-focused. But sharing identifiable patient data with a vendor not in the consent documents is a HIPAA and research protocol violation regardless of intent. A confidentiality agreement with the vendor doesn’t create the missing patient consent.
Right call: Refuse and escalate to the IRB and Privacy Officer. Consent is not retroactive.
Insider Trading — Clinical Operations
A Clinical Trial Employee Learns Phase 3 Results Before the Public Announcement. A Family Member Asks If They Should Sell Their Stock.
A clinical operations manager knows the Phase 3 trial missed its endpoint — 72 hours before public announcement. Their sister calls and casually asks whether the stock is a good hold. She doesn’t know what the employee knows. Nobody is pressuring anyone.
Why it’s harder than it looks: The question is innocent, the sister doesn’t know what the employee knows, and saying something vague feels like it’s not really “sharing” anything. But giving any signal — even “you should probably talk to your financial advisor” — based on MNPI is tipping under securities law. Family members are the most common tippees in SEC enforcement actions involving clinical employees.
Right call: Decline to answer and report the contact to the compliance officer immediately. Create a record that you were contacted and did not share information.
FDA Financial Disclosure
Your Lead Clinical Investigator Holds Equity in Your Company. The Trial Data Is Strong. Do You Have to Disclose It to the FDA?
During NDA preparation, the team discovers the principal investigator holds $75,000 in company equity from an early advisory relationship. A senior colleague says disclosing it will invite FDA scrutiny and delay approval. “The data is clean. It won’t affect the review.”
Why it’s harder than it looks: The colleague’s scrutiny argument is not wrong — disclosure does invite FDA review. But the alternative, submitting an NDA with a known undisclosed financial interest, is far more dangerous. Under 21 CFR Part 54, an equity interest above $50,000 is a covered financial interest requiring disclosure regardless of the sponsor’s view of its materiality. The decision on materiality lies with the FDA, not the sponsor.
Right call: Disclose in the NDA submission. A complete response letter for a known omission is worse than any scrutiny that follows proper disclosure.
What These Scenarios Have in Common
Every scenario in this cluster involves a decision where the employee had a compelling reason to go the wrong direction — commercial pressure, a patient-focused intent, a physician-initiated question, a data package the team believed was clean, a family member asking an innocent question. Biotech and pharma compliance training fails when it presents violations as obvious. These scenarios present them as they actually arrive.
“The local business practice defense has never succeeded in an FCPA enforcement action. The physician initiating the question doesn’t change the off-label promotion analysis. The data being clean doesn’t change the FDA disclosure obligation.” These scenarios make those principles concrete before employees encounter the situations in real life.
More Scenario Clusters
|
Anti-Corruption & FCPA Six scenarios covering bribes, kickbacks, government officials, and FCPA red flags. |
Data Privacy & CCPA Four scenarios covering CCPA coverage, data subject requests, and the sharing-as-selling trap. |
Full Scenario Library Browse all compliance training scenarios across every topic area. |
Want These Scenarios in Your Program?
Xcelus builds scenario-based compliance training for pharmaceutical and biotech organizations — covering the full range of clinical, commercial, and regulatory compliance situations your teams actually face.
These scenarios can be embedded in a new course, deployed as targeted reinforcement before high-risk seasons, or added as a layer on top of any existing pharma compliance program.