Method in four controls
- Define the business question before drawing a path.
- Map visitor and staff zones on one versioned plan.
- Observe selected time windows with an explicit counting rule.
- Separate evidence, interpretation and recommended change.
1. Start with a question the layout can answer
Visitor flow is not a decorative arrow added after a design is complete. The review starts with a question: Can attendees identify the offer from the aisle? Can an interested visitor reach a demonstration without crossing a private meeting? Can staff greet, qualify and hand over a conversation without blocking the entrance? Each question connects the exhibition objective to an observable spatial condition.
The project brief identifies target audiences, key messages and desired actions. Those decisions determine what counts as a useful path. A high number of passers-by is not automatically success if the stand needs a smaller number of technical consultations. HallWalk therefore records the intended action next to every proposed zone.
AUMA planning guidance treats objectives, messages and organizational measures as connected parts of an exhibition concept. HallWalk uses that principle as a methodology source, while the actual plan, observations and conclusions remain first-party project records with a stated date and scope.
2. Build one versioned spatial map
The base map shows aisle edges, open and closed sides, structural boundaries, entrances, product displays, media, demonstration space, conversation areas, storage, staff positions and service access. Every map has a version code and date. The team does not compare observations against an earlier rendering when the built stand differs.
Mark decision points where a visitor can enter, pause, turn, join a queue, move to a deeper zone or leave. Then mark potential conflicts: a reception desk narrowing an opening, a screen creating a crowd in the aisle, a demonstration line crossing a meeting entrance, or staff restocking through a public conversation area.
The map also distinguishes visitor movement from staff and service movement. This matters because an apparently open route may fail when doors, catering, product replenishment or equipment access are active. The method describes these conditions; it does not certify accessibility, capacity or safety compliance.
3. Define observation before collecting numbers
An observation sheet states date, show, hall, stand, plan version, observer position, time window and counting rules. A passer-by, entry, stop, demonstration engagement and qualified conversation need operational definitions. Without them, two observers may produce numbers that look comparable but describe different events.
Use several time windows rather than one convenient period. Note contextual changes such as scheduled presentations, aisle congestion, staff rotation, technical downtime or neighboring activity. These notes do not remove bias, but they keep the apparent count from being detached from its conditions.
HallWalk recommends aggregate, anonymized observation unless a separately approved research process requires more. Do not record faces, names or sensitive behavior in a general flow sheet. Photography, sensors or tracking technologies require venue rules, privacy assessment and appropriate notice before use.
Sources for this section: [3]
4. Separate finding, interpretation and action
A finding reports what was recorded: for example, a defined number of stops occurred at a specified point during a specified window. An interpretation suggests why it may have happened. An action proposes a change. These three lines remain separate so that a plausible story is not presented as measured fact.
Changes should be small enough to evaluate where possible. Repositioning a movable sign, shifting a staff position or changing a demo schedule may be easier to compare than redesigning several zones at once. The log records the change time and keeps pre-change and post-change observations distinct.
A before-and-after difference does not automatically establish causation. Audience mix, program timing, aisle traffic and staff behavior may also change. Recommendations therefore carry a confidence label and list alternative explanations. High-impact structural decisions require broader evidence and professional review.
5. Turn the show record into a reusable design input
After the event, the team combines the as-built plan, selected photographs where permitted, observation sheets, operational incidents and staff debrief. Each asset receives a date, owner and retention decision. The review identifies which layout assumptions were supported, contradicted or left unresolved.
The output is a concise evidence pack: original question, plan version, observation protocol, aggregate findings, context, limitations, interpretation and recommended next test. It can inform a future brief without pretending that a different venue, stand position or audience will behave identically.
HallWalk does not publish invented visitor figures or anonymous success claims. A public case requires client permission, a clear evidence boundary and removal of confidential or personal information. If those conditions are absent, the method can still be published without presenting a client result.
Visitor-flow evidence record
| Layer | Required field | Example form | Limitation |
|---|---|---|---|
| Question | Desired visitor action | Reach demo | Not a KPI alone |
| Map | Versioned zones | Entry A / demo B | Not a safety approval |
| Observation | Rule + time window | Defined stop count | Sampled period |
| Interpretation | Possible explanation | Visibility may matter | Not causation |
| Action | Testable change | Move sign | Recheck context |
Questions about the visitor-flow method
Does HallWalk track individual visitors?
This open method is designed around aggregate, anonymized observations. Any technology that captures identifiable or behavioral data needs a separate privacy, venue-rule and consent assessment.
How long should an observation window be?
There is no universal duration. Define a repeatable window that fits the event question, sample more than one context, and disclose the timing and limitations with the result.
Can the method prove that a layout increased leads?
No. It can document spatial observations and support a hypothesis. Lead outcomes need their own definitions, data sources and analysis, and a simple before-and-after comparison does not establish causation.
Is the map an accessibility or safety assessment?
No. It is a design-review record. Accessibility, occupancy, fire safety and technical compliance require the applicable official rules and qualified review.
Method limitations and privacy boundary
Version 1.0, published and reviewed on 3 September 2026. The method supports planning and retrospective learning; it is not a safety, accessibility, privacy, statistical or commercial-performance certification. Samples may be biased by time, location, audience and observer definitions. Identifiable data must not be collected without a separately approved lawful process.
Open method reviewed against AUMA planning guidance; no client result or causation claim is implied.
Last reviewed: 3 September 2026Planning sources
Create an evidence-ready walkthrough brief
Share the current plan, intended visitor actions and the decisions you need to make. We will structure zones, observation rules and explicit evidence limits.
Start a walkthrough brief →