Feature Guides
Scenario Library
Learn what HotRoute scenario library records mean, how private-preview staff use them, and why broad scenario workflows remain gated while simulation tools mature.
Overview / Purpose
A scenario is a recurring, high-leverage football situation that a staff wants to name, review, and preserve as part of the organization's operating memory.
The scenario library is launch-approved for contracted add-on and private-preview organizations. It is not a broad launch-live customer feature for ordinary users. Public docs should explain the concept without implying that every customer can create, run, or simulate scenarios today.
No public product screenshot is included on this page because broad scenario-library UI remains gated. Do not fabricate screenshots for preview-only or hidden UI.
Who this is for
This guide is for coaches, analysts, staff operators, and product evaluators who need to understand scenario language before a private-preview or validation conversation.
It is also useful for owners who need to explain why scenario work may be hidden even when related preparation workflows are visible.
What to know first
Scenarios are not weekly gameplan notes. They describe recurring situations, such as a pressure-answer moment, backed-up operation, red-zone constraint, late-half clock situation, or other decisive football context.
A scenario should be opponent-invariant enough to reuse. Weekly gameplans can reference or adapt a scenario, but the scenario record should not become a one-week scratchpad.
How it works
This guide covers these routes when private-preview access is enabled:
| App route | What it is for |
|---|---|
/organization/scenarios | Browse scenario library records for the organization. |
/organization/scenarios/new | Create a draft scenario record when allowed. |
/organization/scenarios/[id] | Review or edit one scenario record. |
The route may be hidden, denied, or unavailable for most launch users. That is expected while simulation tools and scenario workflows mature.
Step-by-step instructions for private-preview users
Use these steps only when HotRoute has enabled the route for your organization and account.
- Open Organization.
- Click Scenario Library if the route is visible.
- Review the scenario table for Scenario, Category, Leverage, Lifecycle, Workflow, and Updated.
- Click an existing scenario to review it.
- Click Create Scenario only when the staff has a recurring situation to preserve.
- On New Scenario, enter Canonical Name.
- Choose Category and Leverage Tier.
- Use Custom Category Label only when the available category list cannot express the staff's language.
- Click Create Draft.
- On the scenario detail page, keep the record clear enough that another staff member can understand the situation without private customer context.
- Move lifecycle state only when the staff has reviewed the scenario for reuse.
What good looks like
A good scenario record is specific enough to teach and broad enough to reuse.
Staff should be able to answer:
- What recurring football situation does this describe?
- Why is it high leverage?
- Which category and leverage tier explain it?
- Which staff workflow owns review?
- Is the record draft, review, active, deprecated, or archived?
- Which weekly gameplans or practice plans may reference it later?
Common questions or mistakes
Is the scenario library live for every launch customer?
No. Treat it as contracted add-on or private-preview unless HotRoute explicitly enables it for the organization.
Does creating a scenario run a simulation?
No. A scenario record names and preserves a football situation. Simulation behavior is a separate, gated capability.
Should I create a scenario for every opponent note?
No. Use gameplans for week-specific opponent work. Use scenarios for reusable, high-leverage situations.
Related docs / next steps
Read Modeling and Simulation for the broader product-area framing.
Read Simulation Profiles for the related private-preview simulation-profile concept.
Read Weekly Readiness for staff-owned readiness review language.