7 Ways Buy-Side Firms Structure Expert-Network Usage Reporting to Compliance

Pre-call vetting gets most of the attention in expert-network compliance conversations. The reporting layer that sits behind it, the periodic exports and dashboards that compliance officers actually read to monitor exposure across a book, gets almost none. This guide maps seven concrete structures buy-side firms use to shape that reporting, drawn from workflows at networks including GLG, Guidepoint, AlphaSights, Third Bridge, Dialectica, and Coleman. It is written for compliance leads, heads of research operations, and vendor-selection teams who need to know what a defensible usage-monitoring stack looks like under SEC Rule 206(4)-7 and FINRA Rule 3110.

1. Per-analyst call volume dashboards

The most common reporting shape is the simplest: calls per analyst per month, exported from the network's client portal or pulled via API into an internal compliance tool. Guidepoint exposes this natively through its compliance portal, and GLG offers equivalent exports through its compliance program. A CSV drop into a compliance data lake, refreshed monthly, is the baseline configuration at most mid-sized hedge funds.

The useful version of this report is not the raw count. It is the count flagged against an internal threshold. Firms commonly set a soft trigger somewhere in the range of 20 calls per analyst per month, above which the compliance team pulls the transcripts for spot review. The threshold itself is arbitrary. What matters is that it exists, that it is documented in the compliance manual, and that exceptions are logged. A supervisory record that shows the threshold, the exceptions, and the review outcomes is what Rule 3110 supervision expectations are pointing at.

2. Expert-repeat-usage flags

The second reporting shape surfaces a pattern that is invisible in per-analyst totals: the same expert used repeatedly by the same analyst inside a short window. A common configuration flags any expert consulted more than three times by the same analyst inside a rolling 90-day window.

The reason this pattern is worth surfacing is historical. Enforcement actions in the 2013 era around Level Global and the broader SAC-adjacent expert-network cases (see the SEC press release on the related settlement) cited proximity-to-source dynamics as a risk marker: an analyst who develops a repeat relationship with a single expert inside a covered company is closer to that company's information flow than the vetting record on any individual call would suggest. A reporting shape that surfaces the pattern, not just the individual calls, is what allows compliance to see relationship formation rather than isolated events.

3. Ticker-adjacency reporting

The third shape breaks usage down by security ticker or covered issuer and cross-references it against the firm's restricted list. AlphaSights and Third Bridge both support ticker-tagging on engagements, which lets a compliance officer filter the monthly report to show every call whose subject matter touched a restricted ticker in the window when it was restricted.

This report is the one that catches the specific failure mode compliance is most nervous about: a call that was correctly vetted at the time of booking, on a name that was subsequently added to the restricted list before the call took place. Without ticker tagging on the engagement record, that gap is invisible in the monthly export. With it, the exception surfaces as a single line and can be reviewed against the transcript.

What ticker tagging typically captures

• Primary covered issuer discussed on the call
• Adjacent tickers named in the transcript (competitors, suppliers, customers)
• Sector tag for broader thematic filtering

4. Employer-of-expert lookback

The fourth reporting shape addresses the insider-trading lookback problem. Firms maintain internal policies that restrict engagement with experts who are current employees of covered companies, and typically extend that restriction for 6 or 12 months after departure. The reporting shape that supports this policy is a monthly export showing, for each expert consulted in the window, their current employer and their prior employer inside the lookback period.

The operational question this report answers is whether the employer information the expert provided at vetting still matches the employer information on file today. Experts change jobs. A vetting record from January that cleared an expert as an ex-employee of a covered company two years out is a different risk profile from the same expert in June if they have since rejoined that company as a consultant. A lookback report that refreshes employer data at the point of the periodic review, not just at the point of vetting, is the version that actually monitors the exposure.

5. Compliance-question attestation logs

Before most calls, expert networks put the expert through a standardized set of pre-call questions: are you subject to confidentiality obligations relating to the topic, are you a current employee of the company being discussed, have you signed an NDA that would cover this material, and so on. The answers are captured as structured Y/N fields on the engagement record.

The reporting shape that matters here is the aggregate: how many experts in the period declined to attest to a given question, and which network sourced them. A single decline is not by itself a red flag. A pattern of declines concentrated with one network, or one recruiter inside a network, is a supervisory signal worth escalating. Networks including Dialectica and Coleman surface these attestation fields on the engagement record; the compliance shape is to roll them up rather than review them one call at a time.

6. Chaperoned-call ratio

A chaperoned call is one where a network employee sits on the line and can intervene if the conversation moves toward material non-public information. The sixth reporting shape tracks the ratio of chaperoned to unchaperoned calls, typically broken out by sector.

Sensitive sectors run higher chaperone ratios as a matter of policy. Biotech calls, where a single data point can be MNPI, and semiconductors, where supply-chain color from a fab employee can approach it, are the two sectors most commonly cited by buy-side compliance teams as candidates for a chaperone-by-default rule. The reporting value is comparative: a ratio that drifts down in a sensitive sector over a quarter is the kind of pattern that a monthly review catches and an ad-hoc review does not. Whether that drift is a problem depends on context, which is exactly why the report exists.

7. Spend-vs-approval reconciliation

The seventh shape is the reconciliation report: dollar spend per expert, per network, cross-checked against the internal pre-approval workflow. Every call should have a pre-approval ticket. Every invoice line should map to one. The report surfaces the exceptions.

The failure mode this catches is procedural rather than substantive. A call that happened without a pre-approval ticket, whether because the analyst booked directly through a network relationship or because the ticket was opened after the fact, is a supervision gap regardless of whether the call itself was clean. Under Rule 206(4)-7 the adviser is required to have written policies and procedures reasonably designed to prevent violations, and to review their effectiveness annually. A reconciliation report that surfaces every spend line without a matching ticket is the evidence base for that annual review.

What the reconciliation typically compares

• Invoice line items from each expert network
• Pre-approval tickets from the internal workflow tool
• Analyst names, dates, and expert IDs across both systems