A check and a review are different steps
A broadcast graphic saying “checking” does not promise that the referee will walk to the pitchside screen. IFAB’s protocol describes automatic checks and a separate review process. Only the referee initiates a review; the video assistant can recommend one. The referee makes the final decision.
That distinction helps when a television director stays with the players instead of showing the monitor. A brief pause followed by play continuing is not evidence that a requested screen visit was accidentally omitted. First ask which part of the process the broadcast has actually identified.
Factual information and judgement can use different routes
The protocol distinguishes a decision based on information from the video assistant from an on-field review where the referee watches replays. Matters involving subjective judgement normally benefit from the referee seeing the incident. Factual information can be communicated without the same screen visit. The exact reviewable incidents belong to the current laws and competition implementation.
An illustrative viewing note might say “check announced; referee listening; decision communicated; no monitor visit shown”. Keep those observations separate from “no review occurred”, which asserts more than the pictures establish. Television coverage can omit a useful angle or cut away while officials are communicating.
A slow replay answers only the question it can show
IFAB cautions that replay speed matters: slow motion can help locate contact, while normal speed helps assess intensity. A close-up proving that two boots touched does not by itself settle every question about the challenge. Camera selection also limits what a viewer can confidently infer.
When comparing two broadcasts, start with the same incident timestamp and the same decision. One channel may show a tight replay while another shows the wider build-up. If you are discussing the call with someone, describe the view you saw instead of assuming that every viewer received identical evidence.
Avoid turning the wait into a network diagnosis
The protocol sets no fixed time limit for the review. A long wait accompanied by continuous pictures of players and officials therefore needs a different diagnosis from buffering, a loading spinner or repeated frames. Note whether the match clock is moving and whether commentary continues before changing the app or network.
For a useful playback report, separate your observations into “broadcast event” and “player behaviour”. For example: the officials were checking a goal; the picture continued normally; the app did not display an error. If the image actually stopped, add the pause duration and whether other controls still responded. This makes the technical symptom clear without requiring support to adjudicate the sporting decision.
Use the organizer’s match report for the official outcome. A commentator’s first interpretation, a provisional on-screen score and a later confirmed result can appear at different moments. Keeping the final decision and the sequence of television graphics separate prevents an ordinary correction from looking like a broken programme feed.
Questions answered
Must every VAR check include a pitchside screen visit?
No. A check and an on-field review are different parts of the protocol, and information can be communicated to the referee without a monitor visit.
Does a long VAR wait prove my stream is buffering?
No. Check for a spinner, repeated frames or stopped playback controls. Continuous coverage of the review is a broadcast event.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.