Senior Event Ownership: design an annual BU portfolio and orchestrate cross-BU events across 2-4 units

An operational guide for senior event coordinators (5-10 years, at least three BU events run independently) who need to make the leap from the single event to the annual portfolio, or from single-BU to cross-BU across 2-4 units. No theory: concrete decision frameworks, real tier-1 cases (Atlassian, GitLab Handbook, Stripe Sessions, HubSpot INBOUND), anti-patterns I've seen cost last-minute cancellations and six-figure budget overruns.

TL;DR

The leap from mid to senior is not a quantitative increment (more events, more budget): it's a shift in mindset. You move from thinking in "projects" to thinking in "systems" - the annual portfolio is a living system that requires repeatable decision frameworks (go/no-go, prioritization, vendor substitution) instead of ad-hoc decisions. Project Management Institute research shows that portfolios managed with declared frameworks have success rates of 67% versus 35% for projects managed case by case. This guide proposes a three-tier framework: (1) designing the annual BU portfolio with a mix of event types (4 canonical archetypes), budget allocation and capacity planning for the events team; (2) a go/no-go framework built on five quantitative criteria that make the difference between "we'll decide it in the steering committee" and "we have an objective trigger"; (3) cross-BU orchestration across 2-4 units with symmetric governance (alternating co-chairs, narrative statement, exit strategy). You'll find four deep-dive case studies with public tier-1 sources: Atlassian Team Playbook (internal portfolio), GitLab Handbook (radically transparent cross-functional events), Stripe Sessions (B2B brand event), HubSpot INBOUND (scale-up educational program). Three frequent senior anti-patterns: inflated portfolio (10+ events with no capacity), vendor lock-in (a single strategic supplier), orphan events (the executive sponsor has resigned). If you're already senior and managing a portfolio, jump straight to the Operational steps + Anti-patterns sections. If you're a mid ready for the leap, start from the Conceptual framework.

When you need it / Prerequisites

This guide is written for a very specific profile: the senior event coordinator with 5-10 years of experience who has already run at least three BU events end-to-end and now has (or is about to have) responsibility for something broader than the single event. This typically shows up in two ways.

The first scenario is the annual BU portfolio: you're asked to design and manage the entire events plan for a business unit for the next fiscal year. Typically 5-12 events of varying scale (annual kick-off, quarterly trainings, themed workshops, product summits, team building), aggregate budget of €100-500k, a dedicated events team of 2-4 people plus collaboration with HR/comms/marketing. The real prerequisite is that you already know how to write a 1-pager brief, a cross-functional RACI and a blameless post-mortem - if any one of these three is shaky, start first from the L2-C1 mid event ownership end-to-end cluster.

The second scenario is cross-BU orchestration across 2-4 units: you're asked to lead a shared event across two or more business units with distinct sponsors, split budget and a dual decision topology. Typically it's a product summit involving Engineering + Product + Sales, or an employee event involving Engineering + Design + Marketing. The leap from single-BU is the decision topology: in single-BU there's a single chain of command; in cross-BU the chains are two or more and decisions are negotiated between chains. Without a declared framework, every priority divergence becomes a political crisis.

A cross-cutting prerequisite for both scenarios: you have access (formal or informal) to an executive sponsor who can arbitrate politically when the BUs diverge. Without this anchor, cross-BU orchestration degenerates in the best case into a lowest-common-denominator compromise, in the worst case into a last-minute cancellation (we see this in the Cross-BU without executive sponsorship anti-pattern of the cornerstone guide). If you don't have the executive sponsor, the first operational action is to secure one - not to write the brief.

Minimum active reading time for this guide: 25 minutes if you're at L3 level and reading to apply; 40 minutes if you're at L2 level and reading to grow (with pauses to take notes on the portfolio matrix). The go/no-go framework in the Operational steps section takes 60-90 minutes to actually complete the first time you apply it; it becomes 20 minutes on subsequent iterations.

Conceptual framework: from project to portfolio

The conceptual framework that distinguishes the senior from the mid is the mental transition from the project to the system. It's worth making it explicit because without the transition you end up applying mid-level tools to the annual portfolio - the result: the portfolio turns into a collection of disconnected projects, each with its own RACI, its own brief, its own post-mortem, with no cross-cutting learning.

