The workflow problem
Keep the useful context moving.
Player development becomes subjective when evidence is scattered between team sheets, sessions, clips, and memory. PlayerPath is being built to preserve the player's longitudinal coaching story.
Touchline360 · Player development · In development
An individual-development surface built from evidence the club already creates: appearances, training objectives, coach notes, and season context.
The workflow problem
Player development becomes subjective when evidence is scattered between team sheets, sessions, clips, and memory. PlayerPath is being built to preserve the player's longitudinal coaching story.
This surface is actively being developed. The public product page shows what exists now and keeps unfinished work labeled as such.
Product proof
Real in-development PlayerPath squad capture with evidence and minutes caveats shown on screen.

Core capabilities
Capability language is grounded in the current Touchline360 product registry and product documentation.
Inputs
Outputs
Touchline360 connection
The suite is designed around one coaching loop: evidence, judgement, action, and the next evaluation.