Event Project Planning and Governance

Introduction

An event may appear to be a temporary public occasion, but professionally it is a complex project. It has a defined purpose, a beginning and an end, limited resources, interdependent activities, multiple stakeholders, operational risks, and measurable outcomes. A media launch, conference, music festival, award ceremony, brand activation, or public exhibition must therefore be planned and governed as an integrated system rather than as a collection of isolated tasks.

Event project planning translates an idea into an executable plan. Governance determines who has authority, who is accountable, how decisions are made, how information is recorded, and how deviations are controlled. Weak planning commonly produces scope confusion, budget overruns, late approvals, duplicated work, safety failures, and conflict among clients, sponsors, suppliers, creative teams, and venues. Strong planning does not eliminate uncertainty, but it makes uncertainty visible and manageable.

This chapter examines the principal planning documents and control mechanisms used in event management: the event brief, proposal, scope statement, work breakdown structure, schedule, milestones, risk and issue registers, reporting systems, and governance arrangements.

Learning Objectives

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

1. Explain the project-based nature of events and distinguish planning from governance.
2. Prepare an event brief, proposal, and scope statement.
3. Construct a work breakdown structure and use it to develop a schedule.
4. Identify dependencies, milestones, deliverables, assumptions, constraints, risks, and issues.
5. Design a governance structure with clear authority, accountability, escalation, and documentation.
6. Apply control systems to scope, time, cost, quality, safety, communication, and change.
7. Evaluate ethical, legal, technological, and professional implications of event governance.

1. Events as Temporary Projects

A project is a temporary endeavour undertaken to create a unique product, service, or result. An event satisfies this definition even when it is repeated annually. Each edition has different dates, audiences, suppliers, regulatory conditions, commercial targets, and operational risks. Repetition may provide organisational learning, but it does not remove the need for project-specific planning.

Event projects usually combine five dimensions:

• Strategic purpose: why the event exists and how it supports organisational or client objectives.
• Experience design: what participants should see, feel, learn, or do.
• Operational delivery: how venue, production, staffing, transport, catering, security, registration, and technical systems will function.
• Commercial management: how income, expenditure, sponsorship, procurement, and value will be managed.
• Governance and assurance: how authority, compliance, risk, quality, and accountability will be maintained.

These dimensions are interdependent. A decision to increase audience capacity may affect venue layout, staffing, security, insurance, ticketing technology, catering, accessibility, and budget. Planning must therefore reveal relationships between decisions rather than treating each department as independent.

Planning and governance distinguished

Planning answers: What must be achieved, by when, with what resources, and through which activities? Governance answers: Who is entitled to decide, who is responsible for delivery, how will performance be reviewed, and what happens when conditions change?

Planning without governance may produce a sophisticated schedule that nobody owns. Governance without planning may produce meetings and approvals without a credible route to delivery. Effective event management requires both.

2. From Event Idea to Authorised Project

The planning process begins before detailed scheduling. The event concept must be tested against strategic fit, feasibility, stakeholder expectations, legal requirements, available resources, and acceptable risk.

A useful progression is:

1. Concept: an initial idea or opportunity.
2. Event brief: a concise statement of purpose, audience, requirements, and success criteria.
3. Proposal or business case: a reasoned response describing the event solution, resources, costs, benefits, risks, and assumptions.
4. Authorisation: formal approval to proceed, usually through a signed agreement, purchase order, project charter, or governance decision.
5. Scope baseline: an agreed description of included and excluded work.
6. Detailed planning: decomposition into deliverables, activities, resources, dates, controls, and responsibilities.
7. Execution and control: delivery accompanied by monitoring, reporting, change control, and issue resolution.
8. Closure and evaluation: acceptance, settlement, documentation, learning, and reporting.

A common professional error is to begin procurement or public promotion before the event has been sufficiently defined. Early publicity can create commitments that exceed the approved scope or capacity. Authorisation should therefore precede irreversible expenditure and public promises.

3. The Event Brief

The event brief is the foundational communication document. It may be produced by a client, commissioner, sponsor, internal executive, or event manager. It should be concise enough to guide discussion but sufficiently precise to prevent major misunderstandings.

A robust event brief normally includes:

