LED display content expiration needs three clear decisions: when a message must stop, which screens the rule covers, and what approved content appears next. Record the date, time and time zone, identify every assignment that can play the asset, and test the transition on the proposed player and CMS configuration. A campaign end date in a spreadsheet is useful only when the operating system and the responsible team apply the same rule.
This guide helps retail marketing teams, venue operators and signage integrators plan the end of a promotion, event or temporary announcement. The goal is a controlled changeover with a usable record of the result. The checks below are a proposed project workflow; the available controls and their behaviour depend on the selected platform, software version and deployment.
Define the last permitted display time
Start with the message owner. Ask when the information becomes unsuitable for display and whether the same deadline applies at every location. “Ends Sunday” can leave the operator guessing about the time, the time zone and whether an overnight venue follows a different operating day.
Write the intended outcome in a sentence. For an illustrative campaign, the instruction might be: “From 00:00 on 12 October 2026 in each site’s local time, the autumn offer must no longer appear; show the approved general brand playlist.” The actual date and replacement should come from the campaign owner. Put the chosen time basis beside the deadline wherever the instruction is handed over.
Agree what happens to a video that is already playing at the boundary. Does the requirement allow that clip to finish, or must the image change at the specified time? Ask the supplier how the system implements the requirement and demonstrate the result. Do not assume that a schedule ending, a playlist being rebuilt and an image disappearing are the same event.
Check the meaning of each content control
Several controls can affect an asset’s availability. Their names do not establish their scope. Review the platform documentation and ask the operator to show where each setting takes effect.
On smaller screens, swipe horizontally to view all columns.
| Control or action | Question to resolve | Evidence to retain |
|---|---|---|
| Schedule end | Does this end one event, a recurring series or every assignment of the asset? | The affected schedule and its date/time rule |
| Media expiration | Where is the expiry applied, and when do players receive or evaluate it? | Asset identifier, expiry setting and tested player behaviour |
| Retire or archive | Does the control stop existing playback or only prevent future selection? | The vendor’s definition and current usage record |
| Replacement playlist | What becomes eligible when the promotion ends? | Approved replacement revision and target screens |
| File deletion | What dependencies and retained records would be affected? | A separate, approved library-cleanup decision |
Xibo’s media library documentation illustrates why the distinction matters. Its expiry setting removes media from layouts or playlists where it is used, while retiring media preserves existing assignments and prevents further selection. Those are different outcomes within that product. Confirm the corresponding behaviour in your own system before using a similar-looking control.
Treat library cleanup as a later task. A file’s removal from a server library does not, by itself, demonstrate what a disconnected player is showing. Preserve the information needed to review the changeover, then follow the platform’s supported process for removing material that is no longer needed.
Find every route that can replay the message
Build a usage register for the outgoing asset. Include the approved revision, campaign identifier, layouts, playlists, directly assigned schedules, display groups and any local copy used at a site. Where content fills only part of an LED wall, include that region as well.
A promotion can have more than one route onto a screen. For example, the central campaign may end while a locally maintained playlist still contains an older copy. This is a scenario to check, not a claim that every CMS behaves that way. Review current assignments and ask local operators about any independent source feeding the display.
Use stable identifiers alongside readable names. If “Weekend Offer” is reused for several revisions, the name alone may be insufficient to determine which file must stop. Record the revision being withdrawn and the replacement being approved. Avoid changing a shared asset without first understanding the other schedules that reference it.
For a new installation, include this exercise in LED display CMS selection. The buyer should see how the proposed system locates an asset’s uses and applies an expiry rule across the intended screens before relying on it during a live promotion.
Make local time and central time explicit
Choose whether each site changes at its own local deadline or whether every site changes at one shared instant. These are different requirements for a network spanning time zones. Record the choice in the campaign brief, the schedule and the acceptance notes.
Xibo’s scheduling priority and display-order documentation describes an option to run an event at CMS time instead of local display time. This provides a concrete example of a setting that can change the meaning of a schedule. Check the equivalent control, device time configuration and displayed time basis in the platform you use.
Review overnight schedules, recurring events and clock changes where relevant. Broadsign’s schedule documentation treats date/time ranges, active weekdays and overlapping schedule precedence as separate settings. A buyer should therefore inspect the complete effective schedule, including recurrence and overlap, instead of relying on one visible end date.
For the acceptance exercise, use a short future test window and record the observed time against an agreed reference. Have the person responsible for system time investigate any discrepancy. Keep a time-setting correction separate from the campaign approval so the team can explain both changes later.
Approve the replacement content early
Prepare the next message while approving the current campaign. The replacement might be another approved promotion, general brand content or useful venue information. It should fit the same canvas, orientation and content region and have a clearly assigned owner.
A neutral image can be a suitable part of an approved fallback, but its suitability still depends on the venue and the message requirements. Review visible information for old prices, dates, QR codes, event references and other details that can become misleading. A file named “evergreen” does not make its contents timeless.
Confirm how the replacement reaches the player and how the operator identifies readiness. If the system offers download or synchronisation status, ask what that status proves. Make the replacement available through the supported process before the switch, and verify its appearance on the actual LED canvas during testing.
An empty schedule also needs an agreed result. Ask what the proposed system displays when neither the outgoing campaign nor its replacement is eligible. Record that behaviour explicitly. A default layout, blank output or retained image should never be accepted merely because nobody checked the interval between campaigns.
Plan for a player that misses the update
Ask which expiry and schedule rules are already held locally and which depend on receiving a later update. Establish what happens if a player loses its connection before the changeover, remains offline at the deadline, or reconnects after the campaign has ended.
Distinguish an end time distributed in advance from an urgent withdrawal sent after the player becomes unreachable. The provider should explain the supported behaviour for both. This is particularly useful when a campaign has a firm stop requirement and some sites have intermittent connectivity.
Agree an exception process with the venue team. Record who checks the affected screen, which approved fallback action is available and who decides whether the situation is resolved. Any equipment intervention should follow the site’s established operating procedure. The article does not assume that a CMS command can reach an offline player.
Use LED display remote monitoring to identify useful connection and health information, while keeping the campaign outcome separate. A reconnecting player is an operational signal; the team still needs evidence that the intended content change took effect.
Rehearse the changeover with representative conditions
Use distinct, authorised test assets so an observer can recognise the old and new content immediately. Schedule a controlled exercise with the supplier and the people who will operate the installation. Record the platform, player version, screen mapping and relevant configuration alongside the result.
Test the ordinary transition first. Observe the display before, during and after the boundary, then compare the result with the agreed end condition. Include an in-progress video if clip completion matters. A successful static-image change does not answer that separate question.
Then select the exceptions relevant to the project. These may include an overlapping recurring event, an expired replacement, a missed update or a player restart. Use the supplier’s supported test method in an evaluation environment or agreed maintenance window. Define expected outcomes before running the tests so that a surprising result is recorded as an exception rather than rationalised afterwards.
For a larger estate, demonstrate each materially different player or configuration and document the rollout checks. The multi-site pilot approval guide can help organise the move from a limited trial to the wider network. A successful test on one configuration should have a clearly stated scope.
Keep a compact changeover record
The person taking over the next shift should be able to understand what ended, what replaced it and what still needs attention. A practical record can contain:
- Outgoing campaign and asset revision, including the assignments checked.
- Affected site, screen, player and content region.
- Last permitted display time and explicit time basis.
- Approved replacement revision and readiness check.
- Expected behaviour at the boundary and during the selected exceptions.
- Observed result, supporting evidence and reviewer.
- Unresolved screens, responsible contact and follow-up action.
Retain evidence according to the organisation’s reporting needs. A photograph establishes what was visible during that observation; a player record establishes a different event. The proof-of-play guide explains these distinctions and helps avoid describing one spot check as a complete campaign history.
Close the changeover only when the agreed checks are complete or the remaining exceptions have a named owner. If the deadline changes, record the approval and the revised schedule together. This preserves a useful history without relying on a series of informal messages.
What to include in a supplier enquiry
For an LED display content expiration requirement, send KSSdisplay the screen count, sites and time zones, existing CMS and player details, content types and required stop behaviour. Explain whether screens change at local time or at a shared instant, what should replace the campaign, and which connectivity conditions need testing.
Include the operator workflow and the evidence your team expects at handover. Use the KSSdisplay project enquiry form to confirm the available display, player and integration scope. Ask for a demonstration of the required changeover on the proposed configuration and identify any third-party software or service needed to deliver it.
Frequently asked questions
Does retiring a file stop it playing immediately?
Do not assume it does. In Xibo’s documented workflow, retirement prevents new selection while existing assignments remain. Check the precise control and its effect on the player in your platform, then use the supported process for the intended stop requirement.
Can a campaign end at midnight in every store?
Specify whether midnight means each store’s local time or one central time. Check overnight events, recurrence and the platform’s scheduling rules, then test the boundary on the proposed configuration.
What if the player is offline when an offer expires?
The result depends on the rules already available to that player and the system’s behaviour. Ask the supplier to demonstrate the planned end time and a missed-update scenario, and agree how a site operator handles an unresolved screen.
What should replace an expired promotion?
Use content approved in advance for that screen and context. Confirm that it is available to the player, fits the canvas and has no outdated claims. Also check the system’s behaviour if that replacement is unavailable.
