Your game film is a dataset you are not querying

Every play your program needs this week already exists on film. The touchdown for the recruiting reel, the blown coverage for Monday's install, the opponent's third-and-long tendency: all of it was captured, offloaded, and buried in folders named by date. The film is not the problem. Retrieval is. A season of game footage is a dataset, and most programs are still reading it the slowest way possible, by scrubbing.

The roster is a schema you already maintain

Programs think they have no data infrastructure, then hand a visitor a perfect one: the roster. Jersey number, name, position, kept current all season by someone who would never call themselves a database admin. That sheet is the key that turns footage into records, because the number on the jersey is visible in the frame and the roster maps it to a person.

Treat it that way. In ClipLogger, importing the roster CSV does two jobs at once: every row becomes a person in the project, number bound to name before a single clip is analyzed, and the numbers become a code layer for logging, so holding a modifier and typing 72 resolves to the athlete wearing 72. One identity can hold several kinds of evidence at the same time (the app groups the same face across clips, learns a uniform's look, and carries the roster number), so the kid found by face in one clip and by jersey in another stays one entry, not two.

Numbers are join keys, so treat them honestly

The jersey number is only useful as data if it is handled strictly. A join that guesses is worse than no join, because a highlight tagged to the wrong kid carries a real cost: a recruiter watches three plays that are not the athlete they came to see, and the reel loses its credibility. The rule worth demanding from any tool, and the one ClipLogger enforces, is that a number resolves only when exactly one active player wears it; two players sharing 24 resolve to nobody until a human decides. Slower by one click, correct for the whole season.

The same honesty applies to what a model reads off the frame. Scoreboards, down-and-distance graphics, and jersey digits are exactly the kind of on-screen text an automated pass reads well, but everything a machine proposes should land as a suggestion a coach or a student manager confirms. Confirming is fast. Un-tagging a season of wrong guesses is not.

Outcomes as fields, not memories

Here is the part that needs no software at all: log outcomes with a fixed vocabulary, one decision per field. Play type from a short list. Result from a short list: score, first down, turnover, stop. Personnel as numbers. Write the lists down before week one and refuse variants, because "TD", "touchdown", and "6" are three different searches unless somebody makes them one value. A student manager with a laptop and that vocabulary produces a queryable season. A coach with a perfect memory produces nothing anyone else can use.

The payoff shows up as questions you can suddenly ask: every red-zone snap where 8 was on the field, every third-down stop in October, every kick return that crossed the forty. If the answer to those still costs a night with the film, the season is not data yet.

Reels assembled by filter, not by weekend

A recruiting reel is a query. Athlete, plus the play types worth showing, sorted by your own rating: on a logged season that filter returns in seconds, the hits lay out end to end as one strip you can watch in order, and the sequence exports as FCPXML or an EDL for the polish pass in the edit bay. The opponent scout is the same move pointed the other way: log their film with your vocabulary and their tendencies stop being a hunch and start being a count. What used to be the video coordinator's lost weekend becomes an hour, and the weekend goes back to coaching.

Start with one game, count the minutes

Do not announce a program-wide system in August. Log one game: roster loaded, vocabulary agreed, outcomes tagged the same night while the game is fresh. Then time two retrievals, one from the logged game and one from an unlogged game, in front of whoever owns the budget. The gap is the pitch. Scale to the season only when the vocabulary survives contact with a real Friday night, because the vocabulary, not the software, is the system.

You already paid for this data when you filmed the season; logging is deciding to query it instead of scrub it.