COP31Radar · Practical guide 03

Eight useful interactions for your COP31 stand

Eight practical COP31 stand activities, from short quizzes to visitor-led interactive formats.

03

Standfirst: A good stand interaction helps a visitor understand something, make a choice or begin a worthwhile conversation. It does not have to be technically complicated.

A touchscreen can look impressive without giving people a reason to stay. A simple question can start a much better conversation. Start with the learning or engagement objective, the time a visitor has and what should happen after the interaction. Then choose the technology.

Eight formats to consider

Format What visitors do Typical duration What the organisation learns or shows
1. Climate choices Choose between two imperfect policy or project options 1–2 min Trade-offs and reasons behind preferences
2. Three-question quiz Respond to a short evidence-based quiz 1–2 min One memorable fact; gaps in understanding
3. Priority vote Allocate three votes among a short list of priorities 1 min Aggregate visitor priorities (not a representative survey)
4. Project journey Explore a real project through three stages and verified outcomes 2–3 min How work happens and what can be checked
5. Challenge wall Add a practical barrier or question to a moderated topic wall 1–3 min Recurring implementation problems
6. Myth / evidence cards Open a statement to see its source, limits and relevant data 1–2 min Nuanced understanding rather than slogans
7. Commitment-to-action Select a feasible next action and request resources 1–2 min Follow-up interests, only with appropriate consent
8. Live discussion pulse Respond to a question and view a clearly labelled live count 1 min A conversation starter for speakers or facilitators

Durations are indicative concept targets, not tested performance claims.

Choose the right interaction

Use a quiz when you have well-sourced, genuinely useful answers. Use voting when you want to begin a conversation; do not publish convenience-sample results as public opinion. Use a project journey when you can show concrete outcomes and limitations. Use a challenge wall only if someone will moderate entries and respond. Do not collect personal data merely because the software makes that easy.

Design for the conditions on site

Assume interruptions, noise, queues, different languages and unreliable connectivity. Keep the first screen readable at a distance; make the main action clear without staff explanation; test mobile and large-display versions. Provide an accessible non-digital alternative where possible. Check physical placement, device power, network conditions, screen brightness, language availability and responsibility for daily support.

Make data collection proportionate

Separate anonymous participation from named follow-up. If gathering email addresses or identifiable responses, define the purpose, legal basis, retention period, access rights and notice before launch; avoid bundling promotional consent with participation. Check the applicable data-protection regime, including KVKK or GDPR where relevant, with qualified counsel. Aggregate voting counts need prominent limits, especially if responses are self-selected.

What to ask a developer or supplier

Request a working demo on the intended device, defined offline behaviour, a way to reset between visitors, content editing responsibility, language proofing, an accessible fallback, moderation controls where applicable and a basic analytics/export specification. Clarify who owns the code, hosting and resulting data; what happens when the event ends; and who is on call if something breaks.

A five-step planning sequence

  1. Write the one-minute visitor objective.
  2. Pick one format and define the exact content and sources.
  3. Prototype on the intended screen or phone.
  4. Test with people unfamiliar with the project; revise the question and length.
  5. Agree on live support, privacy, moderation and post-event reporting.

Quick quality check

  • [ ] The interaction conveys one worthwhile point.
  • [ ] A visitor can begin without a long explanation.
  • [ ] Claims and quiz answers have traceable sources.
  • [ ] Consent and data-use language is understandable.
  • [ ] Language, accessibility and offline conditions have been tested.
  • [ ] There is an owner for moderation, technical support and final reporting.

Editorial note: Concepts in this guide are suggestions. They are not a claim that the eight applications are already built, priced or available to deploy.

Support from SICI: Social Institute of Change and Impact (SICI) can scope a visitor journey and, through its digital practice, develop selected interactive tools. Timing and availability depend on the brief. Discuss your COP31 plans · Discuss your COP31 plans