The framework is made up of three orthogonal dimensions. The first is the portfolio typology: every well-designed annual portfolio includes the four canonical archetypes of corporate event - strategic event (annual kick-off, product summit, vision day; 1-2 per year, high budget, high strategic impact), educational event (technical trainings, workshops, internal certifications; 4-8 per year, medium budget, high operational impact), community event (team building, retreats, quarterly parties; 3-6 per year, medium-low budget, high cultural impact), commercial event (product launch, customer summit, partner day; 1-3 per year, high budget, high revenue impact). A portfolio with only strategic events over-invests in rare events; a portfolio with only community events under-invests in training and revenue. The practical rule: no archetype should dominate more than 50% of the annual budget.

The second dimension is the capacity planning of the events team. It's the most overlooked metric by those who have just become senior: people tend to overestimate the team's capacity because they project their own individual experience ("I ran three events in a quarter, so a team of three people runs nine events in a quarter"). Wrong. The real capacity of a full-time senior event coordinator is 4-6 BU events per year managed end-to-end; of a mid it's 6-8 (smaller, more repetitive); of a junior in support it's 8-12 (only as R, never as A). The aggregate capacity of a three-person team (1 senior + 1 mid + 1 junior) is therefore 14-20 events per year, not 30. Overestimating capacity is the number-one cause of the inflated portfolio (anti-pattern 1).

The third dimension is budget allocation per archetype. The cornerstone's 60/30/10 scheme was designed for the cross-BU budget split of a single event; for the annual BU portfolio the canonical scheme is 50/30/15/5: 50% strategic, 30% educational, 15% community, 5% portfolio-level contingency reserve (separate from the contingency of individual events). The portfolio-level contingency reserve serves to cover unforeseen overruns that no single-event reserve can absorb (e.g. a strategic vendor fails and must be replaced with a premium supplier; an external event changes its date forcing the reschedule of an internal summit; an org-chart change makes an event obsolete and calls for a new one).

The fourth dimension, optional but useful for portfolios above €300k, is geography: distribution of events across in-person, hybrid and remote. The Skift Meetings State of Corporate Events 2024 study reports that the median mix in 2024 across EU/US was 40% in-person, 35% hybrid, 25% remote (compared to 70/15/15 in 2019). The hybrid share grew dramatically because it combines in-person engagement retention with remote scale economy. A well-balanced L3 portfolio includes all three modes - not for fashion, but because each mode covers different audience targets (in-person for new relationships, hybrid for scaling executive comms, remote for technical trainings).

Cross-BU specific: symmetric governance

When the portfolio includes one or more cross-BU events across 2-4 units, the conceptual framework is enriched with a fifth element: symmetric governance. It's the extension of the cornerstone's alternating co-chair concept applied to an entire program instead of a single event. Three practical rules.

First rule: alternating co-chairs across the annual cross-BU portfolio. If two BUs co-organize three events during the year, alternate the lead chair role across editions (BU A is chair on the first event, BU B on the second, BU A on the third). This scheme makes the hierarchy between BUs invisible and produces political symmetry in the long term. The practice comes directly from the GitLab Handbook, the section on planning Commit (the annual event).

Second rule: portfolio-level narrative statement. A one-page document, signed by the sponsors of each BU involved, that declares the mission of the annual cross-BU program and the three shared KPIs. It's not the brief of a single event (that comes later): it's the sense-making framework that guides all the events in the program. A real example: the "Engineering × Product Summit Series 2025" program has the narrative statement This three-year program is co-organized by Engineering and Product to accelerate the go-to-market of complex technical initiatives. Success is measured jointly via (a) number of cross-functional initiatives launched post-event, (b) engineering-product engagement NPS, (c) time-to-decision on priority technical initiatives.

Third rule: program exit strategy. Define in advance (at the start of the year) the conditions that may interrupt the cross-BU program before its planned end. Examples: If the engineering-product NPS drops below 60 for two consecutive editions, we interrupt the program and redesign it; If one of the two sponsors leaves the company, the program is paused for 60 days pending re-sponsorship. Having the exit written down in cold blood makes it much easier to trigger in the heat of the moment.

Operational steps: from the annual portfolio to cross-BU orchestration

