Compliance Training Scenario Examples — Real Workplace Decisions
Compliance training scenarios are short, realistic workplace situations that help employees practice recognizing and responding to ethical and compliance risks. These scenarios are widely used in code of conduct training to improve real-world decision-making, not just policy awareness.
Policies tell employees what to do or not to do. Scenarios train them how to decide. Scenario-based training places employees in situations where they must evaluate context, identify risks, and choose the right course of action.
Organizations use these scenarios to reduce compliance risk, strengthen employee judgment, and build confidence in reporting and decision-making across the business.
These scenarios commonly address topics such as conflicts of interest, anti-corruption, data privacy, workplace harassment, and reporting concerns.
Xcelus builds scenario-based code of conduct training and compliance programs around situations like these — putting employees in realistic decision-making situations before they encounter them in real life. See full scenario video examples →
Conflicts of Interest
Conflicts of Interest — Vendor Relationship
An employee’s spouse works at a company that has just been hired as a vendor on a project the employee is directly involved with.
Decision: Stay quiet to avoid complications, disclose the relationship to a manager, or remove yourself from the project without saying why.
Right call: Disclose immediately. A conflict of interest exists even when no improper decision has been made. The company cannot manage what it doesn’t know about.
Conflicts of Interest — Business Opportunity
An employee learns of a business opportunity through their role that their company likely wouldn’t pursue. They pass the information directly to a friend who runs a consulting firm.
Decision: Share it — the company isn’t interested anyway, so there’s no harm. Or share it internally first, then pass it along if the company declines.
Right call: Share internally first. Opportunities discovered through the company role belong to the company first. Bypassing that step violates the Code of Conduct regardless of the company’s likely interest.
Conflicts of Interest — Outside Employment
A senior analyst runs a weekend consulting business helping tech startups. One of his clients mentions they are preparing a bid for a contract with his employer. He’s not on the selection committee.
Decision: Continue the side business — no influence over the bid. Formally disclose the business and the specific client to your manager. Immediately resign from the startup project.
Right call: Disclose formally. Compliance isn’t only about your actions — it’s about institutional risk. If the startup wins the contract and later surfaces that a senior analyst was on its payroll, the entire contract could be voided, regardless of whether any information was shared.
Conflicts of Interest — Vendor Hospitality During RFP
A manufacturing vendor invites you on an all-expenses-paid elk hunting trip to Wyoming. Your company is currently running an RFP for a contract that this vendor wants to win.
Decision: Go, but pay your own airfare. Decline the invitation entirely. Ask your manager for permission.
Right call: Decline. With an active RFP underway, accepting any high-value hospitality from a bidder creates an immediate conflict of interest regardless of how the trip is framed. Paying for your own airfare does not neutralize the $3,000 cost of a hunting trip for an active bidder.
Conflicts of Interest
My Electrician Side Business — Does It Create a Conflict of Interest With My Employer?
Decision: Keep the side business — it’s a different trade than your day job. Disclose it because your employer holds a trade license that covers your weekend work. Do nothing until the business grows.
Right call: Disclose. A trade license that your employer holds that covers your independent work creates a conflict of interest, even if the customers are completely different. The liability and regulatory exposure belong to your employer without their knowledge.
Conflicts of Interest
I Sell Candles on Etsy. My Employer Also Sells Candles. Is That a Conflict of Interest?
Decision: Keep the shop — the scale is completely different, it’s a hobby. Disclose it to be safe. Shut it down because any product overlap creates a conflict.
Right call: Disclose. A side business selling the same product category as your employer creates a potential conflict of interest, regardless of scale. What doesn’t compete today may compete tomorrow — and the disclosure obligation applies now, not when it becomes a problem.
Gifts & Entertainment
Gifts & Entertainment — Vendor Gift at Contract Renewal
A vendor offers tablet computers to the management team as a personal thank-you during contract renewal discussions. The vendor calls it a gift, not a condition.
Decision: Accept the tablets — they’re a thank-you, not a bribe. Decline and report the offer. Accept but disclose to a manager.
Right call: Decline and report. The timing and value place this firmly in bribery territory under most code-of-conduct training standards — bribes don’t need to be cash to be bribes.
Gifts & Entertainment — Holiday Client Gift
An employee wants to send a favorite client a rare autographed football as a holiday gift. The employee considers it a genuine personal gesture.
Decision: Send it — it’s a personal gesture with no business strings attached. Check the company gift policy first. Send a standard holiday card instead.
Right call: Check the company gift policy first. Most organizations set a monetary threshold for gifts. A rare autographed item almost certainly exceeds that threshold regardless of the intent behind it.
Gifts & Entertainment — Personal Email Gift Card
A vendor you’ve worked with for 10 years sends a $100 Amazon gift card to your personal email with a note: “This isn’t for work — just from one friend to another to say thanks for a great decade.”
Decision: Accept it — it’s personal, under $100, and sent to a personal email. Decline and explain company policy. Accept but keep it confidential.
Right call: Decline and explain the policy. The friendship is real — but the gift policy applies to the professional relationship, not the personal one alongside it. The email address, dollar amount, and framing don’t change the compliance classification.
Reporting a Concern & Non-Retaliation
Reporting — Concern About a Manager
An employee suspects their manager is asking them to do personal errands on company time using company property. The employee reports it — and discovers they misunderstood the situation.
Decision: Stay quiet next time to avoid embarrassment. Report concerns as they arise, regardless of certainty. Wait until there is more evidence before reporting.
Right call: Report concerns as they arise. Non-retaliation policies protect good-faith reporting even when the concern turns out to be a misunderstanding. It is better to ask and be wrong than to stay silent.
Reporting — Confidential Complaint
A supervisor finds out someone filed a complaint about horseplay in the office. The supervisor wants to find out who made the report so they can address the issue directly.
Decision: Investigate to identify the reporter — it’s the supervisor’s job to manage the team. Respect the confidential reporting process and escalate to HR. Address the behavior without attempting to identify the reporter.
Right call: Respect confidentiality and escalate to HR. Attempting to identify a confidential reporter — even with good intentions — violates the non-retaliation policy and undermines the speak-up culture code of conduct training is designed to build.
Reporting — Duty to Report Theft
Two colleagues have been taking office supplies home for months. Both do good work. You haven’t reported it because it feels minor and you don’t want to get anyone in trouble. The company hasn’t done anything — but you haven’t told anyone.
Decision: Continue saying nothing — the amounts are too small to matter. Report through the proper channel. Tell the colleagues directly and ask them to stop.
Right call: Report it. Every employee has an affirmative duty to report known policy violations — not just permission to report. Failing to report an ongoing violation can itself result in disciplinary action.
Non-Retaliation — Workplace Mobbing
Three weeks after reporting a compliance concern, you notice a pattern: left off meeting invites, colleagues avoid eye contact, excluded from a team lunch, and manager’s emails have become terse. Each incident seems explainable. But the pattern started immediately after your report.
Decision: Ignore it — each incident is too small to raise formally. Document the pattern and report it to HR. Confront the colleagues directly.
Right call: Document and report. A cluster of exclusionary behaviors that begins immediately after a compliance report is a retaliation pattern, regardless of whether any single incident is severe. Mobbing is designed to be individually deniable — the pattern is the evidence.
Non-Retaliation — The False Complaint Myth
You reported what appeared to be a manager falsifying expense reports. The investigation found a legitimate explanation — the expenses were real. The manager was cleared. Now you’re worried you’ll face consequences for making an accusation that turned out to be wrong.
Decision: Apologize to the manager — the investigation cleared them. Do nothing additional — the report was protected. Resolve never to report a concern again.
Right call: Do nothing additional. A good-faith report that turns out to be wrong is fully protected. The standard is honest intent — not accuracy. Apologizing implies the report was wrong to make, which it wasn’t.
Protecting Confidential Information
Confidential Information — Social Setting
At dinner with friends, an employee mentions that a client under criminal investigation must not be worried — because they just started a new project with the employee’s company.
Decision: It’s fine — friends aren’t going to act on it. It’s a violation — client relationship information is confidential. It’s only a problem if the friends work in finance.
Right call: It’s a violation. Client relationship information is confidential regardless of the social setting or who the audience is. A useful standard: if you wouldn’t be comfortable reading it in the news, don’t say it at dinner.
Confidential Information — Social Media
An employee involved in a confidential new product launch shares their excitement about the upcoming announcement on their personal social media account before the official release.
Decision: It’s a personal account — company policy doesn’t apply. It’s a violation of confidentiality and potentially social media policy. It’s fine if no specific details are shared.
Right call: It’s a violation. Proprietary product information is confidential until officially released, regardless of how vague the post seems. Employees should assume that any non-public company information is confidential.
Workplace Gossip & Personal Confidentiality.
These scenarios address the compliance line between conversation and confidentiality violation.
Confidentiality
A Colleague Shared My Medical Diagnosis With the Team Without Asking. Is That a Policy Violation?
Decision: Tell only one trusted colleague to prepare the team. Keep it completely private. Ask David’s permission before saying anything to anyone.
Right call: Keep it private — or ask first. Medical information shared in confidence is subject to strict confidentiality obligations. Good intent is not a defense. “I only told one person” does not limit how far the information travels.
Confidentiality
A Colleague Shared My Financial Struggles With the Team. They Got Fired. Why Does Gossip Cost Jobs?
Decision: Share it — she didn’t say “keep this private.” Keep it private regardless. If genuinely concerned about her performance, raise it with a manager without the personal details.
Right call: Keep it private. Personal information shared in a private workplace conversation carries an implicit confidentiality expectation — no explicit “keep this secret” instruction is required. Adding unfounded assumptions about performance and sharing both widely is a terminable offense.
HR Confidentiality
Someone filed an HR complaint, and the Details Are Spreading Through the Office. Who Is Responsible?
Decision: Stay out of it — it’s HR’s process. Escalate to HR and your manager immediately. Talk to the complainant first to see if they want to escalate.
Right call: Escalate to HR immediately — as a manager, you have an independent reporting obligation. Every employee who hears about the leak is updating their mental model of whether it’s safe to report. The chilling effect on speak-up culture is as serious as the harm to the individual.
Confidentiality — Field Employees
A Drill Operator Spread a Layoff Rumor on Site. It Wasn’t True. It Cost Her Job. Why?
Decision: Tell the crew — they deserve to know if their jobs are at risk. Keep it to herself. Ask a supervisor directly rather than spreading an unverified rumor.
Right call: Ask the supervisor — don’t speculate with the crew. In a field environment, anxiety and distraction have physical consequences. The near-miss safety incident that followed the rumor is a direct result. “I just heard it” is not a defense when the harm is real and documented.
Diversity, Inclusion & Belonging
These scenarios help managers and employees recognize bias and build inclusive workplaces.
Hiring Bias
Two Qualified Candidates. One Profile Feels More Familiar. Is That Affinity Bias — and What Do You Do About It?
Decision: Go with the familiar profile — consistency in hiring is quality control. Pause and evaluate both candidates against the same objective criteria. Hire the less-familiar candidate to demonstrate commitment to diversity.
Right call: Pause and apply a structured evaluation. The “safer choice” in hiring almost always means “more familiar” — not “more qualified.” Neither defaulting to familiarity nor overcorrecting with demographic preference is a merit-based decision. The process is the answer.
Age Discrimination
The Most Qualified Candidate Gets Rejected Because She Seems Too Old for the Team. Nobody Said the Word “Age.” Is That Legal?
Decision: Go with the team’s recommendation — culture fit is a legitimate criterion. Pause and ask the team to translate vague feedback into specific, role-based evidence. Override the team and hire the stronger candidate.
Right call: Pause and challenge the feedback. “Moves fast,” “feels dated,” and “gel with the team” are the phrases that appear in ADEA litigation — not because they’re illegal on their own, but because they often substitute for age without naming it. If the team can’t provide specific, role-based evidence, the feedback should not drive the decision.
Belonging
A High Performer Has Stopped Contributing in Meetings. Nobody Did Anything Wrong — So What’s the Problem?
Decision: Do nothing — she’s still producing good work. Have a low-pressure one-on-one check-in. Observe for a few more weeks before acting.
Right call: Have the conversation now. Belonging erodes in the absence of active inclusion — not only in the presence of exclusion. Two months of silence from a previously engaged high performer is the signal. Waiting for it to resolve on its own is how organizations lose people they never intended to lose.
Supporting Employee Mental Health
These scenarios help managers recognize when an employee may be struggling and respond appropriately.
Employee Wellbeing
A High-Performing Employee Has Been Missing Deadlines and Withdrawing From the Team for Weeks. You’re Her Manager. What Do You Do?
Decision: Address only the performance issues — keep it professional. Use the Observe-Listen-Support-Refer model for a check-in conversation. Refer directly to HR and let them handle it.
Right call: Have the check-in conversation. A manager’s role is not to diagnose — it’s to notice, open a door, and connect the employee with support. Addressing only the performance ignores the person. Routing immediately to HR removes the manager from a relationship that is theirs to manage.
Anti-Corruption, Anti-Bribery & FCPA
Anti-Corruption — Government Official
A government official at customs asks an employee to pay a $100 entry fee — and offers to expedite clearance for an additional $50. The employee doesn’t know if this is a standard charge.
Decision: Pay it — it’s a small amount, and the trip is important. Ask for proof that the fee is required and whether a receipt will be provided. Pay and document it as a business expense.
Right call: Ask for proof and a receipt. If none is offered, do not pay unless there is absolutely no other option — and if payment is made, document and report immediately. FCPA violations can occur even under pressure.
Anti-Corruption — Competitive Bid
A vendor facing competitive renewal offers to match pricing for three years — and provides tablets to each management team member as a personal thank-you. They frame it as appreciation, not as tied to the contract.
Decision: Accept — the pricing deal and the gift are separate. Decline the tablets and proceed with the open renewal. Accept and disclose the gift.
Right call: Decline the tablets and proceed with open renewal. The timing connects the gift to the business outcome regardless of how it is framed. Accepting creates anti-corruption exposure for both the employee and the organization.
Anti-Corruption — Vague Consulting Fees
A distributor says you need to pay 15% to a “market access consultant” with government connections before a contract can be approved. No specific deliverables are provided. “This is just how business gets done here.”
Decision: Approve the payment — local business practices vary. Stop and escalate to Legal or Compliance before any payment. Negotiate the fee down to reduce the risk.
Right call: Stop and escalate immediately. Vague fees to intermediaries with government connections before contract approvals are a textbook FCPA red flag. Negotiating the fee down doesn’t fix the problem — a smaller bribe is still a bribe.
Anti-Corruption — Inflated Invoice Kickback
After a contract renewal, a vendor contacts you privately and suggests submitting invoices for $15,000 per quarter when the real cost is $10,000 — transferring the $5,000 difference to you as a “thank you for your loyalty over the years.”
Decision: Accept — it’s essentially a bonus for the relationship work you created. Decline and report the offer to Compliance. Decline but don’t report — you’re not doing anything wrong by saying no.
Right call: Decline and report. A vendor offering to inflate invoices and pay you personally has just offered a kickback — fraud against your employer. Declining without reporting leaves the vendor free to make the same offer to someone else.
Anti-Corruption — Quid Pro Quo Internship
During final negotiations for a multi-million-dollar contract, the client’s Procurement Director mentions that his nephew is looking for a summer internship—and hints that having him nearby would “certainly help smooth over the final contract approvals.”
Decision: Fast-track the internship — it’s a small favor to secure a massive deal. Refer the nephew to the standard HR portal. Decline and report the interaction to Compliance.
Right call: Decline and report. Providing a thing of value — including an internship — to a relative of a decision-maker in exchange for a business outcome is bribery regardless of the candidate’s qualifications. The hint is the compliance trigger.
Anti-Corruption & FCPA
A $50,000 Consulting Fee Just Appeared Before My Government Contract Closes. Q3 Ends Friday. What Do I Do?
Decision: Approve the payment — the consulting fee is standard practice in this market. Stop everything and escalate to Legal or Compliance immediately. Approve a reduced fee to limit the risk.
Right call: Stop and escalate. A last-minute consulting fee payable before a government contract closes — with no deliverables specified — is a textbook FCPA red flag. Quarter-end pressure does not change the legal analysis. A smaller fee is still a bribe.
Insider Trading
Insider Trading — Social Disclosure
An employee tells a close friend about upcoming contracts that will significantly affect the company’s revenue. The friend buys company shares before the news goes public.
Decision: Only the friend is liable — the employee just had a conversation. Both the employee and the friend face potential insider trading charges. The employee is only liable if they knew the friend would trade.
Right call: Both face liability. Disclosing material non-public information — regardless of intent — can expose the person who disclosed it to insider trading charges, along with the person who traded on it.
Insider Trading — Investment Club
An employee’s investment club is reviewing a vendor that their company works with. The employee knows confidentially that their company plans to significantly increase business with this vendor.
Decision: Share the information — it’s about a vendor, not your own company. Recuse yourself from the club’s discussion. Stay silent but remain in the discussion.
Right call: Stay silent and recuse. Material non-public information about business partners — not just your own company — is subject to the same insider trading constraints. Code of conduct training on this topic applies beyond direct company stock.
Accurate Records & Reporting
Accurate Records — Inflated Mileage Claim
An employee lost a receipt for a $75 entertainment expense. To recover the loss, they inflate their mileage claims the following month by an equivalent amount. They genuinely spent the money — they’re just adjusting which expense it’s recorded against.
Decision: Proceed — the expense was real, and the amounts balance out. Report the lost receipt and follow the proper process. Absorb the $75 loss and move on.
Right call: Report the lost receipt and use the proper process. Submitting inflated claims to offset a real loss is still a false record — there is no good justification for falsifying expense submissions regardless of the original cost.
Accurate Records — Backdated Sales Receipt
A supervisor asks an employee to backdate a cash receipt by 2 days so a deal counts toward this quarter’s sales figures, affecting bonus calculations. “The deal was verbally agreed upon before quarter-end. It’s just an administrative correction.”
Decision: Backdate it — the deal was real. Decline and consult the finance team. Backdate but document your objection in writing.
Right call: Decline and consult finance. A verbal agreement before quarter-end is not a financial record — changing a document date to affect quarterly reporting is a falsification regardless of the underlying deal. Documenting an objection while proceeding does not create a compliance safe harbor.
Social Media Policy
Social Media — Workplace Photo
A colleague photographs a coworker in a compromising position at work and shares the image with friends and on several social media platforms. The colleague considers it a harmless joke.
Decision: It’s harmless if intended as a joke, and the coworker isn’t upset. It’s harassment and a conduct violation regardless of intent. It’s only a problem if the coworker complains.
Right call: It’s a violation regardless of intent. Taking and sharing unauthorized workplace photos violates harassment and conduct policies. Impact — not intent — determines whether conduct violates company policy.
Social Media — Customer Complaint Response
An employee notices a negative post about their company on social media and wants to respond to correct the record and defend the organization.
Decision: Respond — defending the company is the right instinct. Report the post to the social media or communications team and let them respond. Ignore it.
Right call: Report to the social media team. Employees responding individually to public complaints can escalate the situation, create legal exposure, or contradict official messaging. Social media policy training addresses exactly this scenario.
Anti-Money Laundering
Anti-Money Laundering — Vendor Payment Routing
A vendor based in Spain requests that all payments be sent to a bank account in the Cayman Islands. They say it’s for tax efficiency purposes.
Decision: Proceed — tax efficiency is a legitimate reason. Escalate to Legal or Compliance before entering any arrangement. Request that payment go to a domestic account instead.
Right call: Escalate to Legal or Compliance. Bank accounts in known tax havens that differ from the vendor’s operating jurisdiction are a standard AML red flag. This scenario belongs in code of conduct training for procurement and finance roles.
Anti-Money Laundering — Deposit and Redirect
A client places a large order with an unusually high deposit, then cancels and requests a refund to a different company that cannot be verified.
Decision: Process the refund — the client is just changing their mind. Hold the refund and contact the AML Compliance Officer. Request more information from the client before proceeding.
Right call: Hold and contact AML Compliance immediately. This transaction pattern — large deposit, cancellation, redirect to an unverifiable entity — is a classic money laundering red flag that compliance training is specifically designed to help employees recognize.
Export Controls /Global Trade
Export Controls — Embargoed Country
A client in Malaysia places an order for technology products and mentions during the call that a colleague in North Korea will receive part of the shipment.
Decision: Proceed — the customer is in Malaysia, which is not under an embargo. Hold the order and report to Compliance immediately. Split the order — fulfill the Malaysia portion and decline the North Korea portion.
Right call: Hold the entire order and report to Compliance. The destination of goods, not just the buyer’s location, determines export compliance. Diversion to an embargoed country violates US law even when the ordering party is in a permissible country.
Anti-Competitive Practices / Antitrust
Antitrust — Market Allocation
At a trade show, a competitor’s sales rep pulls out their client list and proposes: if you agree not to pursue their top three accounts for a year, they’ll agree not to pursue yours. “We’d both be better off.”
Decision: Politely decline and return to normal competition. End the conversation immediately and report to Legal. Continue the conversation to understand the full proposal before deciding.
Right call: End the conversation and report to Legal immediately. Market allocation is a per se antitrust violation regardless of how informal the setting. Declining without reporting leaves no documentation that you refused, and your company’s subsequent market behavior could be mischaracterized.
Responsible AI
Responsible AI — Confidential Data in Public Tools
An employee wants to paste a confidential strategy meeting transcript into a public AI tool to generate a summary for the team.
Decision: Proceed — AI tools are secure. Use only company-approved AI tools or sanitize the content first. Summarize it manually instead.
Right call: Use only approved tools or sanitize first. Public AI models may retain and train on submitted data. Pasting confidential strategy content into a public tool is a data privacy and confidentiality violation — a scenario directly addressed in responsible AI training.
Responsible AI — Voice Fraud
An employee receives a voice message that sounds exactly like the CFO requesting an urgent payment to a new supplier before close of business — outside the normal approval process.
Decision: Process it — the voice is clearly the CFO’s. Call the CFO directly on their verified number from the company directory before taking any action. Escalate to IT security.
Right call: Call the CFO directly on a verified number. AI voice cloning can replicate voices from publicly available audio. Urgency and bypassing normal approval channels are the key red flags — both are classic social engineering signals that code of conduct training and AI ethics training both address.
Biotech & Pharma Compliance
Regulatory Integrity
Commercial pressure to submit a drug before two safety studies are complete. The Head of Commercial says the missing data is unlikely to change the profile.
Decision: Submit as requested. Refuse and escalate to the CMO and Compliance. Contact the regulatory agency for an expedited review timeline.
Right call: Refuse and escalate. Submitting a safety package with known omissions is a regulatory integrity violation regardless of commercial pressure or the commercial team’s assessment of the missing data.
FDA Compliance — Off-Label Promotion
A physician asks a sales rep about using an approved oncology drug for an unapproved indication. The rep knows the Phase 2 trial data looks promising.
Decision: Share the trial data informally as scientific background. Decline and refer to Medical Affairs. Mention the ongoing trial without discussing outcomes.
Right call: Decline and refer to Medical Affairs. Off-label promotion is illegal regardless of who initiates the conversation, how accurate the data is, or how patient-focused the intent seems.
Research Integrity — Clinical Trial Data
A Phase 3 trial shows positive primary results but a pre-specified secondary endpoint shows no benefit. A senior scientist suggests de-emphasizing the secondary results in the publication.
Decision: Agree — the primary endpoint is what regulators care about. Insist all pre-specified endpoints are reported with equal transparency. Refer to the publication committee.
Right call: Insist on full transparency. Selective de-emphasis of pre-specified endpoints is publication bias — a research integrity violation whether or not any data is technically falsified.
Anti-Kickback — Speaker Bureau Payments
A top-prescribing physician speaks at 14 events this year — the peer average is three to four. Their prescription volume increased 40% after joining the speaker bureau. Your manager says that’s how the program works.
Decision: Continue — the physician is qualified and the events are legitimate. Flag the pattern to Compliance. Reduce speaking engagements without reporting the pattern.
Right call: Flag to Compliance immediately. A significant correlation between speaking frequency and prescription growth is a textbook Anti-Kickback Statute red flag requiring formal review.
Patient Data Privacy — HIPAA Research
A colleague wants to share the clinical trial participant list with a third-party survey vendor not listed in the consent documents. “The IRB will never know — it’s just a survey.”
Decision: Share the list — the survey serves patients’ interests. Refuse and escalate to the IRB and Privacy Officer. Ask the vendor to sign a confidentiality agreement first.
Right call: Refuse and escalate. Sharing identifiable patient data with a vendor not in the consent documents is a HIPAA and research protocol violation. A confidentiality agreement with the vendor does not create the missing patient consent.
Biotech — Insider Trading
A Clinical Trial Employee Learns Phase 3 Results Before the Public Announcement. A Family Member Asks If They Should Sell Their Stock. What Do You Do?
Decision: Decline without explaining why. Give a vague signal — suggest she talk to a financial advisor. Decline to answer and report the contact to the compliance officer.
Right call: Decline and report the contact. A vague warning based on MNPI is still a tip-off. “I didn’t trade — I just mentioned it” is not a defense. Family members are the most common tippees in SEC enforcement actions involving clinical employees. Report the contact to create a protective record.
Biotech — FDA Disclosure
Your Lead Clinical Investigator Holds Equity in Your Company. The Trial Data Is Strong. Do You Have to Disclose It to the FDA?
Decision: Disclose in the NDA submission as required. Don’t disclose — the interest is immaterial and the data is clean. Remove the investigator’s sites from the dataset to avoid the issue.
Right call: Disclose. Under 21 CFR Part 54, equity above $50,000 in the sponsor is a covered financial interest requiring disclosure regardless of the sponsor’s view of its materiality. The decision on whether the interest is material belongs to the FDA—not the sponsor. Selective exclusion of investigator data creates worse problems than the disclosure.
What These Compliance Training Scenarios Have in Common
None of these situations looks like an obvious violation in the moment. They look like normal business decisions — a vendor relationship, a conversation with a friend, a request from a manager. That is what makes them representative of real compliance risk.
Effective code of conduct training doesn’t just tell employees the rules; it also shows them how to apply them. It places them inside situations like these — before they encounter them at work — and asks them to practice making the right call. That recognition practice is what closes the gap between knowing a policy and applying it when a real decision presents itself.
Each scenario above corresponds to a topic area covered in Xcelus’s scenario-based compliance training library. Programs can be delivered as standalone annual code of conduct training, modular topic courses, or short reinforcement scenarios deployed throughout the year.
Build Training Around Scenarios Like These
Xcelus develops scenario-based code of conduct training and compliance programs for enterprise organizations. Each course is built around realistic workplace decisions — the situations your employees actually face.