Event Theories, Models and Frameworks

Introduction

Event management is more than the coordination of venues, suppliers, schedules and guests. It is the planned design of a temporary experience involving multiple actors, resources, technologies, meanings and risks. A media launch, music festival, exhibition, sporting event or public ceremony succeeds when these elements are aligned with a clearly defined purpose and with the expectations of stakeholders.

Theories and frameworks help event managers move beyond intuition. They provide structured ways to identify interests, understand interdependence, design participant experiences, manage projects and evaluate outcomes. No single model explains every event. Effective practice therefore involves combining complementary perspectives while recognising their assumptions and limitations.

This chapter introduces stakeholder theory, systems theory, the experience economy, service-dominant logic, project life-cycle models, the 5Ws framework and principles associated with the Event Management Body of Knowledge (EMBOK). Together, these frameworks form a foundation for analysing and managing events in professional settings.

Learning Objectives

By the end of this chapter, students should be able to:

1. Explain the purpose and assumptions of major event-management theories.
2. Identify and analyse event stakeholders and their competing interests.
3. Apply systems thinking to event inputs, processes, outputs and feedback.
4. Use experience-economy and service-dominant-logic concepts to design value for participants.
5. Apply project life-cycle models to event planning and delivery.
6. Use the 5Ws framework to clarify event purpose and operating requirements.
7. Relate event decisions to EMBOK domains and professional competencies.
8. Critically evaluate the strengths, limitations and ethical implications of these frameworks.

1. Events as Managed Temporary Systems

An event is a planned or purposeful occasion that occurs within a defined period and location, although contemporary events may combine physical and digital environments. Events are temporary, but their effects may be long term. They can influence brand reputation, community identity, destination image, public opinion, employment, revenue and environmental conditions.

A useful conceptual distinction is between the event product and the event experience. The product includes tangible and operational elements such as the venue, programme, ticket, stage, catering and transport. The experience includes what participants perceive, feel, remember and share. Two events with similar physical resources may produce very different experiences because of differences in service quality, atmosphere, audience expectations and cultural meaning.

Events also display several characteristics that complicate management:

• They are often intangible before delivery; participants purchase a promise of future value.
• Production and consumption frequently occur simultaneously.
• Capacity is perishable; an unused seat or hotel room cannot normally be stored for later sale.
• Quality is variable because employees, volunteers, suppliers and audiences interact in real time.
• Events are co-created by organisers, participants, sponsors, performers, authorities and communities.
• Outcomes are multidimensional, including financial, social, cultural, media and environmental outcomes.

These characteristics explain why event managers need conceptual models rather than relying only on checklists.

2. Stakeholder Theory

2.1 Meaning and purpose

Stakeholders are individuals, groups or organisations that affect, or are affected by, an event. Stakeholder theory argues that organisational decisions should consider the interests and legitimate claims of relevant stakeholders rather than treating shareholders or clients as the only important parties.

Typical event stakeholders include:

• event owners, clients and investors;
• attendees, audiences, delegates and participants;
• performers, speakers, athletes and exhibitors;
• sponsors, advertisers and media partners;
• venues, caterers, transport providers and technical suppliers;
• employees, freelancers and volunteers;
• local residents, businesses and community organisations;
• government departments, regulators, police, emergency services and licensing authorities;
• advocacy groups concerned with accessibility, labour, culture or the environment.

Stakeholders do not possess equal power, but less powerful groups may still have strong legitimacy. For example, residents affected by noise may have limited financial influence but a legitimate interest in operating hours and traffic management.

2.2 Stakeholder identification and analysis

A practical analysis begins by asking four questions:

1. Who can influence event decisions?
2. Who experiences benefits or costs?
3. Who has legal, contractual, ethical or cultural claims?
4. Which relationships could create support, conflict or risk?

Managers commonly assess stakeholders using power, legitimacy and urgency. Power concerns the ability to influence decisions or resources. Legitimacy concerns whether a claim is appropriate or recognised. Urgency concerns the time sensitivity of the claim.

A power–interest matrix can support prioritisation:

This matrix is not a substitute for judgement. Stakeholder positions may change during the event. A community group that initially has low influence may gain public support after a safety or environmental concern becomes visible.

2.3 Stakeholder engagement

Engagement should be proportionate and purposeful. Consultation asks for views; participation gives stakeholders a role in shaping decisions; collaboration involves shared problem-solving or governance. Effective engagement includes clear information, accessible communication, documented commitments and feedback mechanisms.

A sponsor may seek brand visibility, while a public authority may prioritise safety and compliance. An event manager must negotiate these interests without allowing one stakeholder to undermine public welfare. Stakeholder management therefore involves both relationship building and ethical boundary-setting.

