# How to Manage Event Attendees Without Excel

> Replace the attendee spreadsheet with one live list: who is coming, who has paid, who got kit. Plus what still belongs in Excel, and what can't be edited.

Source: https://laces.run/blog/how-to-manage-event-attendees-without-excel (HTML version of this page)

To manage event attendees without Excel, let your registration system hold the live list and treat any spreadsheet as a snapshot made for one job. Excel isn't the problem. It's a fine calculator. The trouble starts when it becomes the record, with three copies and two people editing them the night before. Here is what to move out of the sheet, what to leave in it, and where the limits are.

[Create your event](https://laces.run/app): Each registration lands on one live list your whole team can use. Set up your event free.

## What your spreadsheet has been doing

Look at the columns in your last attendee sheet. Each one answers a question, and most of them have a better home. On Laces, an event opens on tabs in the organizer app, on a phone or in a browser.

| What the sheet did | Where it goes |
| --- | --- |
| Who is coming? | The people list, named for your event type, such as Guests. It only shows people who have paid |
| Did this person pay? | Orders, with filters for All, Paid, Pending, Failed and Refunded |
| Find one person fast | Search by name, phone or order code |
| How do I reach them? | Their order, where phone, WhatsApp and email open with a tap |
| What did they answer? | The order's answers, in the app |
| Did they arrive? | A scan records it, and the scan screen shows the time of the first arrival. There is no list of arrivals |
| Did they collect their kit? | The "Not collected" filter on the people list |

The key difference is that nobody types any of this. When a participant registers and pays from your link, the record appears. A spreadsheet is only as current as the last person who updated it, and at the door that matters.

Remember that one order can hold several people, because a group can sign up together and pay once. Count people on the people list and money on Orders. Those two numbers won't match, and they shouldn't.

## What should stay in Excel

Dropping the master list doesn't mean dropping spreadsheets. Keep them for the jobs they do well.

- **Budgets and cost tracking.** Laces shows your earnings, not your venue bill.
- **Headcounts for suppliers.** A caterer needs a number by ticket, not a list of names.
- **Sums across events.** Exports work one event at a time, so comparing a year of events is a spreadsheet job.
- **Anything the app doesn't show.** A breakdown your board wants can be built from an export.

The one rule: **copy out, never copy back.** A change you make in a downloaded file does nothing in Laces, so the moment anyone corrects a name in the sheet, you have two records again. Laces has no spreadsheet import, either. Each person registers for themselves from the link.

## Decide who sees what

A shared sheet gives everyone everything. Roles fix that, and they're the best reason to give up the sheet.

| Role | Sees | Downloads |
| --- | --- | --- |
| Owner or admin | Everything, including revenue and answers | All files, with answers to your questions |
| Finance | Revenue | Files, with answers left out |
| Event manager | Builds and runs events, no revenue | None |
| Volunteer | Tied to one event, no revenue | None |

Volunteers can do their job at the door without seeing anyone's payment. Invite people by email from the app, and don't send the full list to a volunteer group, however convenient that feels.

## At the door

The spreadsheet's last stand is usually a printed list at the entrance. Here's what replaces it:

- **Scanning.** A valid scan confirms the ticket is paid and records the arrival. A repeat scan stays verified and shows the time of the first check-in, so your staff can spot a shared ticket.
- **No ticket to hand?** Staff can type the order code or search by name or phone. Choosing a paid person there records their arrival, just as a scan does. The participant can also find their own ticket at [laces.run/o](https://laces.run/o) with their order code.
- **Signal.** Scanning needs a data connection, so test it at the venue. Decide in advance what you'll do if the network drops. A paper backup kept by one trusted lead can save the day, but it holds personal details, so collect it afterward.
- **Walk-ins with cash.** Laces does not record cash, and there is no desk registration. Ask them to register on their own phone from your link or QR code, so they land on the same list. If you take cash anyway, keep your own signed list and reconcile it yourself.

For more on running this, see our guide to [QR code tickets and check-in](https://laces.run/blog/qr-code-tickets-event-check-in).

[Ask the team](https://laces.run/contact): Tell the team what your funder or board expects, before you promise it. They can tell you what to expect.

## What you can't change in the app

This is where people miss the spreadsheet, so plan for it.

**You can't edit a participant's details or move their ticket to someone else from the app.** There is no edit button on a person's record. That's why the email is asked twice at registration, and why it's worth checking the form on your own phone before launch.

If a ticket can't be delivered, Laces warns you by email. For anything else that needs fixing, such as a misspelled name on a list you must submit, write down the correction and [contact the team](https://laces.run/contact). For your own planning, record any changes in your own notes, not in a file that pretends to be the master.

Your questions have limits too. Answers are free text, asked once per order, so a group order gets one set. And Laces doesn't have a campaign tool. To tell everyone something, use your own email list or group chat.

## Treat exports as snapshots

Downloading is still useful. Just be clear about what you hold.

- **Orders file:** CSV, Excel or PDF, one row per order.
- **Participant file:** CSV, one row per paid person. Owners and admins also get the answers to your questions.
- **Not included:** check-in data. The app has no attendance list or count either, so if you need a final figure for a report, keep a tally at the door.

Put the date in the filename, so nobody mistakes last week's file for today's list. Export only what the job needs, and delete the file from shared drives when the job is done.

The organizer is responsible for this data. Our guide to [registration records](https://laces.run/blog/event-registration-database) covers privacy duties and retention periods, and the [Privacy Policy](https://laces.run/legal/privacy) has the details.

## Frequently asked questions

### Does replacing Excel mean I can't export my data?

No. Owners, admins and finance members can download their event's orders and paid participants at any time. Those files are yours to use within your privacy duties.

### Can I import my existing attendee spreadsheet?

No. Laces has no import, so each person registers from your link. Send your existing list the link.

### Can volunteers see the whole list?

A volunteer is tied to one event and sees no revenue. Give them the role they need to scan, not a copy of the file.

### How do I see who hasn't paid?

Open Orders and use the Pending and Failed filters. Those people never appear on the people list, which is paid-only. You can nudge them, or send a pay link for one order.

### Can I get a list of who actually attended?

No. The scan screen shows one person's arrival time when you scan or search for them, but there is no list, and exports don't include it. Keep your own sheet or tally if you need a report.
