At a major sell-side conference, 800 investors might submit 12,000 meeting requests across 150 issuers — and the allocation engine has to assign every meeting in a way that’s fair, value-maximizing, and operationally feasible. This guide opens up the black box of conference allocation, explaining how the math works and what shapes the outcome.
The Allocation Problem in Numbers
A typical mid-size sell-side conference has 150 issuers × 12-18 meeting slots per issuer = roughly 2,000 meeting capacity slots. Against that supply, 800-1,200 investors submit an average of 10-15 ranked requests = 10,000-15,000 demand requests. The allocation engine must match demand to supply under multiple constraints.
Step 1: Request Scoring
Each meeting request gets scored on three dimensions. Investor tier — typically 4-6 tiers based on AUM, commission relationship, and historical conference engagement. Request rank — investors rank their requests; top-ranked requests get higher weight. Mandate fit — fund strategy match to issuer (long-only large-cap funds favored for large-cap issuers).
Step 2: Issuer Slot Capacity
Each issuer commits to a meeting count (typically 12-18 1-on-1s plus 1-2 group meetings). The engine respects that capacity strictly — overbooking is the single biggest source of conference dissatisfaction. WeConvene’s allocator caps slots at confirmed availability with no upward flex.
Step 3: Fairness Constraints
Pure score-maximization would assign every Tier 1 investor their top 10 requests, leaving Tier 3 with nothing. Fairness constraints prevent that. Typical constraints: every registered investor gets at least 3 meetings, every Tier 1 investor gets at least 8 meetings, no single investor exceeds 25 meetings. The engine optimizes within those guardrails.
Step 4: Conflict Resolution
Some meeting slots have natural conflicts — same time, same investor on two issuer schedules. The engine resolves conflicts iteratively: assign highest-score conflict-free meetings first, then resolve conflicts by demoting lower-score requests and re-running. Most engines converge in 3-5 passes.
Step 5: Post-Allocation Review
Final allocations get reviewed by sell-side corporate access leads before publication. Manual overrides handle edge cases: a Tier 1 account in a dispute might get a courtesy meeting; a key issuer might request specific investor attendance. WeConvene’s override workflow logs every manual adjustment for audit trail.
Why Allocation Quality Drives Conference Reputation
Investors and issuers both grade conferences on allocation fairness. Conferences with reputation for ‘rigged’ or opaque allocation lose Tier 1 attendance over time. The best sell-side teams publish allocation methodology, share post-conference allocation analytics, and invest in transparent engine logic.
Frequently Asked Questions
How are 1-on-1 meetings allocated at sell-side investor conferences?
Allocation engines score each meeting request on investor tier, request rank, and mandate fit, then match requests to issuer availability under fairness constraints — typically converging in 3-5 optimization passes.
Why do some investors get more meetings than others at the same conference?
Higher-tier investors (larger AUM, deeper relationship, higher historical engagement) get priority allocation under most conference fairness rules — but fairness constraints ensure every registered investor receives a minimum meeting count.
How does WeConvene’s allocation engine work?
WeConvene’s allocator scores requests on tier, rank, and mandate fit; respects issuer slot capacity; enforces configurable fairness constraints; resolves conflicts iteratively; and logs all manual overrides for audit.