2.4 Limitations

Stakeholder theory can become vague if every affected person is treated as equally important. It may also conceal power inequalities when consultation is symbolic rather than influential. Managers should therefore record whose interests are represented, whose are absent and how conflicts were resolved.

3. Systems Theory and Event Interdependence

3.1 The event as an open system

Systems theory views an event as an open system that exchanges resources, information and impacts with its environment. An event is not an isolated programme; it is connected to transport networks, suppliers, communities, media, regulations, weather, technology and wider economic conditions.

A simplified event system contains:

• Inputs: objectives, funding, people, information, equipment, permissions and time.
• Transformation processes: design, procurement, marketing, rehearsal, service delivery and coordination.
• Outputs: attendance, experiences, media content, revenue, learning and social outcomes.
• Feedback: complaints, surveys, incident reports, financial results, digital engagement and stakeholder reviews.
• Environment: laws, culture, economy, climate, competitors, technology and public expectations.

Figure: An event as an open system with feedback and environmental influence.

3.2 Interdependence and emergence

Systems thinking emphasises that a problem in one area can affect the whole event. A late delivery may delay stage construction, which reduces rehearsal time, increases safety risk and damages the audience experience. Conversely, a strong digital registration system may improve queue management, data quality and post-event communication simultaneously.

Events also display emergent properties. Atmosphere, trust and reputation are not produced by one department. They emerge from interactions among design, staff behaviour, audience composition, cultural expectations and unexpected incidents.

3.3 Feedback and control

Feedback allows managers to compare intended performance with actual conditions. During delivery, feedback may include crowd-density observations, queue times, social-media sentiment, weather information and radio reports. Feedback is useful only when someone has authority and resources to act on it. Collecting data without decision procedures creates the appearance of control rather than actual control.

4. The Experience Economy

The experience economy proposes that organisations increasingly compete by staging memorable experiences rather than selling only goods or basic services. For events, this perspective is especially important because the participant’s emotional, sensory, social and symbolic response is often the central value proposition.

Four broad experience realms are commonly identified:

A single event can combine all four. A trade exhibition may entertain visitors through demonstrations, educate them through seminars, immerse them in product simulations and create an attractive environment for networking.

Experience design involves the intentional coordination of touchpoints. These may include ticket purchase, arrival, welcome, wayfinding, programme content, food, staff interaction, accessibility, mobile communication and departure. The event manager should ask not only, “What will happen?” but also, “What should the participant notice, feel, remember and share?”

The experience perspective also creates responsibilities. Emotional intensity should not be manufactured through deception, unsafe crowding or exploitative design. Accessibility must be treated as part of experience quality, not as an optional accommodation.

5. Service-Dominant Logic and Value Co-Creation

Service-dominant logic views service—the application of knowledge and skills for the benefit of another—as the basis of exchange. Physical goods, such as tickets, badges, merchandise or venue facilities, are resources that support service rather than the entire value proposition.

Three implications are especially relevant to events:

1. Value is co-created. Organisers provide a platform, but participants, performers, sponsors, staff and communities contribute to the final experience.
2. Value is contextual. The same programme may be valuable to one participant and irrelevant to another because value depends on personal goals, culture, timing and social setting.
3. Resources are integrated. Event value depends on combining the knowledge and resources of many actors, including transport providers, digital platforms, public authorities and audiences.

For example, a conference organiser may provide speakers and rooms, but professional value is co-created through delegate questions, informal networking, online discussion and the application of learning after the event. A manager should therefore design opportunities for participation rather than treating audiences as passive recipients.

Service-dominant logic does not mean that organisers can transfer all responsibility to participants. The organiser remains responsible for a safe, inclusive and reliable service platform, transparent terms and competent coordination.

6. Project Life-Cycle Models for Events

Events are temporary projects with a defined objective, a start and finish, constrained resources and a distinctive combination of tasks. A conventional project life cycle includes initiation, planning, execution, monitoring and control, and closure. In practice, these phases overlap and may repeat.

6.1 Initiation and feasibility

Initiation defines the event concept, purpose, client expectations, target audience, preliminary scope and success criteria. Feasibility analysis considers market demand, financial viability, legal permissions, venue suitability, operational capability, environmental effects and reputational risk.

A feasibility decision should distinguish assumptions from verified information. For example, “the venue can accommodate 2,000 people” is not sufficient unless capacity, configuration, emergency egress, accessibility and licensing conditions have been checked.

6.2 Planning and design

Planning converts the concept into an integrated management plan. Important components include scope, schedule, budget, procurement, staffing, communications, marketing, risk, health and safety, accessibility, sustainability, technology and evaluation.

