Mid Coordinator: project, risk and budget +/-10% independently for BU events

The mid level of BU event project management isn't "knowing how to use Jira": it's knowing how to build an operational plan, identify 5+ P1 risks with a concrete mitigation plan, and manage the budget within +/-10% without constantly asking the senior for approvals. This guide translates PMBOK 7 and the PCMA risk framework into L2 practice: Gantt vs Kanban, a weekly-cadence risk registry, budget control with biweekly forecasting. Three tier-1 case studies (Atlassian Confluence project tracking, ServiceNow Knowledge risk management, Cvent CONNECT budget governance), five operational anti-patterns, a 15-item plan verification checklist.

TL;DR

The L2-C3 cell of the career matrix in our Team Collaboration & Event Building cornerstone describes the mid event coordinator as the person who uses Gantt or Kanban, identifies P1 risks with a mitigation plan, manages a +/-10% budget independently. The three dimensions - project, risk, budget - are not independent: they intersect in every operational decision. The L2 level is defined precisely by the conscious integration of these three dimensions into a single operational governance. The difference from the junior (who uses standard checklists and flags blockers) is qualitative: the mid generates the plan, identifies the risks before they materialize, controls the budget with a biweekly forecast instead of noting the overrun after the fact. The proposed structure derives from three standards: PMI's PMBOK 7 for the foundations of project management, the PCMA risk framework for the 8 canonical categories of operational event risk, and the widespread practice in tech scale-ups (Stripe, Linear, Notion) of forecasting the budget on a biweekly cadence. The conceptual framework for L2 is the P-R-B triangle: every decision touches at least two of the three vertices (Project, Risk, Budget), and the mature L2 reads every decision through the three vertices before making it. The five L2 anti-patterns are: a Gantt built and never updated, a phantom risk registry, a budget monitored at month-end, over-engineering the plan, chronic optimistic forecasting. If you have 2-5 years of experience and are designing your first BU event end-to-end, start from the Operational steps section. If you have an event already in progress and the budget is creaking, jump straight to the Anti-patterns and the checklist.

When you need it / Prerequisites

This guide is written for those who already have the stakeholder map built (see L2-C2) and are about to enter the operational prep phase: writing the plan, identifying the risks, allocating the budget. The typical profile: 2-5 years of experience in marketing operations, employee experience, learning & development, HR business partner. The event belongs to your own BU, size 50-300 participants, budget €8-25k, half-day or one-day duration.

The operational prerequisites are four. The first: having access to a project management tool (Jira, Asana, ClickUp, Notion, Linear, Monday). You don't need to be a power user; you need to know how to create a board, define tasks with a couple of dependencies, set up two or three filters. The second: having the 1-pager brief finalized with frozen scope (see L2-C1). Without a frozen scope, the plan is written on quicksand. The third: having visibility on the budget and access to the company's financial system to create purchase orders (typically SAP, Oracle, NetSuite, or a scale-up platform such as Pleo/Spendesk). The fourth: having decision-making authority for spending up to the +/-10% budget limit. This authority must be explicitly granted by the BU sponsor at the start of prep; if not granted, you are effectively at L1 level, not L2.

If the fourth prerequisite is missing (+/-10% authority), the first step is to ask for it explicitly. The conversation is a 10-minute one with the sponsor: "To manage the event effectively I would need the authority to move the budget within +/-10% without continuous approval. I'll document every delta in the biweekly forecast I send you on Friday. Above 10% I ask for explicit approval. Does that work?". The mature sponsor says yes; the sponsor who says no reveals a trust problem that must be addressed before starting the event.

A note on what you do not need. You don't need the PMP certification to be an effective L2; the PMP is an investment to consider at the L2-L3 transition (at the senior cross-BU level the PMP adds value). You don't need Microsoft Project: it's a heavy enterprise tool, too formal for the BU scale; a Google Sheets sheet with dependencies + a Kanban on Notion do 95% of the work. You don't need a 30-page PMBOK-format risk register: for the BU scale, 5-8 P0/P1 risks with a simple 3-column table (risk, trigger, mitigation) are enough.

Conceptual framework: the Project - Risk - Budget triangle

The P-R-B triangle is the conceptual device that defines the L2 level on column C3 of our matrix. The three vertices - Project (what is done, when, by whom), Risk (what can go wrong, with what probability, with what impact), Budget (how much it costs, what is allocated to what, how much is left) - are interconnected: a decision that touches one vertex typically impacts at least one other. Example: you decide to move the delivery of print materials forward by a week to reduce the risk of delay (Risk vertex). This decision impacts the Budget vertex (the supplier probably asks for 8-12% more for the rush) and the Project vertex (some downstream tasks shift forward). The mature L2, before making the decision, reads the impact on the three vertices and chooses consciously; the immature L2 makes the decision looking only at the starting vertex (Risk) and is later surprised by the backlash on the other two.

