Tournament setup
Prepare names, schedules, locations, sections, rating basis, rounds, time controls, capacity and registration settings. Check the event state and details before opening registration or pairing.
Plan tournament setupThe PairChamp organizer portal
Organize tournaments, generate chess pairings, manage players and results, and keep participants informedβall from one modern platform.
Approval required. Tournament editing stays with authorized accounts.
Prepare names, schedules, locations, sections, rating basis, rounds, time controls, capacity and registration settings. Check the event state and details before opening registration or pairing.
Plan tournament setupAdd or import players, review public registrations when enabled, and check ratings, federation IDs, section, seed order, withdrawal and attendance. Available check-in tools depend on permissions.
Import players from CSVPrepare first and later rounds with the configured engine, review opponents, colors, byes and boards, and confirm the proposal. Available manual adjustments and round controls depend on state.
Understand the pairing engineAuthorized staff record played results and applicable unplayed outcomes. Review missing results and existing round locks before correcting the record or preparing the next round.
Enter resultsReview individual and team standings, points and configured tie-breaks including cumulative and opponent-score methods. Download available pairing sheets, crosstables and reports.
Explore standings and tie-breaksPublished event details, entries, pairings, results and standings give participants information on mobile or desktop. Organizer editing remains protected; public visibility depends on the event.
See the scholastic workflowThese are fictional players. Review the import tool's current format and errors before pairing.
First Name,Last Name,USCF Id,Grade,Rating,Team Name,Section Name,Seed Alex,Example,12345678,5,712,School A,Elementary,1 Blair,Example,,7,0,School B,Junior High,1
An odd eligible field may need a pairing bye. Preview the recipient and check history; the selected engine and field determine the proposal.
Managing pairing byesUpdate participation before the next pairing and preserve earlier results. Review already-published boards separately; withdrawal does not promise automatic repair.
Managing withdrawalsRecord the request for the affected round and verify its score. Eligibility and points depend on event rules and configuration, not simply on the request.
Requested and pairing byesCheck eligibility, registration and section, then inspect the round state. Entry does not automatically change published boards or guarantee retroactive pairing.
Handling late registrationsLower Primary, Upper Primary, Elementary and Junior High can run separately. The director must check placement and each section's configuration.
Managing sectionsConfirm the actual outcome and use authorized correction controls. Locks and subsequent rounds can restrict edits, so check the round state first.
Correcting resultsPrior colors can affect an engine's proposal. Inspect the pairing and explain decisions under the event rules; color preferences are not a guarantee.
Reviewing pairingsImporting rosters, separating sections and publishing boards can help staff organize a busy event. Check imported data; no capacity or speed claim is implied.
Importing players| Task | Manual workflow | PairChamp workflow |
|---|---|---|
| Player lists | Maintain separate rosters | Enter or import section participants |
| Pairings and byes | Compare scores and history by hand | Preview a proposal and review byes |
| Standings | Recalculate from recorded results | Review standings from entered results |
| Publishing | Distribute updated sheets | Publish available event information |
| Reports | Compile records for submission | Review and download supported exports |
Both approaches require the director to verify the field, apply event rules and submit official reports.
Choose the checklist relevant to your next step.
Practical tools. Clear responsibilities.
Prepare score-based rounds using the selected section engine. Review opponents and colors before committing.
Explore this capabilityGenerate a proposed round from eligible players and recorded history. Generation is a director action, not an unattended publication.
Explore this capabilitySeparate playing groups and manage their rounds independently within one event.
Explore this capabilityBuild the roster through event registration, manual entry, or CSV import, then verify player data.
Explore this capabilityInspect proposed boards and validation findings before commitment and publication.
Explore this capabilityDistinguish a requested absence from the pairing bye needed for an odd eligible field.
Explore this capabilityUpdate participation before the next round without erasing the player's earlier history.
Explore this capabilityAuthorized operators record outcomes and manage the round lifecycle with state-dependent safeguards.
Explore this capabilityRank players by recorded points and configured tie-breaks; inspect special outcomes before finalizing.
Explore this capabilityUse supported federation data and reporting tools. FIDE Dutch pairing is separately gated, not enabled by these pages.
Explore this capabilityReview readiness and download supported CSV, ZIP, or federation reports.
Explore this capabilityGive players and parents published event information without exposing organizer editing tools.
Explore this capabilityPrepare Swiss pairings using the section's supported engine and settings. Review the proposed boards and validation findings before publication. Software assists the tournament director; it does not replace event rules or the director's judgment.
Manage participants within tournament sections, use available imports, and accept event registrations. Check names, ratings, federation IDs, and participation before pairing so an avoidable roster error does not become a round-day problem.
Capture game outcomes and review the section standings as results are entered. Check missing results, byes, and forfeits before preparing the next round. Public tournament pages give players a place to find published information.
Download player and results CSV files or tournament ZIP exports. US Chess reporting readiness and section-level FIDE TRF26 validation help identify report issues. Federation-ready means preparing supported files, not a guarantee of official acceptance.
Clubs can prepare recurring events, schools can separate playing groups into sections, and independent directors can keep round operations together. Access is tied to approved accounts and permissions, not to the public portal.
Organizer access begins with the existing affiliate request. PairChamp reviews the request before creating the organization and approved account. After approval, emailed credentials and a required password change lead into the organizer workspace.
From request to report
The same review-first approach connects onboarding, every round, and the final export.
Submit the affiliate request with your organization, contact details, requested account type, and intended use. Submission is a request, not an activated organizer account.
PairChamp reviews the request. Approval creates the organization and account with the approved role. Credentials are emailed after approval; change the temporary password at first sign-in.
Set the event name, dates, venue, and public information in the authorized organizer workspace.
Set rounds and sections. Choose the supported pairing configuration and rating basis for each section before preparing the field.
Use participant entry, available player import tools, or tournament registration. Review names, section assignments, ratings, federation IDs, and participation before pairing.
Prepare the round, examine the pairings and validation findings, and resolve issues before publishing. The tournament director remains responsible for the event's pairing rules.
Publish reviewed pairings so players can find their board assignments on the tournament's public pages when public visibility is enabled.
Record game outcomes and applicable byes or forfeits. Check discrepancies with the players and tournament director rather than treating an unplayed game as a played result.
Inspect section scores and configured tie-breaks after result entry. Resolve missing or incorrect outcomes before using standings to prepare the next round.
Repeat the review, publish, and result cycle. Recheck withdrawals, participation, and prior results before generating another round.
At the end, review reporting details and export readiness. Download available tournament files or federation-specific exports and complete official submission outside PairChamp.
Make the next round easier to manage
Tell us about your organization and tournament plans. PairChamp reviews requests before granting organizer access.