Programme operating protocol

Version 1.0 — applies across the entire QUIQ Travel installation.

Account controls

Every club must have a verified owner and approved staff. All business records have a club identifier, and no cross-club access is permitted without an administrator privilege.

Event and transport controls

Events may be created freely; travel requests remain unconfirmed until an authorised administrator records operator acceptance. Dates, capacity, vehicle class and luggage needs must be collected before requests can be quoted.

Ticket inventory

Every ticket belongs to a verified order or a pending reservation. Pending reservations hold inventory for 24 hours; successful verification activates QR tickets. Rejected tickets are void. One scan can only check in a ticket once. Bundles issue independent event and travel tickets.

Financial controls

Clubs can see their own gross verified sales, payment verification queue, transport quotes and available record histories. Gross revenue does not automatically represent net profit. Payment verification must follow the club’s actual cash, bank or POS evidence.

Customer support and escalation

Clubs choose and publish approved support channels; they are first contact for event and ticket questions. QUIQ handles platform failures, site availability, data requests and escalations. Operator-dependent issues require joint resolution.

Operational readiness

Do not represent reservations as confirmed JUTC transport or proposed player passes/advertising as activated contracts. Configure SMTP, SSL, tested backups, email delivery and payment procedures before public use.

Contact QUIQ support: admin@itsquiq.com