Objectives should be expressed as intended results rather than activities. “Promote the new product” is a broad intention; “generate 300 qualified demonstrations from invited industry professionals within two weeks of the launch” is more assessable. Objectives should be specific, measurable where possible, achievable, relevant, and time-bound, while recognising that qualitative outcomes such as reputation and audience experience also matter.

The brief should identify assumptions explicitly. An assumption is treated as true for planning purposes but has not yet been fully verified—for example, that a venue will permit rigging or that a sponsor will provide branded materials by a particular date. An untested assumption is a potential source of risk.

4. The Event Proposal and Business Case

A proposal converts the brief into a recommended solution. It is both a persuasive document and a planning instrument. Its purpose is not merely to describe an attractive event but to demonstrate that the proposed event is feasible and responsibly managed.

A professional proposal may contain:

• executive summary;
• interpretation of the brief;
• event concept and participant journey;
• proposed programme and format;
• venue and production approach;
• audience acquisition and communications plan;
• accessibility, inclusion, and sustainability approach;
• staffing and supplier strategy;
• preliminary schedule and key milestones;
• budget, payment terms, and contingencies;
• risk, safety, insurance, and compliance approach;
• governance and reporting arrangements;
• assumptions, exclusions, and client responsibilities;
• evaluation method and proposed deliverables.

The proposal should distinguish cost estimates from approved costs. It should also distinguish a contingency allowance from an unexplained buffer. A contingency is a planned financial provision for identified or reasonably foreseeable uncertainty; it should be governed and not automatically spent.

A proposal is stronger when it presents alternatives. For example, a hybrid event may offer wider reach but involve platform, connectivity, moderation, recording, and technical support costs. A comparison of options allows decision-makers to assess value, risk, and strategic fit rather than selecting an idea solely on creative appeal.

5. Scope Management

Scope defines the boundaries of the project. It specifies what the event team will produce and what is outside its responsibility. Scope management is especially important in events because stakeholders often add requests informally and because creative possibilities are practically unlimited.

Scope statement

A scope statement should include:

• project purpose and objectives;
• major deliverables;
• acceptance criteria;
• included work;
• explicit exclusions;
• constraints and assumptions;
• interfaces with client, venue, suppliers, and authorities;
• approval authority;
• change-control procedure.

A deliverable is a verifiable output, such as an approved floor plan, ticketing system, stage installation, media kit, or post-event report. An activity is work undertaken to produce a deliverable, such as “obtain three catering quotations.” Confusing deliverables with activities makes progress difficult to assess.

Scope creep and change

Scope creep is the uncontrolled expansion of requirements without corresponding adjustment to time, budget, resources, or risk. Not every change is undesirable. A change may improve strategic value or respond to a genuine regulatory or stakeholder need. The issue is whether it is assessed and authorised.

A basic change request should record:

1. requested change and reason;
2. impact on scope, time, cost, quality, safety, and stakeholders;
3. alternatives considered;
4. recommendation;
5. decision and authority;
6. resulting updates to baselines and documents.

A useful principle is that every approved change must have an owner, an implementation date, and a documented effect on the plan.

6. Work Breakdown Structures

The work breakdown structure (WBS) decomposes the total approved scope into progressively smaller components. It is deliverable-oriented: the highest level represents the project, the next levels represent major deliverables, and lower levels represent work packages that can be estimated, assigned, scheduled, and controlled.

The WBS is not simply a to-do list. It provides a common structure for estimating cost, allocating responsibility, creating schedules, tracking progress, and identifying omissions.

An illustrative event WBS might be organised as follows:

Event Project
├── 1. Project governance and administration
├── 2. Audience and communications
├── 3. Programme and content
├── 4. Venue and site operations
├── 5. Production and technology
├── 6. Suppliers, procurement, and contracts
├── 7. Guest services and accessibility
├── 8. Safety, security, compliance, and sustainability
├── 9. Event delivery
└── 10. Closure, evaluation, and reporting

Each branch should be decomposed only as far as useful. A work package is sufficiently defined when its output, owner, estimated effort, dependencies, acceptance criteria, and completion evidence are clear. Excessive decomposition creates administrative burden; insufficient decomposition hides complexity.

Responsibility assignment

The WBS should be connected to a responsibility assignment matrix. The RACI model is frequently used:

