THE EVIDENCE LAYERContext changes everything.
PitchView is what everything else in the suite looks through: the data your club holds, where each piece came from, and what any claim on any screen is actually standing on.
Coverage you can audit
Every source the platform holds, what it carries, how fresh it is and what its licence permits, for the whole club, on one page, with the registry behind each line.
Provenance on every figure
A number on any screen can say where it came from. One this deployment cannot answer says unavailable and names what would have answered it, rather than showing a zero that reads as an empty dataset.
The views that look through it
Opponent intelligence and player development are not separate databases. They are two ways of reading the same evidence, which is why they never disagree with the match review.
Why it matters to a director of football
Analysis is only worth what its evidence is worth. PitchView is the answer to “where did that number come from, and are we allowed to use it”, a question that usually gets a shrug. A source whose terms have not been reviewed is never treated as permitted, and the page says so rather than quietly including it.
What sits on it
- Debrief’s findings each point at the moment they came from.
- ScoutLens reads the opponent through it.
- PlayerPath reads the player through it.
- Kickoff Pulse puts what it captured at the touchline into it.
Where it actually is
The coverage console runs in the app today for club owners, reading the real source registry and the real licence policy. Provenance itself is further behind than the coverage console: figures carry their source in the API, and the badge that shows it is built, but it is not yet placed on any screen. The platform underneath it has been running for months under its engineering name, Groundwork; PitchView is that platform said to a club rather than to an engineer.