Organizer, coach & tournament director learning center

PairChamp Chess League — Complete Organizer & Coach Guide

Learn the actual PairChamp workflow for setting up a league, connecting existing tournaments, confirming student identities, publishing finalized results, and understanding what is not yet available.

Use tournament records as the source of truth. League setup does not change tournament pairings, registration, official scoring, exports, or federation ratings.

Return to League Dashboard

1. Quick start, roles and key terms

League management is organization-scoped. Sign in with an authorized organization account and open Chess Leagues. A league (called a “series” in some controls) collects events across a season; it does not create tournaments.

Know the difference A league/series defines a season and its league-points policy. A tournament is the separately created event with its own registration, sections, pairings, and results. A section is a tournament competition grouping. A division is a league eligibility/scoring grouping; an organizer may map a section to a division.

Role-based paths

  • Tournament director: create the series, link existing events, map sections and divisions, confirm final results, review league totals, and manage awards.
  • School coach: use the School & Club Chess Command Center for school profile, roster, imports, and tournament assignments; use league pages for explicit identity matching and league results.
  • Club administrator: manage club records and event participation in the Club Dashboard; league schools and students are linked separately and must be confirmed by an authorized organizer.
  • New organizer: follow the numbered setup below, add only existing tournaments, then finalize each event after checking the authoritative tournament results.

At a glance: supported league lifecycle

  1. 1 · Create seriesName it; dates and season are optional.
  2. 2 · Set policyChoose visibility and league scoring rules.
  3. 3 · Organize rosterAdd schools, students, divisions, and confirmed identities.
  4. 4 · Link eventSelect an existing tournament from the same organization.
  5. 5 · Map and verifyMatch players and, when needed, section-to-division mapping.
  6. 6 · Finalize and reviewConfirm the source results, then review standings and approved awards.

A league may be private or public. Public display requires the league and event to meet visibility/finalization rules and each tournament player to allow public display. Do not publish student information without appropriate permission.

2. Create and configure a league

Create the series

  1. Sign in as an organization manager, then open /org/leagues. If you do not have permission, ask your organization administrator to confirm your role and organization association.
  2. Under Tournament series and scholastic leagues, enter Series name (required), such as “North District Scholastic League”.
  3. Optionally enter a Season label (for example “2026–2027”), Start date, End date, and a short description. If both dates are supplied, the end date cannot precede the start.
  4. Select Create series. PairChamp creates a draft, private series under the organization associated with your account and opens its management page.

Why the organization matters: it scopes which existing tournaments are available and which managers can access the league. The create form does not let you select another organization.

Example: create “North District Scholastic League”, season “2026–2027”, dates September 1 to May 31. These labels organize the series; they do not automatically schedule events.

Configure policy on the league page

The league page has a Save series and scoring policy form:

  • Status: Draft, Active, Completed, or Archived. Set an appropriate season lifecycle state.
  • Visibility: Private or Public. Public still filters out events and tournament players that are not eligible for public display.
  • Scoring method: Cumulative tournament points, Configured placement points, or Best N event point totals. See the scoring section before changing it.
  • Best N events: number of event totals retained for the Best N method.
  • Maximum scoring students per school per event: optional school scoring cap; the highest scoring eligible students count.
  • Placement points (JSON): a rank-to-points map, such as {"1":10,"2":8,"3":6}. Unmapped places receive zero.

After results have been finalized, confirm the scoring-policy change using the checkbox, save, then re-finalize affected events to create snapshots under the new policy. Existing snapshots are not silently rewritten.

Common mistake: assuming series scoring changes tournament scoring. It does not. Tournament points and results remain under the tournament’s existing rules.

Review the dashboard before adding events

Use the series page to review settings, event list and status, school list, divisions, participants, individual and school standings, and awards. The dashboard is not an event setup wizard; tournament registration and pairings remain in their normal pages.

Open League Management · Create a tournament using the existing workflow

3. Schools, rosters and student identity

Use the School & Club Chess Command Center for organization rosters

  1. Open School & Club Chess Command Center (school coaches) or Club Dashboard (club managers).
  2. Use Add Student to create an organization roster record. A student can be reused for future tournament assignments in that workspace.
  3. Use the roster’s Add to Tournament control or bulk assignment when supported, then complete tournament entry details in the existing tournament workflow.
  4. For a tournament roster import, open that tournament’s participant management/upload page and use its CSV import. CSV imports create or update tournament participants; they do not automatically create league identities or confirm matches.

