Match date to Player ID
Turn the date into one prep cue.
Start with one Smart Attacker card, score the proof, then decide whether to repeat, progress, or test it in a match. Once the match is on the calendar, use the same Player ID read to pick the next rep.
Match prep readWhen the opponent floats a short ball
Training proofPattern clarity: Pattern sheet shows which pattern created advantage most often.
Coach promptWas the attack earned by depth, balance, or court position?
League setup
Publish dates
Structure the season calendar before players and captains start chasing times.
Set schedule →
Scorebook
Team book
Move confirmed matches into score entry when results are ready.
Open book →
Team handoff
Team week
Use the schedule as the handoff into availability, lineups, and messages.
Open week →
Up Next
Confirmed matches stay visible before they become team prep or scorebook work.
Shared schedulerConfirmed dates become prep, messages, and result entry.
DatesWaiting
SitesWaiting
TeamsWaiting
Calendar layersKeep one personal tennis calendar, then layer shared league, team, coach, and message schedules on top.
Scheduling inboxMy calendarEmptyYour private tennis view for matches, practices, lessons, and RSVPs.Open MessagesShared leagueWaitingLeague Office dates everyone can trust before team prep starts.Upload datesTeam overlaysNeeds teamsCaptain views can layer team matches, availability, and lineup work.Open weekExternal syncPlannedGoogle, Outlook, and iCal should subscribe to the same TIQ calendar feed.Coordinate
Loading upcoming matches...
Player ID match prep
Compete from a clear player read.
Start with one Relentless Competitor card, score the proof, then decide whether to repeat, progress, or test it in a match. Use that read before matchup prep, scouting, or captain handoff.
Match priorityWin court position before trying to win the point.
Proof targetMovement: Recovery changes at least three rally outcomes in a set.
Pressure triggerAfter losing two straight games
Captain match-week bridge
Turn Compete context into Team Hub decisions.
Use matchup, scouting, schedule, and team context here to feed the captain week: availability, lineup, scenario, and team message.
1Start with matchup, player, team, and schedule context.
2Turn the read into availability, lineup, scenario, and message decisions.
3Keep Team Hub pointed at the same match-week reality.