{
  "slug": "game-day-reporting",
  "category": "sports",
  "title": "How to write a game recap and keep useful stats",
  "dek": "Short, fair recaps and simple stats that a team will actually use all season.",
  "audience": "Team members, parents, and volunteers who write recaps or keep stats for a rec, club, or community team.",
  "seat": "open",
  "minutes": 6,
  "sections": [
    {
      "heading": "What a good recap does",
      "body": [
        "A good recap tells the reader what happened in a few clear paragraphs. Open with the result and the setting: who played, where, and the final score. Then give two or three moments that explain the game, such as a long rally, a comeback, or a defensive stand. Close with what is next.",
        "Keep it short. A recap that fits on a phone screen will be read by more people than a long one. Use plain American English and active verbs, and check names, scores, and spellings before you post. Accuracy builds trust faster than flair.",
        "Write about what happened, not about what should have happened. Leave out guesses about why someone made a play, and stick to what you saw or what the scorebook says."
      ]
    },
    {
      "heading": "Stats a team will actually use",
      "body": [
        "Track a small number of things consistently instead of many things badly. For most teams that means score by period or inning, attendance, and one or two individual numbers that fit the sport. Pick them with the team so that people understand why they are being counted.",
        "Decide who records stats and how. A single scorekeeper with a simple sheet is more reliable than everyone guessing afterward. Take a photo of the sheet right after the game as a backup, and enter it into a shared file that same day if you can.",
        "Be careful with stats that can embarrass people, such as errors or turnovers. Many teams track them privately for coaching and share only positive or team-level numbers publicly. Whatever you choose, tell players in advance what is recorded and what is shared."
      ]
    },
    {
      "heading": "Fairness across the season",
      "body": [
        "Over a season, every player who showed up should appear in the writing at least once. Keep a simple tally of who has been mentioned, and look for people who have been missed. Quieter contributions count: a great pass, steady defense, encouraging teammates, or showing up every week.",
        "Spread the spotlight on purpose. If the same two names fill every recap, others will notice. Rotating the writer can help, as long as the writers follow the same guidelines on tone and accuracy.",
        "Credit the other team too. A kind line about an opponent’s play makes your recap more honest and builds goodwill in the league."
      ]
    },
    {
      "heading": "No shaming",
      "body": [
        "Never name a player in connection with a mistake. A loss belongs to the team, and the recap should talk about it that way. If something needs to be said about a specific error, say it privately or leave it for coaching conversations, not a public page.",
        "Avoid sarcasm, nicknames the person has not chosen, and comments about bodies, age, or ability. Be especially careful with minors, and use first names or numbers only if guardians have agreed to public mentions.",
        "Read your draft once as if you were the player being written about. If any line would sting, change it. Then read it as a parent, an opponent, and a stranger."
      ]
    }
  ],
  "checklist": [
    {
      "label": "Lead with the result",
      "detail": "Teams, place, and final score in the first lines."
    },
    {
      "label": "Add two or three key moments",
      "detail": "Pick plays that explain the game, not every point."
    },
    {
      "label": "Verify names and numbers",
      "detail": "Check spellings and the scorebook before posting."
    },
    {
      "label": "Choose a small stat set",
      "detail": "A few numbers recorded consistently beat many recorded badly."
    },
    {
      "label": "Assign one scorekeeper",
      "detail": "Photograph the sheet and enter it the same day."
    },
    {
      "label": "Track mentions over the season",
      "detail": "Make sure every player shows up in the writing."
    },
    {
      "label": "Credit the opponent",
      "detail": "Include one fair, specific compliment."
    },
    {
      "label": "Run the no-shaming read",
      "detail": "Reread as the player, the parent, and a stranger."
    }
  ],
  "wanted": [
    "Recap examples that are short, accurate, and kind.",
    "A one-page stat sheet for a sport you keep stats in.",
    "A method for tracking who has been mentioned during the season.",
    "Guidance on what stats are appropriate to share for youth teams.",
    "Tips for writing recaps quickly right after a game."
  ],
  "related": [
    {
      "label": "Baseball",
      "href": "/baseball"
    },
    {
      "label": "Local",
      "href": "/local"
    },
    {
      "label": "Intern program",
      "href": "/intern"
    },
    {
      "label": "All guides",
      "href": "/guides"
    }
  ],
  "tags": [
    "recap",
    "stats",
    "reporting",
    "fairness",
    "writing"
  ],
  "url": "https://pointcast.xyz/guides/game-day-reporting",
  "json": "https://pointcast.xyz/guides/game-day-reporting.json",
  "assignments": [
    "GA-07",
    "GA-11"
  ]
}