Approved by FIDE Council on 11/12/2025

Applied from 01/03/2026

 

1.       Introduction

1.1     The use of electronic chess equipment, including software and hardware solutions, is essential for the efficient management of modern chess tournaments, such as handling player data, pairings, results, and game recordings.

1.2     Complementary to the FIDE Handbook, the FIDE Technical Commission (TEC) has compiled the [TEC Online Forms](https://www.cognitoforms.com/FIDE/TECMenu) containing comprehensive information, including definitions, processes, and clarifications essential for understanding and implementing FIDE's technical regulations.

2.       Definitions and Acronyms

Refer to General Regulations under Chess Equipment Technical Specifications, Rules and Regulations.

3.       Digital Clocks

3.1     General Characteristics

3.1.1       The clock must clearly indicate the battery level (via percentage or low-battery icon).

3.1.2       Any low-battery warning should be displayed prior to or immediately after the clock is set up, allowing timely battery replacement.

3.1.3       The clock must function for at least ten hours under low-battery conditions.

3.1.4       The type and number of batteries required must be clearly stated.

3.1.5       If the clock includes an audible alarm, there must be a setting to switch it off.

3.1.6       Clock levers and buttons must operate quietly, not exceeding 40 dB at a distance of 1 meter during normal operation.

3.1.7       The clock should preferably be compatible with electronic chessboards, enabling integration into electronic scorekeeping and live transmission systems.

3.1.8       The on-off switch and reset button must be positioned or designed to prevent accidental activation during normal operation.

3.1.9       The clock must be durable and stable under normal playing conditions.

3.1.10      The clock’s timing must be accurate, with a tolerance of no more than ±1 second per hour over a two-hour test at room temperature.

3.1.11      From all sides of the clock, and at a distance of up to 10 meters, it must be clearly visible which player’s time is currently running.

3.1.12      Both clocks must stop after a flag fall in the final period.

3.1.13      In rapid or blitz play, the clock must be configurable to continue the opponent’s countdown after one player’s flag falls.

3.1.14      If both flags fall, it should be possible to determine which fell first.

3.2     Display Characteristics

3.2.1       Both displays must be easily readable at a distance of 3 meters in normal lighting conditions (300-500 lux).

3.2.2       The flag signal must be clearly visible at the same distance and under the same light conditions.

3.2.3       The display face should be free from reflections, ensuring clear visibility.

3.2.4       Seconds must be displayed at least during the last 20 minutes of a time control; optionally, they may be displayed throughout the game.

3.2.5       The number of moves completed should be available for display.

3.2.6       For LCD displays, contrast must be adjustable.

3.2.7       For LED/FLD displays, brightness must be adjustable.

3.2.8       Any adjustments to contrast or brightness must function correctly and reliably.

3.3     Time Rates and Programming

3.3.1       The clock must support the following rates of play as default modes or presets:

• 40 moves in 100 minutes + 20 moves in 50 minutes + 15 minutes and 30 seconds increment per move from move 1
• 40 moves in 90 minutes + 30 minutes + 30 seconds increment per move from move 1
• Game in 90 minutes + 30 seconds increment per move from move 1
• 40 moves in 2 hours + 20 moves in 1 hour + 15 minutes and 30 seconds increment per move from move 61
• 40 moves in 2 hours + 20 moves in 1 hour + 30 minutes
• 40 moves in 2 hours + 30 minutes
• Game in 60 minutes
• 40 moves in 2 hours + 1 hours
• Game in 15 minutes + 10 seconds increment per move
• Game in 25 minutes + 10 seconds increment per move
• Game in 25 minutes
• Game in 3 minutes + 2 seconds increment per move
• Game in 5 minutes + 3 seconds increment per move
• Game in 5 minutes

3.3.2       The clock must allow the arbiter to manually input up to 4 time periods with increments.

3.3.3       When using Fischer (increment) mode, the increment must be added before the first move.

3.3.4       The clock must retain the last program used when switched off, ensuring that settings are not lost.

3.4     Usability

3.4.1       The clock must be easy to operate by players and arbiters, with straightforward controls and clearly understandable settings.

3.4.2       A short version of the user manual must be integrated into the clock’s design.

3.4.3       The clock should remain stable on a flat surface, especially during fast time controls, and should not move easily when players press its buttons.

3.4.4       Buttons and levers must be sturdy enough to withstand normal usage in tournament conditions.

3.4.5       The arbiter must be able to correct time and move counts within 60 seconds.

4.       Electronic Boards

4.1     General Characteristics

4.1.1       Chessboard dimensions, weight (net and gross), and full set weight (board, pieces, and required modules) must be documented.

4.1.2       Boards must be water-resistant to ensure durability under various conditions.

4.1.3       The board’s material, colour scheme for light and dark squares, and piece styles must align with FIDE standards (see Boards and Pieces under Chess Equipment without Electronic Components).

4.1.4       Boards must remain stable during gameplay and not be easily unplugged or disturbed.

4.1.5       The design must prevent cables from causing instability or interfering with players.

4.1.6       All squares must correctly recognize the placement of each chess piece.

4.1.7       Boards must save positions and moves after power-off for a specified duration.

4.1.8       Logical recovery of moves after a crash or an error must be supported.

4.2     Connectivity and Power Supply

4.2.1       Battery type, quantity, and operational time must be specified.

4.2.2       The connection must enable simultaneous use of multiple boards.

4.2.3       Boards should preferably support wireless modules.

4.2.4       Wireless modules must include power indicators and ensure stable connections in tournament settings.

4.2.5       The maximum number of wireless modules per access point must be specified.

4.2.6       Boards must integrate with at least one Accepted electronic chess clock to synchronize moves and clock data for broadcast.

4.3     Software Requirements

4.3.1       Software versions, compatibility with operating systems, and recommended hardware must be documented.

4.3.2       Software should support stable detection of boards, recording moves, and broadcasting games in PGN format.

4.3.3       The software must allow input of tournament details and provide visual editing of finished games.

4.3.4       Moves must be recorded accurately with clock times for real-time broadcast on local or internet platforms.

4.3.5       Games must be easily transferable to external devices and allow offline storage.

4.3.6       Arbiter mode must include extensive controls, such as editing results, checking game rules (e.g., threefold repetition), and making corrections during gameplay.

4.4     Operational Performance

4.4.1       Moves must be transmitted from the board to the control system within specified time limits.

4.4.2       The board and software must detect incorrect positions and moves, allowing corrections without disrupting other games.

4.5     Safety and Certification

4.5.1       Boards must comply with safety standards and include certifications for human safety and reliability.

4.5.2       Printed and downloadable manuals in multiple languages including English must be provided for installation and operation.

4.6     Additional Requirements

4.6.1       Packaging for boards, pieces, and connection materials must be durable and suitable for transportation.

4.6.2       All necessary connection equipment (cables, wireless modules) must be included.

4.6.3       Boards must pass tests for stability, functionality, and compatibility in tournament conditions before acceptance.

5.       Electronic Scoresheets

5.1     General Characteristics

5.1.1       The device’s operating system (OS type and version) must be clearly specified.

5.1.2       The device firmware should preferably be updatable.

5.1.3       The device must support one or more of the following input methods: finger, stylus, touch-screen, keyboard, or other clearly defined input mechanisms.

5.1.4       The type and number of required batteries and/or any additional power supply components (battery charger, adapters) must be clearly indicated.

5.1.5       The device must have a reliable battery life and give a warning if there are less than six hours of operating left.

5.1.6       A low-battery indication (icon, percentage, or equivalent) must be displayed before or immediately after the scoresheet is switched on.

5.1.7       If the device includes an audible alarm, there must be a setting to switch it off.

5.1.8       The device must support standard chess notation as required by the FIDE Laws of Chess, including optional figurine notation.

5.1.9       An automatic move counter must be provided.

5.2     Fair-Play and Security Measures

5.2.1       The device should only provide functionalities strictly related to recording the current game’s moves. No extraneous features are allowed during the game.

5.2.2       A “Game Mode” must lock all non-essential functions, preventing players from accessing previous games or unrelated features.

5.2.3       Arbiters must be able to switch between game mode and other modes (e.g., Arbiter or Organiser mode) if necessary, and then return to the game mode.

5.2.4       Players must not be able to exit game mode during the game.

5.2.5       The device must log user actions in game mode to detect or prevent foul play.

5.3     Display Characteristics

5.3.1       All displayed information (moves, mode indicators) must be legible at a distance of 2 metres in normal lighting conditions (300-500 lux).

5.3.2       The current operation mode (Game/Arbiter/Organiser) must be clearly visible at 2 metres distance under normal lighting.

5.3.3       The display must be free from disruptive reflections and glare.

5.3.4       For LCD displays, contrast must be adjustable.

5.3.5       If backlight is available for LCD displays, it should be adjustable. Brightness levels must be adjustable to ensure comfortable viewing.

5.3.6       At least the last 7 moves must be clearly visible to the arbiter at a glance.

5.4     Data Exchange and Connectivity

5.4.1       It must be possible to easily download recorded games onto another device (server, computer, etc.).

5.4.2       The device should support one or more standard communication methods (e.g., USB, Wi-Fi, NFC or wired network).

5.4.3       The device may support SD cards or other external memory devices to facilitate data storage and transfer.

5.5.    Usability and Stability

5.5.1       The device must not exit game mode inadvertently or deliberately without this being clearly indicated to all parties (players, arbiters).

5.5.2       A short manual or quick reference guide must be provided.

5.5.3       The scoresheet must remain stable and not slip or tip over during play, even under time pressure.

5.5.4       In Game Mode, a wrong move must be easily correctable in under 60 seconds.

5.5.5       In Arbiter Mode, it must be possible to correct moves or adjust move counters without difficulty.

5.5.6       The device must allow scrolling through the entire move list.

5.5.7       It must be possible to record clock times, draw offers, and other information allowed by the Laws of Chess.

5.5.8       The device must support skipping moves (leaving empty spots) if a player is temporarily exempted from recording moves (as per the Laws of Chess).

5.5.9       All moves must be recorded. Even if an end of game (stalemate, checkmate, etc) is missed by the players, or an illegal move is made, the device must not display it and allow subsequent moves to be recorded.

5.5.10      The device must be capable of restarting notation from the initial position or re-establishing the current game’s notation in case of technical issues.

5.5.11      In Game Mode, the device must preserve the current game data if it is switched off and back on.

5.5.12      Under no circumstances the device may lock or freeze.

5.6     Arbiter Mode and Advanced Features

5.6.1       Arbiter Mode should enable the checking of threefold or fivefold repetition and the fifty-move or seventy-five move rule.

5.6.2       Arbiter Mode should detect checkmate or stalemate conditions.

5.6.3       Arbiter Mode must allow extensive corrections to the notation, including insertion or deletion of moves, to handle cases of illegal moves or extreme time pressure (zeitnot).

6.       Publishing Software

6.1     General Characteristics

6.1.1       The system must support monitoring games via camera to capture moves.

6.1.2       It must function with all standard chessboards and pieces with a TAPC.

6.1.3       The system should comply with FIDE Laws of Chess, including recognition of all legal moves (e.g., en passant, castling and promotion).

6.1.4       The device must accommodate boards and pieces placed on tables of diverse heights.

6.1.5       Pieces should be recognized even if they are temporarily misaligned or adjusted during gameplay.

6.1.6       Blurred vision, lighting changes, and obstructed views must not significantly impact the system’s performance.

6.1.7       Power supply details (e.g., battery type, operational time) must be documented.

6.1.8       The system should remain operational in low-battery conditions and provide clear warning if there are less than six hours of battery life left (See Article 6.1.7).

6.1.9       Devices must connect seamlessly to the tournament platform and support stable data transmission.

6.1.10      Moves must be recorded in PGN format.

6.1.11      The system should save the game’s state in real-time and allow recovery after interruptions.

6.1.12      It must support offline storage and transmission of game data to other devices or platforms.

6.2     Performance and Capabilities

6.2.1       In case of an illegal move, the system must provide options to reset the game or correct the position.

6.2.2       The system must operate effectively in fast-paced games, including blitz, ensuring immediate recognition and recording of moves.

6.2.3       The system should accurately distinguish between pieces and squares under varying lighting conditions.

6.3     Tournament Management Features

6.3.1       The platform must allow the creation of tournaments, entry of player lists, and management of tournament details through an admin panel.

6.3.2       Features to start, edit, and end tournaments and rounds must be included.

6.3.3       The system must broadcast games in real-time on websites or other platforms, with the possibility of a delay, allowing public viewing.

6.3.4       Recorded games must include names of players, tournament details, and game results.

6.3.5       Admins must have tools to edit game records, including correcting moves, updating player information, and adjusting game results.

6.4     Operational Considerations

6.4.1       The system must function effectively under standard indoor lighting conditions, with specified lux levels for optimal performance.

6.4.2       The system must detect irregularities, such as players moving multiple times or tampering with pieces and log these actions for review without interrupting game recording.

6.4.3       The login process for admins and users must be secure and intuitive.

6.4.4       Manuals for system operation and troubleshooting must be available in English and multiple languages are recommended.

6.5     Compatibility and Safety

6.5.1       Updates to the software and firmware should be supported to ensure ongoing compatibility and security.

6.5.2       The system must meet all relevant safety standards and certifications for hardware and AI technology.

6.6     Additional Requirements

6.6.1       The system must be able to recover after disconnections or errors or start from a set position.

6.6.2       Devices must undergo rigorous testing for stability, functionality, and accuracy under tournament conditions before endorsement.

7.       Tournament Handler Programs (THPs - historically called Pairing Programs)

THPs are programs running on a commercially available operating system and capable to manage Swiss tournaments by handling player data, pairings, and results. Exceptions may be made for applications running on other operating systems or online platforms.

7.1     Conditions of Compliance

7.1.1       The Tournament Handler Program (THP) must:

a.       Import FIDE rating lists via online updates, proprietary methods, or public files.

b.       Pair participants according to at least one of the FIDE-defined Swiss pairing systems and support all FIDE-defined acceleration methods (see FIDE Swiss Rules under General Rules and Technical Recommendations for Tournaments).

c.       Generate final standings for Swiss tournaments by correctly applying the FIDE-defined tie-break rules (see Tie-Break Regulations) for all tie-breaks listed in the Mandatory Tie-Breaks document (see Annexure B, MTB26 - Mandatory Tie-Breaks).

7.1.2       Compliance must be declared for specific pairing systems supported by the THP.

7.1.3       Compliance must be achieved in FIDE mode, an implicit or explicit state in which the following functionalities and services required by FIDE must be provided:

a.       An English language interface, accompanied by a fully functional user manual or online help.

b.       Import/export functionality in the latest version of the FIDE Data Exchange Format, while maintaining backward compatibility with older formats (see Article 7.2.1).

c.       The public availability (i.e. free of charge) of both a pairing and tie-break checker (PTC, see Article 7.2.3) and a generator of simulated tournaments (RTG, see Article 7.2.4), unless exempted by TEC (see TEC Manual for possible reasons for exemption)

d.       A controlled environment for testing (e.g. a virtual machine for web-based programs).

7.1.4       While the FIDE Mode may include additional functionalities (e.g., manual pairing, non-FIDE-defined tie-breaks or acceleration methods), these must not compromise the integrity of the FIDE-defined pairing systems for which compliance is declared.

7.2     Tournament Data and Validation Tools

7.2.1       FIDE Data Exchange Format

Also called Format of Tournament Report File (TRF, see Article 7.2.2), it is the agreed general Data-Exchange Format for tournament results to be submitted to FIDE, for testing pairing and tie-break programs, and for in-tournament data exchange between THPs, and between THPs and pairing engines. See Annexure A -  TRF26 - Tournament Report File Format Version 2026 for the description of the latest version (TRF26), and the TEC Manual for the description of older versions (TRF16 and TRF06).

7.2.2       Tournament Report File (TRF)

It is a data file encoded in one of the standard formats, TRF26, TRF16, or TRF06.

7.2.3       Pairings and Tie-Breaks Checker (PTC)

The PTC is an embedded tool within a THP that verifies pairings and tie-breaks using the program’s built-in pairing and tie-break engine. It operates with a CLI and is freely accessible. See detailed description in the TEC Manual.

7.2.4       Random Tournament Generator (RTG)

The RTG is a freely available tool embedded in the THP, preferably run from a CLI able to generate simulated tournaments based on various customisable parameters. See detailed description in the TEC manual.

7.3     Acceptance Framework for THPs

7.3.1       The official date on which the new pairing and tie-break rules come into effect is referred to as the New Rules Date (NRD). Successive NRDs must be at least four years apart, unless FIDE decides otherwise.

7.3.2       The new pairing and tie-break rules must be published at least twelve months prior to NRD, unless FIDE decides otherwise.

7.3.3       The Acceptance Cycle ("AC") is a period of at least three years during which TEC can issue TAPCs for compliant THPs. It begins six months prior to NRD and lasts until new rules are published, unless TEC decides otherwise.

7.3.4       Any TAPC issued during the CC is valid until the start of a new CC, unless there are THP-dependent reasons for an Automatic or a Manual Revocation (see Revocation of a TAPC in General Regulations under General Rules and Technical Recommendations for Tournaments).

1.       In case of a Credible Complaint (which can bring to a Manual Revocation), TEC will determine a reasonable period of no more than three months depending on the size, impact and origin of the issue.

7.3.5       Any THP receiving an TAPC prior to NRD may be used immediately, provided that the Pairing Controllers inform all interested parties.

7.3.6       The Transition Period ("TP") is a period of at least one year starting at the beginning of a new CC. Its length may be extended by FIDE.

7.3.7       Any THP whose TAPC validity has ended at the start of the new CC may continue to be used effectively (i.e. with the same pairing rules that it implements) for the entire TP (or even beyond if the THP re- acceptance process has started in the meantime), provided that the Pairing Controllers inform all interested parties (see Revocation of a TAPC in General Regulations under General Rules and Technical Recommendations for Tournaments).

 

Annexure A - TRF26 - Tournament Report File Format Version 2026

Annexure B - MTB26 - Mandatory Tie-Breaks

Annexure C - ETT26 - Encoded Type (of tournament) Table