Event Display Planning Workflow: Decisions and Handoffs

An event display planning workflow connects decisions, documents and people from the first brief to the return of the stand. Each stage needs an owner, an agreed input, a review point and a clear handoff. Dates come from the actual event calendar, supplier capacity and technical requirements, rather than a universal number of weeks.

This guide focuses on controlling information and decisions. For the physical work, use the companion production and handover guide and the responsible contractor’s approved methods.

Start with the event and the decisions still open

Record the organiser, venue, event edition, allocated plot, open sides and booked services. Obtain the current exhibitor manual and official deadlines. A previous edition’s plan can identify questions, but it does not establish this edition’s rules or access arrangements.

Then define the visitor activities: viewing a product, watching a demonstration, discussing a project, attending a presentation or arranging follow-up. Identify the staff, equipment, content, storage and services needed for each activity. Agree the budget scope and who can approve changes.

A useful brief also lists uncertainties. A demonstration may depend on a product arriving, a claim being approved, a service being ordered or a particular operating condition being accepted. Give each uncertainty an owner and a date for resolution.

Use stages with visible release conditions

Stage	Decision or evidence	Handoff
Brief	Activities, plot information, budget scope, responsibilities and unresolved questions	Agreed inputs for layout and supplier proposals
Design review	Visitor routes, equipment, dimensions, storage and operating needs	Recorded design decisions and items requiring technical review
Technical and event review	Required drawings, calculations, material records, submissions and service orders	Documented status, conditions and outstanding actions
Production release	Authorised drawing revision, artwork, samples, equipment and agreed scope	Controlled production inputs and acceptance checks
Delivery and installation	Booked access, handling, packing, crew responsibilities and approved work methods	Installed stand with recorded checks and open issues
Show operation	Staff briefing, activity readiness, support contacts and agreed follow-up process	Daily operating records and assigned actions
Return and review	Inventory, damage, actual costs, useful contacts and commercial outcomes	Storage or return decisions and improvements for the next event

A release condition is a decision to proceed with a defined scope. It does not replace an organiser’s permission, an inspection or a competent person’s technical assessment. Record partial releases explicitly so that a team does not mistake approval of graphics for approval of the entire structure.

Build the schedule from dependencies

Work backwards from the official access and opening times. Include required submission dates, review periods, supplier production capacity, artwork, equipment delivery, packing, transport, unloading and installation. Allow time to resolve questions and correct defects where the project permits it.

Use the actual submission route and deadline for the event. For example, Messe Frankfurt distinguishes stand construction submissions from fire protection and safety requests. Sending one type of document does not necessarily complete the other process.

Assign dates to decisions as well as tasks. An artwork deadline is meaningful only if the person approving it is available and has the correct dimensions, translations and content. A transport date depends on packing readiness and a permitted delivery slot; do not arrange arrival before access opens without an authorised arrangement.

Keep one agreed version of each input

• Give drawings, artwork and schedules a revision identifier and date.
• Record who approved each item, for what purpose and with what conditions.
• Identify superseded files so that a workshop or installer can recognise the current release.
• Keep event correspondence, service confirmations and technical responses with the relevant task.
• Provide an accessible contact list and essential documents for the site team if connectivity is limited.

A shared task tracker can help, but the tool does not resolve unclear authority. Agree how urgent decisions are recorded and how the team receives a changed revision. A message saying “looks good” should be clarified when its scope is ambiguous.

Report evidence and exceptions

Progress reports should distinguish completed work, supporting evidence, unresolved issues and the next decision. Photographs can show finishes or assembly progress; they do not by themselves verify hidden connections, electrical testing or structural compliance.

When a change arrives, record the request, affected drawings or components, cost, timing, technical consequences and person authorised to decide. Ask whether event submissions or service orders also need revision. Tell every affected team when the decision is released.

If a milestone slips, identify the downstream effect and available choices. These might include reducing an activity, changing a finish or postponing a non-essential feature, subject to approval and feasibility. Avoid silently compressing technical review or treating an improvised repair as an accepted design change.

Separate handover from opening readiness

The installation team and exhibitor should agree checks for the delivered scope, with competent specialists responsible for their own technical work. Record incomplete items, the owner, the proposed resolution and any restriction on use.

The exhibitor also needs an operating check: can staff explain the product, demonstrate it as intended, access storage, use the agreed lead process and contact support? Test content and equipment in the actual conditions where possible. Use approved spares and the responsible provider for faults; follow equipment instructions and event conditions for power, charging and storage.

Keep a daily issue list during the show. Distinguish a cosmetic defect from a problem that requires the affected activity to stop. Staff should know who can make that decision and how to obtain assistance.

Close the workflow with useful records

After dismantling, reconcile returned items, damage, missing components, storage conditions and charges. Record what can be reused, what requires repair and what needs a new approval or adaptation for another event.

Compare planned and actual costs for the same scope. Review completed demonstrations, relevant meetings and follow-up outcomes against the original objectives. Keep revenue, gross profit and event costs distinct when assessing exhibition return on investment. Neither a busy stand nor an on-time installation proves commercial success.

Frequently asked questions

Who owns the event display planning workflow?

Name a coordinator for the overall record and handoffs, then assign a responsible person to each decision and specialist task. Coordination does not transfer the technical or contractual responsibilities of the organiser, exhibitor or contractor.

How early should planning start?

Start when the event and participation scope are known. Establish the schedule from official deadlines, complexity, approvals, production and transport needs. There is no lead time that suits every stand or European venue.

Does a modular display remove the need for approvals?

No. Review the specific configuration, equipment, activities and event rules. A familiar component system does not establish that every arrangement is permitted or that a previous approval applies.

What should a supplier receive first?

Send the current event manual, allocated plot, intended activities, equipment, budget scope and key dates. Identify open decisions and request a written scope, exclusions, responsibilities and proposed review points.

Discuss the event brief with Adam Expo Stand to confirm availability and the services, partners and responsibilities proposed for your project.