One color may represent different dates or access rights, while one entry point may issue several ticket types. Align the names used by organizers, ticketing teams, and distribution staff before preparing the purchase table. Confirm spare quantities for the specific workflow rather than using a universal percentage.

Use the same ticket names in artwork and systems

List attendees, guests, staff, and other ticket types alongside single-day, multi-day, or zone access. Explain whether the wristband is used to verify admission or mark a completed check, and define re-entry and replacement rules. Retain explicit text or numbers in addition to colors to reduce confusion under different lighting or with similar names.

An internal group code can connect artwork, number files, package labels, and issue records. It is project management information and need not always be printed on the wristband.

Approve quantities, numbering, and packaging separately

For each group, list planned quantity, spare quantity, and approved total, specifying whether samples and rehearsal bands are included in delivery. For serial numbers, barcodes, or RFID, confirm ranges, formats, duplicate handling, and spare-band rules. Where several entry points share numbering, the ticketing team should first define number allocation or on-site binding.

Request packing by date, entry point, ticket type, or shift, with group code, name, quantity, and number range on labels. Confirm pack units, whether mixing is permitted, and additional charges. Align outer-box and inner-pack labels so staff do not need to open every pack to identify it.

Connect the delivery list to on-site stock issue

After sample approval, lock artwork and quantity table versions. Record changes and affected groups. Check delivery schedules against the specific agreement; the event date is not itself a guaranteed arrival date.

On receipt, count groups against the list and sample-check text, colors, and encoded data. Rehearse distribution and define handling for misissues, damage, loss, and returns. Record remaining, voided, and replacement quantities after the event to support future purchasing.

  • Purchase table: group code, ticket type, access rights, planned quantity, and spares.
  • Packing table: pack units, pack counts, labels, and number ranges.
  • Issue record: entry point, responsible person, quantities issued, and exceptions.