Feature Guides
Weekly Readiness
Learn how HotRoute weekly readiness helps staff review preparation signals, ownership, and risks without becoming a medical, roster, or autonomous decision tool.
Overview / Purpose
Weekly Readiness is a preparation review surface. It helps staff look at the state of the week, identify concerns, and connect follow-up work to the right football context and owner.
Readiness is not a medical readiness system, roster authority tool, player-availability decision system, or autonomous coaching decision. It is a staff review aid for football operations.
Who this is for
This guide is for head coaches, coordinators, analysts, staff operators, and owners who need to review the week before the next handoff.
It is especially useful when the staff wants to know which part of preparation needs attention and who owns the next action.
What to know first
Weekly Readiness is available to enabled Veteran, Pro, and All-Pro organizations for owners and staff users.
If your organization, role, or subscription tier does not include Weekly Readiness, HotRoute may hide the navigation item or show an unavailable state. That state is an access message, not a sign that football data is missing.
Readiness should point back to visible source context, such as gameplans, install packages, practice plans, staff responsibilities, standards, or assignments. Do not treat a readiness concern as customer proof, a measured outcome, a medical fact, or a roster decision.
How it works
This guide covers this route:
| App route | What it is for |
|---|---|
/weekly-readiness | Review preparation signals, concerns, owners, and next-action context when enabled. |
In football terms, a readiness briefing answers: "What needs staff attention before the next practice, meeting, or game-prep handoff?"
Step-by-step instructions
- In the left navigation, click Weekly Readiness when it is visible.
- Confirm the selected team and season.
- Review the summary cards first.
- Scan concern cards for the preparation area, severity, owner, and supporting context.
- Open the source object when the concern points to a gameplan, practice plan, install package, assignment, or standard.
- Use the staff owner or responsibility language to decide who should review the issue.
- Record the staff decision in the appropriate source workflow, not as an unsupported readiness claim.
- Return to the briefing after source updates to review whether the visible preparation state changed.
What readiness language means
Use readiness language carefully.
| Term | Meaning in HotRoute docs |
|---|---|
| Concern | A preparation item that may need staff review. |
| Owner | The staff role or person expected to review the concern. |
| Evidence | Visible football or operations context that explains why the concern appears. |
| Next action | The staff-controlled follow-up, such as reviewing a gameplan tab or confirming a practice block. |
Avoid language that implies HotRoute has diagnosed a player, selected a roster, guaranteed performance, or made the coaching decision.
What good looks like
A useful readiness review is traceable and staff-owned.
Staff should be able to answer:
- Which team, season, and week is being reviewed?
- Which concern needs attention?
- Which source object explains the concern?
- Who owns the follow-up?
- What staff-controlled action should happen next?
- Which claims are outside the readiness surface and need a human authority path?
Common questions or mistakes
Why does the page say Feature unavailable?
The organization, role, or subscription feature may not be enabled for Weekly Readiness. That is a gate state, not a data-loss message.
Does readiness decide who plays?
No. Roster, player availability, and medical decisions remain with the appropriate human authorities.
Can I cite readiness as proof that HotRoute improved outcomes?
No. Treat readiness as operational context for staff review unless a separately approved proof source supports a specific claim.
Related docs / next steps
Read Coordinate the Week for the broader preparation flow.
Read Gameplans and Print Exports when a readiness concern points to weekly gameplan context.
Read Staff Authority when the concern depends on ownership or responsibility.