These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Cricket / Sports Association
- Data model
The tables behind Cricket / Sports Association
Cricket / Sports Association ships with 11 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 11
- Features
- 6
- Change it
- Add fields and tables in Proto
How the model is organised
Fixture operations
Fixtures is the event parent. Player registrations and Admissions record participation and gate activity.
Operating context
Teams links to team members and Venues; a fixture points to its team, owner and venue.
Review and effects
Review decisions, record attachments, payment evidence and operation receipts all link to the fixture.
Every table, by feature
- Fixtures and scheduling6
- Player registration6
- Admission and check-in4
- Teams and venues5
- Review and evidence5
- Payment and reconciliation5
- Fixtures
Programs, events and sessions with capacity, lifecycle and revision.
Linked to Teams, Team members, Venues - Teams
Operating organizations that own events, venues and team members.
- Team members
Staff membership linking a platform user to an organization and role.
Linked to Teams, Users - Venues
Physical or virtual venues and resource providers used by events.
Linked to Teams - Admissions
Reserved and admitted admission lines for an event.
Linked to Fixtures - Player registrations
Participant registration records submitted for review and completion.
Linked to Fixtures, Teams
- Player registrations
Participant registration records submitted for review and completion.
Linked to Fixtures, Teams - Fixtures
Programs, events and sessions with capacity, lifecycle and revision.
Linked to Teams, Team members, Venues - Teams
Operating organizations that own events, venues and team members.
- Review decisions
Independent reviewer decisions recorded against a source revision.
Linked to Fixtures, Team members - Payment evidence
Provider payment authorizations, captures, refunds and voids.
Linked to Fixtures - Admissions
Reserved and admitted admission lines for an event.
Linked to Fixtures
- Admissions
Reserved and admitted admission lines for an event.
Linked to Fixtures - Fixtures
Programs, events and sessions with capacity, lifecycle and revision.
Linked to Teams, Team members, Venues - Operation receipts
Idempotent receipts for guarded operations with expected revision and result state.
Linked to Fixtures - Payment evidence
Provider payment authorizations, captures, refunds and voids.
Linked to Fixtures
- Teams
Operating organizations that own events, venues and team members.
- Team members
Staff membership linking a platform user to an organization and role.
Linked to Teams, Users - Users
Users
Linked to Users - Venues
Physical or virtual venues and resource providers used by events.
Linked to Teams - Fixtures
Programs, events and sessions with capacity, lifecycle and revision.
Linked to Teams, Team members, Venues
- Review decisions
Independent reviewer decisions recorded against a source revision.
Linked to Fixtures, Team members - Record attachments
Uploaded evidence files linked to an event with visibility scope.
Linked to Fixtures, Team members - Fixtures
Programs, events and sessions with capacity, lifecycle and revision.
Linked to Teams, Team members, Venues - Player registrations
Participant registration records submitted for review and completion.
Linked to Fixtures, Teams - Team members
Staff membership linking a platform user to an organization and role.
Linked to Teams, Users
- Payment evidence
Provider payment authorizations, captures, refunds and voids.
Linked to Fixtures - Operation receipts
Idempotent receipts for guarded operations with expected revision and result state.
Linked to Fixtures - Admissions
Reserved and admitted admission lines for an event.
Linked to Fixtures - Fixtures
Programs, events and sessions with capacity, lifecycle and revision.
Linked to Teams, Team members, Venues - Review decisions
Independent reviewer decisions recorded against a source revision.
Linked to Fixtures, Team members
Keys and references
A fixture’s record number is the staff-facing event identifier; its Id connects child records through Parent. Team members connects a platform User to a Team. The fixture Owner points to team members and Counterparty points to Venues. Revision and source revision connect decisions to the version reviewed. Operation key identifies a guarded attempt, while provider event ID identifies provider evidence.
Migration order
- Users and Teams. Establish people and operating organizations.
- team members and Venues. Link staff and prepare event locations.
- Fixtures. Import event identity, schedule, owner and capacity.
- Participation. Link player registrations and Admissions to their parent fixtures.
- Evidence. Add record attachments, review decisions, payment evidence and operation receipts with their source references.
Set up Cricket / Sports Association your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.