Nobody Says “Commit Fraud”: Teaching Students to Refuse Their Own Boss

"Just date it the 30th"

It's the second week of October. A twenty-three-year-old, four months into her first job, is closing out a shipment log. Her supervisor stops by her desk at 5:40.

"That last order — the one that went out on the 2nd. Just date it the 30th. It was basically ready in September, the customer had already signed, and it's the difference between us hitting the quarter or not. Everybody does this. It's not a big deal."

He is friendly about it. He hired her. He writes her review in six weeks and his signature is on the reference she'll need in two years. He has not asked her to commit fraud — he has asked her to change a date.

She has about four seconds, and nothing in her education prepared her for any of them.

The ask never announces itself

Business ethics is taught as dilemmas: two competing goods, a hard trade-off, a framework to apply. That's genuine philosophical training and it doesn't resemble how this actually shows up.

Real pressure arrives disguised as something ordinary:

Nobody says the word. The person applying the pressure often doesn't fully think of it as a violation either, because they've done it before and nothing happened.

So the diagnostic students need isn't about content — nobody reasons their way to a violation classification at 5:40 on a Thursday. It's about form. Urgency without a reason. A verbal request that would normally be written. Discomfort about who else knows. An appeal to the relationship rather than the rules. Those signals are recognizable in the moment and teachable in a single class.

Teaching ethical decision making as classification — is this act permissible? — misses the fact that the hard part isn't the classification. It's what you say next to someone who controls your career.

The refusal has to be survivable

Here is where most ethics education fails its students.

Case discussion produces people who can identify the right answer and picture themselves declaring it. Nobody in a classroom has ever refused someone who writes their performance review. The imagined refusal is clean, principled, and costless — and bears no relationship to a supervisor standing at your desk.

The practical skill is refusing in a way that stops the conduct without detonating the relationship — because the goal is not to be heroic, it's to not do the thing and still have a job.

Restate the ask plainly. "I want to make sure I've got it right — you want me to record it as shipping on the 30th when it went out on the 2nd?"

This is the most powerful move available and it looks like nothing. Almost all improper pressure depends on ambiguity and momentum. Saying the request out loud, neutrally, without accusation, frequently ends it on the spot — because the supervisor has to hear it too, and hearing it is different from saying it.

Ask for it in writing. "Can you send that to me in an email so I have it right?"

Procedurally normal, entirely non-confrontational, and decisive. Most improper asks evaporate at this point. The person making them knows what they're asking, even when they've told themselves they don't, and putting it in email makes that unavoidable. Students find this move astonishing when they first see it work.

Take time. "Let me check the revenue guidance and come back to you first thing tomorrow." Pressure is almost always engineered to be immediate. Slowing it down is often sufficient by itself.

Offer an offramp. "I don't think I can date it that way. What I can do is flag it to accounting and see whether there's a legitimate cut-off treatment — want me to do that?"

Most supervisors applying this kind of pressure are themselves under pressure from somewhere. Many will take a compliant alternative if one is handed to them, and offering it lets them retreat without admitting they asked for something wrong. Treating the person as a villain forecloses the best available outcome and guarantees an enemy.

Write it down afterward. Date, what was asked, what you said, who was present. Students hear this as paranoid. It's the difference between an account that holds up later and one that doesn't.

Your escalation path runs through the problem

This is what makes the scenario structurally distinct from the audit escalation conversation, where a junior takes a concern to a partner who is a neutral recipient.

Here, the person you'd escalate about is the person you escalate through. Your supervisor is the ordinary channel, and he's the source. That leaves skip-level, HR, compliance, an ombuds function, a hotline, or eventually a regulator — and each has a different cost, a different confidentiality posture, and a different likelihood of anything happening.

Students should know what these are, practically, before they need one. Most compliance training for students covers the existence of a hotline and stops. It doesn't cover that fear of retaliation is rational rather than a failure of nerve, or that an anonymous report filed without ever having said no forfeits the resolution that works most often — the supervisor backing down once the ask is explicit.

And it's worth being honest that refusal sometimes has a cost. Ethics courses that imply integrity is always rewarded produce graduates who feel deceived the first time it isn't, and a person who feels deceived is less likely to hold the line the next time. Saying plainly that some refusals damage a relationship, an assignment, or occasionally a career — and that people do it anyway, and that the moves above make the cost much smaller than students imagine — produces sturdier behavior than reassurance does.

Four ways it goes wrong