• Responsible: performs or coordinates the work.
• Accountable: owns the result and approves completion; ideally one person or role.
• Consulted: provides required input before a decision or output is finalised.
• Informed: receives relevant information after or during the work.

RACI is a governance aid, not a substitute for judgement. A matrix with many “accountable” persons for one deliverable may indicate unclear authority. Conversely, assigning no responsible person means the work is unlikely to be completed reliably.

7. Scheduling, Dependencies, and Milestones

A schedule translates work packages into activities with durations, relationships, resources, and dates. Event schedules must include not only public-facing programme times but also design, approvals, procurement, fabrication, testing, rehearsals, build, live operation, breakdown, settlement, and evaluation.

Activity relationships

Common dependency types include:

• Finish-to-start: activity B cannot start until activity A finishes. Example: final floor-plan approval before production ordering.
• Start-to-start: activity B may start when activity A starts. Example: audience promotion begins as registration infrastructure is launched.
• Finish-to-finish: activity B cannot finish until activity A finishes. Example: final technical documentation and venue approval may need to conclude together.
• Start-to-finish: uncommon; activity B cannot finish until activity A starts.

Dependencies may be logical, contractual, resource-based, or externally imposed. A venue access restriction, for example, can determine the entire build sequence.

A milestone is a significant point or event with zero planned duration, such as “contract signed,” “permit approved,” “ticket sales open,” “technical rehearsal complete,” or “event accepted by client.” Milestones help senior stakeholders review readiness without examining every task.

Critical path

In a network of dependent activities, the critical path is the longest sequence of activities determining the earliest possible project completion. Activities on this path have zero total float under the schedule assumptions. Delay to a critical activity can delay the project unless corrective action changes the sequence, resources, or duration.

For an activity, the standard forward-pass relationships are:

where ES is earliest start time, EF is earliest finish time, and d is activity duration, all measured in consistent time units. If a task has predecessors, its earliest start is normally the greatest earliest finish of those predecessors:

For a backward pass:

where LS is latest start time and LF is latest finish time. Total float is:

These relationships assume a deterministic activity-on-node schedule, fixed durations, and correctly specified dependencies. They do not by themselves account for resource constraints, probabilistic delays, calendars, or changing scope.

Worked scheduling example

Suppose three activities are sequential: A, “confirm venue,” takes 3 days; B, “approve layout,” takes 2 days and follows A; C, “place production order,” takes 4 days and follows B. Starting at day 0:

• A: ES = 0, EF = 0 + 3 = 3
• B: ES = 3, EF = 3 + 2 = 5
• C: ES = 5, EF = 5 + 4 = 9

The planned completion time is 9 working days. Because all activities form one uninterrupted sequence, each has zero float and the sequence is critical under these assumptions. If a parallel activity of 2 days begins at day 0 and is not a predecessor of C, its delay would not necessarily affect completion.

In practice, an event manager should validate a network schedule against staff availability, venue opening hours, supplier calendars, public holidays, approval response times, and technical constraints. A mathematically feasible schedule can still be operationally impossible.

8. Governance Architecture

Governance establishes the system through which the event is directed and controlled. It should be proportionate to event scale, risk, budget, public impact, and organisational complexity.

A typical governance structure may include:

• Sponsor or commissioning authority: owns the strategic case, funding commitment, and senior-level decisions.
• Steering group: represents key interests, resolves escalated matters, and reviews readiness.
• Event director or project manager: integrates planning and delivery, manages performance, and coordinates decisions.
• Workstream leads: own specialist areas such as production, marketing, venue, finance, guest services, and safety.
• Independent assurance or safety adviser: challenges plans and verifies compliance where appropriate.
• Suppliers and partners: deliver contracted outputs and report risks, dependencies, and performance.

The structure should define decision rights. For example, a production lead may approve technical details within an agreed budget, while only the sponsor may approve a major scope change or additional expenditure above a threshold.

Governance principles

1. Clarity: roles, authority, escalation routes, and acceptance criteria are written down.
2. Proportionality: controls match event risk and complexity.
3. Separation of duties: where practicable, no single person controls procurement, approval, payment, and supplier evaluation without oversight.
4. Transparency: decisions and assumptions are traceable.
5. Challenge: governance forums should test feasibility rather than merely endorse enthusiasm.
6. Timeliness: decisions must be made early enough to affect outcomes.
7. Accountability: named people own actions and results.

