How This Was Built

← Back to the Season Tracker

One Fan, Five AI Tools, One Season

This site is an independent fan project by rions.com. It followed four NASCAR series through the whole of 2026, with a page for every race that was updated as each weekend unfolded. It was built by one person doing the research and making the calls, with AI tools doing the heavy lifting of turning that research into pages. This is how it worked.

118race pages
504published updates
39race weeks
4series
315drivers tracked

It Starts With Research

No page on this site began with an AI. Each one began with the site owner gathering what was actually known about that weekend, and deciding what mattered.

Collecting the sources

Early in every race week, and again after each session on track, the owner collected the raw material by hand:

That came from official NASCAR releases and from the reporting and statistics the sport's fans have relied on for years: NASCAR.com, Jayski and racing-reference.

Cross-checking with two research assistants

Alongside the published sources, the owner asked two AI research assistants, Gemini and Grok, for their own detailed, fact-checked rundown of the same weekend. Using two was deliberate. Where they agreed with each other and with the official record, that was a good sign. Where they differed, it was a prompt to go back and check.

Deciding what the story was

This is the part no tool did. From everything collected, the owner chose the facts and highlights each page should carry: the storylines going in, the milestones in reach, the rookies and the part-timers, the women in the field, the technical changes that might decide the race, and what the result meant for the championship. Everything chosen went into a single working file for that weekend, the one source the page would be written from.

From Research to Race Page

Turning a week's worth of notes, tables and reports into a readable page, several times per weekend, for up to four series at once, is where AI earned its place.

  1. Synthesis. NotebookLM (now Google Notebook) read that weekend's working file and wrote the page from it. It worked only from the sources it was given, which kept the pages tied to the record and not to an AI's memory of how races usually go.
    NotebookLM
  2. A consistent shape. Every page follows the same layout, so a reader always knows where to find the entry list, the technical notes, the storylines and the results. The pages also try to explain why a fact matters, not only state it.
    NotebookLM, to the site's own page layout
  3. Review. Every draft was read and checked by the owner before it went anywhere. Pages that missed something or got it wrong were corrected or run again.
    rions.com
  4. Publish, then update. A race page was not written once. It was first published early in the week, updated after practice and qualifying, and updated again with the result and the fallout. Each update built on the last, and every earlier version was kept.
    rions.com, using scripts written with Microsoft Copilot

On average each race page went through about four published versions. Across the season that came to 504 updates.

Who Did What

WhoRole
rions.com (site owner)Design, architecture and workflow of the site; collected and researched every source, decided what each page should cover, reviewed every draft, published every update
Gemini and GrokResearch assistants: independent, fact-checked rundowns of each race weekend, used to cross-check the sources and each other
NotebookLM (now Google Notebook)Wrote each race page from that weekend's collected sources
Microsoft CopilotBuilt the site's main page and the scripts that publish race pages and keep every version
ClaudeEnd-of-season analysis, and rebuilt the drivers, teams and owners data from the full season's records
VS Code and GitHubWhere the site was put together: revision history and deployment automation

The Season Data

When the season ended, everything collected over those 39 weeks was put to a second use. The entry lists, results and lineups from every race were combined into one record of who drove which car, for which team and owner, with which sponsor and manufacturer, at every race of the year.

4,258car-by-race records
57teams
124owners
1,425sponsors

The driver lists were then checked against the final points standings in all four series. Where the two disagreed, the sources were gone back to until they matched. The result is the Drivers • Teams • Owners browser, where any car can be opened to see every race it ran.

What Was Learned

A note from the site owner

This started with a simple question: how does a retired chief architect keep some technical skills alive, give a little back to fellow fans, and keep track of a NASCAR season for himself, all at the same time? I am a continual learner. AI had my interest well before I retired, and I wanted to find out what I could pull together with the free and inexpensive versions of the tools anyone can sign up for.

That is what built this site. Every race page of the 2026 season was made with those free or low-cost tools. The exception is recent: this summary, the season review and the rebuilt drivers, teams and owners data were done at the end of the year with Claude Code and Anthropic's latest models. Everything before that was the everyday versions.

The pages at the end of the season are better than the ones at the start, and that was not an accident. Early pages varied from week to week in what they covered and how. Over the spring the layout settled, the instructions I gave the tools became more precise, and the checking became more systematic. AI output is only as good as the sources and direction it is given.

AI tools make mistakes. They can state something confidently that is not so, or leave out a driver who should be there. I make mistakes too. I reviewed every page, but there is a great deal of content here, more than one person can check line by line, and I will have missed things. If you spot an error, it is mine, not NASCAR's.

A year of exploring AI through Rion's NASCAR 2026 Season Tracker has shown me the immense power and breadth of knowledge that is now at our fingertips. It has also shown me the other side of that scale: the more a tool can produce, the more room there is for error, unless there is proper validation and there are guardrails on how it is used.

Sources and Thanks

Sources

Event details, results and statistics are compiled from official NASCAR releases, NASCAR.com, Jayski and racing-reference. All analysis, formatting and presentation are independently produced.

Thank you

To NASCAR, first and most of all, for the sport itself: for 118 events across four series, for the access and the information it publishes every week, and for a season that gave a fan this much to follow.

To the networks and streaming services that brought every race home: FOX, FS1 and FS2, NBC and USA Network, The CW, TNT Sports and Prime Video, and the radio crews who called them.

To the fans, who are the reason any of this exists, and to the drivers, who give them something to cheer, argue about and remember.

To everyone behind the scenes who never gets a trophy: the crew chiefs, pit crews and spotters, the people in the shops building and hauling the cars, the officials, the track workers, and the safety and medical crews who stand ready every lap.

The NASCAR family

Something should be said about what happens before the green flag. At each and every race this sport stops to honor family, God, first responders and the military. It prays before it races. It stands for the anthem. It brings the families of drivers and crews onto pit road, and it shows up for its own when one of them is lost, as it did this year. That dedication is not staged for television. It is who the NASCAR family is, and it is a large part of why this fan keeps coming back.

And at home

Finally, to my wife, my family and my friends, who support this hobby and the aspirations that come with it, put up with race weekends that run long, and cheer the project on. Thank you. This would not have happened without you.