How Expert Networks Handle Recusal When a Consultant Becomes Conflicted Mid-Engagement

Most compliance writing about expert networks focuses on the two ends of the engagement: the pre-call screen and the post-call artifact. The middle is where the real operational risk sits. When an already-onboarded expert takes a new job, joins a board, gets added to a deal insider list, or picks up a consulting client that overlaps with a live buy-side project, the network and the client have to decide, often within hours, whether the expert exits, is quarantined, or is replaced.

The workflow is more standardized than the industry lets on. Below is how the mid-engagement recusal process actually runs at the major networks, anchored to the regulatory record that shaped it.

The Attestation Refresh That Catches Most Conflicts Early

The first line of defense is not a compliance officer, it is the expert. Networks including GLG, Guidepoint, and AlphaSights re-prompt every consultant to reaffirm their compliance profile before each call, and on a rolling cadence of roughly 6 to 12 months regardless of call volume. The attestation asks about current employer, board seats, advisory roles, consulting clients, and any recent additions to insider lists.

A changed answer is the trigger. If an expert who was cleared six months ago as an independent consultant now lists a public-company employer, the profile auto-flags before the next call is scheduled. The language of these attestations traces back to the settlements that followed the 2006 rulemaking cycle around adviser compliance, and to the FINRA guidance on expert consultations codified in Notice 10-22.

The rolling cadence matters because most mid-project conflicts are not dramatic. They are quiet: an expert takes a fractional advisory role, joins a nonprofit board that overlaps with a client's portfolio company, or signs a consulting agreement with a competitor. Without a scheduled re-attestation, these changes reach the buy-side client on a call, not in a ticket.

Mid-Project Employer Changes: The Highest-Risk Vector

When an expert joins a public company or a client's competitor while a project is live, the standard response is to freeze the profile and notify the buy-side client the same day. The freeze prevents any further scheduling firm-wide, not just for the affected project.

This workflow exists because the regulatory record is explicit about the risk. The SEC's 2011 enforcement action against Primary Global Research centered on consultants who were also employees of public technology companies and passed non-public information to hedge fund clients. Undisclosed employer changes at consulting experts were the mechanism. Every major network's mid-engagement workflow is built to prevent that specific fact pattern from recurring: an expert whose day job changes without the network or the client knowing.

The operational consequence for the buy-side client is a same-day notification and, in most cases, a decision within one business day about whether the expert can be re-cleared under the new employer (usually no, if the employer is public and in-sector) or must be replaced.

Insider-List Additions and Self-Recusal

When an expert is added to a deal insider list, as an advisor, a banker, a consultant on a live transaction, or a diligence resource, the expert is required to self-recuse from any adjacent engagements. This is the one workflow that depends most heavily on the expert doing the right thing without being prompted.

Networks including Third Bridge and Dialectica route these events through a compliance ticket that suspends the expert's profile firm-wide until the transaction closes or the insider status lapses. The suspension is not sector-specific: a healthcare expert added to a healthcare deal insider list is suspended across all sectors, because the network cannot easily verify that the deal in question is unrelated to a given call topic.

The practical effect is that experts with active M&A advisory practices cycle in and out of the panel constantly. Networks price this in by maintaining larger panels than any single client would ever need.

Client-Side Conflict Discovery

The conflict does not always come from the expert's side. Buy-side firms update their own restricted lists constantly, when a new position is opened, when a deal enters diligence, when a compliance officer flags a name. An expert who was cleared against the client's restricted list on Monday may be conflicted against the updated list on Thursday.

Most networks support a re-screen against the client's updated restricted list on request, typically within the same project window. The re-screen is a mechanical database match, not a judgment call, and it runs against every expert already scheduled or in flight for the client. Experts who fail the re-screen are pulled from the project and, if a call has already occurred, escalated into the retroactive workflow below.

The buy-side firm's compliance team owns this process. The network runs the match; the client decides what to do with the results.

Retroactive Recusal and Call Quarantine

The hardest case is when the conflict is discovered after the call has already happened. The expert took a new job the week after the call. The expert was added to an insider list the day after. The client's restricted list changed and the expert should never have been cleared.

Networks including Coleman and Capvision have documented processes to quarantine the transcript, notify the client's compliance function, and in some cases destroy notes and recordings held by the network. The quarantine is not a soft flag: the transcript is removed from the client's access, the moderator's notes are pulled, and any downstream artifacts (summaries, follow-up questions, ratings) are held pending compliance review.

This maps directly to the buy-side firm's own MNPI containment protocols. The SEC's 2020 guidance on adviser compliance programs reinforced that investment advisers must have documented processes for handling suspected MNPI, including material that arrives through third-party research channels. A retroactive recusal is one of the few moments when the network's compliance record and the client's compliance record have to line up exactly.

Substitute-Expert Workflows

When recusal happens mid-project, the client still needs the answer to the question they were paying for. Networks re-source a replacement expert from the same panel, usually at no incremental fee if the replacement lands within a defined window, often two to four weeks from the original engagement start.

ProSapient and NewtonX market this as a project-level service commitment: the client pays for a research outcome, not for a specific expert, and the network absorbs the cost of the swap. Larger networks like GLG and Guidepoint handle it less formally but with the same underlying economics, because a project abandoned mid-flight is a worse outcome for the network than a substitute call at cost.

The substitute is sourced against the same original brief, re-screened against the client's current restricted list (which by definition is now different from the original screen), and re-attested by the expert before the call is booked. In effect, the mid-project recusal restarts the entire pre-call compliance sequence for a new person.

The Recusal Event as an Audit Artifact

The last piece of the workflow is documentation. The recusal event itself, the trigger, the timestamp, the client notification, the disposition, is stored in the network's compliance record and, increasingly, delivered to the buy-side client as part of the project file.

This is being driven by the client, not the network. Under Rule 206(4)-7, investment advisers must adopt and maintain written compliance policies reasonably designed to prevent violations of securities laws. For firms that rely on expert networks as a research input, the recusal record is the evidence that the compliance program actually functions when tested. In an SEC exam, the question is not whether an expert was ever conflicted, it is whether the firm's process caught the conflict and responded appropriately. The recusal artifact is the answer.

The artifact typically includes the date of the trigger, the nature of the conflict (employer change, insider-list addition, client restricted-list update, self-disclosed), the actions taken (profile freeze, call cancellation, transcript quarantine, substitute sourcing), and the client-side acknowledgment. Buy-side firms with mature compliance functions request this record proactively; less mature firms find out they need it during an exam.