Governance meetings require purpose and discipline. A good agenda may include progress against milestones, new risks and issues, decisions required, changes requested, financial position, safety and compliance, upcoming dependencies, and action review. Minutes should record decisions, rationale where material, owner, deadline, and status.

9. Documentation and the Control Baseline

Documentation is not bureaucracy for its own sake. It creates a shared memory and evidence trail in environments where staff, suppliers, and conditions change rapidly.

Important records include:

• approved brief and proposal;
• scope statement and WBS;
• schedule and milestone plan;
• budget and procurement record;
• stakeholder map and communications plan;
• risk, issue, dependency, and assumption registers;
• design approvals and version history;
• contracts, permits, insurance, and certificates;
• safety plans, incident procedures, and accessibility arrangements;
• meeting minutes and decision log;
• change requests and approvals;
• supplier performance records;
• event-day logs and incident reports;
• acceptance records and post-event evaluation.

A document-control system should establish a naming convention, owner, version, approval status, access rights, review date, and retention period. The authoritative version must be identifiable. Multiple uncontrolled copies of a floor plan or running order can create serious safety and operational errors.

A baseline is the formally approved reference against which performance and changes are assessed. In event management, the principal baselines are scope, schedule, and budget. A baseline is not immutable; it changes only through authorised control.

10. Control Systems for Event Delivery

Control means comparing actual or forecast performance with the approved plan and taking informed action. It is not limited to correcting failure after the event; effective control is anticipatory.

Scope control

Use a change log, acceptance criteria, and regular scope reviews. Ask whether a requested addition is necessary, funded, feasible, safe, and consistent with the event purpose.

Schedule control

Track milestone status, forecast completion dates, outstanding approvals, supplier lead times, and critical dependencies. A useful status classification is: on track, at risk, delayed, or complete. Forecast dates are more informative than reporting only completed work.

Cost control

Maintain an approved budget, committed-cost record, actual expenditure, forecast final cost, and contingency balance. A simple forecast is:

This is an operational forecasting identity, not a guarantee. It assumes the estimate to complete includes known remaining work and that commitments are not omitted. Costs should be recorded in the same currency and treatment of tax, fees, deposits, and accruals should be defined.

Quality control

Quality criteria should be measurable or observable: correct branding, tested audio coverage, approved menu, accessible route, accurate registration data, or response time for guest support. Inspection, rehearsal, proofing, testing, and sign-off are control activities.

Risk and issue control

A risk is an uncertain event or condition that may affect objectives. An issue is a problem that has already occurred. They require different responses. A risk register may contain description, cause, consequence, likelihood, impact, rating, owner, response, trigger, and status. An issue log records immediate effect, interim containment, decision required, owner, due date, and resolution.

A qualitative risk score is sometimes calculated as:

This is a prioritisation aid, not a probability law. It is applicable only when likelihood and impact scales are defined consistently and the organisation accepts the method. It should not disguise severe low-probability risks, such as a catastrophic safety event, as unimportant merely because their product is numerically modest.

Typical responses are avoid, reduce, transfer, accept, or escalate. For example, an outdoor event may reduce weather exposure through a covered alternative, transfer some financial exposure through insurance, and retain residual risk through an approved contingency plan.

Readiness control

Before opening, a readiness review should verify venue access, staffing, supplier arrival, technical tests, permits, emergency procedures, accessibility, signage, registration, communications, payment systems, cleaning, security, and client acceptance. “Nearly ready” should be converted into specific evidence-based checks.

11. Stakeholders, Communication, and Decision-Making

Stakeholders include people or organisations that affect, are affected by, or perceive themselves to be affected by the event. They may include clients, audiences, employees, performers, sponsors, venue owners, regulators, residents, emergency services, suppliers, media, and online communities.

Stakeholder analysis should consider interest, influence, expectations, potential benefits, concerns, and preferred communication. A powerful sponsor may require formal decision reports; local residents may need advance information about traffic and noise; a disabled audience member may require consultation about access rather than merely receiving a generic statement of inclusion.

A communications plan should specify audience, message, channel, sender, timing, approval requirement, and record. Internal operational information should be timely and unambiguous. Public information should be accurate, accessible, brand-consistent, and legally appropriate.

