Football

One incident from the weekend,one standard across the committee

Nextaur gathers the weekend's incidents and lets you do two things with them: an activity where each referee decides first and is marked automatically, or a presentation with the reasoning already set out, ready for the session. Either way, the incident and its explanation stay together.

Standard

The calls that get argued about most in football

None of these are settled by re-reading the Laws. They are settled by watching many incidents of the same kind and agreeing on where the line sits.

What is argued about
The argument is never whether the ball hit the arm, but whether the arm was where it should be: unnatural position, making the body bigger, a deflection off someone close by.
Why the Laws are not enough
The Law describes concepts, not distances or angles. Two referees can read the same text and see two different incidents without either misquoting it.
What settles it
An activity where everyone decides blind and then compares against the reasoned verdict. Repeated over many incidents, that is what pulls the standard together.

The same Law can be applied to a different standard in two competitions. That is why the standard has to be set in-house, and written down next to the incident.

The technical session

How a committee uses it

The method does not change: incident, standard, discussion. What changes is that you can assess or simply show, and either way it is on record.

  1. 1

    The weekend ends

    The incidents worth reviewing come from several matches and several referees. They go up in one place, with their competition, minute and incident type.

  2. 2

    You choose what you need

    Two routes with the same incidents: an activity, if you want everyone to decide and to measure the result; or a presentation, if the job is to teach the standard.

  3. 3

    The activity: everyone decides first

    They see the incident without the decision and answer from wherever they are. The reasoned verdict is revealed afterwards.

  4. 4

    The presentation: the reasoning, set out

    You pick the incidents, order them and add the explanation. It runs in the technical session or is shared with whichever level you choose.

  5. 5

    The reasoning stays with the incident

    Not in the memory of whoever gave the talk. Three months later you come back to it and it still says the same thing.

  6. 6

    And it builds up over the season

    Who gets what right, which incident type the whole group struggles with, and how each referee progresses.

Inside the platform

What an incident looks like

The vocabulary is not generic: these are football's own decisions and sanctions, the same ones you pick inside the platform.

Decision
Penalty kick
Sanction
Yellow card
Explanation
The defender arrives late and catches the attacker's standing leg inside the area, with no chance of playing the ball. The action is careless, not reckless: penalty and a caution.

And if you analyse matches too?

The same stored incidents serve the coaching staff: select, order and build the next opponent's report from them. What changes is what you do with the video, not where you keep it.

Build it with your own incidents

Start with the incidents from the next round of matches. No archive to migrate and nothing to prepare beforehand.