A work breakdown structure divides the event into manageable deliverables and activities. Dependencies must be identified: marketing may begin before all production details are finalised, but ticket release may depend on confirmed capacity and licensing.

6.3 Execution and monitoring

Execution includes supplier mobilisation, installation, rehearsals, participant arrival, programme delivery, service operations and incident response. Monitoring compares actual conditions with the plan and authorises corrective action. Event environments are dynamic, so a good plan must support controlled adaptation rather than rigid adherence to obsolete assumptions.

6.4 Closure and evaluation

Closure includes dismantling, supplier settlement, incident documentation, data protection, lost-property procedures, stakeholder reporting and lessons learned. Evaluation should measure both outputs and outcomes. Attendance is an output; increased brand trust, professional learning or community benefit is an outcome.

A simple performance indicator can be expressed as:

Here, actual result and target result must use the same unit and definition. The measure is meaningful only when the target is specified in advance and the indicator captures a relevant objective. For example, if 840 of a target 1,000 delegates attend, the achievement rate is 84%. This does not by itself establish event success because satisfaction, cost, safety and strategic outcomes also matter.

6.5 Predictive, iterative and hybrid approaches

A predictive approach defines much of the scope and schedule in advance. It is useful where regulatory approvals, construction, procurement and safety controls require formal sequencing. An iterative approach develops elements through repeated testing and feedback, which is useful for digital engagement, content design or audience communications. A hybrid approach combines both: safety infrastructure may follow a predictive plan while the mobile application and social content are refined iteratively.

7. The 5Ws Framework

The 5Ws framework provides a concise method for defining an event:

• Why? What is the purpose, need or strategic objective?
• Who? Who owns, funds, delivers, attends, benefits from or is affected by it?
• What? What is the event concept, content, format and scope?
• When? What date, duration, milestones and seasonal conditions apply?
• Where? What venue, destination, platform and surrounding infrastructure are appropriate?

Some practitioners add “How?” to convert the questions into an implementation framework. The 5Ws should be used early, but revisited throughout the project. A change in “why,” such as a shift from sales generation to public education, may require changes in audience, content, venue and evaluation.

The framework is valuable because it exposes ambiguity. A proposal that describes an attractive theme but cannot explain its purpose, ownership, audience or location is not yet a workable event concept.

8. Event Management Body of Knowledge

The Event Management Body of Knowledge (EMBOK) is a competency-oriented framework that organises event management knowledge into domains, processes and phases. Although versions and professional interpretations may differ, EMBOK is commonly associated with five broad domains:

1. Design: concept, theme, content, programme and experience design.
2. Administration: governance, finance, procurement, contracts, human resources and documentation.
3. Marketing: market analysis, positioning, communications, promotion, sales and public relations.
4. Operations: venue, logistics, production, technology, catering, transport and service delivery.
5. Risk: safety, security, emergency planning, legal compliance, insurance and business continuity.

These domains are not independent departments. Marketing decisions affect operations; design affects risk; administration affects procurement; risk controls affect participant experience. EMBOK is most useful as a completeness check and professional language for multidisciplinary teams.

The framework can be applied by mapping each major work package to relevant domains. For instance, an outdoor film festival may require design analysis of programme and atmosphere, administration analysis of licences and contracts, marketing analysis of audience segments, operations analysis of screens and power, and risk analysis of weather, crowd movement and emergency response.

9. Integrating the Frameworks: An Applied Case

Illustrative case: Riverside Media and Culture Festival

Background. A city cultural office commissions a two-day festival featuring local music, short films, food vendors and workshops. The proposed site is a riverside park. The event aims to increase participation in local culture, support creative enterprises and improve the city’s public image.

Problem. The first proposal focuses heavily on performances and sponsorship visibility but gives limited attention to residents, accessibility, transport, weather, waste and emergency planning. Nearby residents are concerned about noise and congestion. The sponsor wants extensive branding, while community groups fear commercialisation.

Analysis. Using the 5Ws, the team clarifies that the primary purpose is cultural participation and local enterprise development, not merely attendance. Stakeholder analysis identifies the city office, residents, artists, vendors, sponsor, audience, transport authority, emergency services and environmental groups. Systems analysis shows that the riverside location creates dependencies among weather, ground conditions, transport, power, crowd flow and waste management.

The experience-economy perspective leads to a coherent visitor journey: accessible arrival, clear wayfinding, discovery zones, participatory workshops and a comfortable departure experience. Service-dominant logic encourages artists, residents and visitors to contribute stories and activities rather than simply consume a programme.

