event-team-structure

Start with a bus-factor map of every named role, then fix the legal-entity posture, pick a decision-rights shape, and lay out a role taxonomy with written scopes. Events holding money or contracts should adopt a board-plus-organizers split, the shape large durable events converge on.

Fiscal sponsorship is the default for conferences: a parent foundation holds money and signs contracts while you operate. Incorporate your own non-profit only when the event should outlive its founding organizers, accepting bylaws, board duties, and annual filings.

The documented threshold is roughly low-thousands of attendees or a six-figure budget with organizing become a year-round burden. The first hire is an event coordinator or manager in nearly every documented case, never a community manager, and program leadership stays volunteer.

Full-team rotation only works over a standing continuity layer such as a board or paid staff holding institutional knowledge. Without one, it produces recurring host-recruitment failures and lost knowledge, so it should be removed from the option set entirely.

Bus factor counts how many people could run each role if someone disappeared; roughly a third of meetup groups run on a single organizer. Apply the two-deep rule so every named role has a backup, and move accounts and domains off personal ownership with a backup admin.

No. Day-of volunteer sizing, shifts, and briefing belong to the event-volunteers skill in the same collection. This Skill covers only the standing team that exists between editions: leads, decision rights, succession, and paid staff.