How to organize sideline stats and scouting

Most of the data lost in flag football is not lost for lack of a tool. It is lost because nobody decided, before the opening whistle, who logs what.

The outcome is familiar: at the end of the game there is a sheet of notes only one person understands, and a video nobody will watch all the way through. The information existed. It just was not captured in a way that survived until Wednesday.

This piece describes a routine that works on the sideline, within the real time you have between one play and the next.

The constraint that defines everything: the window is seconds

Between the end of a play and the next snap, depending on the rules and the pace of the game, there is little time — and much of it is already committed to reading the defense, calling the play, and communicating with the QB.

Every decision below follows from this. If a step in your process does not fit in 8 seconds, it is not a step in the process — it is post-game work in disguise.

Step 1: assign roles before warm-up

There is no one right setup. There is the setup that matches how many people you have.

One person (a coach alone). Log offense only, and only four fields. Defense goes to the video. Trying to cover both sides alone means covering both halfway.

Two people. One logs offense, the other logs defense. Never split by "quarter" or by "drive" — splitting by side of the ball keeps each person's vocabulary consistent.

Three or more. Offense, defense, and a third person dedicated to opponent scouting. That third person is the one who creates an edge for the next game, and the first to be cut when people are short. If you only have three, that is the best use of the third.

Whoever logs does not call plays. The two tasks compete for the same window of attention, and the play call always wins.

Step 2: lock down the minimum set of fields

The most common mistake is wanting to capture everything. A form with 12 fields becomes a form with 12 blank fields in the second quarter.

Offense, minimum fields:

• Down and distance
• Formation
• Call (the play name from your playbook)
• Outcome: complete, incomplete, run, sack, interception, touchdown
• Yards gained

Offense, fields worth the extra effort if you have the person:

• Zone attacked (short, intermediate, deep) and side (left, middle, right)
• Target receiver
• Whether the defense brought pressure

Defense, minimum fields:

• Down and distance
• Your defensive formation
• Whether there was a blitz and from which side
• Outcome of the opponent's play
• Yards allowed

This set is small on purpose. It answers the questions you will actually ask on Tuesday: what converts on third down, where the defense is giving up ground, whether the blitz is working.

Step 3: a closed vocabulary, set before the game

"Left blitz", "blitz L", "pressure from the left", and "LB" are the same thing to you and four different things to any form of counting.

Before the first game of the season, write the closed list of possible values for each field and do not create any new value during the game (to standardize concepts and calls, see our flag football glossary and the explained IFAF 5v5 rules). If something does not fit the list, mark it "other" and resolve it later on the video.

This applies equally to paper and to an app. On paper, print the list at the top of the sheet. In an app, the field should already be a closed list — if it accepts free text for formation, you will have the same problem with more steps.

Step 4: position, equipment, and redundancy

Stand level with the line of scrimmage, not at midfield. You need to see route depth, not just the result.

Clipboard or phone, not both. Switching between them costs the whole window.

Record the game even when logging live. The video is not bureaucratic redundancy: it is what lets you recover the three or four plays you will inevitably miss, and it is what supports any later review. A fixed, elevated camera framing the whole field. A camera following the ball loses formation and is almost useless for analysis.

Step 5: the halftime routine, in five minutes

Halftime is not the time to analyze. It is the time to answer three questions and leave with one adjustment.

1. What is working on offense?

   Which call has the best average return so far.

2. Where is their defense giving up ground?

   Which zone showed up most on the positive plays.

3. What are they doing to us?

   The answer is one sentence, not a table.

Leave with one adjustment, not five. Five adjustments in the second half is the same as none.

If you logged live, those three answers are already there. If you logged on paper, you will answer from memory — which is legitimate, but admit that it is memory, not data.

Step 6: scouting the opponent without disrupting your own game

Scouting the opponent during your own game is possible, but only when you are not managing that possession.

The practical rule: the scouting person logs the opponent's offense while your defense is on the field. That is the same moment the offensive staff is free.

What to log about the opponent, in order of value:

1. Offensive formation and the frequency of each one
2. Tendency by down — what they call on first, what they call on third and long
3. The zone they attack most often
4. Who gets the ball in a conversion situation
5. What they do in the red zone and on the extra-point conversion

If you can only log two items, log 1 and 2. Formation and tendency by down is the pair that most changes the following week's prep.

League scouting, when you watch a game you are not playing in, lets you cover the whole list. Take it: it is the cheapest collection situation there is.

Step 7: a ten-minute post-game close-out

Still on the field, before everyone scatters:

• Confirm the score and the number of drives.
• Mark the plays you failed to log, with an approximate time reference in the video.
• Write three lines of context: weather, absences, anything that would explain a strange number later.

Context is worth far more written in the moment than reconstructed on Wednesday. A game with two starters out and heavy rain should not enter the average without a note.

Common mistakes

Four mistakes that show up in almost every team that starts logging games.

1. Logging everything in the first game

   Start with four fields. Add one per game, only if the previous one is being filled in consistently.

2. Changing who logs without transferring the vocabulary

   If the person changes, the standard has to be handed over explicitly, not by osmosis.

3. Collecting without ever using it

   If the data changes nothing at Wednesday practice, the whole team notices and stops cooperating. Use one metric per week, publicly, at practice.

4. Keeping the data with one person only

   A file in a personal account disappears when that person leaves the team.

A checklist to print

Before the game:

• Roles assigned (offense, defense, scout)
• Closed list of values printed or configured
• Fixed camera positioned and charged
• Playbook call names aligned with whoever logs

During:

• Whoever logs does not call plays
• Minimum fields only
• Mark a missed play instead of inventing one

Halftime:

• Three questions
• One adjustment

Post-game, still on the field:

• Score and drives confirmed
• Missing plays marked
• Three lines of context

Where SIDELN fits in

The whole routine above works on paper. We built SIDELN because the expensive part is not the collection — it is the transcription and the cross-referencing afterward.

In the app, play logging is done by tapping closed lists during the game, the stats by down and by zone come out already calculated, and Film Room ties each play to the matching point in the video.