The project life cycle is applied as follows:

EMBOK mapping exposes omissions in the initial proposal. Administration adds insurance and contracts; operations adds accessible toilets and transport coordination; risk adds a weather threshold and evacuation procedure; marketing adds audience communication beyond sponsor promotion.

Approach and solution. The team establishes a resident liaison group, limits amplified sound after an agreed time, provides a quiet zone, publishes transport information and creates an accessible route plan. A weather contingency allows selected activities to move indoors or be cancelled according to predefined criteria. Sponsor branding is integrated into the design without obscuring community content. Volunteers receive role-specific training and an escalation procedure.

Outcome. In this illustrative scenario, the festival achieves strong attendance and positive local-media coverage, but evaluation also identifies long queues at one entrance. The post-event review recommends additional entry points, improved real-time communication and earlier resident consultation.

Learning points. The case demonstrates that event quality is systemic. A strong programme cannot compensate for poor access or unsafe operations. Stakeholder legitimacy matters alongside sponsor power. Experience design must include arrival, participation and departure. Frameworks are most useful when they reveal connections and omissions rather than when they are completed as paperwork.

10. Governance, Ethics and Contemporary Practice

Event frameworks must be applied within legal and ethical boundaries. Key responsibilities include health and safety, accessibility and non-discrimination, privacy and data protection, fair labour practices, intellectual property, responsible alcohol service, safeguarding and environmental stewardship.

Data-driven events create additional governance questions. Registration systems, facial recognition, behavioural analytics and targeted marketing may improve convenience or security, but they can also create surveillance, exclusion and data misuse. Consent should be informed, data collection proportionate and retention limited to legitimate purposes. AI tools may assist with scheduling, sentiment analysis, translation, accessibility or scenario modelling, but managers must check accuracy, bias, privacy and accountability. AI-generated content should not replace human review of safety-critical or culturally sensitive decisions.

Sustainability should be treated as a systems issue rather than a promotional label. Managers should consider procurement, energy, transport, food, materials, waste, local economic effects and post-event restoration. Claims such as “green event” require evidence and transparent boundaries; otherwise they risk greenwashing.

11. Limitations and Critical Use of Models

Models simplify reality. Stakeholder matrices may reduce relationships to static categories. Systems diagrams may imply clear boundaries where events are actually porous and political. Experience models can overemphasise pleasurable consumption and understate labour, inequality or cultural conflict. Project life cycles may suggest orderly progression despite frequent uncertainty. EMBOK domains can become bureaucratic silos if teams fail to integrate them.

Critical use therefore requires three habits:

1. State the purpose for which a framework is being used.
2. Identify what the framework leaves out, including marginalised voices and unintended impacts.
3. Combine evidence, professional judgement and stakeholder dialogue rather than treating a model as an automatic answer.

Best-Practice Principles

• Begin with a clear purpose and measurable, ethically appropriate objectives.
• Map stakeholders early and revisit the analysis as circumstances change.
• Treat the event as an interconnected system rather than a collection of departments.
• Design the complete participant journey, including access, waiting and departure.
• Build participation and feedback into the service model.
• Use life-cycle planning with explicit assumptions, dependencies and contingency actions.
• Apply EMBOK domains as an integration and completeness tool.
• Document decisions, responsibilities, approvals and escalation routes.
• Evaluate financial, experiential, social, environmental and safety outcomes together.
• Use technology and AI transparently, proportionately and with human accountability.

Chapter Summary

Event management theories provide different but complementary ways to understand temporary experiences. Stakeholder theory identifies the people and organisations whose interests shape or are shaped by an event. Systems theory explains interdependence among inputs, processes, outputs, feedback and the external environment. The experience economy focuses attention on memorable, meaningful participant experiences, while service-dominant logic emphasises value co-creation among organisers, participants and other actors.

Project life-cycle models structure work from initiation and feasibility through planning, execution, monitoring and closure. The 5Ws framework clarifies purpose, participants, content, timing and location. EMBOK organises professional knowledge across design, administration, marketing, operations and risk. Used together, these frameworks support more complete analysis and better decisions.

Their value depends on critical application. Managers must recognise power differences, uncertainty, ethical responsibilities, accessibility, environmental impacts and the limits of simplified models. A professionally managed event aligns strategic purpose, stakeholder interests, participant experience and operational control while remaining capable of learning and adaptation.

Key Terms

Stakeholder: An individual, group or organisation that affects or is affected by an event.

Stakeholder theory: A perspective that considers the legitimate interests of multiple parties in organisational decisions.

Systems theory: An approach that analyses an event as an interconnected open system.

Input: A resource or condition required by an event system.

