Film
Weekly film and intelligence reports
The coaching staff already logged receiver film in a sheet. The pipeline takes that week file and publishes grades, dashboards, and PDFs without a local Python session.
Problem
Weekly evaluations were trapped in a manual pass from the film log to reports. The staff needed the same rubric every week, for a whole season, in a form players and coaches could open.
Constraints
- The film log in Google Sheets stays the source of truth.
- A week file may arrive as a published CSV, through git, or from an upload helper.
- Players need the rubric in coaching language, not a dump of grade codes.
- Last season has to remain one click away when a new season starts.
What shipped
- Cleaning and grading of the week file against a custom receiver rubric.
- Individual player reports, a weekly summary PDF, group film PDFs, and HTML dashboards.
- A two-season hub with a player-facing “how to score well” panel.
- Publishing when the week file changes, instead of hand-building each page.
Evidence
Year two of the hub is described on the engineering journal, including a live week (dashboards, snapshot, summary PDF, group film, and CSVs) generated from the ingest rather than assembled by hand. The build notes describe the staff impact as moving film analysis from hours of manual work to minutes.
Tradeoffs
The pipeline trusts the sheet’s conventions. Inconsistent logging still needs the validation in the ingest. The product is a report system around the log the staff already kept, not a new film database.
calendar_monthDirect availability with Mitchell Dawkins II
Have a similar operational problem?
Request a 20-minute fit call. We will tell you if automation or a small custom tool is the right next step.
Request a 20-minute fit call