“The app says it is quiet. Why am I waiting an hour?”… BTS FESTA and the back-end design of on-site crowding information

– A protocol for publishing booth crowding information and controlling queue cut-offs, through BTS FESTA 2025

Author: EVENTODIT Editorial Team
Published: 2026-10-25T14:15:53+09:00
Updated: 2026-10-27T01:23:00Z
Original URL: https://eventodit.com/en/stories/bts-festa-2025-booth-crowding-update-interval.html

Practical summary

Event overview: 2025 BTS FESTA · KINTEX Exhibition Center 2, Halls 9–10, Goyang · 13–14 June 2025; ended

Key decision: Decide which status changes need immediate publication rather than the next crowding update.

Responsible roles / intended readers: Fan-event and exhibition operations and visitor-information leads

Record / next task: Booth observations, publication times and intake-status changes

Basis of information: Official advance notice, Starnews post-event coverage and Yonhap on-site reporting. Half-hourly updates are reported execution; operating and closing times are advance conditions.

Editorial review: 2026-10-25

At large festivals and exhibitions with tens of thousands of visitors, the most serious complaints begin with extreme queues caused by crowds concentrating at particular popular booths. BTS FESTA, held at KINTEX in 2025, introduced a system that allowed fans to check crowding at individual booths on its website at 30-minute intervals to address this problem.

It was an excellent system that enabled visitors to decide their next route without asking staff individually. From an event planner’s perspective, however, displaying crowding data is a double-edged tool that requires delicate control. As the queue and admission-control guidelines in the **“Case Article Review”** file also show, the moment the update interval of the information on screen falls out of step with actual conditions on site, visitors’ expectations can turn into forceful complaints.

1. Decoupling crowding and waiting time

The waiting time visitors imagine when they see “crowded” on an app screen is different from the actual wait.

- **Clearly state the limits of status information**: Crowding is density data showing how many people have gathered in a space. It is not a guarantee that “if you join the queue now, you will get in 30 minutes later.” Depending on how long people stay inside the booth and how quickly the activity turns over, visitors may wait an hour even when the status is “clear.” The organiser needs a disclaimer at the bottom of the screen, such as “This information may differ from the actual admission waiting time,” to prevent visitors from misreading it.

2. The dilemma of a 30-minute cycle: control the time lag

Information refreshed every 30 minutes means conditions may change completely while a visitor checks the screen and walks to the booth.

- **Display the reference time for the update**: If the screen says “quiet” but a visitor arrives to find a queue-closed sign already standing at the booth, that visitor will be angry. Whenever crowding data is displayed, it must state when the condition was measured, such as “As of 2:00 p.m.”
- **Immediately override emergency closures**: Some information cannot wait for the regular 30-minute refresh. When souvenirs sell out or the waiting crowd exceeds capacity, the central operations desk needs back-end override authority to disregard the system’s cycle and immediately switch the status to “Closed” or “Temporarily paused.”

3. Separate operating status from density

Visitors need to know not only how many people are present, but also whether they can join the queue now.

- **Display multiple statuses**: A booth may look empty and quiet but have already closed its queue because the scheduled end of operation is approaching or supplies have run out. The crowding information screen needs to go beyond simple colours such as red and green. Complete route guidance requires two separate indicators: [Spatial density: clear / moderate / crowded] and [Intake status: open / temporarily paused / closed for the day].

4. A four-stage protocol for booth crowding information

When planning to provide visitors with real-time booth crowding information through an app or website, the planning team needs the following four stages.

| Stage | Working standard |
| --- | --- |
| **[Stage 1: Define indicators and assign roles and responsibilities]** | Quantify and teach the crowding criteria that each booth lead will report to headquarters by radio or tablet, for example, “crowded” when the queue extends beyond a specified column. |
| **[Stage 2: Separate the fields displayed on screen]** | Design the system to display the observation reference time, crowding or density level, and whether intake is open as separate elements in the app or web interface. |
| **[Stage 3: Activate an override hotline]** | Establish an emergency publication channel that allows headquarters to disregard the regular update cycle and immediately publish a pop-up or closure when a safety issue or stock shortage causes an urgent queue hard stop. |
| **[Stage 4: Synchronise on-site and online messages]** | If intake is shown as closed online, coordinate with on-site staff so that a physical “Queue closed” sign is also placed in front of the booth without even a one-minute delay. |

Planner’s note: the worst information is slow information

The introduction of smart visitor apps at events as information technology advances is highly encouraging. Yet information that cannot keep pace with changes on site is worse than providing none at all.

The moment the words on a visitor’s phone say something different from the sign in a staff member’s hands, trust in the organiser’s system shatters. Before promoting “Check crowding on our app,” the planner first needs to measure the exacting response speed, or latency: how many minutes after a radio call can the app’s text actually change? Complete route control comes from perfectly synchronised back-end operations that move the site and screen together, rather than sophisticated app design.

Application conditions

Crowding information cannot replace admission controls. Proposed fields for another event do not reconstruct the original screen.

Unconfirmed information

Measurement methods, crowding categories, staffing, actual waits and subsequent visitor movement were not established. Reduced waits or improved satisfaction were not verified.

Sources

BIGHIT MUSIC’s official Weverse advance notice: 13–14 June 2025, KINTEX venue, programmes, booth hours and entry and queue closing times
https://weverse.io/bts/notice/27562?hl=ko

Starnews, Kim Su-jin, 16 June 2025: post-event reporting of BIGHIT MUSIC’s closing statement, half-hourly booth crowding information and multilingual support
https://www.starnewskorea.com/music/2025/06/16/2025061607575754103

Yonhap, Shim Sun-ah, 13 June 2025: on-site reporting confirming activities and visitor movement across the two halls
https://en.yna.co.kr/view/AEN20250613006800315