Build an Appreciation Wall That Works Live

Start with the purpose of the appreciation wall

An appreciation event message wall should make recognition visible without creating confusion, awkward delays or an uncontrolled stream of content. Before selecting screens or submission tools, define who is being appreciated, who may contribute, when contributions are collected and how approved messages will appear during the event.

The wall may support employee recognition, volunteer appreciation, partner acknowledgements, donor events or community celebrations. Each context changes the appropriate tone, privacy boundaries and moderation approach. A workplace audience may use names and departments, while a public-facing celebration may require less identifying information. The agreed requirements should reflect the actual audience rather than treating every message wall as interchangeable.

For a broader view of the format, see the appreciation event message wall guide. This page focuses specifically on requirements and acceptance testing.

Define the guest submission journey

Document the complete journey from invitation to display. Guests might submit before the event, at the venue or during a specific programme segment. The selected method could use a mobile web page, a staffed station, a managed device or another tool agreed during scoping. Technical outcomes depend on the chosen platform, venue environment and final brief.

Functional submission requirements

• Specify whether contributors can enter a name, team, relationship or anonymous attribution.
• Set minimum and maximum message lengths that remain comfortable on both phones and the display.
• Decide whether photographs, emojis or predefined prompts are permitted.
• Explain required fields, optional fields and any consent acknowledgement in plain language.
• Provide a clear confirmation after submission without promising immediate publication.
• Prevent accidental duplicate submissions where the selected tool reasonably supports it.
• Define whether guests may edit or withdraw a contribution before approval.

Prompts should produce meaningful appreciation rather than generic filler. Examples might ask what the person contributed, which moment mattered or what the contributor hopes happens next. Keep the prompt short enough to understand without staff assistance.

Specify moderation and publishing controls

Moderation is an operational requirement, not merely a content preference. Assign who can review messages, what they may change and who makes judgement calls. Establish whether moderators can approve, reject, hold or redact entries. Editing a guest’s wording should be limited to an agreed policy, particularly when names, personal stories or sensitive information are involved.

Define prohibited content for the event context, including offensive language, private contact details, confidential information, commercial promotion or comments unrelated to appreciation. The organiser should approve this policy. Any privacy or compliance position should be reviewed against the organisation’s own obligations; event planning guidance is not legal advice.

Moderation acceptance criteria

• New entries appear in a review queue before reaching the public display.
• Authorised operators can distinguish pending, approved and rejected entries.
• A rejected entry cannot appear through the normal display workflow.
• Approved content reaches the wall within the agreed operational window under test conditions.
• Operator permissions and account access match the agreed responsibilities.
• The team can remove an already published message if an issue is identified.

Design for readability, dignity and accessibility

A message wall succeeds only when the room can read it. Record the screen dimensions, orientation, viewing distance, expected audience position and ambient lighting. Agree limits for words per card, number of cards on screen and movement speed. Fast animation may create energy but can make appreciation messages impossible to absorb.

Use strong contrast, legible type and restrained motion. Do not communicate approval status or categories through colour alone. If submission requires a personal device, provide an alternative path for guests who cannot or prefer not to use one. This might be a staffed capture point or assisted submission process, depending on the event plan.

Names, photographs and messages should be displayed in a way that respects the honouree and contributor. Accessibility requirements should be confirmed with the organiser and tested on the actual output configuration where possible.

Confirm technical and venue dependencies

The requirements document should identify every dependency between submission, moderation and display. Typical dependencies include venue internet, local network restrictions, power, display hardware, playback computers, browser compatibility, account access and physical positions for operators. Do not assume venue Wi-Fi will perform like an office connection.

• Record the expected number and timing of submissions as a planning input, not a guaranteed load.
• Confirm screen resolution, aspect ratio, video inputs and any switching arrangements.
• Identify whether moderation and display devices need separate connections.
• Agree who supplies, configures and monitors each device.
• Determine what content can remain available if connectivity becomes unstable.
• Prepare an approved holding screen or curated fallback sequence.
• Set access handover, credential management and post-event retention responsibilities.

Get Out! Events can scope and coordinate these operational elements through GO Labs, subject to the agreed brief and selected tools. The final design should separate required behaviour from optional enhancements so essential event delivery does not depend on untested extras.

Write event-day test cases

Testing should cover real guest and operator actions, not only whether a page opens. Use the intended devices, display output and venue connection whenever practical.

1. Valid submission: Enter an ordinary message, confirm receipt, approve it and verify correct display formatting.
2. Long content: Submit text at the permitted limit and confirm that it remains readable without clipping.
3. Invalid input: Omit required information and verify that the guidance identifies what must be corrected.
4. Moderation hold: Leave a message pending and confirm it never appears publicly.
5. Removal: Publish a test message, remove it and confirm that it no longer cycles.
6. Multiple devices: Test representative mobile operating systems and the managed event devices.
7. Connection loss: Interrupt connectivity and follow the documented fallback and recovery procedure.
8. Display restart: Restart the playback setup and verify that operators can restore the approved wall.
9. Accessibility path: complete an assisted submission and confirm equivalent moderation treatment.

Set operational ownership

Assign named roles for content approval, technical monitoring, guest assistance and escalation. Specify when moderation opens, when the live wall begins, whether messages continue during speeches and when submissions close. The run sheet should show who decides if the experience moves to fallback content.

Brief moderators on tone and edge cases before doors open. Brief guest-facing staff on the submission steps without giving them unnecessary administrative access. If the appreciation segment involves a graduation or retirement, compare the more specific considerations in the graduation message wall guide or retirement celebration message wall guide.

Requirements checklist for buyer sign-off

• Purpose: Honouree, audience, tone and programme role are documented.
• Participation: Eligible contributors, submission period and assisted route are defined.
• Content: Prompts, field limits, attribution options and media rules are approved.
• Moderation: Decision rights, prohibited content and removal procedures are assigned.
• Display: Layout, timing, readability and motion expectations are testable.
• Accessibility: Contrast, legibility and alternative participation needs are addressed.
• Dependencies: Internet, power, hardware, accounts and venue access have owners.
• Fallback: Holding content, recovery steps and escalation authority are agreed.
• Testing: Submission, moderation, display, failure and restart cases have passed.
• Close-out: Export, retention, deletion and access-removal responsibilities are confirmed.

Sign-off should happen against these requirements rather than appearance alone. A polished wall is useful only when guests can contribute confidently, moderators can control publication and the event team can keep the experience running through the appreciation moment.