Employee Event Message Wall Requirements in Singapore

An employee event message wall can collect staff notes, photographs, reactions or appreciation messages and present selected contributions during an event. The visible screen is only one part of the requirement. A workable brief must also address submission, moderation, display behaviour, accessibility, connectivity, privacy, staffing and failure handling.

For a Singapore employee event, requirements should reflect the venue, audience, programme and organisation’s internal policies. Get Out! Events can scope message-wall operations and wider event delivery through GO Labs, with technical outcomes depending on the agreed brief, venue conditions and selected tools.

Start with the employee experience

Define the intended behaviour before choosing a platform. A town hall may need short questions and comments. A dinner and dance may prioritise photographs and celebratory notes. A recognition event may require messages linked to teams, values or award recipients. These are different workflows and should not share an assumed feature list.

• Audience: Identify employees, invited guests, remote participants and any groups requiring restricted access.
• Contribution types: Specify text, photographs, predefined reactions or combinations of these.
• Participation route: Decide whether contributors scan a QR code, open a link or use an event interface.
• Display purpose: State whether the wall supports celebration, feedback, questions, recognition or programme interaction.
• Participation timing: Confirm whether submissions open before, during or after the event.

Functional requirements to document

Write each requirement as an observable action rather than a vague preference. For example, replace “easy to moderate” with a requirement that authorised moderators can approve, reject or hold submissions before they appear. The brief should cover the full path from an employee opening the submission channel to approved content appearing on the intended display.

Submission and display

• State required and optional fields, permitted media formats and any character or file-size limits.
• Define the employee-facing confirmation shown after a successful or unsuccessful submission.
• Specify whether approved posts rotate automatically, appear chronologically or follow a curated sequence.
• Identify screen orientation, output resolution, safe areas and whether names, departments or timestamps are displayed.
• Set expectations for duplicate submissions, unsupported files, broken uploads and interrupted connections.

If remote participation is part of the programme, review the separate virtual event message wall requirements, particularly around access, latency and support outside the venue.

Moderation and content control

Employee content should not reach a public event screen without a clearly agreed control model. Define who may moderate, when coverage starts, how decisions are recorded and who has authority for sensitive cases. The process may include pre-moderation, post-moderation or a managed combination, depending on risk and programme speed.

Prepare written moderation rules covering personal information, offensive language, confidential business material, identifiable third parties and unsuitable photographs. Automated filtering, if selected, should support rather than replace accountable human review. Also specify how an approved post can be removed quickly if circumstances change.

Privacy, access and retention dependencies

Before implementation, identify what personal data the workflow may collect, why it is needed, who can access it and how long it should remain available. Requirements should follow the organisation’s own privacy, information-security and records policies. Obtain appropriate internal or professional advice where necessary rather than treating an event supplier’s workflow as legal guidance.

Clarify whether participation is anonymous, attributed or optional; what notice employees receive; and whether photographs require additional handling. Access controls, exports, deletion timing and administrator permissions depend on the selected tools and agreed configuration. Avoid requesting data that is not necessary for the event purpose.

Accessibility and inclusive participation

A message wall should not make smartphone ownership, fast typing, perfect vision or familiarity with QR codes a condition of participation. Provide at least one supported alternative, such as an assisted submission point or a staff member who can enter a contribution with permission.

• Use readable type sizes, strong contrast and restrained animation on the display.
• Keep instructions short and available in suitable languages for the workforce.
• Ensure controls have clear labels and logical focus order where the chosen interface supports keyboard navigation.
• Provide meaningful text alternatives or moderator-added descriptions when important image content needs to be understood.
• Avoid rapid movement, flashing effects and display timings that prevent comfortable reading.

Measurable acceptance criteria

Acceptance criteria establish what must be demonstrated before sign-off. They should be specific to the event rather than copied from a generic feature list.

1. An authorised test participant can open the submission route on agreed device and browser combinations.
2. Valid text and media submissions produce the expected confirmation, while invalid entries receive useful guidance.
3. Unapproved content does not appear when pre-moderation is required.
4. A moderator can approve, reject and remove test content using the assigned role.
5. Approved contributions appear correctly on every specified output without cropped names, text or photographs.
6. The display remains readable at the planned viewing distance under representative venue lighting.
7. The agreed fallback can be activated by event staff if connectivity or the primary display path fails.

Test cases before event day

Conduct a functional test first, followed by a venue-based rehearsal using the actual network path, playback equipment and display configuration where practical. Include normal use, boundary cases and deliberate failures.

• Submit short and maximum-length messages, portrait and landscape images, repeated posts and unsupported files.
• Test simultaneous contributions at a realistic programme moment without claiming capacity that has not been verified.
• Disconnect a test device during submission and confirm that the participant receives a clear recovery path.
• Check moderator access, role restrictions, content removal and escalation communications.
• Restart relevant display equipment and confirm the documented recovery sequence.
• Review spelling, instructions, consent or privacy notices, QR destination and event branding on final outputs.

Event-day operating plan

Assign named roles for platform administration, moderation, screen playback, employee assistance and escalation. Document opening time, content seeding, moderation rules, programme cues, support contacts and the decision maker for pausing submissions or hiding the wall.

Plan a fallback that suits the event. This could mean holding new submissions while approved content continues rotating, switching to prepared event visuals or pausing the screen until service is restored. The appropriate approach depends on the production setup and should be rehearsed with the wider show team.

Requirements checklist for supplier comparison

• Purpose, audience, event format and participation period are defined.
• Submission fields, media types, limits and error states are documented.
• Moderation roles, rules, escalation and removal procedures are assigned.
• Display locations, orientation, resolution and programme cues are confirmed.
• Venue internet, power, devices, playback equipment and technical ownership are identified.
• Accessibility needs and assisted participation routes are included.
• Privacy notices, access permissions, exports and retention expectations are reviewed internally.
• Acceptance criteria, test devices and venue rehearsal responsibilities are agreed.
• Event-day staffing, support channels and fallback actions are documented.
• Post-event closure, content handling and access removal are assigned.

Use these requirements when reviewing the employee event message wall vendor selection process. A strong proposal should identify assumptions, exclusions and dependencies instead of presenting every desired outcome as automatic. For recognition-focused programmes, the appreciation event message wall requirements provide a more specific companion brief.