Family Day Digital Photo Wall Requirements

A family day digital photo wall lets employees and their families contribute pictures to a shared event display. The concept is simple, but the delivery brief needs more detail than “guests upload photos and they appear on screen”. Buyers should define who can participate, how submissions enter the system, what happens before publication, where the content appears and how the experience will be operated when the venue is busy.

This guide sets out functional requirements, dependencies, acceptance criteria and test cases for a family day in Singapore. Get Out! Events can scope the guest journey, operational plan and suitable delivery approach through GO Labs. Specific technical outcomes remain dependent on the agreed brief, selected tools, venue conditions and supplier responsibilities.

Start with the intended family experience

Decide what role the wall plays in the programme. It might welcome arriving families, collect pictures from activity zones, support a themed challenge or create a visual recap during lunch. A clear purpose determines the submission prompts, screen location, moderation policy and operating hours.

Specify the expected participant groups, including employees, spouses, children and invited guests. Avoid assuming every attendee will have a compatible phone, mobile data or confidence using a QR-led journey. The brief should explain whether facilitators will help families submit content and whether an assisted alternative is required.

Core functional requirements

Photo submission

• Entry route: State whether guests access the submission journey through a QR code, short URL, managed device or another agreed method.
• Required fields: Minimise mandatory information. If names, departments, captions or contact details are requested, document why they are needed and how they will be handled.
• File rules: Define accepted formats, orientation guidance, upload limits and the message shown when a submission fails.
• Confirmation: Tell guests whether their upload was received, is awaiting review or cannot be accepted.
• Repeat use: Clarify whether one person may submit multiple photos and whether duplicate or rapid submissions need controls.

Moderation and publishing

A family event can involve children, accidental background content and playful captions. The operating model should therefore state whether every submission requires approval, who moderates it and which criteria apply. Define the treatment of inappropriate, unsafe, irrelevant, duplicated or unreadable content without promising that automated or manual review will identify every issue.

Moderators should be able to distinguish pending, approved and rejected items using the selected workflow. The brief should also define whether published content can be removed quickly after approval and who has authority to request that removal.

Display behaviour

• Specify whether photos appear individually, as a rotating mosaic, in a branded frame or through another agreed layout.
• Define acceptable cropping for portrait and landscape images so faces and captions are not routinely obscured.
• State the desired rotation pace, transition style and maximum time before approved content should appear under normal operating conditions.
• Provide a holding state for periods with no approved submissions or a temporary connectivity issue.
• Confirm whether the same content should feed one screen or multiple displays, subject to the selected setup.

Operational dependencies to confirm

The digital journey depends on the physical event environment. Confirm venue internet options, mobile reception, power, screen inputs, playback resolution, mounting arrangements and cable routes. Identify who provides each component and who is permitted to troubleshoot venue equipment.

Screen placement should support viewing without creating a queue or blocking activity traffic. Submission prompts must remain legible at the expected viewing distance. If the wall sits outdoors or in a bright space, assess glare, weather protection and screen brightness during a site visit where practicable.

Assign named operational roles for system readiness, moderation, display monitoring, guest assistance and escalation. Also define the opening and closing times for submissions. A fallback can be as simple as retaining approved content on screen while the submission route is investigated, but the exact response should be agreed and rehearsed.

Accessibility and inclusive participation

Use concise instructions, high-contrast prompts and readable type sizes. Do not rely on colour alone to explain whether an upload succeeded or failed. QR codes should be accompanied by a text alternative where appropriate, and instructions should be positioned where wheelchair users and children can see them.

Consider multilingual guidance based on the audience, not as a default assumption. If captions are optional, make that clear. Facilitators should know how to help without taking control of a guest’s personal device unnecessarily. An assisted submission point may be useful, provided its staffing, device handling and content process are defined.

Privacy and content handling questions

The brief should identify what information is collected, why it is needed, who can access it and the intended retention approach. Notices and consent language should be reviewed for the actual event and chosen workflow. Requirements involving children, personal data, reuse after the event or public sharing may require additional review by the organiser or its advisers. This guide is operational guidance, not legal advice.

Avoid collecting data merely because a form can support it. Buyers should also decide whether approved photos are displayed only during the event, supplied to the organiser afterwards or considered for another use. Any later use should follow the agreed permissions and applicable policies.

Acceptance criteria for supplier sign-off

1. A guest can open the submission journey using each supported device and browser combination agreed in the brief.
2. A valid photo can be submitted, acknowledged and placed into the correct moderation state.
3. An invalid file produces a clear recovery message without losing necessary entered information.
4. An authorised operator can approve, reject and remove content through the agreed workflow.
5. Approved portrait and landscape photos render acceptably on the actual display resolution.
6. The wall presents an agreed holding state when no approved content is available.
7. The team can identify and execute the documented response to connectivity, playback or moderation disruption.
8. Instructions, QR placement and assisted participation arrangements match the approved event plan.

Recommended test cases

Run an end-to-end rehearsal with the intended network path and display equipment. Test a standard image, a large file, an unsupported format, a rotated photo, a long caption, repeated submissions and a rejected item. Confirm what happens when connectivity is interrupted during upload and when the display device reconnects.

Operational testing should include a burst of simultaneous family submissions, moderator handover, urgent removal of a published image and operation during a programme transition. Record issues, owners and retest results rather than treating the first successful upload as acceptance.

Buyer requirements checklist

• Purpose, audience and programme timing defined
• Submission route and supported devices agreed
• Required fields and file rules documented
• Moderation criteria, staffing and escalation assigned
• Display layout, cropping and rotation behaviour approved
• Venue network, power, screen and placement dependencies confirmed
• Accessibility and assisted participation considered
• Privacy notices, permissions and retention approach reviewed
• Fallback states and incident responsibilities rehearsed
• Acceptance tests completed on the event setup

Once these requirements are stable, buyers can compare delivery proposals on the same basis. For procurement considerations, see the family day digital photo wall vendor selection guide. If the programme also includes prizes, use a separate family day digital lucky draw requirements brief rather than combining two operational workflows into one specification.