DIRECT ANSWER
Select a CMS by the processes it can support: create, approve, schedule, distribute and withdraw content. Also test network loss, permissions, rollback and leaving the service. Separate content management from device management. Do not accept a feature list as evidence that it will operate correctly across your sites.
Run a real content change
Create a campaign with start and end dates, a local exception and central approval. Check the time zone and what happens when content expires. Change a file and record who published it. Ask a person without permissions to try changing a site: the restriction should be part of the test.
Disconnect a player
Useful caching depends on which files are stored, when they expire and how playback recovers. Test an expired message offline, then restart. On reconnection, verify the current version and the alert. A dashboard showing “online” does not establish that the correct content is visible.
Review access, cost and exit
Request separate roles, change logs and multifactor authentication where available. Ask for user, device, storage and support pricing without assuming everything is included. Export files and documentation during the pilot. Put in writing what happens to content and accounts when the contract ends.
- CMS
- Network / cache
- Verify image
What to request and check
On mobile, scroll right to see every column.
| Criterion | Need | Check |
|---|---|---|
| Publishing | Approval and scheduling | Campaign with an exception |
| Offline | Cache and expiry | Disconnect and restart |
| Access | Roles and logging | Attempt without permission |
| Exit | Export and ownership | Export during the pilot |
Action checklist
- Test creation, approval and withdrawal.
- Test expired content offline.
- Review roles and multifactor access.
- Distinguish licenses and additional costs.
- Export a project before signing.
Document the result of each action and assign an owner for what remains pending.
Common questions
Are CMS and remote management the same?
No. They can be integrated, but publishing content and controlling devices are different capabilities.
Does proof of play measure an audience?
No. It records playback according to the system; it does not establish attention or people’s presence.
Sources and scope
- CISA · Multifactor authentication ↗
Reference on multifactor authentication. It is not an audit of a particular CMS.
Confirm values, operating conditions and warranty in the current model specification before accepting a quote.
Technical references