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.
From one spreadsheet to a stats database
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.
- 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.
- 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).
- Make a new spreadsheet with four tabs: Players, Matches, Points and Dictionary.
- In Players, give each player a code (P1, P2...) and no full names.
- In Matches, add one row per match with a MatchID (M01, M02...), date, player code, surface and opponent level.
- In Points, add the columns from your 10.8.2 tag log plus a MatchID column.
- In Dictionary, write one line for each column: meaning, allowed values and counting rule.
- Enter one real or practice match: one row in Matches, one row per point in Points.
- Check: every MatchID in Points also exists in Matches, and no row contains a total.
Videos by other creators on YouTube, for reference. They are not made by or affiliated with The Future Market.
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."
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.
Sources
- Microsoft Support, Overview of Excel tables: support.microsoft.com/en-us/office/overview-of-excel-tables-7ab0bb7d-3
- Table design (one row per thing, IDs, data dictionary) is common data practice. Example codes are made up.
Clean data in, clean data out
This lesson is part of full access: every course and every level for one payment.
Asking the database questions
This lesson is part of full access: every course and every level for one payment.
Building an honest dashboard
This lesson is part of full access: every course and every level for one payment.
Luck, regression to the mean and false alarms
This lesson is part of full access: every course and every level for one payment.
The season review
This lesson is part of full access: every course and every level for one payment.
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
What are the three main tables in a simple stats database?
Players, Matches and Points.
What links a point to its match?
The MatchID in each point row.
Why use codes like P1 instead of names in shared tables?
To protect privacy; the name list is kept in a separate private file.
Why use drop-down lists?
So everyone types the same exact values and the counts stay correct.
What should you check after entering a match?
That the number of rows equals the number of points played, and Won plus Lost equals the rows.
How do you get a season first serve percentage from several matches?
Add the serves in, add the serves tried, then divide once.
What should appear next to every percentage on a dashboard?
The sample size, for example "400 of 625".
What does a slicer do?
Filters the charts and pivot tables on a sheet, for example by surface.
A player has one great match and then a normal one. What is this an example of?
Regression to the mean; part of the great match was probably luck.
Why are you likely to find a "special" stat if you check 20 stats?
With many stats, at least one will look special by luck alone (about a 64% chance in the example).
The second half of the season is 2.9 points better, and the likely range includes zero. What do you call it?
An encouraging sign or clue, not proof.
What sharing setting should a player's report have?
Viewer access for the player (and parent or guardian), with General access set to Restricted.
Final exam
This lesson is part of full access: every course and every level for one payment.
Certificate
This lesson is part of full access: every course and every level for one payment.