Decision-making should be located as close as possible to the work while retaining appropriate oversight. Escalation is required when a matter exceeds delegated authority, threatens a critical milestone, introduces significant safety or legal exposure, or changes the approved business case.

12. Ethical, Legal, and Regulatory Governance

Event governance carries obligations beyond commercial success. Depending on jurisdiction and event type, requirements may include venue permissions, public assembly rules, occupational health and safety, fire and evacuation standards, food safety, alcohol licensing, music and image rights, employment law, data protection, accessibility, consumer protection, insurance, environmental controls, and noise or traffic regulation.

Compliance should be planned as a set of deliverables and approvals, not left to the final week. Responsibility for each permit or legal obligation must be assigned, and evidence must be retained.

Ethical governance includes:

• truthful communication about programme, price, sponsorship, and access;
• fair procurement and avoidance of conflicts of interest;
• protection of audience, employee, performer, and supplier welfare;
• responsible collection and use of personal data;
• non-discrimination and reasonable accessibility;
• transparent handling of cancellations and refunds;
• responsible environmental and community practices;
• safeguarding against harassment, exploitation, and unsafe working hours.

An event may be legally permissible yet ethically poor. For example, collecting more personal data than necessary may be technically possible but inconsistent with privacy principles. Governance should therefore consider legitimacy, proportionality, dignity, and public trust.

13. Technology and Artificial Intelligence

Project-management platforms can integrate schedules, actions, documents, approvals, supplier records, and dashboards. Digital ticketing, access control, streaming, audience analytics, virtual production, and collaborative design tools can improve reach and coordination. However, technology creates dependency on connectivity, cybersecurity, vendor availability, data quality, and staff competence.

Artificial intelligence may assist with drafting schedules, summarising meetings, identifying duplicate tasks, analysing feedback, generating communication variants, or flagging apparent schedule conflicts. It should not replace accountable professional judgement in safety decisions, legal interpretation, accessibility planning, supplier selection, or crisis communication. AI-generated content requires human verification for accuracy, bias, confidentiality, copyright, and appropriateness. Sensitive event data should not be entered into tools without an approved data-protection basis and contractual safeguards.

A technology control plan should identify system owner, access permissions, backup method, offline fallback, data retention, incident response, and manual alternative. Digital sophistication is valuable only when it improves reliable delivery.

14. Illustrative Case: The Riverfront Innovation Forum

Background

A fictional regional development agency commissions a one-day Riverfront Innovation Forum for 500 delegates, including entrepreneurs, investors, students, public officials, and journalists. The event includes a main stage, workshops, sponsor exhibits, livestreaming, catering, and an evening networking reception. The venue is a converted riverside warehouse with limited loading access and a history of water-level disruption.

Problem

The initial concept is ambitious but vague. The sponsor wants extensive branding and a high-profile speaker. The venue proposes a late access time, the production supplier requires an early technical load-in, and the communications team wants to open registration within two weeks. No one has defined who can approve additional costs or who owns emergency planning.

Analysis

The event manager converts the concept into a brief with objectives: achieve 500 registrations, deliver an accessible programme, obtain at least 85% positive delegate feedback, and generate 100 qualified follow-up contacts for sponsors. The manager identifies constraints: one loading bay, a fixed public transport disruption date, a restricted budget, and a requirement to livestream the main stage.

A WBS identifies governance, programme, venue, production, registration, sponsorship, safety, communications, and closure workstreams. The schedule reveals that venue access, floor-plan approval, power assessment, and production procurement are linked. The riverfront location becomes a high-priority risk with a trigger based on official water-level warnings.

Approach and solution

A steering group is established with the sponsor, venue representative, event director, safety lead, and finance representative. The event director receives authority for routine decisions within the approved budget; the sponsor must approve scope changes and expenditure above a defined threshold. A decision log and shared document repository are introduced.

The team creates two venue plans: the preferred riverside layout and a reduced-capacity alternative in an upper hall. A weather and water-level review is scheduled at defined intervals. Registration is delayed until capacity, accessibility routes, refund terms, and data notices are approved. The production supplier receives a written load-in requirement, and a technical rehearsal milestone is placed before final programme sign-off.

Outcome

