Trade fair day POI management: Gate, WC, press desk — all live
POI (Point of Interest) is an abbreviation for meaningful points on the map: entrance gates, restrooms, press center, dining area, first aid, parking connection. These are marked by the designer before the fair. The real issue is that their status changes on the day of the fair. A static plan showing «WC» doesn't convey that the block is under maintenance in the afternoon.
Field teams try to bridge this gap by phone. A gate closes, the information desk is called, visitors are directed to the wrong corridor. Live POI management updates the same information on the map, freeing up the operations phone and reducing visitors going to the wrong point.
Static map, dynamic reality
One of the Hall 3 entrances closes in the afternoon due to transport. A WC block is temporarily taken for maintenance. The press center is moved one hall further. These are not visible on a static plan; visitors only find out when they arrive at the gate. The cost at that moment is not just wasted time: Queues form, the press team is delayed, and the exhibitor perceives the «fair as disorganized».
Live POI status is when the organizer marks a point on the map as «open», «restricted», or «closed». When visitors open the map, they see the current information. The operations team doesn't have to write a separate announcement for every change; critical changes can be supported with a short push notification or SMS, but the primary source should be the map.
The failure scenario is clear: The gate is closed, but still shown as open on the map, security personnel are not in place, visitors turn back and pile up at the information desk. This chain demonstrates that POI updates are not a «small task».
POI types and layers
Keeping all points on the same layer clutters the map. Visitors looking for a WC don't need to see the loading gate, and the security team looking for an emergency exit doesn't need to see the dining area. In QEMENT, POIs are grouped by layer logic; visitors only open what they need.
- Access: Main entrances, VIP entrance, loading gate, parking connection
- Services: WC, baby care room, disabled access, dining area
- Operations: Press desk, registration point, information desk, organizer's office
- Security: First aid, assembly point, emergency exit
There is a trade-off in layer design. Too many fine-grained layers tire the visitor; too coarse layers expose security or logistics information to the general visitor. The solution in most trade fairs is a combination of the «visitor default layer» and a «separate operations/security publication link».
Field operations panel
The field operations view on the organizer's side is like a control center on the day of the fair. Updating POI status, viewing incoming map feedback in the inbox, and managing stand correction requests are done here. Instead of scattered WhatsApp groups and email chains, a single channel answers the question of who changed what and when.
A visitor can send feedback saying «this stand is in the wrong place»; an exhibitor can open a stand correction request. The operations team tracks it from the inbox. If the same request comes from three different channels, there is a risk of double intervention and conflicting updates unless it is closed via a single record.
Who updates, who approves?
Every field officer being able to close all POIs speeds things up but generates errors. Practical model: Authorized field manager for frequently changing points like doors and restrooms; operations approval for structural changes like moving the press center. If the authorization limit is not clear, entrances accidentally closed in the middle of the fair will be seen.
Embed and external channels
Current POI status does not have to remain only on the portal. With white-label embed, you can embed the map on your fair website; updates are reflected from a single source. Instead of attaching separate PDFs to press releases or SMS, linking to the same live source reduces the risk of «the old plan is gone».
A point to note for external channels: Which publication version the embed shows. If draft and live versions are mixed, site visitors will see incorrect information. It must also be verified in the morning checklist that the embed URL opens the published version.
Measurable indicators
The value of POI management is not proven by the phrase 'the map is nice'. The operations team can monitor the following indicators throughout the season:
- Number of POI status changes: Indicates how dynamic the field reality is.
- Update delay: Time elapsed from when a gate closes until it is marked on the map.
- Map feedback volume: Intensity of complaints about incorrect or missing points.
- Recurring complaints about the same POI: Indicates a systemic placement or naming issue.
- Information desk 'where is the restroom?' question rate: Shows whether map usage reduces the field workload.
If the delay exceeds 15 minutes, the problem is not the vehicle; it's the field-operations communication protocol. The chain of 'who saw, who marked, who verified' must be documented.
Trade fair day shift model
POI updates should not be a single person's 'side job'. During the morning shift, door and WC statuses are verified; during the afternoon shift, entrances where transport is completed are reopened; during the evening shift, remaining restrictions for the next day are noted. Verbal handover is not enough during shift changes: The latest status on the map is transferred with a screenshot or a short checklist. Otherwise, the new shift will assume yesterday's closed door is open.
In multi-hall trade fairs, the hall manager model works well. Each hall is responsible for its own access and service POIs; central operations only reconcile cross-hall conflicts. This model prevents a single inbox from being overwhelmed. Trade-off: Local authority speeds things up; without central visibility, halls can make disconnected updates. QEMENT field operations view reduces this disconnect by bringing local updates into a common record.
Practical implementation plan
- Before the fair: Mark all POIs; don't spend the day 'looking for missing points.'
- Reference card for the door team: Keep on one page which entrance is closed with which code and how it should be marked on the map.
- Morning of the first day: Verify all POI statuses as 'open' or with their actual status.
- Lunch break check: Are doors after transport and WCs after maintenance reopened?
- End of day: Clear the feedback inbox; note recurring issues in the planning notes.
This plan clarifies the distinction between 'there's a point on the map' and 'field updates depend on discipline'. Without discipline, even the best POI layer spreads outdated information.
Frequently asked questions
Should a notification be sent to the visitor with every status change?
No. Constant notifications create noise. For high-impact changes like main entrance closure, an announcement helps; for local changes like WC maintenance, a map update is sufficient.
Does POI management require blue-dot location?
No, it doesn't. Waypoint and status updates are sufficient for most trade fairs. Real-time location is a separate technology layer.
Can an exhibitor change their own stand POI?
Stand location should be managed with organizer approval. The exhibitor can open a correction request; direct publishing authority produces conflicting maps.
Should the security layer be public?
Public information such as emergency exits can be on the visitor map. For sensitive operation layers, it is safer to use a separate public link.
The map should not lie
POI management seems like a small feature; it directly affects visitor satisfaction on the day of the fair. The trust that 'the map does not lie' means returning visitors and a calmer information desk. What bridges the gap between a static drawing and a dynamic field is the discipline of live status.
Explore QEMENT Interactive Map and field operations or to evaluate your POI layer design contact us.
POI status updates depend on the field protocol; delay times vary according to the team authorization model.