The sequence that follows is the operational translation of the conceptual framework. For the annual BU portfolio without cross-BU components you apply steps 1-3; for the portfolio with cross-BU components you add steps 4-5. The sequence is typically run between October and December of year N-1 for the portfolio of year N.

Step 1 - Audit of the current-year portfolio (3-5 days)

Before designing the next year's portfolio, it's essential to run a retrospective audit of the portfolio that just closed. The audit is not the post-mortem of a single event: it's the aggregate reading of all the year's post-mortems, with the goal of identifying cross-cutting patterns instead of one-off lessons. The Atlassian Team Playbook has a specific play called Working Agreements that fits this phase well: every learning from the annual portfolio is turned into an explicit working agreement for the following year (e.g. From January 2026 every event above 200 attendees must have its technology plan B tested in simulation at least 72h before).

The deliverable of step 1 is a 4-6 page document that includes: (a) a summary table of all the year's events with KPI target vs actual; (b) the top 5 cross-cutting lessons learned (things that recurred across multiple events); (c) the top 5 vendors/suppliers evaluated with quantitative scoring (punctuality, delivery quality, responsiveness, cost, re-engageability); (d) the actual capacity of the events team (events actually delivered vs events planned); (e) comparison of actual vs planned budget per archetype.

The most important sub-step is the vendor scorecard. For each strategic vendor (venue, catering, A/V, communications agency, streaming platform) you fill in a scoring across 5 dimensions on a 1-5 scale: punctuality (adherence to contractual deadlines), delivery quality (match between promised and delivered), responsiveness (response time to unforeseen requests), cost (competitive vs benchmark), re-engageability (would you work with them again?). Vendors with an aggregate score below 18/25 should be flagged for substitution in step 2.

Step 2 - Designing the next-year portfolio (5-8 days)

