Football Card Records: Count People Before Coloured Icons

Updated 17/10/2026 · Reviewed content

A red icon beside a team does not tell you who was dismissed, how the dismissal arose or how many players remain on the pitch. Read the person and the event sequence before counting the team's available players. This guide builds a small match log that keeps those questions separate.

The examples below use fictional clubs and players. They illustrate how to record a decision after it has been confirmed, rather than asking readers to referee a challenge from a short clip.

Identify the recipient before counting players

Begin with the name attached to the event. Is that person currently playing, an unused substitute, someone already substituted or a team official? A list of card events needs that role information before it can explain the state of the team.

IFAB Law 12 describes yellow as the communication of a caution and red as the communication of a sending-off. Cards can also be shown to substitutes, substituted players and team officials. The colour therefore describes disciplinary action; it does not identify the recipient's current role by itself.

An event row saying only “Harbour: red” leaves an important gap. A more useful note is “Harbour assistant coach: sent off” or “Harbour number 8, on-field player: sent off.” The second wording preserves information that a compact team-level icon may omit.

Preserve the route to the dismissal

Law 12 includes receiving a second caution in the same match among sending-off offences. A direct sending-off and a dismissal following a second caution should therefore be kept as different event descriptions in your notes. A red symbol alone cannot tell you which route occurred.

Imagine Harbour's player Amir receives one caution early in the match and a second later. Your log can retain both caution events and the resulting dismissal under Amir's name. Counting the later yellow and red as two different dismissed people would turn one person's sequence into an invented second removal.

This table is our recording exercise, not an official results-provider notation. A provider may use a combined icon, separate event rows or a written explanation. Check that display's own labels before deciding that a missing second row means the event did not happen.

Count the on-field consequence separately

IFAB Law 3 says a player sent off after kick-off cannot be replaced. It also states that a named substitute who is sent off cannot be replaced on the substitute list. Those rules concern different roles, so record the role alongside the dismissal.

In our first exercise, Harbour has eleven players on the field immediately before Amir, an on-field player, is sent off. With no other relevant event in this simplified exercise, Harbour then has ten. The change comes from Amir's removal as an on-field player, not from adding together the number of coloured symbols.

In a separate exercise, Ben is an unused substitute when he is sent off. He was not one of Harbour's eleven on-field players immediately before the event. Removing him from the available bench does not remove another person from that on-field eleven.

The starting situation is part of each example. These are independent cases, not three consecutive incidents in one match. They do not account for injuries, temporary absences or other events that a real match log would need to retain.

Keep the timing in the record

Law 3 distinguishes a listed player dismissed before kick-off from a player dismissed after it. A named player sent off before kick-off may be replaced by a named substitute under that provision. The post-kick-off restriction should not be applied to every earlier incident without checking its timing.

For a practical note, keep “before kick-off” or the reported match minute beside the name and role. If a short notification omits the timing, leave that part unknown until the fuller report is available. Do not fill the gap from the order in which notifications arrived on your phone.

This matters when two summaries appear to disagree. One may describe the originally named lineup and another the team that actually started. Comparing their labels and timestamps gives you a specific question to investigate, without assuming that either summary proves an extra player was used.

Build one event log before writing a summary

A compact log is easier to audit than a sentence that mixes cards, people and team strength. Give each person a stable identifier, such as their name and team, and keep the description from the confirmed record. The following order is an i8 Live reading method.

1. Identify the competition, match and stage of the report.
2. Record the recipient's name, team and role at the incident.
3. Preserve the sequence as a caution, second caution with dismissal or direct sending-off.
4. Keep the reported timing beside that sequence.
5. Work out the on-field consequence from the role and starting situation.
6. Mark any missing detail as unknown before sharing your summary.

For a fictional completed report, write: “Amir, playing for Harbour, was sent off after his second caution; Harbour went from eleven on-field players to ten in this exercise.” That is more precise than “two cards, two men down.” It also leaves a separate place to record a later dismissal of another person.

Keep your observation time separate from the event time. A notification received at 01:20 MYT is not evidence that the incident occurred at that clock time. If the report supplies only a match minute, retain that minute without inventing a local timestamp for the incident.

Leave later sanctions unresolved until verified

A match event and a later competition decision are different records. This worksheet does not determine a suspension length, an appeal outcome or eligibility for a future fixture. For those questions, look for the relevant competition's current disciplinary notice and identify the person and fixture it concerns.

Write “later sanction not checked” when that information is unavailable. A confident number copied from another competition adds no evidence to the current case. Likewise, the presence of a dismissal does not support a prediction about the remaining match or its final score.

When checking a disputed summary, ask a narrow question: “Was this the on-field player or the unused substitute?” or “Was this a second-caution dismissal or a direct sending-off?” Those questions target missing fields in the record instead of asking a reader to infer an entire incident from an icon.

Questions about card records

Do two yellow symbols always mean two players were cautioned?

No. Check the names and sequence. Our Amir example contains two caution events belonging to the same person, followed by that person's dismissal. A team total without recipient details cannot reconstruct the sequence.

Does a red card to someone on the bench make eleven become ten?

First establish that person's role at the incident. In the unused-substitute example, the recipient was outside the on-field eleven. Do not subtract them a second time from a group they were not part of.

Can I infer a fixed suspension from the match log?

This log records the match event and its immediate personnel consequence. It contains no verified later disciplinary decision, so it cannot supply a suspension length. Keep that question pending until the applicable competition record is checked.

Sources and further reading

IFAB Law 12: Fouls and Misconduct supports the card meanings, eligible recipients and second-caution rule. IFAB Law 3: The Players supports the replacement distinctions before and after kick-off and for named substitutes. Both were checked in the current 2026/27 Laws view on 17 October 2026; the fictional logs, counting exercises and reading method are i8 Live's own analysis.

For another personnel question, when a substitution is completed explains a different event. If a report is still describing a video check, VAR checks, reviews and decisions helps identify that process before treating the reported outcome as settled.