Stage 6: What must be ready before launch and renewal?

Approve a defined release, not the supplier in perpetuity. Use the following proposed sign-off and monitoring plan.

Launch checklist

[ ] Product: approves the experience, fallback and launch scope.
[ ] Content: approves title identity, metadata provenance and publication readiness.
[ ] Engineering: approves integration, secrets handling, monitoring and rollback.
[ ] Legal/privacy: resolves matters requiring specialist review.
[ ] Commercial: approves costs, commitments, renewal dates and exit exposure.
[ ] Operations: owns supplier contacts, incident handling and change monitoring.

Start with the approved subset. Expand only after new content clears the same gates.

[ ] Monitor launch outcomes using the agreed readiness signal, not iframe load alone. (developer.mozilla.org)
[ ] Recheck priority titles after supplier, browser, authentication or consent changes.
[ ] Track additions, withdrawals, metadata changes and unanswered rights questions.
[ ] Compare actual usage charges and maintenance hours with the buying model.
[ ] Revalidate domains, targeted territories and presentation when the business changes.
[ ] Begin renewal review before the contractual notice deadline.
[ ] Maintain a non-playable editorial fallback and test supplier withdrawal handling.