School/club dashboard features, including optional federation IDs and profile fields, remain distinct from the league identity record. Do not copy contact information into a league or use it as an identity key.

Not a league feature: the league module does not provide league-specific CSV roster import, shared school contact assignment, or a bulk student-to-league matching tool. Use existing organization and tournament workflows, then confirm league matches explicitly.

Create the canonical league school and exact aliases

  1. In an organization league, use the Participating schools / teams section and create the canonical school name (optionally a short name and external reference).
  2. If a source record uses a known alternate spelling, add that exact name as an alias to the intended canonical school.
  3. To connect an organization student record, open Search existing student records and confirm mappings from the student identity section; search by name, choose the source type, and explicitly map the source record.
  4. Review the source school and select the correct canonical school. PairChamp does not merge schools because names look similar.

Aliases assist exact identity mapping only. If “Lincoln Elementary” and “Lincoln Academy” may be distinct schools, keep separate canonical records until an authorized organizer verifies the relationship.

Confirm a tournament player manually

  1. On the league page, link the already-created tournament under Series calendar and tournaments.
  2. Use that event’s Match players action to view tournament players and league participants.
  3. Select the intended league participant for each tournament player. Check an authorized stable reference, school/club roster record, or organizer-confirmed information; do not match by name alone.
  4. Choose that event’s school and division, then save the mapping. The event’s school/division is retained with finalized results.
Same-name example: two fictional players named “Jordan Lee” are not automatically treated as one student. Confirm each using an approved stable reference or the organization source mapping. If you cannot distinguish them reliably, leave them unmatched and ask an authorized administrator to verify.

Returning students and school transfers

For a returning student, reuse the existing league participant and confirm the tournament entry again for the new event. For a transfer, assign the new school on that event’s mapping; finalized event snapshots preserve the school associated with that event, so a transfer does not retroactively move earlier points.

There is no separate dated transfer timeline or historical correction workflow. If an event mapping itself was wrong, correct the source mapping and re-finalize the event where the correction is supported; prior snapshot revisions remain available internally, while current standings use the event’s current revision.

Missing federation IDs do not prevent league identity creation: an optional private stable reference can be used, but the record should only be linked after organizer confirmation. A display name alone is not sufficient evidence for duplicate-name resolution.

4. Divisions, eligibility and league scoring

Create a division and define its eligibility

On the organization league page, use Divisions and create a name, optional description, and eligibility type:

  • OPEN: no grade/rating/age boundary is applied by the division type.
  • GRADE_RANGE: enter inclusive minimum and/or maximum grade values (0 through 12). For example, K–3 uses 0–3.
  • RATING_RANGE: enter inclusive nonnegative rating bounds. The eligibility check uses the tournament’s configured federation-aware rating selector, not a guessed rating.
  • AGE_GROUP: select the explicitly recorded age category, such as UNDER_13, MINOR_13_TO_17, or ADULT_18_PLUS. Age is never inferred from grade.

When mapping a tournament participant, enter or verify grade and age category and select a division. The server rejects a participant whose known grade, selected rating, or explicit age category is outside the division. Unknown required data does not silently grant eligibility; record the correct data or use an appropriate open division.

Examples: Grade 3 is within K–3 (0–3); Grade 5 is not. A rating-range division rejects a rating above its maximum. A student with unknown age category cannot be assumed under 13 from their grade. Do not invent an override.

Map tournament sections to league divisions

In the event’s Match players page, use Section-to-division mapping to associate a tournament section with a league division. Once mapped, linked players in that tournament section must use the mapped division; a conflicting participant mapping is rejected.

A section is an existing tournament rule and remains unchanged. Mapping it does not rename the tournament section, change entry eligibility in the tournament, alter pairings, or change tournament results. If the mapping is wrong, correct the section-to-division association and participant assignments before confirming final results.

Scoring formulas currently implemented

