How Buy-Side Compliance Teams Pre-Clear Expert-Network Experts Against Restricted Lists

Every expert-network call at a hedge fund, mutual fund, or private equity firm starts with the same gate: a proposed expert's name and employment history have to clear the firm's restricted, watch, and grey lists before a call can be booked. The workflow looks routine from the outside and is genuinely intricate underneath, spanning list architecture, matching logic, data sources, and audit retention. This guide walks through how buy-side compliance teams actually structure that pre-clearance layer, and where it tends to break.

What Sits on the Restricted, Watch, and Grey Lists

The three lists that gate an expert-network booking are distinct instruments with different owners, different update cadences, and different consequences when a match fires.

The restricted list is compliance's live record of issuers where the firm holds material non-public information, has an active trading restriction, or is otherwise walled off from transacting. It is maintained under Advisers Act policies and procedures that flow from Rule 204A-1 and is typically updated intraday as deals, board seats, and information barriers change. A match against the restricted list is a hard stop for a proposed expert call, not a flag for review.

The watch list is internal and confidential to compliance. It tracks issuers under active diligence where the firm has not yet crossed into MNPI but wants heightened surveillance on employee activity, including expert-network calls. An analyst requesting an expert with watch-list exposure usually never learns the list exists; compliance sees the flag and routes the request accordingly.

The grey list is the multi-strategy platform artifact. At firms structured like Citadel or Balyasny, where pods trade independently and information barriers separate strategies, the grey list captures issuers with heightened conflict risk from banking relationships, activist positions, a private-side investment, or a sibling pod's exposure. Grey-list matches typically trigger chaperoning or a documented rationale rather than an outright block.

Critically, expert-network pre-clearance is a separate control from trade pre-clearance. A firm can be free to trade an issuer while its analysts remain restricted from calling former employees, and vice versa. Conflating the two is a common early-stage mistake at newer funds.

The Three Matching Approaches

Once the lists are in place, the compliance question becomes: what does it mean for an expert to "match" the list? Three approaches are in common use, and most mature firms layer all three.

Exact-name match compares the proposed expert's current employer against the list. It is fast, cheap, and the weakest of the three. It misses experts who left a restricted issuer six months ago, sit on the issuer's board while employed elsewhere, or consult for the issuer through a personal LLC.

Employer-history match runs the expert's disclosed employment history against the list over a lookback window. Hedge funds typically set the window at 6, 12, or 24 months depending on the sector and the information sensitivity. Private equity diligence teams often extend the lookback to 3 to 5 years, on the view that a former operator retains commercially sensitive knowledge far longer than a former junior employee. The lookback is a policy choice with real trade-offs: a longer window catches more risk and eliminates more experts from the addressable pool.

Beneficial-affiliation match is the most demanding. It screens board seats, advisory roles, equity holdings, and consulting engagements against the list. The data typically comes from third-party sources such as BoardEx or Equilar, and the match logic has to handle the messy reality that board seats and advisory titles are inconsistently disclosed. This is where automated pre-clearance most often needs a human reviewer.

Where the Data Comes From

The workflow only functions if the expert's profile data is trustworthy. Expert networks such as AlphaSights, GLG, Guidepoint, Third Bridge, and Dialectica push structured profile metadata to buy-side clients through their portals and, for larger accounts, via API. The standard payload includes current employer, tenure, prior employers within the network's own lookback, and self-disclosed affiliations.

Many buy-side firms enrich this feed. LinkedIn scrapes are common for surfacing employment gaps and undisclosed advisory roles. PitchBook is used for private-company board seats and equity positions that do not appear in public filings. BoardEx and Equilar cover public-company directorships. The enrichment layer is where firms differentiate: two funds using the same expert network can arrive at very different clearance outcomes based on how aggressively they augment the base profile.

The integrity of the workflow ultimately rests on the expert's own disclosure. Every mature compliance function assumes some rate of underdisclosure, particularly around consulting arrangements and small private-company advisory roles, and calibrates its review depth accordingly.

The Four Common Workflow Structures

How the pre-clearance actually runs depends on the firm's size, strategy, and risk tolerance. Four structures dominate.

