Skip to main content
TalkValue organizes Badge check-in around three entities: an event holds a list of attendees imported from your provider, and a set of templates decides what each attendee’s printed badge looks like.
Badge is built around three entities. Every check-in, every printed badge, and every staff station you set up traces back to one of them. These three entities underlie imports, templates, and staff handoff.

​
Events

An event is a single gathering linked to one external source. Each event has a name, a date range, a timezone, an integration provider (Eventbrite or Luma), a 6-character access code for staff, and a sync status that says whether attendee data is flowing. Events are not created from scratch inside Badge. You bring them in from a connected provider via the Import Event dialog. Once imported, the event lives on the Badge dashboard with stats, a staff access card, and a templates section. Example: Q2 Customer Day on May 22 in San Francisco, imported from Eventbrite, sync status ACTIVE, access code K9F2QT.

​
Attendees

An attendee is one registration on one event. Each attendee carries an email, optional name fields, company and job title, a ticket name (the ticket type they bought), a barcode or ticket ID, a VIP flag, and a check-in timestamp once they arrive. Attendees stream in as the import job runs and continue updating while sync is ACTIVE. New registrations, cancellations, and field edits made on the provider side flow through automatically. Staff check in attendees from the mobile station; VIPs are flagged so you can spot them on the table and apply a different template if you want. Example: Maya Chen, maya@northwind.io, ticket Founder Pass, VIP, checked in at 9:14 AM.

​
Templates

A template is the printed badge layout for an event. Each event starts with a Default badge that applies to every ticket type, and you can add variant templates that target specific ticket names. For example, a different layout for Founder Pass versus General Admission. Templates are designed in the visual editor: text, image, QR, and rectangle elements positioned on the label. Text elements can be bound to attendee fields (full name, company, job title, ticket name, ticket ID, barcode), so the same template renders correctly for every attendee. Example: a Default template with a logo, the attendee’s full name in 14 mm type, company in 6 mm type, ticket name in a colored bar, and a QR with the attendee’s barcode.

​
How they relate

An event contains attendees, and each event has at least one template. When a staff station prints a badge, TalkValue picks the variant template whose target ticket names include this attendee’s ticket name, falling back to the Default template if no variant matches. 
Event  ──►  Attendees  ──┐
  │                       ├──►  Printed badge
  └────►  Templates  ─────┘
              │
              ├── Default (all tickets)
              └── Variant (matching target tickets)
  • Access codes. How staff get into a mobile station without signing in.
  • Sync status. What PENDING / ACTIVE / FAILED / DISCONNECTED mean for an event.
  • Add an event. The Import Event dialog from start to finish.
  • Editor overview. The visual template editor.