Touchline360 · Player development · In development

Follow the player through the season, not just the last match.

An individual-development surface built from evidence the club already creates: appearances, training objectives, coach notes, and season context.

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.

Built forCoaches · Technical directors · Academy staff
In developmentFocused tool

PlayerPath

This surface is actively being developed. The public product page shows what exists now and keeps unfinished work labeled as such.

Product proof

A real surface from PlayerPath.

Real in-development PlayerPath squad capture with evidence and minutes caveats shown on screen.

PlayerPath squad view showing evidence and minutes context
Real in-development PlayerPath squad capture with evidence and minutes caveats shown on screen.

Core capabilities

What this part of the coaching loop needs to do well.

Capability language is grounded in the current Touchline360 product registry and product documentation.

01

Build a player record from club-owned match and training evidence

02

Show season context without hiding evidence gaps or minutes caveats

03

Connect objectives to subsequent appearances and coaching notes

04

Support development conversations with traceable context

Inputs

What comes in.

  • Appearances
  • Training objectives
  • Coach notes
  • Evidence coverage

Outputs

What the staff gets back.

  • Player timeline
  • Development context
  • Objectives
  • Evidence-aware squad view

Touchline360 connection

PitchView + Blueprint → PlayerPath → training priorities

The suite is designed around one coaching loop: evidence, judgement, action, and the next evaluation.