SettingCalculationWorked example
Cumulative tournament pointsSum the authoritative tournament points for each included finalized event.Events worth 3.0, 2.5, 4.0 → 9.5 league points.
Configured placement pointsLook up each event’s place in the configured JSON map; unlisted places receive 0.Map 1st=10, 2nd=8, 3rd=6; 2nd and 4th → 8+0.
Best N event totalsSum up to N highest event league-point totals. Equal event totals are selected by better tournament rank, then event order.With N=4 and event totals 7, 9, 6, 8, 10, count 10+9+8+7=34.
School standingsSum mapped students’ league points. If a per-event student cap is set, retain the top scoring students for that school for that event.Cap 3 means the top 3 eligible mapped students contribute for each event.

Individual standings order by league points, then tournament/game points. Equal scores share rank; the display name is only used for deterministic display ordering. School standings add their mapped students’ scores and use the same point-based ordering.

Policy change: changing scoring does not automatically rewrite existing snapshots. Confirm the change in the settings form, then re-finalize each affected event. Check the displayed results after each re-finalization.

5. Run a recurring tournament series

Example: six district events from January through June

  1. Create one series named “North District Scholastic League” with season dates January 1–June 30 and select the intended scoring method.
  2. Create or select the January tournament using the existing PairChamp tournament workflow. Set up sections, registration, and tournament rules there.
  3. Return to the league, select the existing organization tournament in Series calendar and tournaments, set event order/date, and add it to the series.
  4. On Match players, match tournament players to league students, select event school/division, and map sections where appropriate.
  5. Run the actual tournament in its normal console. Enter and verify results there; league management does not pair rounds or accept official round results.
  6. When the tournament results are checked, return to its league event row and choose Confirm / recalculate. Review updated individual and school standings.
  7. Create the February tournament separately and repeat. Continue through June; do not expect recurring events to be generated automatically.

Repeat the same sequence for March, April, May, and June. Use the event order and dates to make the schedule clear to organizers. A linked tournament can belong to only one series.

Tournament copying is not available. Use the current tournament creation workflow and configure each event yourself. No pairings, results, locks, contacts, scores, or authorizations are copied by a league feature.

What finalization does

Confirm / recalculate requires organizer confirmation that the source tournament results are final. PairChamp reads authoritative tournament standings and stores a versioned league event snapshot. This does not change tournament results. The current snapshot is used in standings.

Re-finalizing creates the next revision and preserves the prior result rows; current standings use the event’s current revision. Finalization relies on organizer verification because tournament lifecycle status is not a reliable automatic signal for every event.

Authoritative played W/D/L results are used for games/outcome summaries. Byes, forfeits, and unplayed results are not turned into played wins. Tournament points can still be reflected according to authoritative tournament standings; consult the tournament’s own result codes and standings when interpreting a special result.

Correction and safe removal workflow

  • Wrong tournament result: correct it in the tournament’s normal result workflow first. Return to the league and confirm/recalculate the event to store a new revision.
  • Wrong student, school, or division mapping: correct the explicit event mapping, verify section rules, then re-finalize the event where the correction is supported.
  • Exclude temporarily: use the event’s Exclude action to omit it from current league standings while retaining the event record.
  • Remove from the series: use Remove, provide a reason, and confirm the action. The tournament is not deleted; it no longer counts in current standings and historical snapshots/audit history remain.

Removal is a soft removal; a restore action is not currently provided in the UI. Do not remove an event just to correct scores—fix tournament results and re-finalize instead.

6. Standings, progress, awards and certificates

Review individual, school and student progress

  • The organizer league page shows individual standings, school standings, divisions, linked events, and awards.
  • Open a participant’s View season progress page for event-level place, league/tournament points, school and division, games, W/D/L summary, and a relative event-points visualization.
  • Public league pages are available at /leagues only for public series and eligible published data. Public navigation includes Overview, Standings, Schools, Schedule, and Awards.

Progress charts visualize relative league event points; they are not performance rating charts. League points are not US Chess or FIDE ratings, and PairChamp does not invent rating changes.

Played games and W/D/L require authoritative played-result codes. Unplayed byes, forfeits, and unplayed games are not counted as games played or as played wins. A tournament’s point-scoring policy may award points for special results; confirm interpretation against the source tournament standings.

Leaderboard pagination, search filters, monthly/season filtering, and separate participation or most-improved leaderboards are not implemented. Current league lists and standings are unpaged.

