Organizer creating and getting a ranking

Most organizers do not define ranking formulas, but your data quality determines whether federation rankings can be created without manual cleanup.

What this step is for

You are preparing a ranking-ready result package by ensuring class structure, statuses, and published results are correct and traceable.

What you own vs what federation owns

You own:

  • class and round correctness
  • accurate participant placement
  • dispute/correction handling before final publish
  • complete result publication

Federation owns:

  • ranking policy and scoring weights
  • cross-event exceptions
  • final ranking publication rules

Where to do it

In Manager, work across:

  • Competition setup
  • Rounds
  • Results publishing

Coordinate with federation admins if ranking sync/export is required.

Step-by-step ranking readiness flow

Step 1: Verify classes that are ranking-eligible

Create a final list of classes that should feed ranking.

For each class, confirm:

  • class code is correct
  • federation mapping is correct
  • class status is active

Step 2: Validate round outcomes before publish

For every ranking-eligible class:

  1. ensure round statuses reached required state (Closed/Confirmed)
  2. ensure qualifiers/finals are correct
  3. ensure ties and disqualifications are resolved per policy

Step 3: Resolve data integrity issues

Before publication, check for:

  • wrong class assignments
  • duplicate participant rows
  • missing placements
  • unresolved withdrawals/exclusions

Do not publish ranking-relevant classes until these are fixed.

Step 4: Publish final results

When integrity checks pass:

  1. publish results for all ranking-eligible classes
  2. record publication timestamp
  3. record operator identity

If your federation requires a review hold, submit for review instead of direct publish.

Step 5: Handoff to federation ranking workflow

Provide federation with:

  • event ID and season
  • published class list
  • known exceptions/corrections
  • contact for follow-up questions

Step 6: Post-publish support window

For 24-72 hours after publish:

  1. monitor federation questions
  2. respond quickly with evidence (audit trail, screenshots, IDs)
  3. apply only approved corrections

Pre-close checklist

  • All ranking-eligible classes published
  • No unresolved disputes impacting placement
  • Withdrawals/disqualifications reflected correctly
  • Event notes include any special exceptions
  • Federation handoff completed

Common blockers and fixes

“Ranking class has missing placements”

Fix:

  1. reopen correction workflow if policy allows
  2. complete placements
  3. republish with revision note

“Published too early before dispute resolution”

Fix:

  1. log incident
  2. follow federation correction procedure
  3. avoid ad hoc edits without audit trace

“Federation says class mapping is wrong”

Fix:

  1. compare class code against federation template
  2. correct mapping
  3. resend ranking package

What success looks like

Federation can process rankings from your event immediately, with minimal manual intervention.

Next step

Continue to Age transfer coordination if participants are moving between age groups.