The Project dimension at L2 level translates into a concrete operational plan. For BU events of 100-300 participants the plan typically has 40-80 tasks spread over 8-12 weeks. The choice between Gantt and Kanban depends on the nature of the event. You use Gantt when the dependencies are strong and sequential - typical for physical events with a venue: you don't sign the catering before you've signed the venue, you don't launch the invitations before having the final agenda, you don't print the swag before having the final logo. You use Kanban when the dependencies are weak and the work is parallelizable - typical for virtual or hybrid events where many tasks are independent (platform setup, registration tracker, speaker training, communications). The rule: Gantt for medium physical events (100-500), Kanban for virtual or hybrid events, hybrid (Gantt for the critical path + Kanban for the parallel work streams) for large or complex events.

The Risk dimension at L2 level translates into an explicit registry with 5-8 documented P0/P1 risks. PCMA Convene has codified eight canonical categories of operational event risk: speaker no-show, technology failure, attendance shortfall, budget overrun, vendor failure, weather/health emergency, security incident, brand/reputation hit. For each category, the L2 assesses whether the risk applies to their event (probability > 5%) and with what impact (P0 = blocks the event, P1 = significantly degrades it, P2 = acceptable). Typically for a 100-300 BU event 5-8 P0/P1 risks emerge - not 30 (over-registry) and not 2-3 (under-registry). For each one you fill in a 3-column row: risk (concrete description), trigger (which signal tells us it's about to happen), action (the pre-planned mitigation).

The Budget dimension at L2 level translates into a biweekly forecast. You start from the budget approved by the brief (e.g. €15,000), break it down by line (venue 6,000, catering 3,500, A/V 2,000, speaker fee 1,500, swag 1,000, contingency 1,000), and every two weeks you compare the committed (signed purchase orders) + spent vs the budget per line. The delta is called variance. Variance < 5% per line: normal situation, no action. Variance 5-10%: communication to the sponsor with the reason, but it's handled internally. Variance > 10%: formal escalation to the sponsor with a proposal to reallocate between lines or a top-up request. The critical operational rule: the forecast is forward-looking, not backward-looking. It means that at week 4 of prep you look not only at what has already been spent (committed) but also at what you estimate spending in the following 4-8 weeks (forecast). The immature L2 looks only at committed; the mature L2 looks at committed + forecast and anticipates overruns before they materialize.

On the relationship between contingency and budget, a useful rule of thumb: the contingency reserve should be 5-10% of the total budget. Below 5% you're too optimistic (any unforeseen event produces an overrun). Above 10% you're too cautious (and in reality the sponsor might contest the budget size as inflated). 7-8% is a reliable sweet spot for the BU scale. The contingency is managed by the L2 independently for unplanned spending up to the reserve limit; above the limit you escalate to the sponsor.

A second level of the P-R-B triangle that the mature L2 introduces gradually is cycle thinking: the single event is not an isolated unit, but part of a cycle of annual BU events. The lessons learned from one event feed the plan, the risk register and the budget of the next event. Concretely: the post-mortem of event N produces 3-5 action items that become tasks in the plan of event N+1; the risk registry of event N (which materialized, which didn't, which new ones emerged) becomes the baseline of the registry of event N+1; the budget variance of event N (overrun per line) informs the initial breakdown of the budget of event N+1. This continuous learning cycle is the fundamental difference between the L2 who grows and the one who stays at a constant level: those who don't close the cycle repeat the same mistakes indefinitely.

A useful L2 practice for closing the cycle: at the end of each event you fill in a half-page delta log with three sections - "P0/P1 risks that actually materialized" (which, with what impact), "budget lines in overrun by more than 5%" (which, by how much), "plan tasks slipped by more than 3 days" (which, for what reason). The delta log of event N is a mandatory input to step 1 (brief decomposition) of event N+1. This practice turns the tacit baggage of experience into explicit operational knowledge, shareable with peers and with succession planning for your role.

Operational steps: the six steps to integrate Project, Risk, Budget

Step 1 - Decomposing the brief into tasks (days 1-2)

You start from the 1-pager brief (output of L2-C1) and decompose it into macro-areas: program (what happens during the event), logistics (where, how, when), marketing/comms (how it's communicated), finance (who pays, how much). For each macro-area you list the necessary tasks. For a 100-200 person BU event, typically: program 10-15 tasks, logistics 15-25 tasks, marketing/comms 8-12 tasks, finance 5-8 tasks. Total 40-60 tasks. For larger events (300+) the numbers rise to 60-100.

The L2 operational rule: every task has 4 mandatory attributes - owner (a person, not a team), deadline (a specific date), output (a verifiable artifact), dependencies (which tasks must finish first). A task without the 4 attributes is not a task, it's a note. You write the task in 3-4 minutes, not in 15.

Step 2 - Choosing between Gantt and Kanban (30 minutes)

You apply the framework rule: Gantt if strong dependencies, Kanban if parallelizable, hybrid if complex. You choose the tool: Asana (good Gantt+Kanban mix), ClickUp (powerful but complex), Linear (simple but Kanban-centric), Notion (flexible but manual), Monday (visual but expensive). For the L2 with a limited budget a Google Sheets sheet with owner/deadline/status/dependencies columns does 95% of the work for events under 200 participants.

A useful L2 practice: critical path highlighting. Even with Kanban, you explicitly identify the sequence of tasks that, if it slips by a day, moves the event date. Typically for BU events: venue contract → final agenda → save-the-date → invitations → registration open → reminder T-2 → reminder T-1 → event. These are 6-8 tasks in sequence; if one slips, they all slip. All the other tasks (catering, A/V, swag, materials) are off-critical-path and have more margin for slippage.

On the aspect of task granularity, a useful rule of thumb: no task should be longer than 3 working days. If a task requires 5+ days, you break it into 2-3 sub-tasks. The reason is that long tasks are opaque: for the 3-4 intermediate days you don't know whether they're "halfway", "three quarters done", "slipping". Tasks of 1-3 days are transparent: they're either done or not, and any slip is recognized immediately. For BU events with 8-12 weeks of prep, this rule naturally produces the 40-80 tasks described above.

Step 3 - Risk register (45 minutes)

You go through the 8 PCMA categories. For each category: does it apply to our event (yes/no)? If yes, you write a 3-column row. Examples for a 100-200 person BU event:

• Risk: keynote speaker cancels within 48h. Trigger: email from the agent with an agenda change. Action: activate a pre-briefed backup speaker (list in advance) + modify the slide deck (template ready) + communicate via email + BU Slack within 4h.
• Risk: attendance shortfall (-30% vs the target). Trigger: at T-2 weeks registrations below 70% of the target. Action: additional push via the BU channel + direct DMs to the 20-30 key unregistered participants + deadline extension of 5 days.
• Risk: A/V technology failure in the plenary. Trigger: the pre-event test fails on one or more devices. Action: activate the backup vendor (pre-signed contract) + emergency kit (spare laptop, wireless microphone, portable projector) + simulation test 24h before.

The deliverable is a sheet with 5-8 rows, shared in read-only with the sponsor and the area owners. The mature L2 reopens it every Friday for 15 minutes during prep: you add emerged risks, close cleared risks, verify the mitigation triggers for those still active.

Step 4 - Budget allocation per line (60 minutes)

You break down the total budget per line. For a 100-200 person BU event with a €15k budget, the typical breakdown is: venue 6,000 (40%), catering 3,500 (23%), A/V 2,000 (13%), speaker fee 1,500 (10%), swag/materials 1,000 (7%), contingency 1,000 (7%). The percentages vary by type of event (a technical workshop with an external speaker pays more for the speaker fee and less for catering; a one-day team retreat pays more for catering and less for A/V).

For each line you collect 2-3 quotes from different suppliers (see L2-C1 on supplier coordination). You negotiate within 5-10% of the first quote. You formalize with a signed contract; the contract is the basis of the committed budget.

Step 5 - Biweekly forecast (15 minutes every 2 weeks)

Every two weeks (e.g. every odd Friday) you open the budget sheet and fill in the forecast. Three columns added to the budget lines: committed (signed purchase orders), spent (actually spent), forecast remaining (estimated spending in the remaining weeks). You calculate variance = (committed + forecast remaining) - budget. If variance > 10% you escalate to the sponsor with a proposal. If variance < -5% (we're spending less than the budget) you assess whether to reallocate to an under-budgeted line or return it to the BU pool.

The biweekly forecast is the single practice that distinguishes a mature L2 from an immature L2. The immature L2 looks at the budget only at the end of the event and notes the overruns after the fact; the mature L2 anticipates them by 3-6 weeks and resolves them while there's still room to maneuver.

An operational evolution of the biweekly forecast is the traffic light dashboard: a compact half-page visualization that, for each budget line, shows a traffic light. Green if variance < 5%, yellow if variance 5-10%, red if variance > 10%. The L2 shares the dashboard every two weeks with the sponsor + area owners; the sponsor sees in 30 seconds where the problems are and which lines they need to act on. The dashboard does not replace the detailed sheet - it's a synthesis layer on top of it. The practice is widespread in tech scale-ups (Stripe, Notion, Linear) and is also cited in the annual Skift State of Corporate Events 2024 report as an emerging practice in the more mature event teams.

On the question of when to intervene on overruns, a useful rule of thumb is the 3-3-3 rule: 3 weeks before a projected overrun of 5-10% you only do monitoring + preemptive communication to the sponsor; 3 weeks before a projected overrun of 10-20% you intervene actively (reallocation, supplier negotiation, cutting non-critical scope); 3 weeks before a projected overrun > 20% you formally escalate to the sponsor + the BU finance controller with a budget top-up proposal. This ladder produces calibrated behaviors instead of reactions proportionate only to the severity of the final moment.

Step 6 - Integrated P-R-B check-point (T-2 weeks, T-3 days)

The two pre-event check-points (see L2-C1) are not just a status update: they are integrated reviews of the three vertices. You look at the plan (tasks slipping, dependencies at risk), at the registry (risks that are materializing, triggered triggers), at the budget (variance, committed vs forecast). You fill in a one-page summary and share it with the sponsor + area owners. Duration 45-60 minutes.

The check-point at T-2 weeks catches recoverable slips. The check-point at T-3 days catches the last unforeseen events. Between the two check-points is the window where the L2 executes the mitigations for the materialized risks, reallocates budget if necessary, adjusts the plan.

The format of the check-point's one-page summary is an important operational detail. The page is divided into four quadrants: top left Plan status (on-track tasks, recoverable slipping tasks, critically slipping tasks); top right Risk status (active P0/P1 risks with updated probability, materialized risks with mitigation outcome); bottom left Budget status (variance per line with a traffic light, scenario at the event); bottom right Decisions needed (3-5 decisions that the L2 asks the sponsor or the area owners to make within 48h). The page reads in 90 seconds and produces concrete decisions. It's a far more effective communication device than a 12-slide presentation or a long email.

An L2 practice worth spending on is the walking check-point: instead of a formal meeting, you organize a 30-45 minute walk with the sponsor (in the office if in person, or as a walk-and-talk phone call if remote). The walking format produces less formal conversations, leads people to talk about risks and doubts more honestly, and typically surfaces information that wouldn't emerge in a conference-room meeting. The walking check-point is particularly effective at T-2 weeks (when there are still intervention windows) and less so at T-3 days (where a more structured meeting format is needed to cover many topics quickly).

Real case: Atlassian Confluence, ServiceNow Knowledge, Cvent CONNECT

Atlassian covers the "how to structure". ServiceNow is famous for its discipline on risk management, applied to internal events too.

The third case study looks at budget governance: Cvent CONNECT.

For those who want to dig deeper: PMI's PMBOK 7 has a chapter dedicated to risk management that is the academic reference standard; Skift Meetings annually publishes the State of Corporate Events with budget benchmarks by event type and geography (useful for validating whether your budget per participant is aligned with the market); HBR - The Real Reason Projects Fail is a classic (2003) on the systemic reasons for project failure that apply directly to events.

Anti-patterns: the five most frequent ways to break the P-R-B triangle

Template, checklist and next steps

The Event Brief 1-pager template (cited in L2-C1) integrates naturally with the Gantt sheet and the risk register sheet described here. The 'risks' section of the brief is the starting point of the risk register; the 'budget' section of the brief is the starting point of the biweekly forecast. For those who want a single operational reference point, the Event Brief template includes the three P-R-B dimensions integrated.

A 15-item operational checklist for verifying the plan before kick-off:

1. The plan has 40-80 tasks for a 100-300 person BU event
2. Every task has owner, deadline, output, dependencies
3. Critical path identified (6-8 tasks in sequence)
4. Gantt vs Kanban choice justified and consistent with the nature of the event
5. Risk register has 5-8 P0/P1 risks
6. Every risk has risk, trigger, mitigation
7. Risk register shared with sponsor + area owners
8. Weekly review of the risk register in the calendar
9. Budget broken down per line with percentages consistent with the event type
10. Contingency 7-8% of the total budget
11. Biweekly forecast scheduled for the 8-12 weeks of prep
12. L2 authority for +/-10% spending explicitly granted by the sponsor
13. Two integrated P-R-B check-points scheduled (T-2 weeks, T-3 days)
14. Plan update cadence defined (real-time or end-of-day)
15. Peer review of the plan and the risk register done with a coordinator from another BU

The next step in L2-C3 growth is completing the other two columns of your matrix row: L2-C4 on the pre-event communication funnel and L2-C5 on the retrospective with an action plan. Once the entire L2 row is consolidated, the leap toward the senior cross-BU passes through L3-C3 (P0 risks and €100k budget).

What I learned writing this