RFIDAK EVENT CREDENTIAL HANDOFF EXAMPLE
Version: 2026-10-03
SYNTHETIC PLANNING ONLY / NOT FOR PRODUCTION

Purpose
Use the accompanying five-record CSV to discuss printed numbers, platform
records, QR content, chip identifiers and acceptance checks with your project
team. All records and outcomes are invented demonstrations. There are no
customer details, chip keys, production UIDs or valid event credentials.
This is not a platform-specific import file, a chip-writing file or evidence
that RFIDAK has tested a particular event platform.

Open the CSV
Import it as UTF-8, comma-delimited data with a header row. Set every column
to text, especially visible_number and packing_sequence. CSV quoting does
not stop a spreadsheet from converting 000123 to 123 when opened directly.
Check the imported visible numbers 000123 through 000127 before editing.
Do not add spreadsheet formulas or encode these demonstration values onto
production credentials. Use the separate agreed production file format.

Columns
dataset_use: Every row is marked SYNTHETIC_NOT_FOR_PRODUCTION.
packing_sequence: Demonstration order only, not an actual packing record.
visible_number: Printed display number. Leading zeros are meaningful text.
platform_record: Fictional application record. Its link to a credential must
  be approved by the event platform owner. Rows 2 and 4 deliberately repeat
  DEMO-RECORD-B to illustrate a duplicate that must be held for review.
chip_identifier_placeholder: Words indicating where an identifier read from
  an approved physical sample would be recorded. These are not UID values.
  Agree identifier length, display format and byte order with the integrator.
qr_content_example: Documentation URL on example.com, not a valid ticket or
  platform enrollment link. QR content may differ from printed or chip data.
writable_data_placeholder: FORMAT_TO_BE_AGREED. No actual memory location,
  NDEF record, application, authentication mode or encoding bytes are supplied.
example_readback_outcome: Hypothetical NOT_TESTED, MATCH, MISMATCH, DUPLICATE
  and READ_FAILURE scenarios. No row is an observed test or passed acceptance.
exception_action: Suggested discussion point, not a completed action.

Agree the handoff before production
1. Name the physical card/wristband build, exact chip and complete reader or
   platform transaction. Material, frequency and chip family alone do not
   confirm system compatibility.
2. The platform owner/integrator supplies and approves the production field
   map, accepted identifier format, enrollment procedure and security setup.
   Keep secret keys and personal data out of public examples and ordinary RFQs.
3. RFIDAK and the buyer agree supply, print/encoding scope, artwork version,
   source-file version, quantity, preparation and delivery terms in the quote.
   This example does not assign platform enrollment to RFIDAK.
4. Test agreed samples in the intended workflow before approving a batch.
   Record device/model, firmware/software version, date, configuration and
   expected versus observed data. Define required bytes or NDEF content,
   reading conditions and acceptance criteria for the selected chip.
5. Define the batch checks and sampling plan. Reconcile physical items,
   visible print, identifier mapping, QR content and agreed writable data.
   A readable chip identifier alone does not verify the whole transaction.
6. Hold failed or duplicate items. Decide who can authorize replacement,
   re-encoding or platform record updates. Record exception disposition and
   prevent rejected credentials from entering accepted packing counts.
7. Reconcile accepted, held, rejected and replacement counts. Approve any
   packing order/grouping and the final data-file version before release.

Responsibilities to confirm
Buyer/organizer: quantity, destination, required arrival date, artwork and
  credential roles. Approves the project acceptance and delivery criteria.
Platform owner/integrator: identifier/data map, security and enrollment,
  validation in the intended system and duplicate/replacement decisions.
RFIDAK: the physical supply and agreed print/encoding/inspection deliverables
  listed in the accepted quote. Production starts against approved inputs.
Roles can differ by project; record their owners and scope in writing.

For a quote or sample evaluation
Use https://www.rfidak.com/contact?intent=oem&solution=event-nfc-rfid#contactForm
for an event project. Share non-sensitive synthetic field examples first.
Sample configuration, availability and charges must be confirmed. Terms:
https://www.rfidak.com/sample-policy

Format and example-domain references
CSV format: https://www.rfc-editor.org/info/rfc4180/
Reserved example domains: https://www.iana.org/help/example-domains