Explain a reusable-stand framework within its actual scope

Identify the framework and purpose

Record the exact framework, issuing organisation, current source and relevant guidance version. Explain whether it is intended to structure decisions, review participation or describe another defined programme. Do not portray the existence of a framework as independent certification of every stand. Ask which edition or event applies it and what the actual responsible organiser or provider expects. Keep the framework’s terms distinct from the platform’s own learning and planning labels.

Map its requirements to real components

Inventory the stand structure, graphics, flooring, furniture, packaging and other relevant parts in the actual scope. Record what is retained, hired, newly supplied or intended for another use. Identify owners and condition. A planned reuse statement is not a completed future use, and a retained count does not create a quantified environmental benefit. Ask providers for evidence relevant to the exact material or component rather than applying a badge to the whole campaign by assumption.

Keep review and claims attributable

Identify who can review the stand against the framework, what evidence they require and how findings or conditions are recorded. If the event offers a mark or authorisation, follow its actual permitted-use process rather than inventing one. Keep public statements within verified scope and dates. An operational asset record can support the review, but the browser tool cannot manufacture physical inspection, certification or an accepted environmental assessment.

Worked example — fictional

A fictional exhibitor plans to retain its stand frame and change printed faces across two events. The asset register identifies the frame, actual condition and proposed graphic replacements. The team reads the relevant organiser framework and asks which evidence belongs to its review. After the first event, the frame’s actual return and inspection are recorded; the second use remains planned until it occurs. Public wording distinguishes retained equipment from unconfirmed future deployment and does not claim a carbon saving from a numerical inventory count.

Common pitfalls

A framework’s general promotional description may not explain current evidence or mark-use rules. Different events can adopt different implementation arrangements. A rented component can support repeated use without the exhibitor owning it, so record the actual relationship. Avoid copying a supplier’s broad reusable statement as independent proof of the programme’s complete outcome. Keep unresolved recovery and condition questions visible.

Create a scoped evidence pack

Use the evidence and asset tools to link actual components, provider documents, custody and review state. Open the framework’s official source and confirm current conditions directly with its responsible operator where needed. Export only permitted evidence and retain the accepted scope. After each event, update real outcomes and preserve limitations so the next programme can improve decisions without exaggerating what a planning framework has proved.

Decision checkpoint

Ask whether a public statement describes a component, a stand review or the entire event programme. Evidence for one boundary cannot silently support the others. Name the actual reviewed scope and date, and keep any use of an external mark within its confirmed authorisation.

Take this to the next job

• Identify actual framework and version
• Inventory components within its scope
• Separate planned and completed reuse
• Use attributable review evidence
• Keep public claims and mark rights scoped

Sources and further reading

• https://betterstands.org/