Review and Correct Tournament Registration Records

The short answer

Work from a copy of your registration export. Compare every entry against your approved event list, then label each problem by type: wrong event or division, missing or inconsistent details, or possible duplicate. Confirm each issue with the registrant through your usual contact process. Have the person authorized to make changes carry them out using the registration platform's own procedure. For every change, log the old value, the new value, the reason and who approved it. Never overwrite the original submission, and never delete a record just because it resembles another one.

This guide covers checking records after people have registered. Changing the registration form to prevent future errors is a separate job that belongs with the registration page itself. Rules on transfers, refunds and eligibility come from your organization, governing body or platform, not from this workflow.

What you need before you start

• Your approved event list, with every event, division and published eligibility criterion.
• Field definitions that say what each registration field should contain. For example, does "team name" mean the club name or the name the roster plays under?
• A full registration export that includes record IDs and submission times.
• A named reviewer, plus the named person authorized to approve and make changes. This can be the same person, but write the name down.
• Your platform's documented procedures for editing, moving, cancelling or merging records.
• The contact channel you normally use to confirm details with captains or registrants.

Step 1: Set up a review register

Create one row per issue, not one row per registration. The register records what you found and what was decided. Do not edit the submitted values in the export; you need them for your audit trail. A simple spreadsheet with these columns works:

record ID | event/division | team identifier | submitted team name | captain/contact reference | submission time | discrepancy category | supporting reference | reviewer | next action

Use a contact reference, such as a record ID or captain ID, rather than copying phone numbers or email addresses into the register. Limit access to the people who are actually doing the review.

Step 2: Check each record against the event list

• The event and division exist on your approved list and match what the team intended to enter.
• The entry fits the eligibility criteria you published for that division.
• Every required field is filled in and matches its field definition.
• The submitted team name matches the team identifier and how that team appears elsewhere, such as on a club roster or in a prior season's entry.
• A captain or contact reference is present, so you can confirm any correction.

Give each issue one clear category: wrong event, missing detail or possible duplicate. If a record has two problems, log them as two rows. Keeping the categories separate stops a missing phone number from being treated like a duplicate team, and it lets different people work different queues.

Step 3: Flag possible duplicates without deciding too early

Common triggers include identical or near-identical team names, a shared captain or contact, overlapping player names and submissions made minutes apart. Each trigger means the records need review. None of them proves a duplicate. Clubs often enter several teams, one adult may captain teams in two divisions, and unrelated teams can pick the same mascot name. Record each candidate pair in a matching worksheet:

candidate record IDs | shared identifiers | conflicting details | possible explanation | identity-confirmation owner | authorized disposition

Fill in the conflicting details as carefully as the shared ones. Differences such as a different captain, division or roster are often what show that two entries are separate teams.

Illustrative example

Hypothetical case: Records R21 and R35 are both named "Falcons" but list different captains and different divisions. Flag both records for clarification and assign someone to confirm with each captain. If the authorized reviewer confirms they are separate teams, keep both records and close the flag with a note explaining why. Suppose instead that R35 turns out to belong in a different event. Then record the approved disposition and the platform action actually taken. Do not assume a transfer between events is possible.

Step 4: Confirm and authorize the correction

Contact the registrant through your organization's approved channel and record their confirmation as the supporting reference. Before anything changes, the authorized person signs off on the disposition. Possible dispositions include correcting a field, moving the entry, cancelling it, or keeping both records as they are. Volunteers who spot problems should flag them, not fix them, unless they are the named approver.

Step 5: Make the change through the platform's procedure

Follow the documented procedure for your registration platform. Not every platform supports every action, and some actions cannot be undone. MotorsportReg's help guidance on merging duplicate accounts is one example. It asks you to check that the selected accounts really belong to the same person and to keep the account that has the login information or the correct email. It also states that a merge cannot be reversed. That guidance covers user accounts on one platform, not a method for deduplicating team entries. The principle still applies to team records: confirm identity before you take any action you can't reverse, and read your own platform's instructions first.

After making the change, add a row to the register or extend the existing one with the old value, new value, reason, approver, the platform action taken and the date.

Step 6: Recheck the affected lists and close the flag

A correction in one place can leave stale data elsewhere. Pull fresh views of every list the record feeds, such as division rosters, bracket or seeding lists, the schedule, check-in sheets and captain contact lists. Confirm the change shows up correctly in each one. Close the flag only when this check is done, and record who checked and when.

Readiness checklist by responsibility

Stage	Check	Owner	Done when
Setup	Approved event list and field definitions available	Event lead	Both documents are attached to the review register
Setup	Reviewer and change approver named	Event lead	Names are recorded at the top of the register
Review	Every record compared against the event list	Reviewer	Each record ID is marked reviewed, or has at least one categorized issue row
Review	Possible duplicates logged in the matching worksheet	Reviewer	Each candidate pair has an identity-confirmation owner assigned
Confirmation	Registrant confirmation obtained	Identity-confirmation owner	Supporting reference recorded for each issue
Correction	Disposition approved before any change	Change approver	Approver name and date entered on the row
Correction	Change made using the platform's documented procedure	Change approver	Old value, new value, reason and platform action logged
Verification	Affected rosters, brackets, schedule and check-in lists rechecked	Reviewer	Recheck date recorded and flag closed
Wrap-up	No open flags remain before brackets or schedules are published	Event lead	Register shows zero open rows