The tennis match log: what to record and why.

Most juniors who start a match log keep it for two weeks and abandon it. The reason is always the same: at three matches in, the log is just three rows of data — there's nothing useful to ask of it yet. The work feels disconnected from the payoff.

That changes at around match fifteen or twenty. Once there are enough matches to aggregate, the log starts answering questions you cannot answer any other way. What's my win rate against opponents at or above my level? What chip keeps showing up in "broke down"? Did the player I'm practicing actually show up in the last five matches? Is my form trending or noisy? Those are the questions a season is decided on, and the log is the only honest way to answer them.

The job, then, is to make the log cheap enough to maintain that you actually get to match twenty. Cheap means a small set of fields, captured quickly, in the parking lot before you drive home. Below is the set.

Every match log entry should carry these:

• Date. Obvious, but the only field that lets you ask "trend this season."
• Opponent name. The only field that builds a head-to-head record. Repeat opponents are the most informative matches you play.
• Opponent's level. Their rating, even if it's just "+0.5 above me." Without this, wins and losses are noise.
• Tournament / level of play. A league match, a tournament round, a hit. They are not the same data.
• Score, set by set. The arc of the match matters more than the result.
• Outcome. Win or loss. Separate field because it powers aggregates cleanly.
• What worked. One to three from a fixed chip vocabulary (see the match notes guide).
• What broke down. Same vocabulary, the other side.
• Turning point. One sentence on the moment the match tipped.
• Identity outcome. Did the practice player show up — fully, partly, or no.
• Performance rating. 1–5 of how well you played, independent of result. Lets you separate "played well but lost" from "won ugly."

Eleven fields. Most are one tap. Total time at the end of a match: under three minutes, done before you've finished your post-match recovery drink.

Opponent level + outcome together drive the most important aggregate in junior tennis: win rate by opponent strength. A 70% win rate is flattering until you split it into "vs juniors below my level" (often 90%) and "vs peers and above" (often 30%). The second number is the one that moves your rating; the first one is the one that flatters your confidence.

Set-by-set score opens the loss-leak diagnosis. Across most junior records, the single most predictive loss pattern is lost the first set → lost the match. If that fraction is 60% of your losses, first-set composure jumps to the top of the training plan — regardless of what happens stroke-by-stroke.

The chip pair (worked / broke down) is the bridge from one match to the next practice. Over twenty matches, the chip that shows up most in "broke down" is your live training edge for the next block. It's not always the chip you'd guess.

Turning point exists for re-reads. When you come back to this match six weeks later because you're preparing to play the same opponent or the same level, the turning point is the line that brings the match back. Without it, the row is data; with it, it's a memory.

Identity outcome is the single most underrated field in junior tennis. The practice-self vs match-self gapis one of the largest drags on competitive performance — and it is invisible unless you log it.

Performance rating separates outcome from process. Some losses are good matches; some wins are bad ones. The rating gives you the second number.

Resist the urge to record everything you remember. Things that don't belong in the structured log:

• Stroke counts. Unless you have a coach watching with a spreadsheet, your "first-serve percentage" is a guess. A guessed number that gets aggregated is worse than no number.
• Long freeform descriptions. Anything more than the turning point sentence should live in a separate "notes" field, not in the structured data. The structure is for aggregation; the freeform is for memory.
• How you felt. Mostly. The identity outcome is the structured version of "how you felt." Anything more nuanced belongs in notes.

Twenty matches in, here is what the log can tell you in under a minute:

• "What's my win rate against players at or above my level — and how is that trending across the season?"
• "What chip shows up most in 'broke down' across my last ten matches?"
• "Of my losses, what fraction came after I lost the first set?"
• "In the matches where the practice player showed up fully, what was my win rate vs. the matches where they didn't?"
• "Who's my head-to-head against, and what's the pattern?"
• "Am I playing better than my results say, worse, or about the same?"

You cannot get any of these from a notebook. You cannot get them from a rating. You can get them — within seconds — from a complete, structured log. That is what the log is for.

Forge's match log is exactly this template — every field above maps to a single input, and the aggregates above are surfaced on the growth arc and the Performance page automatically. The match form sits one tap from the home screen on the installed app, so the parking-lot capture is real, not aspirational.

If you're using a notebook, copy the eleven fields above into the front of it and fill them in every match. The structure is the value; Forge just removes the maintenance cost.