Manual award review and public certificates

  1. On the league management page, use Awards to create one manual award for a selected student or school. Enter the title, description, and optional date.
  2. The award starts as PENDING. Review the recipient, event results, and eligibility before changing the status.
  3. Set status to APPROVED to approve; select public display only when the recipient’s privacy conditions are satisfied. Use REVOKED to withdraw an award while retaining its record.
  4. Approved public awards that pass privacy checks show a Print certificate link on the public league. Open it and use the browser’s Print command.

Manual examples: an organizer may review finalized records and manually award “January Division Champion” or “District Participation Recognition”. Do not describe this as automatic calculation.

Not implemented: automated award rules, automatic monthly/division/school/season champions, perfect-score or consistency awards, most-improved player awards, bulk certificate creation, downloadable PDF reports, individual/school progress report exports, and monthly/season summary exports. Certificates are print-friendly HTML, not generated PDF.

Finish a season

After the final event, verify every event is included as intended, each eligible result is finalized, and school/student mappings are correct. Review individual and school totals; manually create and approve awards; decide whether the series should remain Active, become Completed, or be Archived. Keep public visibility at Private unless publication is intended and privacy checks are satisfied.

7. Real-world scenarios and examples

All names below are fictional. Use the role permissions and source-of-truth rules described above; do not expose student contact information in league records.