Process: An activity that transforms event inputs into services or outcomes.

Output: An immediate product or result of event delivery.

Feedback: Information used to compare actual conditions with intended performance.

Emergence: A property arising from interactions among system elements rather than from one element alone.

Experience economy: The view that memorable experiences are a major source of organisational value.

Experience realm: A category such as entertainment, education, escapism or esthetics describing participant involvement.

Service-dominant logic: A perspective that treats service and the application of skills as the basis of value exchange.

Value co-creation: The joint production of value by organisers, participants and other stakeholders.

Project life cycle: The sequence of phases through which a temporary project develops and closes.

Feasibility: The assessment of whether an event is viable, lawful, affordable and operationally achievable.

5Ws framework: A method based on why, who, what, when and where.

EMBOK: The Event Management Body of Knowledge, a framework for organising event-management competencies.

Governance: The structures and processes used to direct, control and hold an event accountable.

Contingency: A planned response to a possible change, disruption or emergency.

Outcome: A longer-term effect or change produced by an event.

Review Questions

5 Short Answer Questions

1. What is the difference between an event product and an event experience?
2. Identify four stakeholder groups commonly involved in an event.
3. What are the main elements of an event viewed as an open system?
4. State the five questions in the 5Ws framework.
5. Name the five broad EMBOK domains discussed in this chapter.

5 Long Answer Questions

1. Explain how stakeholder theory can help an event manager address conflicting interests.
2. Discuss the contribution of systems theory to event planning and operational control.
3. Explain the experience economy and service-dominant logic, showing how they differ.
4. Describe the stages of a project life cycle and explain why event projects require flexibility.
5. Evaluate the strengths and limitations of using EMBOK as a professional planning framework.

3 Analytical / Application Questions

1. A city plans a large outdoor concert in a residential district. Apply stakeholder theory and systems theory to identify major risks, relationships and feedback mechanisms.
2. Design a participant experience for a one-day professional conference using the experience-economy and service-dominant-logic perspectives.
3. Use the 5Ws and EMBOK domains to analyse whether a proposed campus cultural festival is ready to proceed to detailed planning.

Multiple Choice Questions with Answers

Question 1

Which statement best reflects stakeholder theory in event management?

A. Only the event owner’s financial interests should guide decisions.

B. Event decisions should consider parties that affect or are affected by the event.

C. Stakeholders are limited to people who purchase tickets.

D. Stakeholder interests should be considered only after the event.

Correct Answer: B. Event decisions should consider parties that affect or are affected by the event.

Question 2

In systems theory, complaints collected after an event are primarily an example of what?

A. Input

B. Transformation process

C. Feedback

D. External environment

Correct Answer: C. Feedback

Question 3

Which experience realm involves active participation and immersion?

A. Entertainment

B. Educational

C. Escapist

D. Esthetic

Correct Answer: C. Escapist

Question 4

Service-dominant logic suggests that event value is mainly:

A. Embedded entirely in the ticket.

B. Co-created by multiple actors in context.

C. Determined only by the venue’s physical quality.

D. Created exclusively by sponsors.

Correct Answer: B. Co-created by multiple actors in context.

Question 5

Which project phase normally includes feasibility assessment and confirmation of purpose?

A. Initiation

B. Execution

C. Closure

D. Dismantling

Correct Answer: A. Initiation

Question 6

In the 5Ws framework, the question “Why?” primarily identifies the event’s:

A. Venue

B. Audience

C. Strategic purpose

D. Schedule

Correct Answer: C. Strategic purpose

Question 7

Which EMBOK domain most directly includes emergency planning and safety controls?

A. Marketing

B. Design

C. Administration

D. Risk

Correct Answer: D. Risk

Question 8

An event reaches 840 attendees against a target of 1,000. Using the achievement-rate formula, what percentage is achieved?

A. Seventy-four percent

B. Eighty-four percent

C. Ninety-four percent

D. One hundred and nineteen percent

Correct Answer: B. Eighty-four percent

Question 9

Which is the best example of value co-creation at a conference?

A. The organiser prints badges before arrival.

B. The venue supplies chairs without participant interaction.

C. Delegates create professional value through questions and networking.

D. A sponsor pays for exclusive advertising.

Correct Answer: C. Delegates create professional value through questions and networking.

Question 10

Why should event frameworks be used critically?

A. They eliminate the need for professional judgement.

B. They are legal documents that cannot be adapted.

C. They simplify reality and may omit power, uncertainty or marginalised perspectives.

D. They apply only to festivals and not to business events.

Correct Answer: C. They simplify reality and may omit power, uncertainty or marginalised perspectives.