Project planning
A practical checklist for choosing a digital signage system
Make the demo resemble a real working day. Record what you tested and which questions still need answers before choosing a system.

Key takeaways
- Compare systems using everyday tasks and real files from your business.
- Keep verified device test results separate from promises and open requirements.
- Review support, renewal and service terms before paying and rolling out.
Write down the tasks you actually need to complete
A system may look convincing when it plays a prepared video on one screen. A buying decision needs a trial closer to your work: changing a menu, sending a campaign to selected branches or identifying a display that needs attention. List the essential tasks and use them as test cases when comparing systems.
Record the number of screens and branches, who prepares and publishes content, and how often it changes. Separate current needs from possible future requirements. This gives each supplier a clear brief and helps you verify essential work before installing the equipment.
Provide a device list with full model details
Record the model number, operating system or firmware version, and player for each type of device. Ask which route is proposed for each group: a built-in player, external device or another verified option. Support for LG, Samsung and Android does not establish compatibility with every product carrying those names.
Request a trial on a sample matching what you will use. If a device needs special setup or user confirmation after a restart, record that as part of daily operation. Check the screen’s own instructions, operating hours and permitted orientation too. Software compatibility does not change hardware limits or warranty terms.
Run a publishing trial from start to finish
Use images and videos from your business. Try uploading, arranging, publishing and updating them, starting with one screen or a small group, then check the result on site. Test different content at two branches so you can see how to select the intended displays and keep a local offer limited to its location.
Try a campaign start and end time, then observe what appears when it ends. Check how the dashboard reports screen connectivity and what information is available when something goes wrong. Distinguish an accepted publishing request from downloaded files and correct on-screen playback. Record what you saw on the display as well as what the dashboard reported.
Test outages and ask about integrations
If you need playback during an internet outage, test it on the actual device after media downloads have completed. Ask which content types keep working, which need a connection or local alternative, and how you check the device when it reconnects. Test the files and web-based content you intend to use rather than generalizing from one cached image.
For a point-of-sale, inventory or other integration, request a written description of the data exchanged and how the connection will be tested. Publishing artwork manually is a different workflow from automatically updating prices from another system. Keep an unavailable or untested integration marked as an open requirement until it has been resolved.
Review support and subscription terms before paying
Ask how to open a support request, what information to provide and who takes responsibility when the cause is the screen, network or player. Request written service terms and any specific response commitments. Establish what the subscription includes and what requires a separate service.
Review the subscription term, licence count, taxes, adding screens, renewal, cancellation and refunds. Understand what happens to content and account access when the subscription expires, and how you will retain your original files. Within your team, also decide who approves prices and campaigns before they are published.
Keep a decision record before approval
Use three columns: the requirement, what you observed in the trial, and what remains open with a named person to follow up. You do not need to test every possible scenario, but resolve the points your daily operation relies on before rollout.
- Target devices and test stages are documented by model and version.
- Uploading, editing and distributing content have been tested with your own files.
- Scheduling, campaign end behaviour and playback have been checked on screen.
- Offline behaviour and required integrations have been tested or recorded as unverified.
- Support responsibilities, subscription terms and renewal conditions are clear in writing.
- Someone owns publishing, and someone on site can confirm the actual display.
Download the checklist
Record each check and your team’s notes in a ready-to-use spreadsheet. Open it in Excel or Google Sheets.
Download checklist CSVFind your display setup guide
Compatibility depends on the model, firmware and player. Check the relevant guide before subscribing.