1 · One school runs a monthly tournament
Situation / goal
Maple Ridge School plans six events and wants one season total.
Prerequisites
An authorized school/organization manager and existing tournament setup.
Actions
Create a series; create each monthly tournament separately; link each event; match players, map sections, run results, then Confirm / recalculate.
Expected
Finalized included snapshots contribute under the selected league formula.
Mistake / recovery
Do not expect recurrence automation. Create the missed event through the normal tournament workflow and link it if still appropriate.
Limitation / related
No monthly templates. See monthly workflow.
2 · Five schools share a district league
Situation / goal
Five fictional schools compete for individual and school totals.
Prerequisites
All events belong to the same organization series.
Actions
Create each canonical school; add exact verified aliases; map students and event entries; optionally set a per-event top-student cap.
Expected
School totals sum mapped league points, respecting the configured cap.
Mistake / recovery
Do not merge schools by similar names. Keep separate records until identity is verified.
Limitation / related
There is no school performance report export. See school identity.
3 · A chess club serves students from multiple schools
Situation / goal
Oak Club manages its roster while students retain their school affiliation.
Prerequisites
Club manager workspace and an organization league.
Actions
Manage club members in the Club Dashboard; create canonical league school identities as needed; explicitly map each league participant and event school.
Expected
Club roster administration remains separate from league school scoring.
Mistake / recovery
Do not use the club name as every student’s school; correct each event school mapping before finalization.
Limitation / related
League does not consolidate all club records automatically. See identity linking.
4 · A returning student plays multiple events
Situation / goal
Fictional student Alex Morgan appears on a new tournament roster.
Prerequisites
Prior league participant identity and authorized confirmation source.
Actions
Link the new tournament; open Match players; select the existing Alex record only after checking a stable reference or school source.
Expected
Both finalized event results roll up to the same participant.
Mistake / recovery
Do not match because names look alike; if uncertain, leave unmatched pending verification.
Limitation / related
Matching is manual. See returning students.
5 · Two students have identical names
Situation / goal
Two participants are both named Taylor Kim.
Prerequisites
Authorized independent identity evidence, such as a confirmed roster source or stable reference.
Actions
Create/verify separate league identities, then manually map each tournament entry to the correct identity.
Expected
Each student’s results remain separate.
Mistake / recovery
If a wrong match was saved, correct the mapping before finalizing, or correct and re-finalize the event as supported.
Limitation / related
No name-only auto-match or merge. See identity confirmation.
6 · A student changes schools midseason
Situation / goal
Riley transfers from Cedar School to Harbor School in April.
Prerequisites
Authorized verification of the new affiliation.
Actions
Keep prior event mappings intact; set Harbor School on Riley’s April event mapping before finalizing it.
Expected
Earlier snapshots remain with Cedar; later event result uses Harbor.
Mistake / recovery
Do not edit historical event affiliation to reflect today’s school unless correcting an actual past error.
Limitation / related
No separate transfer timeline. See transfers.
7 · Grade or rating category changes
Situation / goal
Sam advances from grade 3 to grade 4, or a tournament rating changes.
Prerequisites
Verified current grade and authoritative rating used by the tournament.
Actions
Update the student eligibility information and assign a division that matches the current event’s rules; check section mapping.
Expected
Ineligible assignments are rejected rather than silently overridden.
Mistake / recovery
Do not infer age category from grade. Correct the data or use an appropriate open division if program rules permit.
Limitation / related
There is no eligibility override. See division rules.
8 · Odd number of participants and a pairing bye
Situation / goal
A tournament round has one unpaired player and awards a bye according to tournament rules.
Prerequisites
Tournament director runs the existing pairing workflow.
Actions
Review the tournament pairing and result using its rules; do not alter league records to simulate a played game.
Expected
League W/D/L games do not count an unplayed bye as a played win/game.
Mistake / recovery
Distinguish tournament points awarded for a bye from played-game summaries; inspect the authoritative standings.
Limitation / related
League does not change pairing logic. See source results.
9 · A student withdraws from a tournament
Situation / goal
A student withdraws after registration.
Prerequisites
Organizer handles withdrawal in the tournament workflow.
Actions
Apply tournament withdrawal rules in the existing console; do not create a league played result. Verify standings before finalizing the event.
Expected
Only authoritative finalized tournament data informs the snapshot; unplayed rounds are not games played.
Mistake / recovery
Do not fabricate a league score. Correct the tournament source first, then re-finalize.
Limitation / related
League is not a registration/withdrawal manager. See finalization.
10 · Correct a result after finalization
Situation / goal
A recorded round result is found to be wrong.
Prerequisites
Authorized tournament result editor and league manager.
Actions
Correct the tournament result first; verify the tournament standings; return to league and Confirm / recalculate the event.
Expected
A new event snapshot revision becomes current; the older revision is retained.
Mistake / recovery
Editing league totals directly is unsupported. Re-finalize from the corrected authoritative result.
Limitation / related
Previous snapshot revisions are preserved. See corrections.
11 · Remove a tournament from league standings
Situation / goal
An event should no longer count in the season.
Prerequisites
Authorized league manager, a reason, and explicit confirmation.
Actions
Use Remove on the event row, enter the reason, confirm, then review recalculated current standings.
Expected
Event is soft-removed from the series; source tournament and historical snapshots remain.
Mistake / recovery
Do not assume removal deletes the tournament or has a restore action. Use Exclude if it should be omitted without removal.
Limitation / related
Restore UI unavailable. See event removal.
12 · A student attends only two of six events
Situation / goal
Casey participates in October and March only.
Prerequisites
Both events are linked and finalized.
Actions
Confirm Casey’s identity for each event and review the selected league scoring method, including Best N if chosen.
Expected
Only the two event totals are included; no participation minimum is invented.
Mistake / recovery
Do not expect absent events to create zeros or automatic participation awards unless the configured formula dictates a zero total.
Limitation / related
No participation leaderboard/automatic participation award. See scoring.
13 · A school misses one monthly event
Situation / goal
Harbor School cannot attend February.
Prerequisites
League policy is established before the season.
Actions
Leave no fabricated entries for February; continue linking and finalizing other events. Apply the same scoring rules to all schools.
Expected
The school total reflects only its mapped student results at included finalized events.
Mistake / recovery
Do not use Remove for a school’s nonattendance; there is no event result for that school to remove.
Limitation / related
No attendance-normalized school report. See standings.
14 · Two students finish with equal league points
Situation / goal
Two players have 20.0 league points.
Prerequisites
Current finalized events and scoring policy.
Actions
Review the displayed tournament/game points and ranking; inspect event-level progress if needed.
Expected
Standings use league points then tournament/game points; exact tied scores share rank. Name order is display ordering only.
Mistake / recovery
Do not claim names break a sporting tie.
Limitation / related
No additional configurable tiebreaker. See scoring.
15 · A coach tries to open another organization’s league
Situation / goal
A coach navigates to a different organization’s league URL.
Prerequisites
Signed-in account without membership in that organization.
Actions
Ask the target organization administrator for correct access; use only the assigned organization’s workspace.
Expected
Server-side organization checks deny management access; UI visibility does not grant authorization.
Mistake / recovery
Do not share URLs or use another person’s login. Contact your organization administrator.
Limitation / related
League access is scoped to the account’s primary organization association. See access controls.
16 · A roster import creates duplicate-looking student records
Situation / goal
CSV import yields two students with similar names.
Prerequisites
Review of the tournament or organization source records by an authorized manager.
Actions
Compare reliable authorized identifiers in the source workflow; choose or create separate league identities; explicitly map each event player.
Expected
No unverified name-based merge is made.
Mistake / recovery
Do not infer identity or merge by similarity; correct source roster data in the owning workflow, then reconfirm mappings.
Limitation / related
League does not import CSV or deduplicate its roster. See identity.
17 · A student has no US Chess ID
Situation / goal
A new student is unrated or has no federation ID.
Prerequisites
Organizer-confirmed student information.
Actions
Create a league participant without an external reference, record verified eligibility data, and manually match the event entry using approved evidence.
Expected
League identity does not require a US Chess/FIDE ID or student account.
Mistake / recovery
Do not use a made-up federation ID. Use an open division if rating data is required but unavailable and event policy allows.
Limitation / related
Rating division checks require usable selected rating. See eligibility.
18 · Event contains forfeits, requested byes, or unplayed games
Situation / goal
Some event scores are forfeits or unplayed bye results.
Prerequisites
Correct authoritative tournament result codes.
Actions
Review result codes and tournament standings; finalize only after the source record is correct; interpret league points separately from played-game W/D/L.
Expected
Unplayed results are not counted as games played or converted to played wins in league W/D/L summaries.
Mistake / recovery
Do not relabel an unplayed outcome as a played game to affect analytics.
Limitation / related
League inherits tournament points. See result handling.
19 · A coach wants to print student progress reports
Situation / goal
A coach needs to review a student’s season progress privately.
Prerequisites
Authorized organizer access and appropriate student privacy permission.
Actions
Open the participant’s organizer-only progress page; review displayed event scores and W/D/L summary.
Expected
The page provides a progress summary and relative event-points visualization.
Mistake / recovery
Do not distribute a public link or include contact data; keep student records within authorized channels.
Limitation / related
No dedicated printable/downloadable individual report or PDF export. See progress.
20 · The league reaches its final championship event
Situation / goal
The June championship completes a six-event season.
Prerequisites
All intended events linked and mappings reviewed.
Actions
Verify the June tournament results; finalize/recalculate; check included events and school caps; review standings; manually enter, review, approve or revoke awards; set series status to Completed when appropriate.
Expected
Current standings reflect the selected policy and current event revisions; public awards appear only when approved and allowed.
Mistake / recovery
If a result needs correction, fix the tournament source and re-finalize rather than editing league totals.
Limitation / related
There is no automatic season champion award or bulk certificate. See awards.

