Content readiness and health

Launch Readiness

Content > Overview ends with a Launch Readiness section. It reports whether your approved, reviewed content covers your organization. It only reports. It never creates or changes learner content. Choose Refresh evidence to check again.

Each card shows Ready or Gap.

• Microlearning coverage by exact workbook role: each role label needs at least 10 reviewed-ready micro-learnings made for that exact role. Universal ones are listed separately and do not count toward the 10.
• Tier 1 universal foundation: counts the reviewed-ready universal micro-learnings and quests shared with every learner.
• Tier 2 active-Evolver coverage: starting with your largest role groups, checks whether role groups with reviewed-ready role-based quests cover at least 80% of your active Evolvers. A message shows how many active Evolvers have no role group. They are not counted.
• Challenge seed and Prompt starter bank: check coverage against the requirements you set, for challenge themes and for prompt use cases.
• Legacy review backlog: counts legacy versions that still wait for a decision.

Set launch requirements

The Challenge seed and Prompt starter bank checks use the requirements in Governed launch requirements, above the report. If no reviewed requirement is in effect, the report says none are configured and does not pass.

• A draft never changes your readiness report until it is reviewed ready.
• Deactivate requirement stops a requirement from affecting future readiness, and it needs a reason.
• Your reviewed requirement replaces a Stride default with the same key.

1. In Governed launch requirements, choose Weekly requirement for a challenge or Prompt requirement for prompt coverage.
2. Enter a stable requirement key and the exact labels, and choose the role groups or role.
3. Save the draft, then choose Submit for review.
4. A different Client Admin chooses Mark reviewed ready, or Request changes with notes.

Legacy Readiness

Legacy content stays available, but every exact legacy version must either meet today's rules or name a successor.

1. Open Data and choose the Legacy Readiness tab.
2. Select a legacy version and read its snapshot.
3. Complete the Human review checklist.
4. If the version meets today's rules, choose Record reviewed ready.
5. If it does not, choose or create a direct child as its successor, add a rationale, and choose Record successor required.

Content Status

Content Status lists quests, challenges, and learning modules that are blocked or degraded for learners right now. It is computed live. Open it from Challenge Ops > Status, which shows quests and challenges. The Status item in the sidebar lists the same items with other things that need attention.

• Linked module missing, not published, or inactive: a quest or challenge points at a micro-learning that learners cannot open.
• Approved but inactive: the item is approved, but its Active switch is off.
• Training missing its resource, or its link broken or unverified.
• Each row has a severity of Broken, Warning, or Info, and an Open button that takes you to the item.

Where this fits in setup

The Content phase of the Setup guide has five steps that open these pages: Shared Stride content, Organization content, Content review, Content coverage, and Challenge schedule.