Scenario Library

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 currently available only to staff whose organization has an existing simulation agreement or private-preview access.

Who this is for

This guide is for coaches and analysts who want to preserve recurring football situations for staff review.

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.

Scenario records and planned simulation

Saving a scenario records the situation and assumptions your staff wants to review. It does not run a simulation.

Simulation is planned as part of Pro and is not available yet. Its planned workflow uses supported, explicitly recorded conditions and event times to check conditional assignments alongside saved movement and timing or spacing requirements. It does not infer an opponent's reactions from your notes.

The settings in a scenario describe staff inputs, not measured football outcomes. Heuristic preview scores are separate from these play-step checks and cannot tell you a play's chance of success.

How it works

This guide covers these routes when private-preview access is enabled:

If Scenario Library is missing or unavailable, check your organization's access with an owner.

Step-by-step instructions for private-preview users

Use these steps only when HotRoute has enabled the route for your organization and account.

1. Open Organization.
2. Click Scenario Library if the route is visible.
3. Review the scenario table for Scenario, Category, Leverage, Lifecycle, Workflow, and Updated.
4. Click an existing scenario to review it.
5. Click Create Scenario only when the staff has a recurring situation to preserve.
6. On New Scenario, enter Canonical Name.
7. Choose Category and Leverage Tier.
8. Use Custom Category Label only when the available category list cannot express the staff's language.
9. Click Create Draft.
10. On the scenario detail page, keep the record clear enough that another staff member can understand the situation without private customer context.
11. 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. Current access is limited to existing simulation agreements and private-preview organizations.

Does creating a scenario run a simulation?

No. A scenario record names and preserves a football situation. Pro simulation remains planned.

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 to review preparation concerns with your staff.