Analyst self-attestation is the lightest touch. The analyst reviews the expert profile in the network's portal, attests that no restricted-list conflict exists, and books the call. Compliance sees the attestation record but does not touch the profile pre-booking. This model is common at smaller long/short funds where the analyst carries direct compliance accountability and the volume does not justify a dedicated reviewer.

Portal-integrated auto-block connects the expert network directly to the firm's restricted list via SFTP or API. Blocked experts simply never surface in the analyst's search results. Guidepoint and AlphaSights both offer this integration to enterprise clients. The benefit is that a restricted match becomes invisible to the analyst, which reduces information leakage about what is on the list. The trade-off is that the firm must trust the network's matching logic, which is typically limited to exact-name and employer-history checks.

Compliance-reviewed pre-booking puts every proposed expert through a manual compliance queue before the call is confirmed. Service-level agreements typically run 2 to 4 business hours, longer for cross-border experts or profiles requiring enrichment. This is the standard at large mutual funds and event-driven hedge funds where the cost of a missed restricted match materially exceeds the friction of the review.

Tiered workflows combine the above. Self-serve for cleared coverage sectors, compliance-gated for restricted or watch-list-adjacent sectors, and full manual review for anything touching a live deal. This is where most multi-strategy platforms have landed, because it matches the review depth to the risk without imposing uniform friction across the analyst base.

Edge Cases That Break Simple Matching

The four workflows above handle the majority of proposed experts cleanly. The residual cases are where compliance judgment does the work.

A former employee of a restricted issuer whose departure falls just inside the lookback window is the archetypal edge case. Compliance has to decide whether the expert's likely retained knowledge crosses the MNPI line, and often imposes topic restrictions or requires a chaperone rather than blocking outright.

An expert who sits on the board of a restricted issuer's direct competitor raises a mirror-image risk. The expert is not affiliated with the restricted issuer but has ongoing fiduciary exposure to competitive intelligence that could be inferred as MNPI-adjacent in either direction.

Experts flagged for prior MNPI incidents at another network are a persistent challenge because incident data does not cleanly travel between networks. Some firms maintain internal do-not-call lists that survive across their vendor relationships. Cross-network duplicate registration, where the same expert appears under variant names at different networks, complicates enforcement.

Independent consultants whose current client roster is undisclosed are perhaps the hardest category. A consultant may accurately represent that they hold no equity in a restricted issuer while actively advising that issuer under an NDA. The workflow typically handles this through pointed disclosure questions in the profile intake and, at the highest-sensitivity firms, through chaperoning of any consultant whose client roster is not fully visible.

Documentation, Audit, and Retention

Everything the workflow produces has to be retained in a form the SEC examinations staff can reconstruct. Under Rule 204-2, advisers are required to preserve books and records that evidence their compliance program, and expert-network pre-clearance falls squarely inside that perimeter.

The typical retention package includes the cleared profile snapshot as of the clearance timestamp, the restricted-list and watch-list state at that same moment (because both lists change intraday), the analyst's attestation of purpose and topic scope, and any chaperone assignment or topic restriction imposed by the reviewer. Retention runs 5 to 7 years in most policies, longer at firms with heightened enforcement history.

The list-state snapshot is the piece most often mishandled. A call cleared against yesterday's restricted list, reviewed by an examiner against today's list, will look like a miss unless the point-in-time list state was captured at clearance.

Where the Workflow Actually Breaks

Three failure modes recur across firm types.

Same-day booking pressure collides with 2 to 4 hour compliance SLAs. Analysts working an earnings surprise or a breaking regulatory event push for calls the same afternoon, and the workflow either compresses review time in ways that erode quality or delays the call past its research window. Firms handle this with pre-cleared expert rosters for named coverage areas, which shifts the compliance work upstream but does not eliminate it.

Experts added to the restricted list between clearance and call time create a re-clearance obligation that many workflows handle poorly. A profile cleared Monday morning for a Thursday call may need to be re-cleared Thursday morning if the issuer's status changed midweek. Firms with tight information barriers automate this; firms without automation rely on the analyst to notice.

Cross-network duplicate registration is the quiet failure. The same expert appears at two networks under variant names, is blocked at one, and clears at the other. Firms that use multiple expert networks in parallel, which is now the norm at mid- and large-cap buy-side accounts, have to run their internal do-not-call list against every network's roster, not just against each network's outputs one call at a time.