What Event Coordinators Are Asked to Do: Evidence from 100 Current Vacancies
The complete open archive - an 11-page visually reviewed PDF, the rights-reviewed 100-row coded dataset, quality records, methods and data dictionary - is preserved at Zenodo DOI 10.5281/zenodo.22178908. The direct public PDF is available here.
MTF Institute Research Report
Evidence freeze: 30 August 2026
Study type: descriptive vacancy-content analysis with occupational-context triangulation
Language: English
Abstract
Event coordination is often described through visible moments: a venue opens, attendees arrive, speakers take the stage, catering is served, and a programme unfolds. Current vacancies show that the less visible work is at least as important. Employers ask coordinators to translate objectives into controlled plans, align many stakeholders, source venues and suppliers, maintain budgets and operational records, manage attendee and hospitality workflows, support live delivery, and close events with financial and performance evidence.
This report analyses a frozen corpus of 100 publicly accessible vacancies collected on 30 August 2026. The sample includes 54 first-party employer applicant-tracking pages, 23 public national job-listing records, and 23 other public job-listing pages. Each record preserves a source URL, employer, title, location, retrieval date, freshness evidence, a concise responsibility summary, a deterministic deduplication key, and structured codes. Counts are row-presence counts: a vacancy contributes at most once to a theme, even when that theme appears several times in the source.
The most frequent themes were event planning or lifecycle ownership (97 vacancies), operational logistics (68), stakeholder management (60), vendor or supplier work (55), venue or space work (49), event documents and control records (46), and financial control (44). Seventy-five vacancies contained venue and/or supplier decision work. Forty-four contained budget-control decisions. Thirty-nine contained marketing and/or measurement work, and 22 contained risk, safety, insurance, approval, or permit-related coordination. The evidence supports a practical learning design built around an integrated event lifecycle and a portfolio of usable artifacts rather than isolated theory.
The sample is purposive and is not presented as representative of all employers, countries, event types, or seniority levels. The 100 records contain 80 unique source URLs because 21 distinct Canadian Job Bank listings share one public search-results URL while retaining different employers, titles, locations and listing identifiers. Vacancy availability changes over time. The findings describe the selected public records at the evidence freeze and should be interpreted together with the stated sampling and coding limits.
1. Research question
The study asks:
What responsibilities, decisions, skills, and work products recur across 100 current public vacancies for event coordinators and closely adjacent event-planning roles?
The question is intentionally operational. It does not estimate hiring probabilities, salary returns, course effectiveness, or future employment. It also does not evaluate any employer, event supplier, professional association, or training provider.
2. Why this role merits close analysis
The vacancy evidence sits within a recognised occupational field. O*NET OnLine identifies Meeting, Convention, and Event Planners as occupation 13-1121.00 and reports a 21-task model that includes consultation, service coordination, audiovisual arrangements, venue work, recordkeeping, negotiation, provider selection, budget and programme planning, supervision, monitoring, and evaluation [1]. The page was recorded as updated in 2026.
The U.S. Bureau of Labor Statistics describes the occupation as organising events and professional gatherings through client discovery, scope and cost decisions, bids, venue inspection, service coordination, live monitoring, invoice review, logistics, and supplier negotiation [2]. In its 2025 employment base and 2025–2035 projection, BLS recorded 172,100 U.S. jobs, projected 6% growth, and estimated about 16,800 openings per year over the decade [2]. These are U.S.-specific contextual statistics. They do not predict outcomes for a learner or for any other labour market.
BLS Occupational Requirements Survey data add an important practice signal: 80.7% of sampled jobs required prior work experience and 86.6% required on-the-job training [3]. Those figures do not mean a course can replace experience. They instead support practice-rich learning in which learners work through decisions, calculations, handoffs, documents, and realistic operational constraints.
O*NET also records strong importance for dependability and attention to detail, with scores of 98 and 91 in the accepted occupational evidence [1]. The vacancy corpus helps explain why. A coordinator frequently maintains many linked facts—dates, owners, quantities, prices, access needs, supplier commitments, room requirements, and communication deadlines—where a small inconsistency can propagate into delivery problems.
3. Evidence base
3.1 Corpus composition
The accepted corpus contains exactly 100 unique records after deterministic deduplication.
| Source class | Vacancies | Share |
|---|---|---|
| First-party employer ATS/application pages | 54 | 54% |
| Public national job-listing records | 23 | 23% |
| Other public job-listing pages | 23 | 23% |
| Total | 100 | 100% |
The geographic composition was:
| Geography | Vacancies |
|---|---|
| United States | 45 |
| Canada | 31 |
| United Kingdom | 16 |
| Australia | 4 |
| Singapore | 2 |
| Germany | 1 |
| Multi-country role covering Canada, Mexico, Portugal, and Spain | 1 |
| Total | 100 |
The records cover corporate and B2B events, conferences, universities, event venues, hospitality, public-sector and community events, fundraising, healthcare and medical meetings, arts and culture, trade shows, experiential activation, membership programmes, and internal events. Eighty-two titles explicitly contain “Coordinator.” The remaining 18 are manager, producer, or specialist roles with directly adjacent planning and coordination work. Including this adjacent group helps show progression from task support into broader ownership, but the study does not treat title labels as uniform seniority grades.
3.2 Inclusion logic
A vacancy was eligible when a public page was current or actively accepting applications at retrieval and the visible role scope contained substantive event planning, coordination, production, event operations, meeting, conference, hospitality-event, or special-event work. Roles limited to one-day staffing, generic promotion, unrelated marketing, or non-event administration were excluded. A detailed protocol is provided in methods.md.
3.3 What “current” means
“Current” means that an active application page, current listing, requisition, or recent posting condition was visible on 30 August 2026. It does not mean every page will remain available after that date. The corpus records the retrieval date and the freshness evidence used for every row.
4. What employers repeatedly ask coordinators to do
Table 3 reports deterministic row-presence counts. Each vacancy contributes no more than one count to a code.
| Responsibility or skill family | Vacancies | Share |
|---|---|---|
| Onsite or live delivery / event-day monitoring | 100 | 100% |
| Event planning, scoping, lifecycle, or calendar ownership | 97 | 97% |
| Operational logistics and setup/teardown coordination | 68 | 68% |
| Client, partner, or cross-functional stakeholder management | 60 | 60% |
| Vendor or supplier sourcing, contracting, negotiation, or performance | 55 | 55% |
| Venue/space selection, booking, floor plans, or room management | 49 | 49% |
| Briefs, timelines, run of show, BEOs, checklists, or records | 46 | 46% |
| Budget, quotation, purchasing, invoicing, or reconciliation | 44 | 44% |
| Catering, food-and-beverage, banquet, or hospitality coordination | 35 | 35% |
| Event promotion, sponsorship, or brand activation | 24 | 24% |
| Audiovisual, virtual/hybrid platform, or event technology work | 24 | 24% |
| KPI, survey, ROI, report, or continuous-improvement work | 23 | 23% |
| Invitation, RSVP, registration, or attendee management | 21 | 21% |
| Safety, risk, insurance, accessibility, or contingency coordination | 19 | 19% |
| Staff, contractor, or volunteer scheduling/supervision | 15 | 15% |
| Travel, transport, lodging, room block, or itinerary work | 11 | 11% |
| Materials, shipping, freight, stock, or inventory control | 10 | 10% |
| Speaker, faculty, talent, content, or stage-program coordination | 10 | 10% |
| Permit, licence, or formal approval coordination | 5 | 5% |
| CRM, lead capture, pipeline, or event-linked sales data | 4 | 4% |
4.1 Planning is not a single preliminary task
Planning appeared in 97 vacancies, but the sources do not use the term as a narrow “make a checklist” activity. Across detailed records, planning includes clarifying requirements, sequencing work, assigning responsibilities, setting deadlines, estimating resources, recording assumptions, coordinating approvals, and maintaining plans as facts change. Some roles own a complete event lifecycle; others support a manager while controlling a defined workstream. In both cases, planning is continuous and connected to delivery.
This finding argues for teaching planning as a traceable system. Objectives should connect to requirements; requirements should connect to scope, owners, dates, costs, and acceptance conditions; changes should be logged; and live decisions should be linked back to approved boundaries.
4.2 Logistics is an integration problem
Sixty-eight vacancies included operational logistics. The detailed sources span room configurations, catering, AV, signage, deliveries, transport, accommodation, equipment, security coordination, stock, shipping, setup, teardown, and internal handovers. The practical challenge is not merely knowing these categories. It is ensuring that their dates, quantities, dependencies, owners, and constraints agree.
For example, a programme change can alter catering timing, speaker transport, room reset, audiovisual staffing, and attendee communications. A good learning task should therefore force learners to reconcile several connected plans rather than complete each artifact in isolation.
4.3 Stakeholder work is central
Sixty vacancies contained explicit client, partner, internal-team, or other stakeholder coordination. Coordinators act as information hubs among sponsors, event owners, venues, caterers, technical teams, speakers, attendees, finance, procurement, marketing, facilities, and operational staff. The role calls for active listening, concise writing, expectation management, follow-up, negotiation, and escalation.
The evidence also shows that communication quality is operational control. A polished message is not enough if it contains an unverified date, an unclear owner, an unapproved commitment, or a missing response route. Training should assess accuracy and actionability as well as tone.
4.4 Venues and suppliers require defensible choices
Venue work appeared in 49 vacancies and vendor/supplier work in 55. Seventy-five vacancies contained at least one of these two themes. Detailed records ask coordinators to define requirements, source options, request quotes, compare inclusions, inspect spaces, communicate operational needs, track contracts, monitor performance, and resolve gaps.
The repeated decision is not “find the cheapest supplier.” It is “select the strongest evidence-based fit for the event’s objectives, constraints, service needs, timing, risk, and total cost.” Practical training should use comparable-quote matrices, venue scorecards, site-review logs, decision notes, and contract handoff checklists. Contract interpretation and approval should remain with authorised commercial or legal owners.
4.5 Financial control is part of coordination
Forty-four vacancies contained budgets, quotes, purchase orders, invoices, expense tracking, or reconciliation. The work ranges from preparing an estimate to maintaining a forecast, checking supplier charges, tracking approvals, and explaining variances. BLS occupational evidence also identifies cost, bids, invoice review, and supplier negotiation as recurring occupation-level work [2].
This is a numerical and documentation capability. Learners should practise quantity-by-rate calculations, fees and contingencies, committed versus forecast cost, variance analysis, version control, and evidence checks before recommending payment. Examples should identify jurisdiction-specific tax or contractual questions for specialist review instead of giving universal answers.
4.6 Live delivery depends on prepared controls
All 100 coded records included event-day delivery, monitoring, setup, troubleshooting, or comparable live operational responsibility in the accepted evidence. The sources repeatedly emphasise adaptability, prioritisation, calm communication, and service recovery. Yet improvisation is not the whole job. Strong live response depends on earlier work: a usable run of show, accurate contact information, clear decision rights, supplier briefs, escalation routes, tested technology, and predefined fallback triggers.
For training, the most useful simulation is not an abstract question about “handling pressure.” It is a time-bound scenario with incomplete information, competing impacts, an authority boundary, and a required factual decision log.
4.7 Measurement is present but not universal
Twenty-three vacancies referred to surveys, KPIs, ROI, dashboards, performance summaries, leads, or continuous improvement. Marketing and/or measurement appeared in 39 vacancies. The signal is meaningful, especially in corporate, B2B, public, membership, and higher-education settings, but it is not present in every role.
Evaluation should therefore be taught proportionately. Coordinators need to define useful measures, preserve denominators and source definitions, calculate basic results, report response-rate and attribution limits, and translate findings into actions. They should not claim causality from a satisfaction score or report ROI when benefits, costs, attribution, and time horizon are undefined.
5. The professional decisions hidden inside the work
Responsibility lists describe activities; decision analysis reveals the judgment learners need to practise.
| Decision family | Vacancies with supporting evidence | Typical decision question |
|---|---|---|
| Venue and/or supplier choice | 75 | Which option best fits requirements, constraints, evidence, service risk, and total cost? |
| Budget allocation and control | 44 | Which cost is estimated, committed, contingent, avoidable, or outside the approved baseline? |
| Travel and/or hospitality configuration | 40 | How should catering, transport, lodging, and guest needs be coordinated within limits? |
| Marketing and/or measurement | 39 | Which objective, audience, measure, data source, and follow-up action make the event useful? |
| Attendee and/or speaker workflow | 26 | What information, timing, access need, briefing, or approval is needed for a workable experience? |
| Risk, safety, insurance, and/or permits | 22 | What can the coordinator control, what requires a predefined fallback, and what must be escalated? |
These decisions share a pattern. The coordinator rarely has unlimited authority or complete information. Good performance involves making assumptions visible, identifying decision owners, comparing options on consistent criteria, recording the rationale, and escalating specialist questions early.
A practical decision sequence
A reusable sequence for low-to-moderate complexity events is:
- State the objective and the decision to be made.
- Separate confirmed facts, constraints, assumptions, and open questions.
- Identify the person authorised to decide and the deadline.
- Define consistent criteria before collecting options.
- Normalise units, inclusions, exclusions, timing, and dependencies.
- Compare costs, service implications, risks, attendee effects, and evidence quality.
- Record the recommendation, trade-offs, conditions, and items for specialist review.
- Obtain the required approval.
- Update linked plans, budgets, communications, and logs.
- Verify that the accepted change reached the people who must act on it.
This sequence is not a substitute for employer policy or professional advice. It is a coordination discipline that helps authorised people make decisions from organised evidence.
6. The artifacts employers implicitly expect
The vacancy language points to tangible outputs. The following 25 artifacts were synthesised from the corpus. They should be taught as connected tools with a blank template, a completed example, use instructions, and a quality checklist.
| # | Artifact | Evidence connection |
|---|---|---|
| 1 | Event brief / requirements intake | planning, stakeholder requirements |
| 2 | Objectives and success-measures sheet | planning, measurement |
| 3 | Master timeline / workback plan | planning, document control |
| 4 | Event calendar and conflict view | portfolio and venue scheduling |
| 5 | Budget estimate and variance tracker | financial control |
| 6 | Vendor requirements document and comparable-quote matrix | supplier decisions |
| 7 | Venue evaluation and site-review checklist | venue decisions |
| 8 | Contract and approval tracker | supplier and approval handoff |
| 9 | Event logistics plan | integrated operations |
| 10 | Floor plan / room-setup specification | venue and setup communication |
| 11 | Banquet Event Order or function-sheet checklist | catering and operations |
| 12 | Run of show / production schedule | programme and live control |
| 13 | Stakeholder responsibility matrix and briefing pack | ownership and communication |
| 14 | Invitation, RSVP, and registration tracker | attendee management |
| 15 | Speaker/faculty/talent briefing sheet | programme coordination |
| 16 | Travel, transport, and accommodation manifest | attendee and speaker logistics |
| 17 | Catering, dietary, and hospitality requirements sheet | guest service and inclusion |
| 18 | AV / virtual-platform requirements and technical check | event technology |
| 19 | Staffing and volunteer roster with briefing checklist | people coordination |
| 20 | Event materials, freight, and inventory tracker | logistics and stock control |
| 21 | Safety/risk/insurance/permit checklist and contingency log | evidence, ownership, escalation |
| 22 | Event-day issue log and escalation matrix | live decision traceability |
| 23 | Post-event survey and feedback plan | evaluation design |
| 24 | KPI / ROI dashboard and post-event report | performance interpretation |
| 25 | Invoice, payment, and final-reconciliation checklist | financial closeout |
The code frequencies provide direct support for these outputs: event documents (DOC) appeared in 46 vacancies, budgets (BUD) in 44, technology (AVL) in 24, measurement (MET) in 23, registration (REG) in 21, safety or risk (SAF) in 19, staffing (STF) in 15, travel (TRV) in 11, inventory (INV) in 10, speaker/programme work (SPM) in 10, permits (PER) in 5, and CRM/lead work (CRM) in 4.
The artifacts should not become a collection of forms completed for their own sake. A useful course case should require cross-checks. The attendee count should reconcile with room capacity, catering quantities, staffing assumptions, transport, budget, and communication timing. The run of show should agree with supplier access, speaker readiness, AV cues, catering service, and venue limits. The closeout report should trace results back to the objectives defined at the start.
7. A vacancy-informed event coordination lifecycle
The evidence supports eight connected stages.
7.1 Initiate and align
Clarify purpose, audience, constraints, success measures, budget and date boundaries, assumptions, and decision rights. Produce a bounded event brief rather than planning from an ambiguous request.
7.2 Design the event
Translate objectives and audience needs into format, programme, capacity, service, access, communication, and experience requirements. Record trade-offs and unresolved questions.
7.3 Plan delivery
Break the work into deliverables, owners, dependencies, milestones, acceptance conditions, and reporting routines. Establish a controlled source of truth.
7.4 Source venues and suppliers
Define needs before asking for options. Compare like with like. Inspect or verify claims. Record the recommendation, gaps, conditions, approvals, and specialist review items.
7.5 Build the operating plan
Integrate budget, programme, registration, communications, staffing, hospitality, travel, AV, materials, risk, contingencies, and the run of show. Reconcile facts across documents.
7.6 Review readiness and hand over
Confirm deliverables, brief teams, test critical information flows, freeze controlled details when appropriate, and record open issues with owners and deadlines. Use ready / conditionally ready / escalate decisions.
7.7 Execute and control
Coordinate setup, registration, programme, suppliers, attendees, communications, and approved changes. Apply predefined responses within authority, preserve a factual log, and escalate issues requiring specialist or sponsor decisions.
7.8 Close and improve
Reconcile invoices and records, collect feedback, review results, capture lessons, assign follow-up actions, and archive a complete closeout pack.
8. Curriculum implications
The evidence supports an applied programme for aspiring and early-career coordinators, administrative or marketing professionals asked to organise events, hospitality and community professionals moving into coordination, and small-team event owners who need a repeatable method.
A suitable observable outcome is not “understand event planning.” It is the ability to prepare and defend a coherent coordination pack for one realistic low-to-moderate complexity event. The pack should reconcile dates, quantities, costs, owners, requirements, approvals, and decision records. It should show clear boundaries around regulated or safety-critical questions.
8.1 Suggested learning priorities
- Purpose, audience, stakeholder alignment, and measurable objectives.
- Event format, requirements, scope, assumptions, and decision rights.
- Work breakdown, ownership, schedule, and document control.
- Budget construction, forecasting, trade-offs, and reconciliation.
- Venue requirements, review, and defensible selection.
- Supplier briefs, comparable quotations, negotiation preparation, and authorised handoff.
- Programme, speakers, attendee journey, and registration.
- Logistics across rooms, catering, AV, transport, accommodation, signage, materials, and communications.
- Staffing, volunteers, briefings, handovers, and live team communication.
- Risk, issue, change, contingency, and escalation coordination.
- Readiness, run of show, event-day control, and service recovery.
- Evaluation, survey interpretation, financial close, and lessons learned.
- Responsible AI assistance for drafting, checking, and analysis with approved data and human verification.
8.2 Assessment design
Assessment should combine:
- decision scenarios with incomplete information and clear authority limits;
- numerical checks for budgets, quantities, capacities, and variance;
- artifact production with blank templates and realistic completed examples;
- consistency checks across plans;
- written recommendations that state evidence, trade-offs, assumptions, and approvals;
- a final applied case built around one event, one clear task, and one principal coordination pack.
Because BLS records high prevalence of prior experience and on-the-job training in the occupation [3], assessment should be explicit about what it can show. A simulated pack can demonstrate structured reasoning and artifact quality. It cannot show that a live event occurred or replace workplace supervision.
9. Responsible boundaries
Event coordination intersects with legal, safety, financial, personal-data, and access questions. The vacancy evidence supports teaching how to identify, document, assign, and escalate these matters. It does not support presenting a coordinator as the final authority in every domain.
9.1 Matters for qualified local owners
Applicable law, permits, insurance, contracts, tax, immigration, accessibility duties, food and alcohol rules, data protection, fire safety, crowd safety, structural engineering, rigging, electrical work, medical response, security, and emergency command depend on jurisdiction, event conditions, and organisational authority. A coordinator can maintain requirements and evidence, ask structured questions, track decisions, and confirm handoffs. Qualified local owners should make the relevant technical or regulated decisions.
9.2 Financial and commercial boundaries
Training can cover budgets, forecasts, bid comparison, and invoice checking. It should not imply authority to sign contracts, approve payments, make tax determinations, or commit an organisation without the learner’s actual delegated role.
9.3 Responsible AI use
AI can assist with clarification questions, first-draft work breakdowns, communication drafts, scenario generation, checklist critique, de-identified comment coding, and plain-language summaries. It should be used only through organisation-approved tools and permitted data. Dates, names, prices, capacities, calculations, commitments, and source claims require human verification. AI should not make safety, legal, medical, security, payment, supplier-selection, or attendee access decisions. Generated material remains a draft until an accountable person accepts it.
9.4 Claims boundaries
The report does not claim that the sample represents all vacancies. It does not claim employment outcomes, professional accreditation, equivalence with an external credential, or conformity with a standard. It does not certify any person, organisation, supplier, or event.
10. Limitations
- Purposive sample. The records were selected to analyse a defined role family, not to estimate population prevalence.
- Geographic skew. English-language U.S., Canadian, and UK records dominate because their public ATS and listing pages were more accessible.
- Dynamic pages. Vacancies can close, change, or disappear after the evidence freeze.
- Variable detail. First-party ATS pages often provide rich duties; some public national-list records provide only title, employer, location, date, identifier, and a narrower visible description.
- Shared listing page. Twenty-one distinct Canadian Job Bank records share one public search-results URL. They remain separate units because their employer, title, location and listing identifiers differ, but source-level review of those records depends on the frozen listing metadata.
- Derived summaries. The corpus uses concise paraphrases rather than bulk copies. Conservative coding was used where source detail was limited.
- Presence, not weighting. A count shows that a theme appears in a vacancy. It does not measure the time spent on the task or its importance within that job.
- Title ambiguity. “Coordinator,” “manager,” “producer,” and “specialist” do not have consistent seniority across employers.
- No inferential statistics. The study reports descriptive counts only. It does not compute sampling errors or population estimates.
- Occupational context is U.S.-specific. O*NET and BLS facts provide useful context but should not be generalised to other countries without local evidence.
- Course implication is interpretive. Curriculum recommendations are an evidence-informed synthesis, not proof that a particular course design will cause workplace performance or employment outcomes.
11. Conclusion
Across 100 current public vacancies, event coordination appears as a disciplined integration role. Employers ask people to combine planning, logistics, stakeholder communication, supplier and venue work, documentation, budgets, hospitality, event technology, risk awareness, live delivery, and improvement. The repeated pattern is not simply creativity or hospitality presence. It is the ability to turn an approved objective into an executable and traceable operating system for an event.
The most defensible educational response is an applied course built around one coherent event lifecycle, realistic decisions, numerical and documentation checks, reusable artifacts, live-delivery scenarios, and explicit escalation boundaries. Such a course can help learners practise the work described in the evidence while remaining honest about the continuing role of workplace experience, local policy, qualified specialists, and authorised decision-makers.
Sources
- O*NET OnLine. Meeting, Convention, and Event Planners, 13-1121.00. Updated 2026. Retrieved 30 August 2026. https://www.onetonline.org/link/details/13-1121.00
- U.S. Bureau of Labor Statistics. Occupational Outlook Handbook: Meeting, Convention, and Event Planners. 2025 employment base and 2025–2035 projection. Retrieved 30 August 2026. https://www.bls.gov/ooh/business-and-financial/meeting-convention-and-event-planners.htm
- U.S. Bureau of Labor Statistics. Occupational Requirements Survey: Meeting, Convention, and Event Planners. 2025 occupational requirements. Retrieved 30 August 2026. https://www.bls.gov/ors/factsheet/meeting-convention-and-event-planners.htm
- MTF Institute. Accepted vacancy corpus for Professional Certificate in Event Planning and Coordination. Evidence freeze 30 August 2026. One hundred records with source URLs, retrieval data, responsibility summaries, codes, and deterministic deduplication keys. Corpus SHA-256:
55937e362e7df657cb9c7d7c1404d18d316f5fbabc057490bf47e6f805856914.
The complete 100-record source register, including 80 unique URLs, is preserved in the accepted corpus. The method and field definitions accompanying this report are provided in methods.md and data-dictionary.md.
Continue learning
The capabilities examined in this report are developed in MTF Institute's Professional Certificate in Event Planning and Coordination through structured learning and applied practice.