| Your starting point | Do this first | Evidence needed before proceeding |
|---|---|---|
| Existing demos are failing | Contain the incident: stop sending visitors into known failures, preserve logs and check recent supplier changes | Reproduction steps, affected pages, current permissions and a named technical owner |
| You have working links but unclear permissions | Pause expansion and complete the rights register | An applicable licence or written clarification covering the intended use |
| Rights are clear but essential titles are missing | Compare a named editorial shortlist against supplier exports | Title-level eligibility, configuration details and unresolved exclusions |
| You are choosing between suppliers | Give each the same brief and pilot specification | Comparable rights, coverage, test results and twelve-month costs |
| A pilot passes | Approve only the evidenced launch scope | Product, engineering, commercial and relevant legal/privacy sign-off |
| A critical requirement remains unresolved | Reduce scope, change route or defer launch | A documented exception decision—not an assumption that silence means approval |
Recommended order: brief → rights gate → usable catalogue → controlled pilot → commercial approval → staged launch.
Is there an immediate migration deadline to check?
Existing Slots Launch users should check their signing implementation now. Its Getting Started documentation, last updated on 26 August 2026, announces server-signed iframe embeds and API calls from 15 November 2026. It says unsigned requests will be rejected after that date unless account-level legacy mode is enabled. That deadline is still ahead of this report’s 27 October 2026 review date. (docs.slotslaunch.com)
For affected integrations:
- [ ] Confirm the account’s enforcement date and any exception with support.
- [ ] Assign an engineer to server-side signing and keep the API secret off the client.
- [ ] Test registered-domain matching, expired signatures and production-like page caching.
- [ ] Verify the deployed WordPress plugin’s signing support; do not assume an update is already available.
These actions follow the documented signing, expiry and plugin requirements. The cache-expiry test is a recommended implementation check, not a reported defect. (docs.slotslaunch.com)