THE FUTURE MARKETACADEMY
Your classroomRoom 10 · Sports Arena
School of Sports & Health (education only)

Performance Analysis Systems: databases, dashboards and season reviews

Education only. This course is not legal advice or privacy advice. Spreadsheet facts come from Google Docs Editors Help, Google Drive Help and Microsoft Support (menu names can differ by version). All match numbers are made-up practice numbers for one imaginary player, checked with Python, not real players. Statistics here are standard textbook methods, not a guarantee that any change will make a player win. Privacy rules differ by country: see In your country in Lesson 7, and ask your club, school or venue about their filming and data rules.

What you'll be able to do
  • Design a small stats database with separate tables for players, matches and points, linked by IDs.
  • Keep data clean with drop-down lists, fixed codes and a data dictionary.
  • Answer questions from the database with pivot tables, COUNTIFS and the QUERY function.
  • Build an honest one-page dashboard with sample sizes and slicers.
  • Explain luck, regression to the mean and false alarms in a season of matches.
  • Run a season review that compares blocks, surfaces and opponents fairly.
  • Present results to players and parents, and share the system safely and privately.
Words in this course 57Open the Vocabulary Hall
01

From one spreadsheet to a stats database

In simple words

Imagine a library. One shelf lists the readers, one shelf lists the books, and a card says which reader borrowed which book. A stats database is the same: one list of players, one list of matches and one long list of points, joined by ID numbers.

Before this course: Match Analysis in Practice (course 10.8.2), which builds on Match Stats & Video Analysis Basics (course 10.8). You should already chart rallies and serves, tag video, use COUNTIFS, compare matches with rolling totals and keep player data private. This course turns those single files into a system that lasts a whole season.

Key facts
  • A database (here, a spreadsheet with several tabs) keeps each kind of thing in its own table. One row = one thing. One column = one kind of fact.
  • Three tables are enough for most clubs (common practice):
Table (tab)One row isExample columns
PlayersOne playerPlayerCode (P1), Group (U14), Hand (R or L)
MatchesOne matchMatchID (M01), Date, PlayerCode, Surface, OppLevel, Format
PointsOne pointPointID, MatchID, Server, ServeNo, Direction, Result, Shots, Ending
  • IDs link the tables. Each match row has a PlayerCode; each point row has a MatchID. You never retype the date or surface on every point, so you cannot type it wrong 80 times.
  • Use codes, not names, in shared tables (course 10.8.2, lesson 7). Keep the list that matches codes to real names in a separate, private file.
  • One row per point is the most useful level. You can always add points up into matches and seasons, but you cannot split a total back into points.
  • Never put totals inside the data tables. Totals belong in a separate Summary or Dashboard tab, built with formulas.
  • A data dictionary is a short tab that explains every column: its name, what it means, the allowed values and the counting rule (for example, "Shots: the serve counts as shot 1").
  • In Excel, Format as Table turns a range into a table with a header row, filter buttons, calculated columns and structured references. Google Sheets also has table tools (names can differ by version).
  • Pickleball works the same way: add columns for the things you count (for example, ThirdShot = Drop or Drive).
Step by step
  1. Make a new spreadsheet with four tabs: Players, Matches, Points and Dictionary.
  2. In Players, give each player a code (P1, P2...) and no full names.
  3. In Matches, add one row per match with a MatchID (M01, M02...), date, player code, surface and opponent level.
  4. In Points, add the columns from your 10.8.2 tag log plus a MatchID column.
  5. In Dictionary, write one line for each column: meaning, allowed values and counting rule.
  6. Enter one real or practice match: one row in Matches, one row per point in Points.
  7. Check: every MatchID in Points also exists in Matches, and no row contains a total.
Watch it
Watch on YouTube
Structured tables for Google SheetsDavid Benaim · YouTube · youtube.com

Videos by other creators on YouTube, for reference. They are not made by or affiliated with The Future Market.

LESSON 01From one spreadsheet to a stats database
LESSON 01 / ANIMATED LESSON / AI VOICE00:00 / 01:00
Read the video script
[Host] "One spreadsheet per match works for a week. For a season, you need a database."
[Text on screen: Players, Matches, Points] "Keep three tables: players, matches and points."
[Text on screen: IDs link the tables] "Each point carries a match ID. Each match carries a player code. Type the details once."
[Text on screen: Codes, not names] "Use codes like P1 in shared files, and keep the name list private."
[Host] "One row per point, no totals in the data, and a dictionary that explains every column."
Try it now

