Player registration

A registration links a team to a fixture. Its status makes the next decision visible: a draft can be prepared, a submitted record can be reviewed, and an approved record can be completed when the required effects exist. The ticket quantity informs the capacity check. The registration keeps its own revision so a reviewer can decide the version actually submitted.

The Registration Coordinator checks the parent fixture before submission. That check matters when several people register near the same capacity limit. Capacity and payment evidence are separate questions. A place in the fixture does not itself establish a verified capture, and a provider record does not increase the venue limit. The coordinator can see the decision time and later check-in time on the registration.

• Choose the fixture. Link the registration to the actual event and operating team.
• Agree the evidence. Decide what must be attached before the coordinator submits a registration.
• Separate decisions. Give the reviewer a clear revision to approve or reject, and keep completion tied to verified effects.

Agree who prepares registrations, who reviews them independently and when a rejected registration may be revised. Decide how the team will handle a registration submitted as capacity changes. Keep the quantity meaningful for both the fixture limit and the eventual admission plan.

A team requests places for a match. The coordinator prepares the registration and checks the fixture capacity. Submission freezes the revision for review. The Independent Reviewer records an approval against that revision. Before completion, the coordinator checks persisted capacity and verified provider evidence. If either check fails, the record remains available for follow-up rather than being treated as complete. When attendees arrive, the admission work is recorded against the same fixture.

A rejected request still explains an earlier decision. Keep its fixture and team links intact while the coordinator decides whether to prepare another submission. Reviewers need to see both the requested ticket quantity and the current parent fixture, since capacity can change between the first draft and a later request.

If the fixture fills while a request awaits review, the coordinator checks capacity again before completion. The earlier approval records what the reviewer decided; it does not create extra places. The team can keep the submitted request and its decision visible while resolving the changed capacity.

• Registration review queue — See submitted registrations awaiting an independent decision.
• Registration status board — Follow draft, submitted, approved and rejected work.
• Completed registrations — Review registrations with completion recorded.

See the first related process and the next handoff.