Skip to main content
TalkValue organizes Badge check-in around three entities: an event holds a list of attendees, synced from your provider or uploaded as a CSV, 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. Each event has a name, a date range, a timezone, a source, and a 6-character access code for staff. The source is an integration provider (Eventbrite or Luma), with a sync status that says whether attendee data is flowing, or TalkValue itself (Manual) for an event you create. You bring an event in from a connected provider with Import Event, or make one with Create Event. Either way, 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. On an imported event, 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. On an event you created, attendees come from your CSV uploads, and a walk-in added at the check-in desk becomes an attendee too. Staff check in attendees from the mobile station; VIPs are flagged so you can spot them in the attendee table and filter to them at the staff station. 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 prints for every ticket type no variant claims (the templates page marks it Fallback), and you can add variant templates that apply to specific ticket types. For example, a different layout for Founder Pass versus General Admission. Each ticket type belongs to one template, so assigning a ticket to a new variant moves it off the old one. A variant left with no tickets shows No tickets assigned and prints for nobody until you assign one. 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 badge 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 every event has a Default badge. When a staff station prints, TalkValue matches the attendee’s ticket ID (on an event you created, the Ticket Type value from your CSV) against each variant’s assigned tickets, then falls back to the Default badge. Matching on the ticket ID keeps variants attached after you rename a ticket type on the provider.
  • 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. Import an event from a provider, or create one in TalkValue.
  • Editor overview. The visual template editor.