Family Day Digital Lucky Draw Requirements in Singapore

A family day digital lucky draw needs more than an animated name picker. The requirements should cover who may enter, how entries are created, when the pool closes, how winners are validated and what happens when connectivity or equipment fails. A precise brief helps organisers compare proposals on operational fit rather than presentation alone.

Get Out! Events can scope the participant journey, guest communications, registration operations and event-day delivery, with technical elements supported through GO Labs where appropriate. The final approach should remain conditional on the agreed rules, venue conditions, selected tools and approved data-handling process.

Start with the draw rules

Document the rules before choosing a platform or designing the screen. Ambiguous eligibility criteria create disputes that technology cannot resolve. Confirm whether the draw covers employees, spouses, children, invited guests, contractors or selected groups. State whether each person, household, registration or completed activity receives one chance.

• Entry trigger: Define whether an entry is issued after RSVP, onsite check-in, activity completion or another verified action.
• Cut-off: Record the exact time and authority responsible for closing the eligible pool.
• Exclusions: Identify organisers, vendors, previous winners or other groups that cannot win.
• Repeat wins: Decide whether a winner remains eligible for later prize tiers.
• Claim rule: Set the response window and redraw procedure if a winner is absent or ineligible.

Rules should be approved by the event owner and communicated in language suitable for the audience. They may also require review by the organisation’s legal, privacy or compliance teams.

Define the functional requirements

The functional specification should describe outcomes without assuming a particular product. The selected setup may need to import an approved participant list, receive entries from a registration workflow, prevent duplicate eligible records, lock the pool before drawing and select winners without manual substitution.

Specify the information shown publicly. A full legal name may be inappropriate on a large screen, while initials alone may be insufficient for verification. Depending on the brief, a displayed record could use a first name, masked identifier, team or queue number. The authorised operator may require a separate verification view that is not visible to the audience.

If the draw is part of a broader programme, document its relationship to family day planning and delivery. The run sheet should identify draw times, prize order, stage cues, presenter responsibilities and the person authorised to approve a redraw.

Map data and operational dependencies

A draw can only be as reliable as its eligible-entry source. Identify the system of record, required fields, file format, update frequency and owner of the final list. If entries depend on check-in, activity stations or QR participation, define how those records reach the draw pool and how late or incomplete submissions are handled.

• Expected participant volume and any peak entry periods
• Venue internet availability, restrictions and backup options
• Operator laptop, display output, power and adapter requirements
• Screen resolution, aspect ratio and audio or lighting cues
• Access permissions for organisers and technical operators
• Time required to reconcile, freeze and approve the final pool

The requirements should distinguish essential dependencies from enhancements. For example, live synchronisation may be useful but unnecessary if the approved process uses a controlled final import. Any offline or backup mode must be tested with the selected tools rather than assumed.

Include accessibility and family-day conditions

Family days involve mixed ages, languages and levels of digital confidence. Entry should not depend solely on a participant owning a suitable smartphone unless an assisted alternative is available. Instructions should be readable, concise and clear about whether successful registration also means successful draw entry.

Consider colour contrast, text size, screen viewing distance and announcements for participants who cannot see the main display. Avoid relying on colour alone to distinguish winner states. If children may participate, define who provides consent, who receives communications and how a winning child is verified through an accompanying adult.

Set measurable acceptance criteria

Acceptance criteria turn broad expectations into observable results. They should be agreed before the final rehearsal and linked to named owners.

1. The system accepts the approved entry format without dropping required records.
2. Duplicate treatment matches the documented rule for individuals or households.
3. The eligible pool can be reviewed, approved and locked by an authorised person.
4. A completed draw produces one eligible winner and records the result required by the brief.
5. Public output reveals no more participant information than the approved display format.
6. The redraw process follows the agreed absence, timeout and disqualification rules.
7. The operator can recover using the approved fallback procedure within the event run sheet.

Where a requirement depends on connectivity, an external platform or venue infrastructure, the acceptance wording should state those conditions explicitly.

Run realistic test cases

Testing should use representative dummy records rather than unnecessary personal data. Cover the normal journey and failure conditions, then record the result, owner and remedy for each issue.

• Valid participant enters once and appears in the approved pool.
• Duplicate registration is handled according to the agreed policy.
• Excluded participant cannot become a confirmed winner.
• Winner of one tier is retained or removed correctly for the next tier.
• Entry submitted at the cut-off boundary receives the intended status.
• Presenter requests a redraw and the operator follows the approval sequence.
• Internet, display connection or primary device becomes unavailable.
• Long names, similar names and masked identifiers remain distinguishable.
• Assisted entry works for a guest without a compatible personal device.

Conduct a venue rehearsal using the intended screen path and operator position. A technically correct draw can still fail operationally if the presenter cannot identify the winner, the operator cannot see stage cues or the audience display is unreadable.

Use a requirements checklist

• Approved eligibility, exclusion, repeat-win and redraw rules
• Named owner for the participant source and final pool approval
• Defined entry trigger, opening period and closing time
• Approved public display and private verification fields
• Documented privacy review and retention expectations where applicable
• Accessible entry alternative and readable audience presentation
• Confirmed venue connectivity, power, display and operator dependencies
• Prize sequence, stage cues and winner-verification procedure
• Test cases completed with issues resolved or formally accepted
• Fallback process, backup files and authorised decision-makers identified
• Post-event result handling and access responsibilities assigned

For broader system considerations, review the digital lucky draw system guide. Keep the family day specification focused on its mixed audience, participation rules and live programme. Once stakeholders approve the checklist, suppliers can respond against the same requirements and the event team can rehearse a clearly defined operating plan.