We’ve rebuilt our most popular feature with a new intelligence layer underneath every recap you generate. It’s the most advanced recap engine in college athletics.

September 2, 2026

Game recaps are the bread and butter of college athletics communications.

After every contest — win or lose — someone on your staff is responsible for turning a box score, a set of notes, and a few quotes into a readable, shareable story. Multiply that across a full schedule of sports and you’re looking at seemingly countless recaps every week, especially during crossover season.

It adds up fast. And it never stops.

That’s exactly why game recap production has been at the core of FanWord Assist since day one. Last season alone, communicators generated 30,000 recaps through the platform.

Whether you’re covering a sport with an XML stat file or one without, the goal has always been straightforward: get your staff 90% of the way to a publish-ready recap in 10% of the time, without sacrificing quality or voice. Each of the 20 sports we support has been configured individually, so baseball sounds like baseball and volleyball sounds like volleyball.

This summer, we rebuilt the feature to get that first draft even closer.

Game Recaps 2.0 does a better job surfacing the game elements worth writing about, how your sport tells that story, and how your department wants it written.

It’s our best version of game recaps — ever.

What’s New in Game Recaps 2.0

There is a lot happening behind the scenes in this release. Here are the biggest changes you’ll notice:

• Storyline Intelligence — identifies the moments, performances and statistical developments most worth writing about.
• AP Style, Integrated — applies common athletics-writing conventions more consistently.
• More Control Over How the Game Gets Told — gives each recap block a clearer editorial purpose.
• Natural Sportswriting Language — improves sentence construction, transitions, terminology and phrasing.
• Smarter Trends — surfaces more meaningful milestones, streaks, highs and standout performances, with more customization where applicable. Plus the ability to customize Trends thresholds yourself.

Here’s what each of those changes means in practice.

Storyline Intelligence

The first version of Game Recaps was strong on structure. It knew the shape of a recap, moved quickly, and was reliable.

Version 2.0 goes after the harder part, the instincts of what made a game memorable. Like picking out the thing you would have led with having sat at the scorers table or standing on the sideline. That’s at the center of our newest iteration of Game Recaps.

The platform now weighs what happened contextually against the shape of the recap. Keep in mind, all of this happens behind the scenes — but now instead of generating a list of things that happened in a game, it surfaces the moments, performances and statistical developments that communicators would find worth writing about.

Then it puts them where a communicator would put them.

AP Style, Integrated

We’ve heard you — now every game recap draft goes through an additional writing layer focused specifically on AP and athletics-writing conventions.

That includes details such as numerals, scores, time references, rankings, team and player references, attribution and other formatting choices that readers may rarely notice, but you’d spot in a second.

Our team wanted FanWord Assist to deliver greater consistency across sports and your department’s entire recap workflow. Now it does.

More Control Over How the Game Gets Told

Not every recap needs the same kind of game detail, so we gave our Game Data blocks clearer editorial jobs.

• Our Team Focus prioritizes what’s most important for your team.
• Text surfaces the statistical and performance-based takeaways.
• Bullet Points gives you the quick statistical highlights.
• Game Flow follows the action as it unfolded (also available in bullet points).

The result is less overlap between sections and more control over whether you want the story of your team, the important statistics, or the progression of the game itself.

Natural Sportswriting Language

We rebuilt the language layer from the ground up, using hand-selected examples of exceptional college athletics writing to educate our platform about what natural phrasing sounds like in this specific corner of the industry.

You know this natural phrasing, because it’s how you communicate. Sentence structures vary; some short, some long. There’s a cadence to the communication of information with transitions that are meant to land. And in an age of vapid AI slop, verbs that feel chosen rather than coldly assembled.

Game Recaps 2.0 is better at varying sentence construction, reducing repetitive phrasing, choosing sport-appropriate terminology and connecting information without making the copy feel mechanical.

Smarter Trends

We also overhauled the logic behind Trends so that FanWord Assist is more selective about what it considers noteworthy.

Our team reviewed trend behavior sport by sport, taking time to refine thresholds and remove low-value signals. We’ve reevaluated which milestones, season highs, streaks and above-average performances deserve to surface.

The goal was to find the best trends and elevate them to you more effectively.

We’ve also given you the ability to customize select thresholds within Trends so what counts as noteworthy better matches your program.

A stat appearing above a mathematical benchmark doesn’t automatically make it worth putting into a story. Game Recaps 2.0 puts more emphasis on whether the performance is actually meaningful in the context of the sport and the athlete.

Copy That Reads Like You Wrote It

All of these changes point toward the same goal.

There are plenty of tools that can turn structured data into sentences. That’s not the standard we’re aiming for.

From the Division I to small college athletic departments and the NJCAA, your writing is a point of pride. The details. The terminology. The difference between a game-changing play and one that’s not.

Game Recaps 2.0 combines the structural reliability that made the original feature tremendously useful with a much stronger editorial layer underneath it: better story selection, better sport context, better language, better application of your preferences and better judgment about what deserves space in the finished recap.

Consider this release a love letter to the people who care about those details as much as we do.

Shaped by the People Using It

At FanWord, we’ve always said we practice customer-driven development.

We build around what our partners tell us they need.

Nearly every meaningful change in Game Recaps 2.0 traces back to those conversations: what a great lede looks like at your school, which storylines your fans care about most, why a particular stat isn’t worth highlighting, where the first draft still makes you spend time editing and how your voice differs from the school down the road.

Because we’re able to ship improvements quickly, those conversations can turn into meaningful product changes without waiting through a year-long release cycle.

That loop is the development model. FanWord Assist evolves on the schedule of the people producing recaps at 11 p.m. on a Saturday, because they’re the ones telling us what the next version should do.

Built to Get You 90% There

The goal of FanWord Assist has never been to replace the communicator. It’s to handle the structural heavy lifting so you can focus on the elements that require your expertise, like the details, angles, and the story behind the score.

Think of it as getting you 90% of the way there in about 10% of the time.

The other 10% has always been about your voice, your editorial eye, and the moments you remember from being there in person.

With Game Recaps 2.0, our goal is simply to make that remaining 10% a little smaller.

Not a partner? See what FanWord can do for your communications team: 
➡️ Request a demo using the contact form below
➡️ Reach out to our CEO directly to talk through your team’s workflow
➡️ Case Studies: See how departments across America save time for their teams with FanWord Assist