Start Here
Getting Started
Use HotRoute by first understanding the organizational problem it solves, then reading the platform through the lens of role clarity, workflow continuity, and shared memory.
Who should start here
Start here if you are opening HotRoute with a broad question like “what do I look at first?” or “how should my staff think about this product?”
The best first move is not to hunt for every feature. The better move is to understand the kind of operating problem HotRoute is designed to solve.
The right first questions
Early evaluation usually goes better when you ask questions like these:
- Where does our staff lose continuity between concept, teaching, and execution?
- Where do responsibilities blur between coaches, analysts, and operators?
- What knowledge do we keep recreating instead of retaining?
- Where do weekly coordination demands create avoidable burden?
If those questions feel familiar, you are reading HotRoute through the right lens.
Pilot lens
The strongest first pass is not a feature inventory. It is a continuity check: where does intent lose shape as it moves between design, teaching, weekly operations, and memory?
A practical first reading path
Use this sequence for an MVP-level understanding:
- What is HotRoute? to get the category and boundaries right
- How HotRoute Is Organized to understand the five connected areas
- the product area most aligned with your role
- one workflow page that shows how the areas connect in practice
- Glossary if you want the shared language in one place
This path is deliberate. HotRoute becomes easier to understand when you see how the pieces connect, not when you inspect them as isolated screens.
product frame -> five-area model -> role-specific product area -> workflow example
Modeling and Simulation
Start with the product area that makes football logic explicit.
Coordinate the Week
Jump to a practical workflow that shows how the areas connect.
What not to expect on day one
Do not expect this docs site to serve as a click-by-click operator manual. That is not the MVP goal.
These pages are meant to help you answer:
- what the product is trying to make true
- how the work is organized
- how roles and workflows fit together
- where to go next for deeper evaluation
That is enough to build trust without pretending the product is simpler than it is.