Hospitality screens: scheduling and playback evidence

Publishing establishes that content or a playlist was made available through the supported workflow. Playback evidence concerns what a particular device reported displaying at a specified time. Ask about the available device records, timestamps and reporting limitations for your proposed setup. A preview, playlist assignment or screenshot alone should not be treated as a complete playback receipt.

Prepare two sample menus with clear versions and the intended service times. Test the supported scheduling or publishing process on a representative display, then check the result during the change. My Venue covers hospitality content and Screens covers broader display management. Confirm time zones, player connectivity and who corrects a missed update before using the workflow during service.

Agree the intended change time and the player’s time zone, then observe the physical screen before and after the transition. Include a dated offer that should expire. Compare what the scheduling workflow says with the actual display, and confirm the supported behaviour for the proposed device and content type.

A device can display content at one time and deliver its report later. Ask the supplier to identify which timestamp describes each event in the available evidence. When investigating a missed promotion, compare the appropriate playback field with the schedule instead of assuming that the report’s arrival time was the display time.

Assign an owner to remove or replace the asset at the agreed time and check the physical display. Review any copied playlists or local versions that may still contain it. Confirm whether the proposed setup supports expiry rules and test them; an asset disappearing from one editor does not prove it disappeared everywhere.

Use the booking reference, display location, approved asset and required start and end times in the handover. Have the venue manager confirm the content before service. If the booking system is expected to trigger the display, test that specific connection; otherwise name the person responsible for the manual My Venue update.

List the content versions, intended service times, local time zone and target display. Confirm the supported scheduling or publishing workflow on the actual player.

Keep the content publication event separate from the device's dated playback evidence. Ask which records the proposed configuration supplies for each.

No. Device playback evidence describes reported display activity. It does not independently establish audience attention, customer impressions or a purchase.

Observe the supported behaviour during the interruption and after reconnecting. Agree who checks the display and corrects a missed content change.

Use clear service-period and revision identifiers. Let the approver and local team distinguish the intended version before testing publication.

Ask for the device, content and relevant time information actually available. Keep absent or incomplete reporting visible rather than assuming continuous confirmation.

Inspect the target screen during the intended service change. A schedule entry or browser preview alone does not prove the physical display showed the correct version.

Confirm the intended time zone and supported timing behaviour with the actual setup. Test a known change instead of assuming every device uses the same clock.

Use My Venue for the hospitality-content brief and confirm broader display-management requirements with Screens. Demonstrate the specific scheduling and evidence features needed.

Record content accuracy, the target device, observed timing and unresolved exceptions. Agree the supported recovery and reporting scope before relying on the workflow during service.