TL;DR
A full room can still be a weak use of the year. A small event can still earn scarce team time. The decision gets clearer when you compare what each event influenced with the capacity it used.
What does it mean for an event to earn its place?
Portfolio Yield is pipeline generated per capacity hour across the event portfolio. That’s the canonical definition.
It doesn’t create a universal pass or fail score. It gives leaders one comparable lens for events competing for the same people. The Event Intelligence Glossary keeps this definition separate from True ROI and attendance.
Why are attendance and ROI not enough?
Attendance shows reach. True ROI compares pipeline influenced with fully-loaded cost. Portfolio Yield answers a different question: which events make the best use of scarce team capacity?
Key Insight: Here’s the take most event ROI posts won’t make: an event can look successful and still be the wrong trade-off for the portfolio.
If the financial lens is the open question, use the True ROI guide. Don’t force one measure to answer both decisions.
How do you compare unlike events?
Compare the evidence on the same terms before you compare the result.
- Attribution — Use one rule for how pipeline is credited.
- Capacity — Use one governed method for capacity hours.
- Time — Keep the decision period consistent.
- Confidence — Label inputs as synced, estimated, or not connected.
Tiers still matter because a flagship and a roadshow ask different things from the team. The event tiering guide helps make that effort context visible without inventing a benchmark.
What do Cvent, Bizzabo, Salesforce, and Float each miss?
They aren’t wrong. They’re answering separate parts of the decision. Cvent and Bizzabo run the event. Salesforce holds opportunity evidence. Float helps plan team workload. A spreadsheet can stitch those exports together, but someone still has to govern the comparison.
The missing layer is the portfolio trade-off between capacity and impact. That’s the category question behind Event Portfolio Intelligence.
How should you use the Yield Card?
Use the free Yield Card as a directional comparison, not as the canonical Portfolio Yield calculation. It ranks events using pipeline per attendee and can add pipeline per direct-spend dollar when you provide spend.
That view can expose a useful event pair to investigate. Before you protect or cut anything, add governed capacity hours and check the attribution source. Increased evidence creates a better decision, not a louder score.
Which decision follows the comparison?
Name the trade-off for one event. Don’t end with a ranking.
- Protect — Keep the event’s capacity when the evidence supports its role.
- Redesign — Change the audience, format, scope, or proof model before repeating it.
- Shift — Move timing or capacity when the event earns investment but collides with stronger work.
- Stop — Remove the event when the evidence and strategic role don’t support another cycle.
If timing is the real constraint, use Absorb, Swap, or Shift to take the trade-off to leadership. If the capacity model itself is missing, the 2P Audit is the separate path.
Frequently Asked Questions
What is Portfolio Yield?
Portfolio Yield is pipeline generated per capacity hour across the event portfolio. It's the portfolio north star for comparing event mix and scarce team investment.
What is the formula for Portfolio Yield?
Build the Year defines Portfolio Yield as Pipeline divided by Capacity Hours. Use one attribution policy and one governed capacity-hour method across the comparison.
How do you know which events are earning their place?
Compare events under the same attribution policy, capacity-hour method, time period, and Data Confidence labels. The relative result helps you decide what to protect, redesign, shift, or stop. There's no universal cutoff.
How is Portfolio Yield different from True ROI?
Portfolio Yield compares pipeline with capacity hours. True ROI compares pipeline influenced with fully-loaded cost. Use Portfolio Yield for event-mix and team-time decisions, and True ROI for the broader financial return lens.
Does Cvent or Bizzabo calculate Portfolio Yield?
Cvent and Bizzabo run events and can support event-level attribution. Portfolio Yield adds the capacity-hour lens across the full event mix, which is a portfolio decision rather than an event-execution report.
Is Portfolio Yield the same as resource planning in Float?
No. Float can help show team workload, while Salesforce can hold pipeline evidence. Portfolio Yield connects those two sides so the event team can compare business value with the capacity used to create it.
Does the free Yield Card calculate canonical Portfolio Yield?
No. The current Yield Card compares pipeline per attendee and, when provided, pipeline per direct-spend dollar. It doesn't ask for capacity hours, so use it as a directional event-comparison card before adding the canonical capacity-hour lens.
What should I do after comparing event yield?
Check the source, attribution policy, and Data Confidence behind the result. Then name one decision for one event: protect it, redesign it, shift its timing or capacity, or stop it. Recheck the portfolio when the evidence changes.
Which event deserves a closer look?
The free Yield Card compares your events by pipeline per attendee and optional pipeline per direct-spend dollar, then gives you a directional ranking to investigate.
Build the Yield Card