# How to Organize Race Bib and T-Shirt Collection

> Run bib and T-shirt pickup without chaos: collect sizes, number bibs, lay out tables, and handle wrong sizes and friends collecting. Laces' limits included.

Source: https://laces.run/blog/how-to-organize-race-bib-and-t-shirt-collection (HTML version of this page)

To organize bib and T-shirt collection, collect sizes at registration, order from those numbers, tie every bib number to a name before pickup starts, and sort your tables by how you packed the kit. Then record each handover once, so nobody collects twice. Most of the pain comes from decisions made weeks earlier. This guide walks through them, and says where Laces helps and where it doesn't.

[Create your race](https://laces.run/app): Add a kit to your ticket, and Laces asks each runner for a size, so your order comes from real entries.

## Weeks before: get the sizes right

Sizes are cheapest to fix before anyone has registered.

On Laces, set **Comes with a kit?** to Yes on any ticket that includes one. Then list what's included under **What runners get**: a shirt, a bib, a medal. Sign-up then asks for a size, with no separate question to set up. You can offer shirt colours on a ticket too. A ticket with no kit doesn't ask, so nobody on a kit-free entry is left guessing.

Two things to watch for:

- **The size can be blank.** Some entries will come through as "Size not given". Plan for a small spare stock in common sizes, and for a person to chase those runners.
- **Publish a size chart.** Put real measurements in your event description. Sizes differ by supplier, and that's what causes most swap requests on the day.

## When to order shirts

Set your deadline from your supplier's lead time, then work back. Ask them in writing how long they need, including delivery. If you want every shirt ordered from real entries, close registration by that date. If you want to keep selling after it, order extra and say on your page that late entries may not get their first-choice size.

An owner, admin or finance team member can download the participant CSV from the app, with one row per paid person. It includes `shirt_size` and `shirt_color` columns, so a spreadsheet pivot table gives you totals to send to your supplier. Laces doesn't total sizes for you, or print shirts.

How much spare stock to order depends on your budget and your history, so we won't give you a percentage. In your first year, lean towards the common sizes, because unused extras cost less than angry runners.

## Bibs: Laces won't number them for you

This is an important limit. **Laces doesn't assign bib numbers, and you can't enter them in the app.** The participant CSV has a `bib_number` column, but you should expect it to be empty. Laces also has no start waves, no chip timing and no results. Keep your numbering in your own spreadsheet.

You have two workable approaches.

**Pre-assign.** Download the final list, sort it, and give each person a number. Use ranges for each distance so marshals can read them at a glance. For example, and this is just an example, 1 to 999 for the 21K and 1000 to 2999 for the 10K. Print a bib list for each table, sorted by name.

**Assign at the table.** Sort bibs by distance, and give out the next one. Write the number beside the name on your sheet. It handles late entries with no gaps. It also means a person can walk off without the number being recorded, so keep the writing step strict.

Either way, your timing provider, if you have one, will need a list that matches bib numbers to names. Ask them for their format early. Our [marathon planning checklist](https://laces.run/blog/how-to-organize-marathon) covers timing and the rest of race week.

## Choose your pickup days and places

Try not to leave collection to race morning. Offering it a day or two earlier reduces the start-line crush. It also gives you time to deal with problems. Keep a small morning table for people travelling in, if you can.

Tell runners exactly what to bring, and when and where. Laces emails paid participants a reminder two days before the event, but don't rely on it for pickup details. Put them on your event page, and send them through your own channels too.

## Set up the tables around how you packed

A pickup flow has three steps, and they shouldn't be in the same place:

1. **Scan.** Check the ticket, then read the name, ticket type and size.
2. **Hand over.** Pass over the bib and shirt.
3. **Check and go.** Let the runner look at the size and pin the bib away from the queue.

Sort stock so someone can find it without looking up. Common layouts:

- **By distance, then size.** Good when each distance has a different shirt.
- **Bibs by number or name, shirts by size in separate stacks.** Good for a single design.
- **Pre-packed bags by name.** Fastest at the table but slowest to prepare, and a nightmare if a size changes.

Put the largest stacks near the handover, and keep a table apart for problems. Then keep your own running count of each size. Don't plan on the app telling you what's left on the table.

## What the scanner does at pickup

A team member scans the runner's QR ticket. Scanning needs a data connection, so test the signal at the venue, especially in a mall or a basement. A green screen shows the name, ticket type, size and colour, and a **What they get** list. Staff hand over the items, then tap the confirm button.

Some details that matter on the day:

- **The tap needs the right role.** Confirming a handover takes a Pickup point lead or higher. Volunteers can scan and check people in, but the handover itself is refused for them. Give your table leads that role, and test it with their own accounts before pickup day.
- **It covers everything still owed.** One tap issues all outstanding items at once. You can't tick off a bib now and the shirt later on this screen. If shirts are delayed, hold your tap until they arrive and track the bibs on paper.
- **There's no undo.** Once confirmed, the kit is marked as collected. So hand over first and tap second, not the other way round.
- **A second try is stopped.** A kit already collected shows a red "Already collected" card on an otherwise valid ticket. If someone taps confirm from another phone at the same moment, only one succeeds, and the other shows the same warning and is recorded.
- **A pickup scan also counts as a check-in.** Any valid scan records an arrival, and the app only shows the first one. So if you run pickup on Friday, a Saturday scan at the start line will show "Checked in" with Friday's time. Warn your race-day scanners, or they will think the ticket has been used.

When someone has nothing to scan, staff can type the order code or search by name or phone. Since email is the only way tickets go out, plan for this to happen often.

## Keep an exceptions sheet

The scan screen doesn't record a swapped size or who collected on someone's behalf. So keep a printed sheet at the problems table, with columns for: order code, what was owed, what was given, the reason, who collected, their phone number, and initials.

Decide these rules before the day, and write them on the table:

- **Wrong size.** Allow swaps only from spare stock, and only after the main rush if stock is short. Note it on the sheet.
- **Size ran out.** Offer the nearest size now or a later collection, and write down which they chose.
- **A friend collecting.** Ask for a copy of the ticket and the friend's name, and consider limiting how many one person can collect. Log them on the sheet.
- **Says they never got it.** The app says it's been collected, so don't hand out a second one at the table. Send it to your named decision-maker, and check your sheet.

[Check the total](https://laces.run/pricing/ug): Enter your entry price to see what runners pay at checkout and what reaches you.

## After pickup closes

The Overview tab shows kits collected, and the people list shows each person's kit status, so you can see who hasn't been yet. The participant CSV has a `collected` column for a list you can work through. To reach those people, use your own channels, without sharing the full list in a group.

Decide now what happens to kit nobody collects, and put it in your event description. Keep your exceptions sheet and bib list with your event records.

For the wider race plan, see our guides to [organizing a charity run](https://laces.run/blog/how-to-organize-a-charity-run-2027) and to [checking in a big crowd](https://laces.run/blog/how-to-check-in-1000-event-attendees).

## Frequently asked questions

### Does Laces assign bib numbers?

No. Keep bib numbers in your own spreadsheet, and print a list for each table.

### Can runners choose their T-shirt size on Laces?

Yes, when the ticket comes with a kit. The size question then appears at sign-up. It can be left blank, so expect some "Size not given" entries.

### Can a volunteer hand out kit?

A volunteer can scan the ticket and see what's owed, but confirming the handover needs a Pickup point lead or higher. Give one of those roles to whoever runs each table.

### Can someone collect for a friend?

That's your rule to set. The app doesn't record who collected, so log it on your own sheet.

### What if the signal fails at pickup?

Scanning needs data, so scans will fail until it returns. Keep a printed list and a sheet, hand over against those, and confirm in the app when the signal is back.
