How to write tennis match notes that actually help.

The match ended badly. You drive home. By the next afternoon at practice, the memory has compressed into a single sentence — "I played terribly" or"my forehand was off". A week later, when the coach asks what happened in that match, that sentence is all you've got. It does not tell you what to work on. It does not connect to last week's training. It is closer to a feeling than a report.

The fix is not "write more." The fix is to capture a small, repeatable set of things while the match is still vivid — within an hour of the last point. Three minutes in the parking lot beats thirty minutes the next morning. The match has decayed by then.

Resist the urge to write a paragraph. Capture these:

• The score — including the set-by-set games. The arc matters, not just the result.
• What worked — one or two specifics. "First-serve placement to the T was a weapon today." Not "I played well."
• What broke down — one or two specifics. "Second serve sat up after I lost the first set." Not "my serve was off."
• The turning point — the moment the match shifted, in one sentence. "Up 4-2 in the second I missed an easy putaway, broke me mentally."
• Did the practice player show up? — yes, partly, no. One answer, no caveats.

That's it. Five fields. The score, two specifics on what worked, two on what broke down, the turning point, and the identity question. Whatever else you remember can live in a "notes" field if you want, but the five above are the structured data that connects to your training plan.

The single biggest upgrade in match notes is replacing adjectives with specifics. Adjectives feel meaningful when you write them and tell you nothing when you read them back.

• Bad: "Forehand was bad." Better: "Forehand short on the cross-court rally — couldn't push past the service line by mid-second set."
• Bad: "Felt nervous." Better: "Tightened up serving for the first set; pulled the toss; double-faulted at 30-30."
• Bad: "Couldn't close." Better: "Serving for the match at 5-3, got passive — three first serves missed by the line."

The specific version connects to a drill. The adjective version connects to nothing.

A faster version of "what worked, what broke down" that scales across a season: a small fixed vocabulary of chips. Forge uses fourteen: first serve, second serve, returns, forehand, backhand, depth, footwork, net play, focus, calm under pressure, shot selection, energy, between-point routine, closing.

After a match you tap the two or three that worked and the two or three that broke down. Same vocabulary, every match. That gives you something the freeform sentence can never give you: aggregation. Twenty matches in, you can ask "across my last twenty matches, what chip shows up most in 'broke down'?" If the answer is "second serve" for the fourth season in a row, that's a training plan decision.

The chips are also fast. The full reflection takes ninety seconds. There is no excuse not to do it.

One more field worth recording every time: did the player you practiced show up today? Three answers — fully, partly, no. That's the whole field.

On its own it feels too simple to mean anything. Logged across twenty matches it is one of the most predictive signals you have. A junior who reports "fully" 75% of the time is in a different place than one who reports "no" 50% of the time — regardless of rating. The practice-self vs match-self gapis one of the most important things to track honestly.

Notes that don't drive action are diary entries. The action loop:

• After the match — capture the five fields.
• Within 48 hours — translate one "broke down" item into a concrete drill for the next practice. Not "work on my serve" — "fifteen kick second serves to the deuce side, deeper than the service line, score one each landing, restart at zero on a short one."
• Next match — see if it stayed fixed. The chip either shows up in "worked" or back in "broke down."

That loop — match → notes → drill → next match — is what separates training that transfers from training that fills time. Without the notes, the loop is broken at step one.

A common mistake is to only write notes after losses. Wins are at least as worth reading back. The chip method makes it easy: record what worked alongside what broke down. The point of writing what worked is not to celebrate; it is toprotect it. The skills that are working are the ones you stop drilling — which is how they quietly stop working. Logged, they stay on the radar.

The reflection dialog in Forge runs exactly this method. After every logged practice or match the chip picker comes up; you tap what worked and what broke down, answer the identity question on a match, save. Forge then composes the action items deterministically from what you marked — up to three concrete next steps you confirm or dismiss. The confirmed items carry forward to the next session so the loop closes by itself.

The chips, the identity question, and the five-field discipline work just as well in a notebook. Forge just makes the loop cheaper to maintain across a full season.