Official Tournament Match Incident Report

1. Section 1: Match & Competitor Metadata

Provide complete identification details for the tournament match during which the incident occurred. All fields marked as mandatory must be filled to ensure proper tracking and resolution.


Tournament Official Name

Tournament Phase

Unique Match Identification Code

Match Scheduled Start Date & Time

Incident Occurrence Date & Time


Venue or Server Location

Game Title

Game Version/Patch Number

Gaming Platform

Team A - Official Team Name

Team A - Captain Name

Team A - Complete Roster (Player IDs & In-Game Names)

Team B - Official Team Name

Team B - Captain Name

Team B - Complete Roster (Player IDs & In-Game Names)

Your Role in This Match

Your Full Name

Your Official ID Number

Match Format (e.g., Best of 3, Best of 5)

Current Match Score (Team A)

Current Match Score (Team B)


Current Game State (Map, Round, Time Remaining)

2. Section 2: Technical Issue or Rule Violation Details

Describe the nature of the incident with precise details. Classify the issue type, specify when and where it occurred, and assess its impact on competitive integrity.


Primary Incident Category

Severity Level Assessment (1 = Minor, 5 = Critical)

Detailed Incident Description

Exact Game Time/Timestamp of Incident

Specific Map Location/In-Game Coordinates

Which Party Was Directly Involved?

Specific Player(s) Involved (In-Game Names & IDs)

Does this incident involve a specific rulebook clause violation?


Is this a recurring technical issue that has happened before in this tournament?


Technical Component Affected (select all that apply)

Impact Assessment on Competitive Integrity

No Impact

Minimal Impact

Moderate Impact

Significant Impact

Severe Impact

Affected Fair Play

Affected Match Outcome Potential

Caused Unfair Advantage

Caused Unfair Disadvantage

Disrupted Competitive Balance

Was the incident immediately reported to match officials when it occurred?


Estimated Number of Players Affected

Potential Consequences if Left Unresolved

3. Section 3: Evidence Log & Video/Log Attachments

Upload all available evidence to support the incident report. Include visual documentation, system logs, and witness testimonies. Timestamp correlation is critical for accurate review.


Screenshot Evidence - Pre-Incident Game State (mandatory)

Choose a file or drop it here

Screenshot Evidence - Post-Incident Game State (mandatory)

Choose a file or drop it here

Video Clip Evidence - Continuous Recording of Incident (mandatory)

Choose a file or drop it here
 

Additional Video Angles or Perspectives (optional)

Choose a file or drop it here
 

Video Evidence Timestamp References

Game Server Logs (if accessible)

Choose a file or drop it here
 

Client-Side Logs/Error Reports

Choose a file or drop it here
 

Network Diagnostics/Ping Plotter Data

Choose a file or drop it here
 

Witness Statement(s) from Neutral Observers

Were there any chat logs or in-game communications relevant to this incident?


Evidence Inventory Checklist

Collected?

Evidence Type

File Name/Reference

Capture Time

Submitted By

Pre-Incident Screenshot
pre_incident_001.png
6/30/2025, 2:22 PM
Head Referee
Post-Incident Screenshot
post_incident_001.png
6/30/2025, 2:22 PM
Head Referee
Server Logs
 
 
 
Network Diagnostics
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Is any evidence withheld pending further review?


4. Section 4: Match Pause & Immediate In-Game Actions Taken

Document all actions taken immediately following the incident, including match pause protocols, communications with teams, and any on-the-spot decisions made by officials.


Was the match officially paused after the incident?


Match Pause Start Time

Match Pause End Time


Total Pause Duration (minutes)

Communication Log with Team Captains During Pause

Were any immediate corrective actions attempted during the pause?


Match Timeline & Actions Log

Time

Event/Action

Acting Official

Team Response

Score State

2:22 PM
Incident occurred - Player disconnect
System
N/A
A: 14, B: 9
2:23 PM
Pause requested by Team A Captain
Referee Smith
Team A: Confirmed/Team B: Acknowledged
A: 14, B: 9
2:25 PM
Initial investigation started
Head Referee
Both teams waiting
A: 14, B: 9
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Were any official warnings or penalties issued on-the-spot?


Game State After Resolution Actions

Did both team captains agree to resume play?


I confirm that all immediate actions taken were logged in real-time and communicated to both teams before resuming play.

5. Section 5: Head Referee & League Operations Clearance Sign-Off

Final review and authorization section for head referee and league operations personnel. This section confirms official review, determination of validity, and authorization of any further actions or sanctions.


Head Referee Name

Head Referee Official ID

Head Referee Review Completion Time

Head Referee Validity Determination

Head Referee Official Findings and Rationale

Does this incident warrant official sanctions or penalties beyond on-the-spot actions?


Should this incident be escalated to the Tournament Integrity Committee?


League Operations Manager Name

League Operations Manager Official ID

League Operations Approval Timestamp

League Operations Final Disposition

League Operations Final Decision Statement

Head Referee Digital Signature

League Operations Manager Digital Signature

Has an appeal been filed by any involved party?


Appeal Window Closure Date & Time

I certify that all information in this report is accurate, complete, and submitted in accordance with tournament regulations and code of conduct.

I acknowledge that false reporting or misrepresentation may result in disciplinary action including suspension or permanent ban from tournament participation.

This template’s a handshake… Zapof teaches you the secret high-five! ✋
This form is protected by Google reCAPTCHA. Privacy - Terms.
 
Built using Zapof