Forum countdown loading Open the fund guide
For sponsors

Make meetings specific

Use the Fund Guide before outreach. Reference plan size, funded ratio, return assumption, asset mix, or expense context instead of opening with a generic pitch.

PreparePersonalize
For trustees

Bring sharper diligence

Use fund profiles to compare assumptions, long-run returns, and expense signals so sponsor conversations stay grounded in public data.

CompareAsk
For administrators

Turn hallway talk into follow-up

Keep notes by plan, provider type, and next step. The best post-forum follow-up starts with a clean record of who asked for what.

CaptureFollow up

Conversation starters

Use before, during, and after the forum
Plan context

What changed since the last filing?

Start with public PRB metrics, then ask what has shifted since the FY2024 reporting window.

Governance

What decision is hardest right now?

Trustees and administrators usually know which topic needs more context: allocation, fees, manager review, policy, or funding.

Provider fit

Where does outside help matter?

Ask where advice, reporting, operations, audit, actuarial, legal, or investment research support would reduce friction.

Follow-up

What would be useful after the event?

Offer a short memo, a data pull, a board-friendly summary, or a focused follow-up call instead of a generic deck.

Meeting plan

A simple prep sequence

  • Pick ten funds you want to understand before the forum.
  • Open each profile and note one data-backed question.
  • Choose one sponsor, peer, or administrator conversation tied to that question.
  • Use the Area Guide to suggest a realistic meeting spot near the Westin.
  • Before leaving San Antonio, convert the conversation into a specific follow-up.
Work lounge at The Westin Riverwalk San Antonio
Forum use case

Good sponsor prep is practical: know the plan, pick the right question, suggest the right place, and make the next step easy.

After the forum

Turn useful conversations into specific follow-up.

The best follow-up does not sound like a blast email. Send the plan name, the issue discussed, the next artifact promised, and one clear date for the next step.