How to Handle a Question You Cannot Legally Answer on a Live Call

When a question lands that you cannot legally answer, the words you use in the next ten seconds will matter more than anything else you say on the call.

The Short Version

You will get a question you cannot answer. Not might — will. The question might come from a buyside analyst on a GLG call who is fishing for MNPI without knowing that is what they are doing. It might come from a consultant on an AlphaSights project who uses the word "broadly" as if it changes what they are actually asking. It might come mid-call, mid-sentence, or mid-thought.

The right move is not silence, not a long disclaimer, and not a nervous ramble about what you can and cannot discuss. Three words carry most of the weight: "I can't go there." What follows those three words is where the craft lives. This post covers what to say, in what order, and what to do in the twenty-four hours after.

What Is Actually Happening When a Dangerous Question Lands

Not every off-limits question is the same kind of off-limits. Recognising the category in real time is the first skill.

Material non-public information (MNPI) is the most common trap on buyside calls. A question like "what was the pipeline read-out like before it was announced" is obvious. "How were internal teams feeling about the quarter going into the close" is less obvious and equally dangerous.

Confidential employer or client data covers current and former roles. "Can you walk me through what the budget was for that programme" sounds routine. If the programme is from your last employer and the budget was never made public, it is not routine.

Regulatory safe-harbour territory includes anything touching FDA pre-approval discussions, clinical trial data not in the public domain, or antitrust-sensitive market share figures that a competitor's client is asking about.

Network-specific compliance fences vary by network. Tegus, Third Bridge, Dialectica, and others each have their own rules about how recently you can have left a company before that company becomes off-limits as a discussion subject. These rules are not uniform. You are responsible for knowing which apply to you.

Clients ask these questions in good faith more often than you might expect. They are not always trying to extract something improper — they are often just following the thread of what interests them. That does not reduce your liability by one degree.

The Asymmetry You Should Keep in Mind

A clean deflection costs you roughly thirty seconds and signals professional competence. A bad answer — or a muddled one — can cost you your standing on the network, your employer's trust, or considerably more.

"I don't remember" is not a safe fallback. A sophisticated interviewer on a Guidepoint or Capvision call hears "I don't remember" about a budget you managed six months ago and draws a conclusion. It is worse than a clean refusal because it looks like a refusal dressed up as incompetence.

Career risk and legal risk are different things. Both are real. Both are recoverable if you handle the moment cleanly. Neither is fully recoverable if you handle it badly.

The Protocol, In Order

1. 90-second pre-call scan
   Before you dial in, read the brief for flagged companies, recent employment, and any regulatory context. Surface danger zones before they surface you.
2. Buy three seconds
   When the question lands, use a bridging phrase: "Let me make sure I'm addressing the right part of that." It is not evasive — it is what careful thinkers do.
3. Identify the category
   MNPI, employer-confidential, regulatory, or network fence. The category determines the formulation.
4. Deploy the deflection
   Use the correct formulation for the category — see below.
5. Redirect to value
   Immediately pivot to what you can offer. The client should leave with something useful.
6. Document within the hour
   One paragraph to yourself, timestamped, noting what was asked and what you said.

For MNPI and employer-confidential questions: "That touches on information I'm not in a position to share — here's what I can offer instead." Then offer it. Do not leave a silence.

For regulatory safe-harbour territory: "I'd want to keep us on the right side of FDA guidance here — let me reframe what I can speak to." Then reframe.

For network compliance fences: "My compliance requirements restrict me on that specific company — happy to discuss the dynamic more broadly." Inex One, Prosapient, and Coleman all have variations on these rules; the language above works across all of them.

For genuinely ambiguous questions where you are unsure: It is acceptable to say "I want to give you the most useful answer I can — let me take thirty seconds." Most networks have a live compliance line. Use it. Clients who are doing legitimate research will wait.

If you were already mid-answer when you caught it: "Actually, I want to pull back on that — I'm moving into territory I should keep off the table. What I can say is..." Walking back cleanly is not incompetence. It is exactly what a professional does.

Same-day written reporting to the network is the standard. Waiting makes it look like deliberation. The point is to establish that you flagged it, not to escalate unnecessarily.

Reviewing how different networks handle compliance disputes, understanding how honorarium rates relate to call risk, comparing network-specific compliance policies, learning how to pass compliance screening without unpaid preparation work, and tracking income from multiple networks for tax purposes are all topics worth understanding before you find yourself in a difficult moment rather than after.

If I deflect a question, will the client mark me down on quality?

Most clients doing legitimate research will not. A confident, professional deflection signals domain expertise and compliance sophistication, which is what they are paying for. Clients who push back aggressively after a clean refusal are the ones you should be documenting, not accommodating.

What if the project manager pressures me to answer before the call?

A PM asking you to "just speak broadly" about something that is clearly off-limits is a compliance escalation event, not a negotiation. Decline in writing, reference the network's own compliance policy, and keep the email. Networks with functioning compliance desks will back you. Networks that do not are telling you something important about how they operate.

Does the network's compliance call protect me legally?

No. The compliance screener is designed to protect the network's client and the network's licence to operate. It is not legal advice to you and creates no legal shelter for your statements on the call.

Can I just end the call early if it goes badly off-course?

Yes, and it is sometimes the right decision. If a client is systematically probing for MNPI across multiple questions, ending the call is a legitimate and documentable choice. Most networks allow you to log a compliance-related termination note. Use it. You are still paid for time taken in most cases — though this varies by network.

How quickly should I report a concerning question to the network?

Same day, in writing, through whatever channel the network has published for compliance concerns. Waiting 48 hours makes it look like you deliberated. The goal is to establish that you flagged it promptly.