Badge runs

Cards and badges on paper: the 4×6 handout cards for people who will be handed their ticket, a pack per group and day for a group lead to carry, and badges.

Who uses it: an organizer or group lead the week before, on Events → Badge runs. Somebody limited to a group (a Group Lead, or a custom role with printing) prints only for that group and the groups below it — "Everyone" means everyone they can see — and sees and downloads only the packs printed inside their group.

What they came to do: get one PDF they can send to a printer, in the order they will hand the cards out.

What must be true when they leave: every card in the PDF scans exactly like the ticket it prints, and anyone who should have a card but does not is named, with the reason.

Decided

• A pack is built from a print_sheet or badge template, for the whole event or narrowed to a group (with everyone under it) and a day (tickets for every day are included in each day's pack).

• The template's settings decide the card and sheet size (4x6in, 4x3in, cr80, letter, a4, or a size in inches or millimetres), grouping (group, day, type), sort (code, names, type, group, day, a form answer), a cover page with counts per group, and whether cancelled people and voided tickets are left out (they are by default).

• Cards smaller than the sheet are laid out in a grid with cut marks in the margin; a card the size of the sheet needs none.

• The card layout is the product's: organization strip, badge in the type's colour, then — centred in the card's free height — the event's name, the date (the ticket's day, or the event's dates for an every-day ticket) and the venue, the name and role, group · type · day, and the one free line the template's body fills in; then the QR code, Code128 and code under a divider (Pilot Day, C8).

• On Scale, a template can lay out the whole card instead (Settings → Templates → Edit → Body: "The whole card"), starting from the product card written out so any of it can change. The card keeps its size, place on the sheet and cut marks. It must show the ticket's QR code and barcode; it is checked against a sample ticket when saved and refused, with the reason, if it would not print, would print nothing, leaves out a code, or points at anything outside the card (pictures come as variables, already inside it). A card that fails for one person at print is left out and listed. After a move down from Scale, a card already laid out keeps printing; it can be changed only back to one line.

• Ticket images are the ones made when the ticket was issued. A ticket whose image is missing is left out and listed — the pack never makes images itself.

• Packs build on the queue with progress, appear in the list with a download, and the link is emailed to whoever built it. Downloading needs permission to print tickets.

• Badges come from a badge template: CR80 unless the template says otherwise (4×3 for larger lanyards), the type's badge label and colour, and a photo box. At the help desk, "Print badge" builds one while the person waits and opens the PDF.

Open

• Photos on badges: the box is empty until the form's photo field arrives in week 12.
• Official print-shop bleed settings, if a pilot's printer asks for them.