Build the four-tab database and enter one match. Ask a friend to read the Dictionary tab and tell you what "Shots" and "Ending" mean.

ClaudeStuck? Copy a ready-made prompt for Claude

Copy this, open Claude, paste it, and Claude will walk you through the lesson step by step.

For a grown-up: Claude is for adults (18+). Copy this, paste it into Claude, and use the answer to explain the lesson to your child.

I'm learning "Performance Analysis Systems: databases, dashboards and season reviews" on The Future Market. Lesson 1: "From one spreadsheet to a stats database".

What the lesson teaches:
- A database (here, a spreadsheet with several tabs) keeps each kind of thing in its own table. One row = one thing. One column = one kind of fact.
- Three tables are enough for most clubs (common practice):
- Table (tab) - One row is - Example columns
- Players - One player - PlayerCode (P1), Group (U14), Hand (R or L)
- Matches - One match - MatchID (M01), Date, PlayerCode, Surface, OppLevel, Format
- Points - One point - PointID, MatchID, Server, ServeNo, Direction, Result, Shots, Ending
- IDs link the tables. Each match row has a PlayerCode; each point row has a MatchID. You never retype the date or surface on every point, so you cannot type it wrong 80 times.

The exercise I'm working on:
Build the four-tab database and enter one match. Ask a friend to read the Dictionary tab and tell you what "Shots" and "Ending" mean.

I'm stuck. Please:
1. Explain the main idea in plain, simple words with one everyday example.
2. Walk me through the exercise one small step at a time. Ask me what I've done so far before giving the next step.
3. Don't just give me the final answer. Help me do it myself, and check my work when I share it.
4. This is for learning only. Remind me to check with a licensed professional before I make a real decision about my own money, health or legal situation.
I'm a parent helping my child (about 8 years old) with a lesson called "From one spreadsheet to a stats database" from the course "Performance Analysis Systems: databases, dashboards and season reviews".

Here's what the lesson says:
Imagine a library. One shelf lists the readers, one shelf lists the books, and a card says which reader borrowed which book. A stats database is the same: one list of players, one list of matches and one long list of points, joined by ID numbers.

The activity:
Build the four-tab database and enter one match. Ask a friend to read the Dictionary tab and tell you what "Shots" and "Ending" mean.

Please explain this so an 8-year-old understands: short sentences, a fun everyday example, and no hard words.
Then give me 3 simple questions I can ask my child to check they understood, and a way to do the activity together, one tiny step at a time.
Keep it general and educational. This is not advice for a real situation.
Open Claude
Sources
My notes
02

Clean data in, clean data out

This lesson is part of full access: every course and every level for one payment.

03

Asking the database questions

This lesson is part of full access: every course and every level for one payment.

04

Building an honest dashboard

This lesson is part of full access: every course and every level for one payment.

05

Luck, regression to the mean and false alarms

This lesson is part of full access: every course and every level for one payment.

06

The season review

This lesson is part of full access: every course and every level for one payment.

07

Presenting to players and parents, and sharing safely

This lesson is part of full access: every course and every level for one payment.

++

Final project

This lesson is part of full access: every course and every level for one payment.

??

Quiz

  1. What are the three main tables in a simple stats database?

  2. What links a point to its match?

  3. Why use codes like P1 instead of names in shared tables?

  4. Why use drop-down lists?

  5. What should you check after entering a match?

  6. How do you get a season first serve percentage from several matches?

  7. What should appear next to every percentage on a dashboard?

  8. What does a slicer do?

  9. A player has one great match and then a normal one. What is this an example of?

  10. Why are you likely to find a "special" stat if you check 20 stats?

  11. The second half of the season is 2.9 points better, and the likely range includes zero. What do you call it?

  12. What sharing setting should a player's report have?

EX

Final exam

This lesson is part of full access: every course and every level for one payment.

CE

Certificate

This lesson is part of full access: every course and every level for one payment.