8. Searchable troubleshooting

Access and visibility

ProblemLikely causeSupported next step
Chess Leagues link or league list is missingAccount role or organization association does not meet the league manager check.Sign in with the intended account; ask the organization administrator to verify your role and primary organization. Direct route: /org/leagues.
Permission denied for a leagueThe league belongs to another organization, or your manager role is absent.Use the correct organization account or ask that organization’s administrator for access. Do not try another user’s credentials.
League is not publicSeries visibility/status, tournament visibility, event finalization/inclusion, or player public-display permission is not satisfied.Review the series’ Public setting and status; verify each event and privacy permission. Private student entries remain hidden.

Setup, identity and eligibility

ProblemLikely causeSupported recovery
Tournament cannot be linkedIt is not an available active tournament for this organization, or it is already linked to another series.Confirm the organization and tournament status; use the existing organization tournament. A tournament can link to only one series.
Student cannot be assigned to divisionGrade/rating/explicit age-category is missing or outside bounds, or section mapping conflicts.Verify authoritative student data; select a policy-compatible division; check the event’s section mapping. No override is available.
Student appears in the wrong divisionEntry assignment or section-to-division mapping may be incorrect.Before finalizing, correct the event mapping and section map. If already finalized, correct the source mapping and re-finalize where supported.
Duplicate or ambiguous studentNames are not unique evidence; source roster may contain duplicate records.Check an authorized stable reference or organization record; keep identities separate until verified; explicitly match in the event page.
Wrong school or alias mappingAlias/source school mapped to a different canonical school or wrong event affiliation.Verify the exact source identity; add an exact alias to the correct canonical school and set the correct event school before finalization. Similar names do not merge schools.
Student transferred schoolsLater event should use a new event-specific affiliation.Set the new school on later events only; earlier snapshots remain unchanged. No separate transfer timeline exists.