The event proceeds with 462 delegates. A water-level warning causes the reception to move indoors, using the pre-approved alternative. The change increases catering cost but is authorised through the change process. The livestream experiences a brief interruption, but a local recording and backup connection preserve the main sessions. Sponsor follow-up targets are met, and the post-event report records both successful controls and weaknesses in workshop-room sound isolation.

Learning points

The case demonstrates that governance is not an obstacle to creativity. Clear authority allowed the team to adapt quickly without confusion. Early scope definition exposed the consequences of ambitious requirements. A realistic schedule made venue access a strategic dependency rather than a logistical detail. Contingency planning was effective because it was prepared, assigned, costed, and rehearsed before the risk materialised.

15. Challenges and Limitations

No planning system can predict every event condition. Stakeholders may provide incomplete information, political priorities may change, suppliers may fail, and audience behaviour may be difficult to forecast. Formal documents can also create false confidence if they are treated as complete regardless of evidence.

Common limitations include:

• schedules based on optimistic durations;
• risk scores that conceal low-frequency catastrophic events;
• governance forums that delay urgent decisions;
• excessive approval layers that discourage responsibility;
• WBS structures that omit interfaces between departments;
• dashboards that measure activity rather than outcomes;
• “lessons learned” reports that are not converted into changed practice;
• technology systems that fail during connectivity or power interruptions.

Professional judgement remains essential. The event manager must combine planning discipline with situational awareness, communication, ethical reasoning, and the ability to act under pressure. Plans should be reviewed at meaningful decision points and adapted through controlled change, not defended simply because they were approved earlier.

16. Best-Practice Planning Sequence

A practical sequence for a bachelor-level event project is:

1. clarify purpose, audience, outcomes, and sponsor expectations;
2. prepare and validate the event brief;
3. develop options and a feasible proposal;
4. obtain formal authorisation and define decision rights;
5. baseline scope, assumptions, exclusions, and acceptance criteria;
6. construct the WBS and responsibility matrix;
7. develop the integrated schedule, milestones, and critical dependencies;
8. prepare budget, procurement, risk, compliance, accessibility, and sustainability plans;
9. establish document control, reporting, and change management;
10. conduct design, supplier, safety, and readiness reviews;
11. deliver with live monitoring, logs, escalation, and contingency procedures;
12. close contracts, evaluate outcomes, record lessons, and secure acceptance.

This sequence is iterative rather than strictly linear. New information may require revision, but revision should be visible, authorised, and communicated to affected parties.

Chapter Summary

Event management is project management applied to a temporary, complex, stakeholder-rich experience. The event brief establishes purpose, audience, requirements, constraints, and success measures. A proposal converts the brief into a feasible solution and should distinguish estimates, assumptions, exclusions, risks, and approval requirements. Scope management defines included and excluded work and controls changes that could affect time, cost, quality, or safety.

The work breakdown structure decomposes deliverables into manageable work packages and supports estimating, responsibility assignment, scheduling, and control. Schedules express activities, durations, dependencies, milestones, and critical paths. Governance complements planning by defining authority, accountability, escalation, assurance, and decision records. Control systems monitor scope, time, cost, quality, risk, issues, readiness, and compliance against approved baselines.

Professional event governance requires accurate documentation, ethical procurement, legal compliance, accessibility, data protection, safety, and transparent stakeholder communication. Technology and AI can improve coordination and analysis but require human oversight, privacy safeguards, cybersecurity, and fallback arrangements. Effective event planning is therefore neither a purely creative exercise nor a purely administrative one: it is the disciplined integration of strategy, experience, operations, resources, risk, and accountable decision-making.

Key Terms

Accountability: Obligation to own a result and answer for performance.

Assumption: A proposition treated as true for planning purposes but not fully verified.

Baseline: An approved reference version of scope, schedule, budget, or another control dimension.

Change control: A formal process for assessing, approving, rejecting, and recording changes.

Critical path: The longest dependent sequence determining the earliest project completion.

Deliverable: A verifiable output produced by project work.

Dependency: A relationship in which one activity or decision relies on another.

Event brief: Foundational document describing purpose, audience, requirements, constraints, and success criteria.

Event governance: The structures and processes through which an event is directed and controlled.

Issue: A problem or condition that has already occurred.

