Teams and people

The team record carries its name, code, active state, time zone and currency. Staff membership connects a person to that team and to a platform user. A fixture owner is a person, so the coordinator can identify who is responsible for a particular event rather than relying on a shared team name. Venues also belong to teams; the ownership link matters when a host location is selected.

An active team with an active member can be prepared for fixture work. Admin checks the person’s team and user link before Fixture Coordinator assigns that person as owner. If the person changes teams, review existing fixture ownership deliberately. The fixture still retains its responsible team and owner references, which makes the handoff visible to the people reviewing the event.

• Identity and membership. Match each staff person to the correct platform user and operating team.
• Operating context. Keep each team’s time zone and currency explicit before planning dates or reading amounts.
• Venue ownership. Confirm which team maintains each venue record before a fixture uses it.

Agree who maintains team codes, when a team or person becomes inactive, and who can update user membership. Decide how a person’s role title maps to access for fixture preparation, independent review and admission. Use the same team identity across participant entries and hosted fixtures; a team may appear in either position on different events.

Take a new team preparing its first hosted fixture. Admin creates the team, links the coordinator’s person record to the correct user, and checks that the intended venue is owned by the host team. Fixture Coordinator then chooses that team and person as the fixture’s responsible records. Open the person’s membership and the fixture side by side: the team references should agree, and the owner should be identifiable without guessing from a free-text organizer name. Then add a participating team entry to show that the host team and participating team are separate roles in the same event.

Before the first live event, rehearse a staff change. Move a person to inactive status and confirm that the work is reassigned to another named owner before the event opens. Keep the original fixture and review history readable so the team can explain who prepared earlier decisions. The current owner should be able to find the event through the board and follow its participant entries without inheriting somebody else’s user identity.

• My staff membership — See the signed-in person’s team, role title and active state.
• Fixture board — Check which owner and team carry each fixture through preparation and review.

See the operating process for the decision and evidence sequence.