Designing the portfolio is done in three successive steps. First: define the three annual strategic objectives of the commissioning BU (obtained via a brief with the BU's VP/Director; not something the event coordinator can invent). Without the three strategic objectives, the portfolio becomes a list of accumulated internal requests, not an intentional program.

Second step: for each strategic objective, identify the relevant subset of archetypes (strategic/educational/community/commercial) and propose 2-4 candidate events per archetype. You end up with a list of 10-20 candidate events. The deliverable is a portfolio canvas: a table with the three strategic objectives on the rows and the four archetypes on the columns, where each cell lists the candidate events for that intersection.

Third step: apply the capacity criteria (step 1) and the 50/30/15/5 budget allocation to reduce the list of 10-20 candidate events down to the 5-10 actual ones in the portfolio. The cut is excruciating because every candidate event has an internal sponsor who wanted it: this is where you apply the go/no-go framework of step 3 to objectively justify the exclusions.

A sub-step that's often skipped is seasonality planning: distributing the portfolio's events across the annual calendar while respecting the seasonality of the business. January is sales kick-off (high), February-March is Q1 planning (low), April-June is Q1-Q2 execution (medium), July-August is EU holidays (empty), September-November is the Q3-Q4 push (high), December is the Christmas dinner + planning for the following Q1 (low). Concentrating 60% of events into three months (September-November) is a sure recipe for team burnout and sub-standard quality. The practical rule: no month should contain more than 15% of the portfolio's annual budget.

A second sub-step is vendor pre-allocation. After identifying the 5-10 events of the portfolio, you pre-allocate the strategic vendors (venue, A/V, agency, streaming platform) even before writing the individual briefs. This scheme allows you to negotiate annual contracts with volume discounts of 12-18% versus spot contracts, and to secure availability of venues/suppliers for critical dates (which are pre-booked with 10% deposits). The pattern is documented in the GitLab Handbook Events Team section: all strategic vendor contracts are annual, never per single event.

Step 3 - Go/no-go framework for each portfolio event (90 min/event the first time, 20 min on iterations)

The go/no-go framework is the deliverable most typically associated with the senior level. It's a series of five quantitative criteria that every candidate event must pass to enter the year's portfolio. The five criteria are adapted from Atlassian's DACI framework applied to portfolio management.

First criterion (strategic alignment, 1-5 scale): does the event contribute to one of the three annual strategic objectives in a measurable way? Pass threshold: ≥4. A candidate event scoring 1-3 is an orphan event (without a strategic anchor) and should be excluded or re-proposed as an event of a different BU with a different sponsor.

Second criterion (capacity feasibility, 1-5 scale): does the events team have real (not aspirational) capacity to manage this event within the proposed calendar, considering the other events already confirmed? Pass threshold: ≥4. A capacity-feasibility of 1-3 indicates that the event is crammed into an already-full period and will produce sub-standard delivery.

Third criterion (budget feasibility, 1-5 scale): is the event's estimated cost within the allocation range for its archetype? Pass threshold: ≥4. Events that require a budget beyond 25% of the total archetype should be re-scoped or excluded.

Fourth criterion (sponsor commitment, 1-5 scale): is there an executive sponsor identified and formally committed? Pass threshold: ≥4. A sponsor commitment of 1-3 indicates that the event is informally searching for a sponsor - it's a huge red flag and typically a prelude to an orphan event (anti-pattern 3).

Fifth criterion (measurability, 1-5 scale): are the 3 target KPIs declared with a baseline and an achievable target number? Pass threshold: ≥3 (more permissive because many new events have no historical baselines). A measurability of 1-2 indicates that the event is symbolic, not measurable, and will therefore offer no learning for the next cycle.

A portfolio event enters the go state only if all five criteria clear the thresholds. Events with one or two criteria below threshold enter the conditional go state: they must be re-scoped and re-proposed within 2-3 weeks. Events with three or more criteria below threshold go to no go: you formally communicate to the candidate sponsor why the event was excluded.

The politically most costly part of the framework is communicating the no go to sponsors who see their candidate event excluded. A practice that works is writing the rejection memo: a half-page document containing (a) the five criteria evaluated with the assigned score, (b) the two or three criteria that failed with a concrete (not generic) rationale, (c) the three re-scoping options that could bring the event to a conditional go at the next review, (d) the deadline by which to resubmit the candidacy. The rejection memo is sent directly to the sponsor (not CC'd to the manager) and discussed in a dedicated 20-minute call. This practice transforms the rejection from an "opaque political no" into an "objective no with a path to recovery", reducing the political cost by 70-80%.

A useful extension of the go/no-go framework is the quarterly portfolio review. At every quarter-end, the senior coordinator re-applies the five criteria to the portfolio's remaining events for the rest of the year: changed situations (e.g. the executive sponsor resigns, an annual budget cut, team capacity) can move events from go to conditional go or no go. The quarterly review makes the portfolio adaptive instead of rigid - an annual portfolio decided in December and never revisited is almost always obsolete by June.

Step 4 - Cross-BU orchestration: symmetric governance setup (2-3 weeks before the first event)

For the portfolio's cross-BU events, step 3 is followed by the setup of symmetric governance. Three concrete deliverables.

First: program narrative statement (see the framework section). A 1-page document, written in 90 minutes with the two BU sponsors. Signed and committed to a Notion/Confluence repo accessible to all program stakeholders.

Second: program steering committee with a monthly cadence for the entire annual program (not bi-weekly as for a single event). Minimum composition: the two BU sponsors + one DRI per BU + the senior coordinator (you). Duration 60 minutes, fixed agenda: 15 min portfolio review (what happened during the month), 20 min next-events deep-dive, 15 min cross-cutting decisions, 10 min program look-ahead.

Third: formalized exit strategy. A 1-page document with the conditions for interrupting the program (see framework). Signed by the sponsors and archived alongside the narrative statement.

Step 5 - Execution + resource arbitration (ongoing all year)

The execution of the annual portfolio is not the sum of the executions of the individual events: it includes an additional function, which is portfolio-level resource arbitration. It typically shows up in three situations.

Situation 1 (capacity squeeze): a portfolio event is in trouble and requires additional resources (e.g. the senior coordinator of an event fell ill during a critical phase). Senior decision: temporarily reallocate the mid from a less critical adjacent event, accepting a sub-standard risk on the second event to save the first.

Situation 2 (budget reallocation): one event has budget surplus (e.g. a vendor turned out cheaper than expected, 15% saving) while another is tight. Senior decision: reallocate the delta between events within the same archetype category (not cross-archetype, because that would violate the 50/30/15/5 rule).

Situation 3 (strategic cancellation): a portfolio event is in chronic difficulty and the opportunity cost of keeping it is higher than the benefit of bringing it to delivery. Senior decision: propose a formal cancellation to the steering committee, reallocating the freed-up budget to the portfolio-level contingency reserve or to a more strategic adjacent event.

This last one is the most unpopular and politically costly decision. It can be bought with a standardized protocol: cancellation is proposed only if the event has violated at least two of the five go/no-go criteria during execution (e.g. capacity feasibility has dropped, budget feasibility has dropped, sponsor commitment has expired). Proposing cancellation via the protocol is far more politically defensible than proposing it "by gut feeling".

Real case: Atlassian Team Playbook, GitLab Handbook, Stripe Sessions, HubSpot INBOUND

Four tier-1 case studies, chosen because they cover four different modes of portfolio organization: internal operational portfolio (Atlassian), radically transparent cross-functional portfolio (GitLab), single B2B brand event with a programmatic effect (Stripe), scale-up educational program (HubSpot).

Atlassian is the reference for the standardized internal portfolio. For the cross-functional portfolio in a fully remote company (the most complex frontier for a senior coordinator), the reference is GitLab.

The third case study looks at the single B2B brand event that has a programmatic effect on the annual portfolio: Stripe Sessions.

The fourth case study looks at the ongoing educational program, the most relevant pattern for internal portfolios focused on upskilling: HubSpot INBOUND.

Three additional sources for those who want to dig deeper: Harvard Business Review - Managing Yourself category has academic articles on the mid→senior transition that also apply to event ownership; PMI Project Management Institute offers the Portfolio Management Professional (PfMP) certification, the single international reference for portfolio management applied to corporate contexts; the Cvent Blog in the Event Strategy category has quarterly case studies on the annual portfolios of enterprise clients.

Anti-patterns and how to recognize them

Senior anti-patterns differ from junior/mid anti-patterns because they don't concern the execution of a single event but the management of the portfolio or cross-BU orchestration. They're more costly because they impact the entire fiscal year, not a single deadline. They're also harder to recognize because they manifest slowly - not in a one-off crisis, but in a gradual degradation of the portfolio.

Templates, checklists and next steps

The cornerstone's Event Brief 1-pager template remains the starting tool for every portfolio event. For the L3 senior level, the template that makes the difference is the cross-BU RACI applied to the annual cross-BU program (not to the single event): it tracks roles, accountability and decision-rights across the BUs involved for the entire year.

The personal growth path from the L3 senior level toward L4 executive includes three conceptual transitions. First: from a single BU's portfolio to a division/region portfolio (10+ events/year aggregated across 3-5 BUs). Second: from informal cross-BU orchestration to formalized governance via an internal MOU and permanent multi-BU steering committees. Third: from event lead to programs director, where events become a lever of a broader strategy (employer branding, customer education, partner enablement).

For those who want to dig into the certifications applicable to portfolio management: PMI's Portfolio Management Professional (PfMP) is the international reference but is designed for portfolios of generic projects, not specific to events. The combination I see most often among EU senior coordinators is CMP (Events Industry Council) + PMP (Project Management Institute) - aggregate costs of roughly €1500-2000 for the exams, €4000-6000 for the preparatory courses. Average preparation time for someone starting from L3 mid: 8-12 months part-time for both certifications in parallel.

Three additional readings that influenced the framework of this guide: Good Strategy Bad Strategy by Richard Rumelt (2011, Crown Business) - the single most powerful book on distinguishing real strategy from strategic rhetoric, applicable to portfolio design; The Phoenix Project by Gene Kim, Kevin Behr, George Spafford (2013, IT Revolution Press) - on portfolio management applied to the IT/DevOps context, with many cross-cutting applications to event portfolios; The Hard Thing About Hard Things by Ben Horowitz (2014, Harper Business) - on managing difficult decisions in corporate political contexts, particularly relevant to cross-BU orchestration.

The most effective practical experience for the L3 level in transition is the understudy program: shadowing a senior coordinator who already manages portfolios for a full year, participating as a "shadow" in steering committees, go/no-go frameworks, vendor scorecards. 12 months of shadowing on a real portfolio produce more growth than three years of delivering single events.

What I learned writing this