When the Corner Office Asks for a Shortcut: A Compliance Leader's Field Guide to Unreasonable Requests
Photo: business executive tense meeting boardroom professional, via img.freepik.com
Somewhere in every compliance career, the request arrives. It rarely sounds like a demand. More often it arrives dressed in the vocabulary of pragmatism: Get creative. Find a path. Other companies do this. The CEO is not asking you to break the law — at least not in those words. The executive is asking you to make a problem disappear, and the difference between those two requests is precisely where careers and companies are lost.
The uncomfortable truth is that most compliance failures in US regulated industries do not begin with villains. They begin with reasonable people under revenue pressure who treat a compliance objection as a negotiating position rather than a boundary. Understanding that dynamic is the first step in handling it well.
Why the Request Is Rarely the Real Problem
When leadership asks a compliance officer to enable a questionable practice, the immediate issue is the transaction at hand — a billing arrangement, a disclosure timeline, a vendor relationship that would not survive scrutiny. But the deeper problem is what the request signals about the control environment. Regulators reading the record later will not ask whether the compliance officer was polite. They will ask whether the organization's escalation structure functioned when it mattered.
The Department of Justice's evaluation of corporate compliance programs asks exactly this: whether compliance had the authority and the practical standing to say no, and whether saying no changed anything. A compliance officer who documents an objection and is overruled has, in most scenarios, fulfilled a professional duty. A compliance officer who softens the objection to stay agreeable has authored the government's opening exhibit.
Document Before You Discuss
The instinct after a difficult conversation is often to follow up verbally, to keep things informal. Resist it. Written contemporaneous records — a dated memo to file, an email summarizing the discussion, a formal risk memorandum — are the single strongest protection available to both the officer and the enterprise.
Effective documentation shares three characteristics. First, it is neutral in tone; a record that reads as self-justification invites skepticism. Second, it identifies the specific regulatory concern, the affected business units, and the potential exposure in plain terms. Third, it states clearly what was asked, by whom, and what was recommended. A memo that says I was directed to approve invites a fight over characterization. A memo that says I was asked to evaluate X; my assessment was Y; the decision-maker was informed is simply a record.
Escalation Is a Ladder, Not a Leap
Compliance officers sometimes treat escalation as a nuclear option. In practice, it is a graduated process, and moving through it deliberately demonstrates good faith at every rung:
- Written restatement. Confirm the request and your assessment directly to the requesting executive.
- Formal risk memo. Elevate the issue to the general counsel or the compliance committee with a documented recommendation.
- Board-level notice. Where the conduct involves senior leadership, the audit or compliance committee chair is the appropriate recipient — not the full board, and not a leak.
- Independent review. Request that outside counsel assess the question, which both insulates the analysis and creates a privileged record.
- Regulatory self-disclosure. Where the conduct has already occurred, cooperation credit may be the last lever that meaningfully reduces exposure.
Each step should be documented as it happens. The pattern of escalation — not any single act — is what regulators weigh when assessing whether a program was real.
Knowing When the Answer Is the Door
There are situations where escalation cannot cure the problem: when the conduct is ongoing, when the person overriding you controls every escalation channel, or when you are asked to conceal rather than merely tolerate. At that point, resignation is not a failure of loyalty. It is the discharge of a professional obligation, and in many licensing regimes it is a legal one.
A resignation under these circumstances should be in writing, should state the reason in factual terms, and should preserve records lawfully in your possession. Counsel should be engaged before the letter is sent. Officers who resign loudly and litigate publicly often create more exposure for themselves than those who leave with a clean, documented record and let the paper speak.
What Regulators Expect to See
When this moment eventually lands on the record — and in industries under supervision, it usually does — enforcement staff look for a consistent story: contemporaneous documentation, escalation that followed the org chart, and a compliance function that neither obstructed nor accommodated. Companies that can produce that record frequently resolve matters without charges. Companies that cannot often discover that the workaround cost far more than the revenue it protected.
The dilemma is real, but it is navigable. The officers who survive it are not the ones who win the argument. They are the ones who made sure the argument happened on paper.
