# Event Calendar Planner

> Plans the annual event calendar that allocates budget to the events most likely to generate pipeline. Use when asked to event calendar planner. Suggest when relevant.

- Skill: `mittuled/event-calendar-planner` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add mittuled/event-calendar-planner`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mittuled/event-calendar-planner/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: mittuled (https://skillmd.com/u/mittuled)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/mittuled/event-calendar-planner

---


# event-calendar-planner

## Agent: Social Media Manager

L2 event marketing manager responsible for conference presence, sales kickoffs, user conferences, company offsites, and virtual events.

Department ethos: [ideal-marketing.md](../../../../departments/marketing/ideal-marketing.md)

## Skill Description

Plans the annual event calendar including conferences, webinars, and hosted events, allocating budget and resources to the mix that maximises pipeline contribution across quarters.

## When to Use

- Annual planning season begins and the events budget needs allocating across the year.
- A mid-year strategy shift requires re-prioritising the remaining event calendar.
- New market segments or geographies are targeted and the event mix needs expanding to reach those audiences.
- Post-year analysis reveals the event portfolio is unbalanced and needs restructuring.

## Workflow

1. Gather inputs: annual pipeline targets by segment, sales territory priorities, product launch dates, and the total events budget.
2. Inventory candidate events: industry conferences, hosted events, webinars, partner events, and community meetups. Score each using the event scoring matrix in `references/framework.md` on ICP attendance, cost, timing, and historical pipeline data. Require composite score ≥ 3.0/5 to include.
3. Draft the calendar with event types distributed across quarters following the cadence model in `references/framework.md` to maintain consistent pipeline contribution and avoid clustering.
4. Allocate budget per event using the allocation guidelines in `references/framework.md` including sponsorship, travel, production, and promotion costs. Reserve 10% contingency for opportunistic additions.
5. Map resource requirements: headcount per event, cross-functional dependencies on sales, product, and design, and lead times for production assets.
6. Present the draft calendar to marketing leadership and sales for alignment. Incorporate feedback on priority events and timing conflicts.
7. Publish the approved calendar with key milestones, deadlines, and owners for each event.
8. Review the calendar quarterly following the process in `references/framework.md`: compare actual pipeline attribution per event against plan, and reallocate budget from underperforming events to higher-ROI opportunities.

## Anti-Patterns

- **Repeating last year's calendar without re-evaluating ROI.** *Why*: Market conditions, ICP behaviour, and competitor strategies change; events that worked last year may not be worth attending this year.
- **Clustering all major events in one quarter.** *Why*: Event fatigue burns out the team, creates pipeline lumps that stress the sales funnel, and leaves other quarters without event-driven leads.
- **Planning events without sales input on target accounts and territories.** *Why*: Events in markets where sales has no coverage or pipeline targets waste budget on leads that will not be worked.
- **Committing the full budget in Q1 with no contingency.** *Why*: Emerging conferences, competitor moves, and strategic pivots require flexibility to add or swap events mid-year.

## Output

**Success artifacts:**
- Annual event calendar with event type, dates, budget, and owners
- Event scoring matrix with ICP relevance and historical pipeline data
- Quarterly calendar review with pipeline attribution and reallocation recommendations
- Resource plan mapping headcount and cross-functional dependencies per event

**Failure reporting:**
- Flag budget shortfalls or scheduling conflicts that threaten committed events at least 6 weeks in advance
- Escalate events with declining ROI trends to the marketing lead at the quarterly review

## Related Skills

*No related skills defined yet.*
- [`company-offsite-producer`](../company-offsite-producer/SKILL.md) — sibling skill under the same agent — combine with company-offsite-producer for end-to-end coverage
- [`conference-presence-manager`](../conference-presence-manager/SKILL.md) — sibling skill under the same agent — combine with conference-presence-manager for end-to-end coverage
- [`sales-kickoff-producer`](../sales-kickoff-producer/SKILL.md) — sibling skill under the same agent — combine with sales-kickoff-producer for end-to-end coverage
- [`user-conference-producer`](../user-conference-producer/SKILL.md) — sibling skill under the same agent — combine with user-conference-producer for end-to-end coverage
- [`webinar-and-virtual-event-manager`](../webinar-and-virtual-event-manager/SKILL.md) — sibling skill under the same agent — combine with webinar-and-virtual-event-manager for end-to-end coverage