Milestone: A significant scheduled point with no planned duration.

Proposal: A recommended event solution prepared in response to a brief.

Risk: An uncertain event or condition that may affect objectives.

RACI: Responsibility framework identifying responsible, accountable, consulted, and informed roles.

Scope: The boundaries of included and excluded project work.

Scope creep: Uncontrolled expansion of requirements without authorised adjustment of resources or baselines.

Steering group: Senior governance body that reviews progress and resolves escalated decisions.

Work breakdown structure: Deliverable-oriented decomposition of total approved project scope.

Review Questions

Short Answer Questions

1. What is the difference between event planning and event governance?
2. Identify four elements that should appear in an event brief.
3. Why is a work breakdown structure deliverable-oriented rather than merely a to-do list?
4. Distinguish a risk from an issue.
5. What information should be recorded in a change request?

Long Answer Questions

1. Explain how an event proposal converts an event brief into a feasible and governable solution.
2. Describe how a WBS, RACI matrix, and schedule work together to support event delivery.
3. Explain the meaning of the critical path and discuss its limitations in real event projects.
4. Design a governance structure for a 1,000-person public conference and justify the decision rights assigned to each role.
5. Discuss the ethical, legal, and documentation responsibilities involved in governing an event.

Analytical / Application Questions

1. An event client requests a celebrity performer ten days before the event. Analyse the likely effects on scope, budget, schedule, safety, contracts, and communications, and recommend a change-control response.
2. A festival has a late venue handover, a supplier delay, and an unresolved accessibility concern. Prepare a prioritised action and escalation approach using governance and control principles.
3. Design a concise risk-register entry and contingency response for an outdoor event threatened by severe weather. Explain the trigger, owner, response, and decision authority.

Multiple Choice Questions with Answers

Question 1

Which document primarily defines an event’s purpose, audience, requirements, constraints, and success measures?

A. Event brief

B. Issue log

C. Supplier invoice

D. Post-event survey

Correct Answer: A. Event brief

Question 2

What is the main purpose of a work breakdown structure?

A. To record audience complaints

B. To decompose approved scope into manageable deliverables and work packages

C. To replace the event budget

D. To provide a legal contract with the venue

Correct Answer: B. To decompose approved scope into manageable deliverables and work packages

Question 3

In a RACI matrix, who owns the result and approves completion?

A. Responsible

B. Accountable

C. Consulted

D. Informed

Correct Answer: B. Accountable

Question 4

An activity has an earliest start of day 5 and a duration of 4 working days. Using EF = ES + d, what is its earliest finish?

A. Day 1

B. Day 4

C. Day 9

D. Day 20

Correct Answer: C. Day 9

Question 5

Which statement best describes a milestone?

A. A significant point with zero planned duration

B. A supplier’s hourly rate

C. An unapproved change request

D. A list of audience demographics

Correct Answer: A. A significant point with zero planned duration

Question 6

Which situation is an example of scope creep?

A. A documented and approved change to the event format

B. A scheduled technical rehearsal

C. Adding unapproved deliverables without adjusting time or budget

D. Closing a completed work package

Correct Answer: C. Adding unapproved deliverables without adjusting time or budget

Question 7

What is the primary purpose of a decision log?

A. To advertise the event publicly

B. To record decisions, authority, rationale where relevant, owners, and dates

C. To calculate ticket taxes automatically

D. To replace emergency procedures

Correct Answer: B. To record decisions, authority, rationale where relevant, owners, and dates

Question 8

Which of the following is an issue rather than a risk?

A. The venue may lose power during the event

B. A performer might cancel

C. The required permit has already expired

D. Rain is forecast next month

Correct Answer: C. The required permit has already expired

Question 9

If actual cost to date is $18,000 and the estimate to complete is $7,500, what is the forecast final cost using the chapter’s forecasting identity?

A. $10,500

B. $18,750

C. $25,500

D. $135,000

Correct Answer: C. $25,500

Question 10

Why should AI-generated event plans receive human review?

A. AI outputs are automatically legally binding

B. Human review is needed for accuracy, bias, confidentiality, safety, and professional judgement

C. AI cannot generate any text

D. Human review eliminates the need for governance

Correct Answer: B. Human review is needed for accuracy, bias, confidentiality, safety, and professional judgement