Skip to content

The PairChamp organizer portal

Prepare federation reports with clear boundaries

PairChamp provides federation-oriented data and export tools, not federation approval. Plan your event around its actual enabled pairing configuration and the reporting requirements of the authority receiving the report.

Approval required. Tournament editing stays with authorized accounts.

Federation workflow comparison

CapabilityUS Chess workflowFIDE workflow
Ratings and identifiersUS Chess IDs and rating fieldsFIDE IDs and category ratings
Results and tie-breaksUS Chess result classifications and configured tie-breaksFederation-aware unplayed-result and tie-break handling
ReportingReadiness checks and reporting packageSection-level TRF26 validation and export
PairingUS Chess Swiss engine available by configurationFIDE Dutch integration available as an opt-in testing mode; its engine installs automatically and validation is incomplete

Support for federation-specific workflows and export formats does not itself constitute official federation approval or certification.

Practical director guides

Choose the checklist relevant to your next step.

Practical tools. Clear responsibilities.

Verify the data, then prepare the file

US Chess Tournament Support

The organizer export workflow includes a US Chess validation and readiness stage. Reporting issues must be addressed before generating the reporting package. Review event details, participant identifiers, outcomes, and any split reporting requirements relevant to the event. Independent N/R/S outcomes remain distinct from ordinary wins, draws, and losses.

FIDE Tournament Support

Section-level TRF26 generation validates the supported reporting data and can reject incomplete or incompatible input. Confirm federation IDs, dates, result types, and section details before export. Federation-specific treatment of unplayed results and tie-breaks must match the configured event. A generated file still needs review by the responsible organizer or arbiter.

Ratings and identifiers are not interchangeable

A player's US Chess ID and FIDE ID identify different federation records. Review the rating basis chosen for the section and correct imported player details. A rating lookup or stored identifier is not proof of membership eligibility for a particular event.

Pairing support and export support differ

An available export format does not mean every corresponding pairing engine is enabled. FIDE Dutch pairing remains gated and disabled by default; enabling it requires deployment configuration and native-engine gate checks. This page does not change that gate.

Use downloadable working records

Player, game, result, and crosstable CSV downloads support review and movement of tournament data. The general tournament ZIP is distinct from a federation reporting package. Choose the file for the receiving workflow instead of assuming every CSV is an official submission format.

Keep official responsibility explicit

No federation certification, endorsement, or automatic acceptance is claimed. Verify current federation rules and submission procedures independently. PairChamp prepares supported files; organizers submit through official systems and resolve any receiving-system validation issues.

Make the next round easier to manage

Bring your next event to PairChamp

Tell us about your organization and tournament plans. PairChamp reviews requests before granting organizer access.

Request Organizer Access
Organizer HelpExplore All Features Software FAQContact PairChamp