Exhibition booth case evidence standard: what a case can prove

1. Define the claim before collecting proof

A case study should answer one bounded question. It might document how a brief became an approved spatial plan, how a particular detail was produced, how the built stand compared with the approved render, or how a handover issue was closed. It should not combine unrelated observations into a broad claim that the project was successful in every respect.

The claim is written as a statement that can be supported or rejected by named evidence. The evidence owner, relevant period and intended audience are recorded at the same time. If the team cannot state what would count as contradictory evidence, the claim is probably too vague for a formal case.

Business objectives from the exhibition brief provide context, but an intended outcome is not an achieved outcome. A target number of meetings, for example, cannot be published as a result. HallWalk keeps objective, execution record and observed result in separate fields.

Sources for this section: [1], [2]

2. Secure permission and document ownership

Publication permission identifies the client or rights holder, approved brand name, project references, permitted images, permitted statements, territories, languages and channels. A general project contract is not assumed to grant public case-study rights unless it says so. Approval is retained as a project record.

Each asset has an owner and provenance note. The record distinguishes client-supplied brand files, designer-created renders, contractor production images, venue documents and photographs captured by other parties. A file being present in a shared folder does not prove a right to republish it.

If naming permission is absent, anonymization must be genuine. Removing a logo while leaving a unique product, show, date and visible staff may still identify the client. When reliable anonymization is not possible, HallWalk publishes the general method without presenting the project as an anonymous success story.

3. Label visual evidence by stage

A design render, technical drawing, production photograph, installation photograph and completed-booth photograph represent different states. Captions name the state, relevant date and what the image is intended to show. A render is never captioned as a completed result, and a cropped detail is not described as proof of the whole stand.

Before-and-after layouts use comparable viewpoints where practical and explain when camera position, lens, crop, lighting or retouching differs. Visual adjustment for colour or privacy is disclosed when it could change interpretation. Decorative imagery remains separate from evidence imagery.

The evidence register stores the original filename, capture or creation date, creator, permission status, published derivative and related claim. It can also store a checksum when file integrity matters. A public page does not need to expose confidential originals, but editors must be able to trace the published asset back to its controlled source.

4. Make every metric auditable

A number is publishable only with a definition, unit, time range, data source and accountable owner. Counts of passers-by, entries, qualified conversations, demos, scans, leads and sales are not interchangeable. The collection method and known exclusions appear near the result.

A percentage requires both numerator and denominator. A comparison identifies the baseline, equivalent period and material changes in context. If a figure was supplied by a client and not independently verified, that status is visible. Estimated values are labelled as estimates and never mixed with measured results in one total.

A difference after a redesign does not by itself prove causation. Audience mix, stand position, show edition, program, staff and market conditions may also change. The case states whether a figure is descriptive, observational or based on a more rigorous study design. HallWalk does not promote an association to a guaranteed result.

Sources for this section: [2], [3]

5. Apply privacy and data-minimization controls

The evidence plan starts by asking whether personal data is needed at all. Aggregate counts and de-identified operational records are preferred for a public layout or flow case. Names, faces, badge details, contact records and conversations are not added merely to make a case look more authentic.

Article 5 of the GDPR sets out principles including purpose limitation, data minimization, accuracy and storage limitation. A project involving identifiable data requires an appropriate lawful process, access control, retention decision and privacy review. This page is not legal advice and does not declare a processing activity compliant.

Published screenshots and photographs are checked for badges, screens, documents, QR codes, vehicle plates and reflections. Redaction is reviewed on the exported file, not only in the editing application. The evidence register records that a privacy check occurred without publishing sensitive internal details.

Sources for this section: [4]

6. Review, publish and correct transparently

Before release, an editor compares the claim matrix, permission, evidence register, captions, metric definitions and limitations. A second review is required for named clients, quantitative performance claims or potentially sensitive images. Open items block publication or are removed from the public claim.

The page displays publication, modification and review dates. A substantive change to client identity, evidence meaning, metric definition, conclusion or source relationship receives a correction note. Minor spelling or accessibility fixes can be updated without implying that the project facts changed.

If permission is withdrawn or evidence can no longer support the claim, the case is corrected, anonymized, withdrawn or de-indexed according to the documented decision. The aim is not to preserve a marketing asset at all costs; it is to keep the public record within the evidence that remains valid.