Results, standings and awards

ProblemLikely causeSupported recovery
Tournament results missing from leagueEvent has not been linked, entries are not mapped, or no finalized snapshot exists.Link the existing event; complete explicit player mappings; verify source results; use Confirm / recalculate.
Standings did not updateEvent excluded/removed, not finalized, wrong current revision, or scoring policy changed without re-finalizing.Review event inclusion and revision; verify the settings confirmation; re-finalize affected events after validating their source records.
Finalization failedSource results/mappings or eligibility may be invalid; event may not belong to this organization/series.Read the displayed message, correct source tournament or mapping through supported UI, then retry. Do not edit the database.
Re-finalization changed pointsSource results or scoring policy changed; a new snapshot revision is now current.Compare current event data and policy with the prior snapshot context; correct the tournament and re-finalize again if needed. Old result rows are retained.
Unexpected league pointsSelected method, placement map, Best N count, school cap, included event, or tournament source points differ from expectation.Review the settings JSON and event-level participant progress; verify tournament standings and re-finalize only after correction.
Event removal restriction or unexpected standingsRemoval requires confirmation/reason and changes current inclusion; Exclude is a separate reversible inclusion control.Use Exclude to omit without removal. For removal, confirm and provide the reason. No restore action is available; tournament remains intact.
Certificate is unavailableAward is not approved/publicly displayable, or student privacy conditions are not met.Review award status and privacy permissions. The award must be approved and eligible on the public league. Use browser print; PDF export is not provided.

Tournament CSV import and assignment problems

CSV imports are handled by tournament participant management, not league management. Check the tournament upload page’s required file/format messages, select the intended tournament and section, and resolve participant data in the owning tournament workflow. A successful CSV import does not automatically link students to league identities.

For a missing organization tournament assignment, use the School & Club Chess Command Center’s student assignment controls or the tournament’s existing registration/admin workflow. Then return to the league event’s Match players page to make the explicit league mapping.

9. Season quick-start checklist

This is an informational checklist only. PairChamp does not automatically mark league setup steps complete.

  • Create your league
  • Configure scoring and visibility
  • Create divisions and eligibility
  • Add canonical schools
  • Add or map students
  • Confirm student identities
  • Link existing tournaments
  • Map sections to divisions when needed
  • Run the tournament in its own workflow
  • Verify authoritative results
  • Finalize each league event
  • Review individual and school standings
  • Repeat for each event
  • Review and approve manual awards
  • Complete/archive the season when appropriate

Privacy, authorization and safe sharing

  • League management is organization-scoped and enforced on the server. A visible link is not permission to access another organization.
  • Use fictional examples in training. Do not put email addresses or phone numbers in league records or public descriptions.
  • Manual student matching requires organizer-confirmed information; do not identify a student from a name alone.
  • Public results require the configured public visibility and event/player display eligibility. Review consent and minor privacy before publication.
  • Organizer-only progress and mapping pages are not public reports. Share only through authorized, privacy-appropriate channels.

For school roster and profile tasks, use the existing School & Club Chess Command Center; for tournament result entry, use the existing tournament console.

Current feature boundaries — do not plan around unavailable functions

  • No automatic tournament copying, recurrence scheduling, or monthly event templates.
  • No automatic award calculation, most-improved or participation leaderboards, or configured award-rule engine.
  • No monthly/season filters, leaderboard pagination, league CSV import, downloadable league reports, school report exports, or bulk certificates.
  • No PDF generation for league reports or certificates; approved public certificates are print-friendly HTML.
  • No separate dated school-transfer timeline or transfer correction wizard. Event snapshots retain the event affiliation.
  • No event restore control after soft removal. Use Exclude when the event should simply not count but should remain in the series.
  • Standings are calculated synchronously from current snapshots; there is no background recalculation/cache.

Use the PairChamp Help Center for general tournament operations. Report incorrect behavior through the existing support channel rather than attempting direct database edits.