Feature Guides
Simulation Profiles
Learn what HotRoute simulation profiles control for contracted add-on and private-preview access, and how to describe them without making launch-live AI or simulation claims.
Overview / Purpose
A simulation profile describes the controlled parameters for contracted add-on or private-preview simulation-related advisory workflows.
Simulation profiles are launch-approved for contracted add-on and private-preview organizations. They are not a broad launch-live customer feature, not an autonomous coaching system, and not a promise that HotRoute will make live game decisions.
No public product screenshot is included on this page because broad simulation-profile UI remains gated. Do not fabricate screenshots for preview-only or hidden UI.
Who this is for
This guide is for coaches, analysts, owners, operators, and product evaluators who need careful language for simulation-profile conversations.
It is especially useful when a customer or staff member asks why a route exists in architecture or validation material but is not visible in ordinary product navigation.
What to know first
Simulation profiles roll up to a simulation-tools feature area that is contracted add-on or private-preview for controlled validation. Ordinary launch users should not assume access.
When enabled, the profile is configuration context. It does not replace the coach, select a play, decide a roster, diagnose readiness, or guarantee an outcome.
Any output connected to a simulation profile should remain advisory, explainable, and tied to staff authority.
How it works
This guide covers these routes when private-preview access is enabled:
| App route | What it is for |
|---|---|
/organization/simulation-profiles | Browse simulation profiles for the organization when enabled. |
/organization/simulation-profiles/[id] | Review or edit one profile when enabled. |
The route may show a private-preview unavailable state or be hidden for ordinary launch users. That is expected.
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 Simulation Profiles if the route is visible.
- Review the current team, season, and lifecycle filters.
- Open an existing profile when the staff needs to inspect its configuration.
- If create controls are enabled, create a draft profile only for an approved validation purpose.
- Give the profile a clear football name, not a generic test label.
- Keep parameter descriptions tied to coach-readable football context.
- Save the draft.
- Activate, deprecate, or archive profiles only through the approved staff or validation path.
- Do not describe private-preview profile behavior as generally available until the product gate changes.
What good looks like
A good profile is controlled and explainable.
Staff should be able to answer:
- Which team, season, and validation purpose does this profile belong to?
- Which staff authority approved the profile?
- Which scenario or preparation context may use it?
- What lifecycle state is it in?
- Which claims are allowed, and which are still preview-only?
Common questions or mistakes
Are simulation profiles available to all launch customers?
No. Treat them as contracted add-on or private-preview unless HotRoute explicitly enables the organization.
Does a simulation profile mean HotRoute is coaching autonomously?
No. Profiles are intended as controlled configuration for advisory workflows. Coaches and staff remain the authority.
Can docs show screenshots of preview-only simulation UI?
No. Public docs should not fabricate or imply broad access to hidden UI.
Related docs / next steps
Read Modeling and Simulation for the broader product-area framing.
Read Scenario Library for the related high-leverage scenario concept.
Read Staff Authority when the workflow depends on human responsibility.