Football Match Records in a Club App: A Requested Substitution Is Not a Player Appearance

A coach selecting a replacement on a phone has recorded an intention. That action alone does not prove that the substitute entered the match. If your club app uses the same button to request a substitution, update the players on the field and credit an appearance, it can create a match history that nobody actually observed.

Commission a record of the substitution process, not merely an editable team list. This article concerns software requirements. The referee and competition authorities determine the applicable rules and actual match decisions; a club application does not replace their authority or certify player eligibility.

Keep the named bench separate from the field

Begin with the team list submitted for the particular match. A person in the club's membership database is not automatically a named substitute for that fixture. The IFAB Law 3 text states that substitute names must be given to the referee before the match and that an unnamed substitute may not take part.

For the application, ask for distinct records of the match's starting players, named substitutes and later changes. A corrected member profile should not silently rewrite the submitted team list. Separately record the authority and evidence for an authorised correction.

Competition registration and eligibility checks require the organiser's own approved requirements. Do not infer eligibility from a name appearing in the app, a paid membership or a successful roster upload.

Record the event that actually occurred

Law 3 describes informing the referee before a substitution and the substitute entering during a stoppage, after the replaced player has left and after the referee's signal. Its ordinary completion rule connects the substitute's entry with the change from substitute to player.

A proposed application workflow can therefore distinguish requested, awaiting the official process, completed and cancelled or unresolved according to the competition's approved vocabulary. Record the outgoing and incoming players together, with the match event and responsible recorder. Do not credit playing time merely because a request was saved.

There is an important boundary to that ordinary rule. IFAB circular 34, dated 27 July 2026, clarifies that where entry is delayed under the time-limited substitution protocol, the substitution procedure is considered completed when the outgoing player leaves. Completion and the incoming player's physical entry can therefore be different events. The application must preserve both where applicable rather than implement “completed always means entered”.

Have a competent competition official review that protocol, its applicability and the required record. This is not a complete implementation guide for delayed entry, sanctions or goalkeeper exceptions. A countdown in an app must not purport to grant permission to enter.

Count players and opportunities separately where required

A replacement count is not always the same as a substitution-opportunity count. Law 3 says multiple substitutions and requests by one team during the same stoppage count as one used opportunity under the described restrictions. It also distinguishes interval changes from counted opportunities.

Ask the competition owner which restrictions apply to the match format. Do not apply a top-division configuration to every youth or grassroots fixture. The brief should identify the permitted settings, the treatment of intervals and extra time where relevant, and the official who resolves ambiguous events.

Store the relationship between a substitution and its stoppage or interval. Two player changes saved as separate rows need not imply two opportunities. Conversely, two actions at different stoppages must not merge just because an operator entered them together afterwards.

Do not make return substitutions a universal feature

Law 3 restricts return substitutions to specified football categories, subject to the relevant governing body's agreement. A button that puts any previously substituted player back on the field would therefore be an unsafe generic default for match records.

Require an explicit competition-approved configuration. Where return substitutions are permitted, the history should distinguish another participation interval from the player's first entry. Where they are not, the app should surface the conflict for authorised resolution rather than silently rewrite the earlier substitution.

Corrections also need a reason and traceable review. Editing an incorrectly recorded minute is not evidence that an official event was reversed. Preserve the original entry and the approved correction so a later appearance report has an understandable basis.

Demonstrate the difficult transitions

Use fictional teams to show a named unused substitute, an ordinary completed substitution, a request that never proceeds and multiple changes during one stoppage. Include delayed entry under the applicable reviewed protocol and both permitted and prohibited return scenarios. Obtain expected records from the competition official.

Check the field view, bench view, appearance report and opportunity totals together in the acceptance criteria. Bring the approved match rules and a worked fictional record to a club-app discussion. The deliverable is an explainable match history, not an unofficial referee decision generated by a status button.