The silent complier does it and tells herself it was small. The real damage is the ratchet: the next ask is bigger, and she has already established that she's someone who goes along. Almost every serious case begins with a person who complied with something minor.

The moralizer makes it about the supervisor's character. "I'm not comfortable with what you're asking me to do ethically." Guarantees retaliation, doesn't stop the conduct, and converts a solvable moment into a permanent adversary.

The paralyzed says nothing, does nothing, hopes it resolves itself, and functionally complies.

The premature reporter goes straight to the hotline having never said no out loud. Sometimes exactly right — particularly where safety or serious fraud is involved — and frequently a lost opportunity to end it in thirty seconds.

Why the curriculum can't build it

Ethics is taught as analysis, and the gap is between knowing and doing. Students become skilled at reasoning through dilemmas — stakeholders, frameworks, positions. None of that is what fails in the moment. What fails is a twenty-three-year-old's capacity to say a sentence out loud to someone with power over her.

Classroom discussion has no power asymmetry. A student arguing an ethical position in a seminar risks nothing. The entire difficulty of the real situation is the cost, and the classroom removes it by design.

Compliance modules are click-through. They establish that a policy exists. They rehearse no behavior.

Peer role play can't produce a boss. A classmate has no authority, writes no review, and will not apply the friendly, relationship-based pressure that makes this hard. The pressure is the entire content.

And the first real instance happens alone, early, and fast. Usually to someone in their first two years, without warning, with no one to consult, in under a minute.

What simulation changes

Ethics role play scenarios built as simulations put a student in front of a supervisor who applies real pressure, in the several forms it takes:

That last persona is pedagogically essential. Students need to experience the move working, not merely be told it works — because the belief that refusal is always catastrophic is the thing that produces compliance, and one rep of a supervisor retreating does more to dislodge it than any lecture.

Transcripts make the assessment concrete: whether the student ever restated the ask plainly, whether they requested it in writing, whether they offered an alternative, whether they eventually complied.

Designing the module

Pass one — make it explicit. The deniable supervisor. Score whether the student restated the request in plain terms and whether they extracted a direct ask.

Pass two — the written request. Score whether the student asked for it in writing and how they framed it — procedurally, or as an accusation.

Pass three — the escalation. The supervisor pushes back with irritation and an implied cost. Score whether the student held, whether they offered a compliant alternative, and whether they identified an appropriate next step beyond their supervisor.

Rubric on observable behavior: Was the request restated neutrally? Was writing requested? Was time taken rather than answering immediately? Was an alternative offered? Was the refusal free of character judgment? Did the student ultimately comply?

That final criterion is the one that matters and the one no written assignment can measure. A student can write a flawless analysis of why the request is improper and still say yes when someone asks them at 5:40.

The program-level case

Ethics is an accreditation expectation with the weakest assessment in the building. Nearly every program is required to address ethics, and nearly every program measures it through reflection papers, self-report surveys, or embedded exam questions — instruments that measure whether students can identify the right answer, which was never in doubt.

A behavioral measure closes exactly that gap. Whether a student, under pressure, restated the ask and declined is a direct observation of the outcome the curriculum claims to produce. For AACSB assurance of learning on ethical reasoning, that is a categorically better artifact than anything currently in use — and it's the strongest assurance-of-learning argument in this entire catalog.

It integrates cleanly. The same scenario serves a business ethics course, an accounting or finance course where the specific violation lives, and a compliance or law module.

The corporate market is large and unserved by anything effective. Organizations spend heavily on compliance training that everyone acknowledges changes no behavior. Something that rehearses refusal is a different product in a market that knows its current one doesn't work.

The short version

Business ethics simulation matters because the failure in ethics education isn't analytical. Students know that backdating a shipment is wrong. They have never once had to say so to someone whose approval they need, in under a minute, with no time to consult anyone.

Whistleblower training and hotline awareness address the last resort. The far more common and more winnable moment is thirty seconds earlier, at a desk, when someone asks for something they shouldn't and the response is: "Let me make sure I understand what you're asking — can you send me that in an email?"

That sentence stops more misconduct than any policy manual. It just has to be available under pressure, and it only gets there by being practiced.

Foretell AI lets faculty build conversational simulations — including ethical pressure scenarios like the one above — with configurable counterparties, transcripts, recordings, and rubric-based evaluation. If you're strengthening ethics assessment or mapping outcomes to assurance-of-learning goals, we're happy to walk through how other programs have structured it.