Team entries

A team entry is the registration record for one participating team on a fixture. It retains the linked fixture, participating team, status, revision and requested ticket quantity. Submission freezes a revision for review in the described process. Review and completion are separate moments: approval addresses eligibility, while completion depends on persisted capacity and verified payment effects. The fixture reference and team reference should be checked together before anyone acts on an entry.

Team Manager prepares and submits the entry. Independent Reviewer considers the current context and records a decision. Admissions Operator later needs the approved entry and the open fixture when handling reservations and check-in. A rejected entry remains in the record with its decision rather than disappearing from the event history.

• Entry identity. Keep the participating team distinct from the team that owns the fixture.
• Decision timing. Record when a decision is made and which submitted revision it concerns.
• Completion evidence. Compare requested tickets, capacity and verified provider effects before treating an entry as complete.

Agree who may submit for each team and who reviews an entry independently. Decide what evidence the reviewer needs for eligibility and how a returned or rejected request is handled in ordinary operations. If ticket quantity changes, review the new scope against the fixture’s capacity; an earlier decision should not simply float to the changed request.

Take a participating team requesting places at an open fixture. Team Manager creates the entry and checks the parent fixture and team before submitting. Independent Reviewer checks the demand against event capacity and records an approval or rejection. For an approved entry, Admissions Operator reserves admission lines and later records the actual check-in. Before the entry is completed, compare those lines with the fixture’s remaining capacity and the verified provider capture. If evidence is incomplete, keep the entry at its current status and resolve the discrepancy using the linked records.

A team may submit more than one entry across different fixtures. Each entry should be read with its own parent event, not as a general team approval. When a reviewer sees a requested quantity, compare it with the capacity of that exact fixture and its other commitments. On event day, the admissions operator can then use the approved entry as context while keeping the reservation and actual scan as separate records.

• Submitted team entries — Review requests awaiting a team-entry decision.
• Team entry board — Follow drafts, submissions, approvals and rejections by fixture and team.

See the operating process for the decision and evidence sequence.