The HallWalk evidence standard
- Every published fact must trace to a project record or authorized source.
- Concept and finished images are paired only when they belong to the same project.
- Anonymous clients remain explicitly anonymous; no identity is inferred from visuals.
- Unmeasured outcomes are labelled as unmeasured, not converted into marketing claims.
Why visual case studies need an evidence method
Exhibition imagery is persuasive, but it is also easy to over-interpret. A finished booth photograph can show visible materials, graphics and spatial relationships. It cannot, by itself, establish the original objective, exact floor area, schedule, client approval, visitor count or return on investment.
HallWalk separates observation from documented fact. Visual observations describe what is visible. Project facts require a record such as an approved brief, drawing revision, production file, dated photograph, delivery note or authorized client statement. The page does not fill missing fields with plausible detail.
1. Record the brief and known constraints
A case begins with the project question: what did the booth need to communicate or enable? The answer is published only when it is present in the brief and cleared for disclosure. Functional requirements, stand geometry, product needs, technical interfaces and time constraints are treated the same way.
If the client name, show, city, year or dimensions cannot be disclosed, the case remains anonymous and those details are omitted. An anonymous case can still show process evidence, but it must not hint at an identity through logos, metadata or unsupported labels.
- Disclosure status and image rights
- Project identifier used for internal matching
- Approved brief or documented functional requirements
- Known constraints and their source
- Fields that are intentionally not disclosed
2. Match the 3D concept to the build record
A design-to-build comparison is published only after the files are matched through project records. Useful checks include project identifier, file path, revision name, timestamps, drawing features and the build photo sequence. Visual similarity alone is not sufficient when files could belong to related variants.
The comparison should note visible changes and, where documented, explain their cause. A late graphic change, unavailable material or technical requirement may alter the result; without a recorded cause, the page describes the difference without inventing an explanation.
3. Document construction and handover
Build evidence is most useful as a sequence: arrival or pre-build, structural stage, graphics and technical integration, finished booth and handover. Each image receives concise alt text describing what is visible rather than repeating a keyword or claiming an outcome.
A handover record can support statements about delivered elements and open items at a specific time. It does not prove that every later operational issue was absent, nor does it establish marketing performance. Those require separate data and methodology.
4. Separate delivery facts from performance claims
Delivery facts can include approved scope, visible build state, documented handover and disclosed changes. Performance claims—such as higher footfall, more leads, greater awareness or increased sales—need a defined metric, data source, measurement period and suitable comparison.
When those records are not available, HallWalk says that the outcome was not measured or not disclosed. This limitation is more useful than a generic success statement because readers can see exactly what the case supports.
What current HallWalk material can support
The current media library contains images labelled as an anonymous medical-device finished booth and an anonymous AI/technology project with concept and on-site material. Before a public case page identifies them as one project sequence, image ownership, publication permission and file-to-project matching must be checked.
Until that review is complete, HallWalk can publish the methodology and describe available material conservatively. It will not add client names, show names, cities, dimensions, schedules, testimonials or commercial results that are not supported by the archive.
Evidence required for a publishable booth case
| Case field | Acceptable evidence | Image alone? | Publication rule |
|---|---|---|---|
| Client identity | Written permission / approved credit | No | Anonymous until cleared |
| Project match | Project ID, files, dates, sequence | Not always | Verify before pairing |
| Delivered scope | Approved scope and handover record | Partial | State only recorded items |
| Dimensions / timing | Plan, schedule or project record | No | Omit if unavailable |
| Business outcome | Metric, source, period and method | No | Label unmeasured if absent |
Questions about case-study evidence
Can an anonymous case still be credible?
Yes. It must clearly state that the client is undisclosed and limit claims to facts supported by project records and cleared media.
How do you know a concept and photograph belong to the same booth?
The files should be matched through project identifiers, revisions, timestamps, documented features or delivery records. Visual similarity alone may not be enough.
Does a finished photo prove project success?
It proves only what is visibly present at the photographed moment. Visitor, lead, awareness or revenue claims require separate measurement evidence.
Does every project include a Matterport digital twin?
No such blanket claim is made. A digital-twin case should appear only when a real scan, accessible asset, service record and publication permission are available.
Limitations and disclosure
This page explains HallWalk's publication standard; it is not itself proof of a specific client's project result. Case facts are limited to cleared project records. Anonymous identities, unavailable metrics and unverified relationships remain undisclosed. A case does not guarantee equivalent results for another project.
Evidence sources used for future case pages
- Project brief or approved scope — internal record, published only with permission
- Design revisions, build records and handover evidence — internal records, where available
Have a project that needs this level of traceability?
Share the booth brief and the evidence you want preserved. We will clarify which design, build and handover records can be included in the project scope.
Discuss a similar project →