Glossary.

Every term the platform uses, in plain language.

Archived guest

A guest set aside without being deleted. Hidden from the default guest list, and produces an attention warning at a terminal rather than a clean check-in. Reversible.

Attendance record

The record created when a guest is checked in. It stores the guest, the schedule, the terminal, and the time. One guest can hold several: one per schedule they attend.

Attendee

The person actually coming to the event. Not always the person who paid. See billing contact.

Billing contact

The person responsible for a registration, whose email receives the acknowledgment and the tickets. One registration has one billing contact and up to 10 attendees.

Billing currency

The one currency a team bills and prices in. Chosen when payments are activated and fixed from then on.

Broadcast

Sending tickets to every billing contact on an event in one action. Each contact receives one message containing all their tickets.

Check-in

The act of admitting a guest to a session, by scanning their QR code or by finding them on the door desk. Produces an attendance record.

Closed event

An event that is completed or cancelled. Its guest records are frozen: no adding, editing, importing or deleting.

Door desk

The manual check-in page. Search for a guest by name and check them in without scanning. Also where check-in times and terminals are corrected.

Event

One thing that happens. Owns its schedules, ticket tiers, guest list, terminals and public page. Belongs to a team.

Event website

The free public page at /event/your-address. Where people read about the event and register.

Fieldset

A reusable set of registration questions, built once and attached to ticket tiers across any number of events.

Flagged guest

A guest marked for attention at the door. The scan is not blocked; the terminal alerts the person scanning so they speak to the guest.

Guest

One person attending, holding one ticket tier, carrying one QR code.

Guest manifest

The copy of a schedule's guest list held on a scanning device, which lets the scanner keep making correct decisions with no connection.

Guest sheet

An export: a CSV per ticket tier holding each guest's details, registration answers, and check-in time per schedule.

Inspector

The tool that reads a ticket and tells you what it is without checking anyone in.

Location

A saved venue with an address, attached to schedules. Belongs to a team, so it is reused across events.

Member, Editor, Administrator

The three team roles. Member is read-only. Editor can build and run events and edit the team's name, logo and team website. Administrator can also manage members, billing and orders. Only the team owner can transfer or delete the team.

Microsite

Another name for the event website, or the team website.

Observer

The live view of an event in progress: check-in stats, a scan-by-scan feed, and a terminal leaderboard.

Order

One registration's money: what was bought, what was paid, what was refunded, and where it stands. Every registration has one, including a free one.

Order sheet

A CSV export of an event's orders: billing contacts, payment methods and references, amounts, and attendees. Only team administrators and the owner can download it. See exports.

Payment method

A way a team collects. Either bank or wallet instructions you publish yourself, or a payment gateway you connect with your own keys.

Platform fee

The 3.5% we charge on tickets sold through a connected gateway. Nothing is charged on free tickets, offline payments or door sales.

Proof of payment

The file a buyer uploads against an order they paid offline, so you can check it before confirming. One per order.

Reconciliation

The nightly check of a connected gateway against our own record of the same money, which settles a payment a missed notification never told us about.

Registration

A single sign-up transaction: one billing contact and up to 10 tickets, from one or more ticket tiers, each for a named attendee.

Scan queue

Scans held on a device because they have not yet reached the server. Drains automatically when the connection returns.

Schedule

A session people check in to. Check-in always happens against a schedule, never the event as a whole. Has its own dates, location, publish switch and check-in switch.

Slug

The web address fragment for an event, as in /event/your-slug. A new event starts with a random one. Change it to something readable in the event website builder's settings.

Stock

The capacity limit on a ticket tier. Empty means unlimited.

Suspension

What an unpaid platform invoice does to a team's payments. New money stops. Settling and refunding what you already collected does not.

Team

The account everything belongs to: events, locations, fieldsets, exports. People join teams with a role.

Team website

Your team's free public page at /o/your-team, listing your published events. Hidden until you publish it. Take an event off it under the event's Settings > Team Website. See the team website.

Terminal

A named place people check in: a door, a gate, a lane, a desk. Not a device. Several phones can work the same terminal at once.

Ticket tier

What a guest holds. Carries a name, a price in the team's billing currency, an optional stock limit, an optional fieldset, and the schedules it admits its holder to.

User number

A personal, reusable identity code belonging to a person rather than an event. Can be rotated or deactivated, and has a retirement history.