Football Shot Statistics: Reconcile Attempts and Shots on Target

Updated 17/10/2026 · Reviewed content

A line showing eight attempts and three shots on target needs more than a quick subtraction. Build a small event ledger, identify the definition being used and then reconcile the categories. This guide uses a fictional match to show which questions a compact statistics row can answer.

The worksheet is for reading a report. It does not establish an official match total or predict the next goal, and none of its numbers describe a real team.

Fix the scope before checking the numbers

Write down the team, match period and observation time first. A first-half team total and a full-match player total are different records even when both use the word shots. Put those labels beside the figures before comparing them.

For our exercise, the report covers Harbour's first half against Cedar. We use one completed ledger containing eight deliberate attempts, with no own goals or unresolved incidents. This defined scope lets us check the arithmetic without claiming that every website has the same display or update schedule.

Keep a separate field for the data provider and its glossary. If neither is identified, write “definition not checked” rather than assuming that a familiar heading supplies all the missing details. A screen label is the starting point for a question, not the evidence needed to answer it.

Use the provider's categories

Opta's published definitions count scoring attempts that become goals, goalkeeper saves and goal-preventing last-line defensive interventions as on target. Its blocked category includes interceptions of attempts with defensive cover behind the blocker. An effort hitting the frame and staying out is off target under that glossary.

These are Opta-specific classification facts checked against Stats Perform's primary glossary. Our ledger below adopts that framework for a teaching exercise; it is not a claim about the provider used by any particular i8 Live screen.

Before assigning an ambiguous clip, retain the report's confirmed classification or leave it unresolved. An obstructed view may not show the path of the ball or the positions of the other players. The purpose of this worksheet is to audit a defined record, not replace a statistician's event assessment.

Build the fictional event ledger

Harbour's eight attempts are listed below. The descriptions deliberately provide the details needed for the exercise, so readers do not have to guess from video. Each numbered row represents one attempt.

The assigned categories produce three on target, three off target and two blocked. Their sum is eight, matching the number of event rows. A second pass through the event numbers checks that no attempt was counted twice or lost between categories.

This also shows why subtracting three on target from eight attempts leaves five remaining attempts, rather than proving that five were off target. In this ledger, those five consist of three off target and two blocked. Keep the remainder unnamed until its component categories are established.

Reconcile totals without counting a goal twice

Our ledger already places event 1 in the on-target group. Adding its goal again to three on target would create a fourth attempt that is absent from the event list. A category can include a scoring event without the goal becoming an extra event.

For a mismatch, compare the event identities before changing a headline total. Look for a duplicated row, a different period filter or an unresolved classification. Our method asks for an explanation of the difference; it does not assume that a replay impression should overwrite the provider's record.

If you cannot retrieve the event list, keep that limitation visible. A note such as “eight attempts reported; category split unavailable” preserves what you have checked. Inventing the missing split makes the note harder to correct later.

Write the fraction before naming the percentage

For this exercise, three divided by eight is 37.5%. We can accurately call that the share of our eight recorded attempts assigned on target. We should not automatically label it a provider's shooting-accuracy measure.

Opta's glossary gives shooting accuracy a denominator that excludes blocked attempts and own goals. Applying that definition to this simplified ledger gives three divided by six, or 50%. The two percentages answer different denominator questions; neither calculation changes the eight event rows.

Record the numerator, denominator and definition beside any percentage you share. In our note, “3 of 8 recorded attempts on target” is explicit enough to reconstruct. A bare “accuracy 37.5%” discards the denominator and invites a comparison the worksheet has not justified.

Keep revisions traceable

Imagine that event 8 was initially marked unresolved in your own notes. When a confirmed classification becomes available, update that event and recompute the category totals from the ledger. Preserve a short revision note instead of silently replacing an earlier screenshot.

A useful check sequence is:

1. Confirm the same team, period and observation time.
2. Identify the provider and the applicable category definitions.
3. Give each recorded attempt one event number.
4. Reconcile the category counts against those event numbers.
5. Write the denominator for each calculated percentage.
6. Mark unresolved events and later corrections explicitly.

This is i8 Live's reading method, not a promise that a live report will remain unchanged. When two captures differ, save both observation times and ask which event or filter changed. Do not use the later capture alone to invent the reason for the earlier number.

Questions about shot totals

Does hitting the post automatically mean on target?

In the Opta framework used here, event 6 stays in the off-target group because it hits the post and does not enter. Keep that exercise separate from a different sequence involving a save or a later attempt. Check the provider's full event description before transferring our row to a real incident.

Are all defensive blocks the same category?

Our events 3 and 7 deliberately describe different situations. The distinction comes from the last-line and defensive-cover details provided in the exercise. If those details are missing, the worksheet leaves the classification unresolved rather than guessing.

Can the larger total tell me who will win?

Our table checks eight recorded events and the arithmetic linking them. It contains no model of future play and no evidence for a match prediction. Use it to test a statistical description, not to turn a count into an outcome promise.

Sources and further reading

Stats Perform's Opta Event Definitions is the primary source for the on-target, off-target, blocked and shooting-accuracy definitions, checked on 18 October 2026. The same provider’s event glossary also supports the shot-category distinctions. The fictional Harbour ledger, arithmetic comparisons, revision exercise and checking sequence were independently designed by i8 Live. No actual match statistics are presented.

For checking the provenance of a captured result, read sports screenshot source and date checks. For a different football reporting problem, match and aggregate scores in two-leg ties keeps a single match result separate from the tie total.