TL;DR
If every event feels urgent, you are not behind. You are under-sorted.
This is the shift. Stop asking, "What's the priority?" Start asking, "What tier is this, and what does it require?"
That is how an event planner becomes a Portfolio Manager.
This guide gives you the sorting logic. Use it to tier events fast, then fix the mismatch that hurts most.
The 60-second tier test
Do not start with budget. Do not start with importance. Start with complexity and lead time.
Use this test to pick a tier:
- Tier 1 — 500+ attendees, cross-functional delivery, or 8+ months lead time.
- Tier 2 — 100 to 500 attendees, 6 months lead time, or one owner plus support.
- Tier 3 — under 100 attendees, 4 months lead time, or 1 to 2 people with templates.
- Tier 4 — internal, repeatable, or under 2 months lead time.
Key Insight: If you are between tiers, pick the higher one. It is easier to scale down than catch up.
Add two modifiers (this is where teams get burned)
Most tiering fails because teams skip modifiers.
Modifier 1: Hybrid bumps complexity
Hybrid adds coordination, tech, and rehearsal time. If you are on the fence, bump it up a tier.
Rule of thumb: Hybrid adds about 20% hours.
Modifier 2: Net-new costs more than repeatable
A first-time event always takes longer. Even in the same tier.
Rule of thumb: Net-new adds effort on top of the tier baseline. A repeatable roadshow stop is not the same as a one-off VIP dinner with custom work.
Tier benchmarks (use these until you have your own data)
You do not need perfect numbers to start. You need defensible numbers.
| Tier | Lead time | Est. hours | Typical team |
|---|---|---|---|
| Tier 1 | 8+ months | 400 to 800+ | 4 to 8 people |
| Tier 2 | 6 months | 100 to 200 | 2 to 4 people |
| Tier 3 | 4 months | 30 to 60 | 1 to 2 people |
| Tier 4 | 2 months | 5 to 15 | 1 person |
These ranges are editorial estimates for planning, not product defaults. Replace them after your team has at least three comparable events of its own data.
The part nobody does: mismatch detection
Tiering is not the finish line. It is the flashlight.
Once you have assigned tiers, look for these mismatches.
Insufficient lead time
Tier 1 under 8 months is a risk. Tier 2 under 6 months is a risk.
Fix: Move the date, reduce scope, or add support.
Overinvestment
If a Tier 3 or Tier 4 is getting Tier 1 effort, you are leaking capacity.
Fix: Build a playbook and lock approvals. One team cut webinar hours in half by templating decks and reducing approvals.
Underinvestment
If a Tier 1 or Tier 2 is staffed like a Tier 3, the team will pay for it later.
Fix: Add support, extend the timeline, or reduce scope.
Tier collisions
Multiple Tier 1 events in one quarter is not ambitious. It is math.
Fix: Spread flagships across quarters or downgrade scope. Lock deliverables so "one extra thing" does not become 40 extra hours.
Key Insight: Tiering stops over-investing before it becomes burnout.
Do it now (10 minutes)
- List your events for the next 12 months.
- Run the 60-second tier test on each.
- Add modifiers (hybrid, net-new).
- Flag mismatches (lead time, overinvestment, underinvestment, collisions).
- Choose one fix this week.
That last step is the shift. Portfolio Managers make tradeoffs.
Use these tiers in your event portfolio analysis, then compare events with Portfolio Yield to decide which work earns the team's hours.
Key Insight: The goal is not perfect tiers. The goal is clear tradeoffs.
How to talk about this
When you say, "I need more time," your boss hears, "You are behind."
When you say, "We have 27 events across four tiers. Our Tier 1 is short 200 hours," your boss hears, "You have a strategy."
| Instead of... | Try... |
|---|---|
| "We have too many events." | "We are short 200 Tier 1 hours. We need to reallocate or cut." |
| "This takes a lot of work." | "This is Tier 2. It needs 120 hours. We have 80." |
| "I need more lead time." | "Tier 1 needs 8 months. We have 5. That is a capacity risk." |
Key Insight: "We are not just planning events. We are allocating resources across a portfolio."
Frequently Asked Questions
How do event tiers help forecast staffing needs?
Start with the tier's estimated hours and typical team size, then adjust for format, lead time, and net-new work. These are editorial estimates, not product defaults. Use Capacity Lite to spot collisions across the portfolio. Replace the ranges after your team has at least three comparable events of its own data.
Should I tier by budget or complexity?
Always tier by complexity. A simple $100K event might be Tier 3. A complex $20K event might be Tier 1. Budget is one input. Complexity drives resource needs.
What if I am between two tiers?
Pick the higher tier. It is easier to scale down than catch up.
What if my boss treats everything as Tier 1?
Show them the math. Say, We have 27 events. If they are all Tier 1 at 800 hours each, that is 21,600 hours. Our team has 8,000. Which ones do you want to protect?'
The bottom line
An under-sorted year makes it hard to defend the work or the hours it needs. Event tiers give each request an effort estimate you can discuss with the team.
Tier the work. Identify one mismatch. Run Capacity Lite to see which team hours collide, then choose what to shift, support, or reduce this week.
Want the tool to do the sorting for you?
The Tier Tool suggests tiers from your inputs, estimates hours with modifiers, flags risks, and exports a portfolio view you can share.
Tier my portfolio in 10 minutes