Lighting Scene Acceptance Test for Guest Areas

A guest-area lighting acceptance checklist for scene names, presets, fallback controls, tablet labels, night-mode behaviour, and handover.

Lighting scenes are part of the yacht's guest-facing AV experience. A scene that is too bright at night, a keypad label that does not match service language, a shade integration that behaves differently in port, or a tablet button that does not match the wall control can make an otherwise high-quality space feel unreliable.

Acceptance testing should be done in the spaces, at the relevant time of day, with interior crew involved. The goal is not only to prove that loads respond. The goal is to prove that guests and crew can select the right mood or fallback control without technical help.

• Area name and the exact name used in control UI, keypad engraving, drawings, and stewarding notes.
• Scene list: arrival, dining, relaxed, party, cinema, cleaning, night, turn-down, emergency practical, and custom owner scenes where used.
• Control points: keypad, touch panel, tablet, central control, crew service control, and fallback wall control.
• Integrated systems: shades, curtains, AV scenes, fireplace/effects, exterior deck scenes, and occupancy or daylight dependencies.
• Approval owner and date, including interior crew sign-off where service language matters.
• Database/project backup, processor/controller version, and who is authorised to edit scenes.

1. Agree labels first: Confirm scene names with interior crew and Captain before testing. Avoid programmer labels that are technically clear but operationally confusing.
2. Test every control point: Trigger each scene from keypad, touch panel, tablet, and service control where fitted. The same scene should mean the same thing across controls.
3. Check real conditions: Test during daylight, evening, night, guest arrival, dining, cinema, cleaning, and pathway use where relevant.
4. Test fallback operation: Confirm what happens if the tablet is flat, a touch panel is offline, or central control is unavailable.
5. Record edits: If tuning changes are made, capture the before state, after state, editor, reason, approval owner, and updated backup file.
6. Close open issues: Log over-bright scenes, slow fades, wrong shade behaviour, confusing labels, failed loads, and guest-safety concerns with an owner and due date.

• Language: Scene names do not match how interior crew actually operate the space.
• Night use: Low-level scenes are too bright, unsafe, or inconsistent between cabin and ensuite.
• Fallback: Tablet controls work, but wall controls are unclear or missing a practical mode.
• Integration: AV, shades, and lighting are not synchronised for cinema, dining, or arrival scenes.
• Change control: A scene is improved during testing but the project file and approval record are not updated.

Scene changes are operational changes. If a guest-facing scene is tuned, the yacht needs an updated backup and a short record of what changed and why.