Charting a match through a parent's eyes
Match charting is the foundation of CourtSide. This is the full picture of how it works, why we made each choice, and why it's deliberately not built like every other charting app — because you're not an analyst scoring two strangers. You're a parent in the stands, watching your own child.
It starts before the first serve New
Set the plan together
Before the match, you and your child pick up to three things to focus on. Not goals. Not a scoreline. Focuses — the handful of things that actually matter for this match. It mirrors the pre-match talk you already have walking to the court, and it turns that conversation into the frame the whole match is charted against.
Free text, one line each, fully optional. "No focuses this match" never blocks you from charting — it's a ritual, not a requirement.
Then, after each set, you rate one thing about each focus — how well they held it:
Notice what that question is, and what it isn't. It's "did they stick to the plan," never "did they win the point" or "did it work." A kid can stick to their first-serve targets and still get passed. They stuck to it. That's the thing worth seeing, worth saying on the drive home, and worth building on next week.
This is the eyes-forward mindset made literal. Every other number in CourtSide describes what happened on the court. Focuses describe your plan for your child — and rating them on commitment instead of outcome is the whole philosophy in one screen. You're not measuring them against the scoreboard, or against the kid across the net. You're measuring them against the path the two of you chose. That's the path Proverbs is talking about.
The difference that changes everything
Every other tennis charting app is symmetric. There are two players, treated as perfectly equal sides — you assign each shot to whoever hit it, and the app doesn't care which one is yours. That's the correct design for a coach scouting both sides, or a ranking system, or an analyst. It is the wrong design for a parent.
A parent isn't refereeing a contest between strangers. You have one child you care about, one phone, usually one free hand, and one goal: help my kid get better. So CourtSide flips the whole model around a single anchor.
Your child is "the player." The person across the net is "the opponent." Every screen, every button, every stat is organized around what your child did. You never think in "Player 1 / Player 2." You follow one path — your own child's.
A normal charting app
"A forehand winner was hit." → you decide which of two equal players gets it. Neutral. Built for analyzing a matchup.
CourtSide
"What did your child do this point?" → the question, and the answer, always center on your child. Built for developing one player.
Start with one tap. Go as deep as you want.
You're charting live, often nervous, sometimes one-handed. So charting has four depths, and you can switch between them mid-match. Tap as little or as much as the moment allows.
A brand-new tennis mom can start by tapping who won — and still walk away with a real match record. A seasoned tennis dad can capture an inside-out forehand. Same app, same child, growing with the family instead of overwhelming the beginner. Low floor, high ceiling.
How we think about a single point
Here's the heart of it. After every point you answer one question — "Who won this point?" — and then the app asks the only thing that matters for development: "What was your child's role in it?" There are exactly six ways a point can end. Put CourtSide next to a normal charting app, ending by ending, and the difference is impossible to miss — the same point, but one app keeps what teaches you about your kid and the other quietly throws it away.
| What happened | A normal charting app records | What CourtSide records |
|---|---|---|
| Your child hits a winner | Winner — logged to whichever side hit it. Recorded, yes — but as one of two equal sides, not tracked as your child's weapon over a season. | Your child's winning shot + direction. The weapon — how your child ends points on their own terms. |
| Your child forces the error (point won) | Error — charged to the side that missed. Your child's forcing shot — the aggressive ball that won the point — isn't captured at all. It vanishes. | Your child's forcing shot + direction, and the opponent's error wing. The aggressive shot that broke the opponent down — see below, this is the big one. |
| Opponent gives it away (their unforced error / double fault) | Unforced error — charged to the side that missed. Same outcome — but it's just a tally on a neutral, two-sided ledger. | Just the outcome — a free point. Your child didn't do anything to learn from, so we don't make you tap detail you don't have. |
| Your child's unforced error (point lost) | Unforced error — charged to your child's side. How they missed (net/long/wide/shank) is usually optional, so it's often skipped. | Your child's shot, direction, and how it missed (net/long/wide/shank). Their own mistakes are the #1 thing to work on. |
| Your child's forced error (point lost) | Forced error — charged to your child's side. The opponent's shot that beat them isn't linked to your child's record at all. | Your child's shot + direction, and the opponent's forcing shot. What beats them — their defensive exposure. |
| Opponent is too good (their winner / ace) | Winner — logged to the opponent's side. Counted for the other side; nothing that tells you how your child got beaten. | The opponent's winning shot. That's the record of how your child got beaten. |
A normal app is symmetric on purpose — two equal sides, each shot filed to whoever hit it, whether you've typed real names in or not. That's the right design for an analyst scoring two strangers. But look down that middle column: for a parent, that symmetry keeps throwing away the one thing you came for. The parent's real question is never "what happened in the abstract?" It's "what did my kid do, and what does it tell me?" Every CourtSide row centers the detail on your child; the opponent appears only as context, or as the reason your child lost the point.
The shot that wins points — without being a winner
This is the change that matters most, and it's the clearest example of the parent's lens in action. Picture it: your child crushes a heavy forehand, the opponent stretches wide and nets the reply. Your child won that point — with a forehand. They earned it.
But a normal charting app records it as the opponent's error, on the opponent's racket, and throws your child's forehand away entirely. The shot that actually won the point vanishes from your child's record. That's backwards for a parent.
A forced error is your child's offensive achievement, not just the opponent's failure. So when your child forces the error, we record your child's forcing shot — the weapon that did the work — right alongside the opponent's miss.
You saw: your child's forehand forces the opponent into a netted reply. Your child wins.
It works both ways. When your child gets forced into an error, we record their shot under pressure and what the opponent hit to force it — so you learn what beats them, not just that they missed.
In a real 6–3, 6–3 win, your child forced 9 errors. Without this, all nine of those points would say "the opponent missed a forehand" — and you'd have zero record of how your child actually won nearly a third of the points they took. Now you do.
"Are they hunting their forehand?" — inside-out and inside-in
The best junior baseliners run around their backhand to hit a forehand instead. It's a tell — it means the player is aggressively looking for their weapon. A plain "forehand, cross-court" can't capture that the kid moved their feet to make it happen.
So on a forehand, the direction choice isn't three options — it's five:
- Cross-court
- Down-the-line
- Middle
- Inside-out
- Inside-in
Inside-out and inside-in are forehands hit after running around the backhand — one captures direction and footwork in a single tap.
Inside-out and inside-in already are directions (out goes to the opponent's backhand, in goes down the line). Folding them into the direction button means no extra work courtside — but it unlocks a "run-around forehand %," your direct answer to "are they hunting their forehand?" Backhands keep three options; run-around backhands are rare.
Read the kid, not the scoreboard New
A note at the changeover
At a changeover, CourtSide gives you one optional, quiet place to write down what you actually see in your child — and pair it with a cause. Not a stat. A read.
State + cause, in your own words. Always optional — skip every changeover and nothing breaks.
The scoreboard already tells you they're down a break. What it can't tell you is why, or whether they're still in it. You can. "Rattled after the double faults," "settled once they started moving their feet," "tight, gripping the racket" — that's the read only the person who knows this kid can make, and it's the context that makes the numbers mean something six matches from now.
CourtSide will never tell you your child looks rattled — that's load awareness, not load management, and it's your call, not the app's. The changeover note is a calm clipboard at the fence: a place to capture what you're already noticing, so the emotional thread of a match isn't lost the moment the next point starts. Like everything else here, it stays private to you by default.
Every button names the player
The single most confusing moment in charting is "wait — whose error was that?" We removed the guesswork entirely: every prompt says the name out loud.
Confusing
"Unforced Error" · "Winner" · "What shot?" — whose? You're left to remember.
CourtSide
"Your child's Unforced Error" · "Opponent's Winner" · "What did your child hit to force it?" — you always know whose shot you're logging.
The hardest call stays yours — and we keep the real words
Forced error versus unforced error is the most subjective judgment in tennis. We thought hard about softening it with friendlier words. We decided against it: the families CourtSide is built for already speak this language fluently, and dumbing it down would insult them.
You make the forced/unforced call — that's the parent's job, and you're qualified to make it. We keep the standard tennis terms and teach the nuance in onboarding, rather than inventing watered-down words a tennis family would never use.
In that same real match the split was 9 forced, 14 unforced for the opponent — a deliberate, coherent read of a dominant, aggressive win. That's not a coin flip; that's a parent who knows the difference. The data backs the decision.
What we deliberately don't do
- No "Player 1 / Player 2." No neutral, two-sided model. Your child is always the subject.
- No rankings, leaderboards, or "who's better." CourtSide compares your child to themselves over time — never to other kids.
- No gamification. No streaks, trophies, or confetti. Calm clipboard at the fence, not a slot machine.
- Record once, view two ways. Every shot is stored consistently against whoever hit it. A simple "My child / Both players" toggle on the summary lets you widen the view without ever changing what was recorded — so your season-long trends can never be corrupted by charting one match differently than the next.
Everything that makes CourtSide valuable — trends, progress reports, a coach's view — adds matches up over a season. If two matches were charted by different rules, that whole picture turns to noise. So the parent's choices live at the display layer, never the recording layer.
What it all adds up to
Here's that same match (6–3, 6–3 win) read back as a parent's development conversation — every line is something you can act on:
- How they win: 34 winners plus 9 forced errors — genuinely aggressive, not just waiting for mistakes.
- The weapon: the forehand, decisively (15 forehand winners to 4 backhand) — and now we can see how often they run around to hit it.
- The pattern: systematically attacking the opponent's forehand side (19 forehand errors forced out of the opponent).
- The clear thing to work on: 10 double faults in a straight-sets win — the obvious next conversation.
A normal charting app would hand you a neutral box score of two players. CourtSide hands you your child's game — what's working, what's a weapon, and what to work on Monday.
What's intentionally not here yet
The forcing-shot and run-around-forehand numbers are brand new, and right now they live on the individual match summary only. We have deliberately not rolled them into the season-long Trends view or fed them to AI Reflect yet.
These stats sit on top of the forced-vs-unforced judgment — the hardest call in charting. Before we let them shape long-term trends or AI-written feedback, we want to confirm they're being charted consistently in real matches across real families. A development metric that looks precise but is captured unevenly is worse than none. So: prove the data in live charting first, then wire it into the bigger picture. Per-match insight today; season trends once it's earned trust.
The short version
CourtSide charts a match the way a parent actually watches one: one child at the center, every tap telling you something about them, the opponent kept only as context. Set the plan together before the first serve, read your kid at the changeover, start with one tap and go as deep as you like — and never lose track of whose shot you just recorded. That's the foundation — and it's deliberately unlike any charting app built for someone other than a parent.
Keep your eyes on your own child's path.
CourtSide is in early access for competitive junior tennis families.
Get Early Access