How Expert Networks Handle Do-Not-Use Lists: A Field Guide for Buy-Side Compliance

Do-not-use lists are the quiet infrastructure of expert-network compliance. Every serious buy-side firm maintains some version of them, every major network ingests them, and almost no public documentation explains how the two layers meet. The gap matters because a mis-synced exclusion list is the most common path from a routine primary-research call to a conversation with the firm's general counsel.

This field guide walks through the seven structural models that govern how experts get blocked, who maintains each list, and what fails at sourcing time when the plumbing is wrong. It is written for compliance officers, research-operations leads, and buy-side analysts onboarding a new network.

1. Firm-maintained exclusion lists uploaded to the network portal

The most visible layer is the client-side exclusion list. Buy-side compliance teams upload a file (usually keyed by expert ID, work email, or current employer) to the expert network's client portal, and the network's sourcing system filters against it before any profile reaches an analyst. The major networks all offer this intake. AlphaSights, GLG, Guidepoint, and Third Bridge each describe some form of client-controlled exclusion-list ingestion in their published compliance overviews.

The list itself is usually a composite. It carries experts flagged from prior MNPI incidents, individuals who appeared on an insider register under Reg FD or MAR Article 18, names tied to restricted-stock tickers, and people the firm has internally decided not to use for reasons that may never be documented beyond a compliance memo. Ownership typically sits with the compliance team, with research operations as the day-to-day administrator.

The failure mode is version drift. If the uploaded list is refreshed quarterly but the restricted-stock list changes weekly, every gap between uploads is a window in which a blocked expert can clear sourcing. Mature compliance functions push for API-level sync; most buy-side firms still email a spreadsheet.

2. Employer-level restrictions

Title and name blocks catch individuals. Employer blocks catch categories. When a ticker lands on a firm's restricted list, the standard compliance response is to bar any current employee of the named issuer from expert-network sourcing until the position closes or the restriction lifts. The mechanic maps cleanly onto the MAR Article 18 insider-list regime in Europe, which requires issuers and persons acting on their behalf to maintain registers of anyone with access to inside information , see ESMA's market-soundings guidelines for the underlying framing.

At the network, the enforcement runs against the expert's self-reported current employer field. That field is the weak point. Experts update it inconsistently, and someone who left a restricted issuer last month may still appear as a current employee in the network's database, or vice versa. A current employee who hasn't updated their profile will clear an employer-level filter that should have blocked them.

Research-ops teams managing this layer should ask every network how often the employer field is re-verified and whether the exclusion check runs at profile-match time or at scheduling time. The two moments can be weeks apart.

3. Title-level and named-officer restrictions

Some exclusions are not about who the expert is but what seat they hold. Named executive officers, CFOs, general counsel, and other defined-officer roles at public companies carry heightened Reg FD exposure , see the SEC's final rule on Regulation FD for the scope of selective-disclosure concerns. Buy-side firms frequently instruct networks to block any current holder of these titles at covered issuers, regardless of whether the specific individual is on an exclusion list.

The control is usually implemented as a title-plus-employer filter rather than a pure title filter. A "CFO" filter alone would exclude thousands of private-company finance chiefs who present no Reg FD risk at all. The precision depends on how granular the network's title taxonomy is and how reliably experts self-classify. The common failure is a near-miss title , "Deputy CFO" or "Head of Finance" , slipping through a filter calibrated to the exact string "CFO".

4. Expert self-attested exclusions

The fourth model is the one buy-side firms see least directly, because it operates on the expert's side of the network. Many professionals carry employer-imposed restrictions on who they can take calls from and what they can discuss. Big Four audit staff operate under PCAOB independence rules that bar engagement on audit clients. Current consultants at McKinsey, Bain, or BCG sign non-disclosure obligations covering recent client work. Lawyers at firms with investment-bank clients face conflicts rules that pre-block certain discussions.

Expert networks capture these restrictions at onboarding and re-verify them periodically. When an analyst requests an expert, the network's compliance layer checks the expert's declared employer policy against the client's identity and the project's subject matter, and will block the match before the analyst ever sees the profile. The buy-side client often never knows a specific expert was excluded; the expert simply does not appear in the results.

This model is the one most likely to be invisible to the client, which is both a feature (the exclusion is enforced regardless of what the client requests) and a limitation (the client cannot audit what they cannot see).

5. Network-wide blacklists

Separate from any client-specific list, the networks maintain their own terminations. Experts who have failed compliance training, violated call restrictions, or been subject to enforcement action are removed from the panel entirely. The practice traces to the enforcement wave that followed SEC v. Primary Global Research, the 2011 action in which the SEC charged a California-based expert-network firm and several of its consultants with insider-trading schemes involving MNPI passed to hedge-fund clients.

That case, together with the related prosecutions of the same period, established the baseline that networks are responsible for policing their own panels. The major networks' published compliance overviews now describe some form of mandatory expert training, call-attestation requirements, and termination procedures for violations. GLG's compliance page and AlphaSights' compliance page both describe layered controls of this type.

Network-wide blacklists are the one list a client cannot upload to, override, or inspect. For buy-side diligence on a new network, the right question is not whether the blacklist exists , it does , but what the termination criteria are and how often they are applied.

6. Cooling-off and garden-leave windows

A significant share of DNU status is time-boxed rather than permanent. An expert who recently left a restricted issuer, a former sell-side analyst inside a research-rules cooling-off period, or a public-company officer in a garden-leave window all carry temporary exclusions, typically running six to twenty-four months from the triggering event.

The operational challenge is that time-boxed exclusions require the list to age correctly. An expert blocked today should become eligible on a specific future date, and the network's filter must respect both the start and the end of the window. Static exclusion files loaded as flat lists do not handle this well. Firms with mature controls either push a dated exclusion with an expiry field or re-upload the full list on a schedule tight enough that the lag is immaterial.

The failure mode here is the opposite of the version-drift problem in model one: experts stay blocked long after they should have cleared, which is less dangerous legally but a real cost to the research workflow and a persistent source of friction between compliance and research teams.

7. Cross-fund and cross-strategy propagation

The seventh model is organizational rather than technical. Large asset managers run multiple funds and strategies under one umbrella , a long-short equity book, a private-credit sleeve, a systematic strategy, a venture arm. Restricted lists and expert exclusions generated by one strategy frequently need to propagate to the others, because MNPI reaching any arm of the manager can taint trading across all of them.

The propagation is rarely automatic. Each fund often maintains its own portal relationship with each network, uploads its own exclusion list, and relies on a central compliance function to reconcile them. When a new sibling fund is launched, or when a manager adopts a new strategy that uses the same networks, the exclusion-list architecture has to be rebuilt rather than inherited.

This is the model where buy-side onboarding of a new network most often falls short in practice. The first fund gets a clean exclusion-list integration; the second gets a copy of the first fund's file; the third gets whatever the research-ops team can assemble on a deadline.