To manage event volunteers and staff well, write down every job first, then give one named person responsibility for each area, brief everyone on what to do when things go wrong, and limit each person’s access to what their job needs. Most volunteer problems come from unclear jobs, not from unwilling people. This guide covers the human side, then the settings in the Laces app.
List the jobs before you ask for people
“We need 20 volunteers” isn’t a plan. Write the jobs out, with a time and a place for each:
- Parking and directions
- Gate scanning and queue marshalling
- Help desk
- Kit or lanyard collection
- Stage, room or course support
- Setup and take-down
Beside each job, write the hours and how physically hard it is. Note whether it needs a skill or a phone. Now you can count people from your jobs instead of guessing. For gates, there’s real arithmetic in our guide to checking in 1,000 attendees.
Then add leads. Someone running six scanners should not be scanning. One lead for each area means a volunteer always knows who to ask, and you aren’t the answer to every question.
Laces doesn’t handle rosters. It has no shift planner, no volunteer sign-up form and no volunteer messaging. Use a spreadsheet and a group chat for those.
Paid staff and volunteers aren’t the same
Be careful with this distinction. Paid staff can be asked for more, and they may have rights under your country’s labour rules. A volunteer is giving you their time, and can walk away. Don’t rely on a volunteer for anything that would stop your event if they failed to turn up, such as handling cash, medical cover or crowd safety decisions.
Ask a local adviser if you are unsure how labour law treats allowances in your country. It’s also worth asking your insurer whether volunteers are covered, and getting a parent’s or guardian’s consent for anyone under 18.
Give each person the right access
The Laces app has six roles. Each person signs in on their own account, so never share the owner’s login. Here is what each role is for.
| Role | For | Limited to one event? | Money |
|---|---|---|---|
| Volunteer | Scanning tickets at the door | Yes, always | None |
| Pickup point lead | Running a table or gate, confirming kit handovers | Yes, always | Sees what a person’s order paid when looking them up |
| Event manager | Running events end to end | Optional | No earnings or payouts |
| Finance | Payouts, statements and payments | No | Yes |
| Admin | Everything except handing the organization over | No | Yes |
| Owner | Everything | No | Yes |
A few details people get wrong:
- Volunteers can scan and search. That includes searching your event’s list by name or phone. So you are still trusting them with personal details. Tell them not to look up people out of curiosity or share what they see.
- Handing over kit needs a higher role. A Volunteer can scan a ticket and record an arrival, but can’t confirm a kit handover. For kit tables, give the person doing it the Pickup point lead role, and read the bib and T-shirt guide.
- A lead can see order amounts. When a Pickup point lead looks someone up, they can see what that order paid. Volunteers can’t. Neither sees your revenue.
- Exports are limited. Only finance, admin and owner roles can download your lists, and only owners and admins get question answers in those downloads.
Keep the higher roles few. If you can’t say why someone needs to see payouts, they don’t need the Finance role.
How to invite people
Only an owner or admin can invite people, and you can only grant a role below your own. So an admin can’t create another admin, and nobody can be invited as an owner.
From Your team, enter the person’s name and email, and choose a role. For a Volunteer or Pickup point lead, the invite is tied to the event you are working on. Laces emails them a code that works once and expires after 7 days. If the email fails, the app shows you the code, so you can read it out instead.
Each person then needs the Laces app on their phone, and needs to join and sign in before the day. Don’t leave this for the gate, where the signal may be poor. Invite people early enough to chase any code that has expired.
Brief people on the awkward moments
A good briefing takes minutes and prevents most problems. People rarely need to hear how to do the normal case. They need to know what to do when it goes wrong:
- Red screen, cancelled or unpaid. Stay polite, say “let me get someone to help”, and send them to the help desk.
- “Could not check that ticket.” That’s the network, not the ticket. Try again. Never turn someone away for it.
- A “Checked in” label on a person who says it’s their first time. Send them to the help desk. Don’t accuse them.
- Someone angry. Don’t argue. Call your lead.
- A medical or safety problem. Stop what you’re doing, and call the person you named for this.
- No signal. Wait for your lead to call the switch to the paper list.
Have everyone scan a test ticket during the briefing, on their own phone. It’s also a useful way to discover missing logins, camera permissions and flat batteries while there’s still time to fix them. Our QR ticket guide lists what each screen means.
Look after them on the day
People who feel looked after come back next year. Plan for:
- Water, food and shade. Include these in your budget. Tell people when and where they’ll eat.
- Breaks. Name the relief cover, because nobody leaves a lane unless someone replaces them.
- Transport. A shift ending at midnight needs a way home. Sort it before you ask them to stay.
- Something to wear. A bright shirt or lanyard makes helpers easy to find. Budget for shirts only once you’ve counted real numbers.
- A real thank-you. If you promised a free ticket, an allowance or a certificate, deliver it on time.
If you give volunteers free entry on Laces, remember that anyone with your link can select a free ticket. A cap on that ticket and a list you check by hand help prevent it being used by others.
Close the door when the event ends
Laces access doesn’t expire when your event ends. A volunteer remains on your team, tied to that event, until someone removes them. So after each event:
- Remove people who no longer need access. In the app, this is done by the owner.
- Ask anyone who downloaded a list to delete it from their phone and any shared drive.
- Ask for feedback while it’s fresh. Your scanners know exactly which part of your gate didn’t work.
Keep a simple record of who did what and how reliable they were, so next year’s team starts from something better than a blank page.
Frequently asked questions
Can volunteers see how much money the event made?
No. Volunteers see no revenue and no order amounts. They can see the names and ticket details of people at the event they are tied to.
Can a volunteer work on more than one of my events?
A volunteer’s access is tied to one event. Someone already on your team can’t use a second invite, so for the next event, the owner removes them and you invite them again.
Can Laces schedule shifts for my volunteers?
No. Laces handles access and scanning, so use a spreadsheet or your own tool for rosters and shift messages.
What if a volunteer’s phone is lost during the event?
Have the owner remove that person from your team, so the lost phone can’t reach your list. Then invite them again and let them sign in on another phone.
Set up your team before event day
Creating an event on Laces is free for organizers. Invite your team, choose each role, and let them test scanning first.
Read next
For organizersHow to Organize an Event in 2027: Step-by-Step Planning GuideHow to organize an event in 2027, step by step: purpose, entry, budget, approvals, date, payments and the door, with guides for five African countries.5 Nov 2026 · 7 min read
For organizersHow to Manage Event Registrations, Payments and Attendance in One PlaceHow to run event registrations, payments and attendance from one record: the workflow, team access, numbers to track, exports and handling exceptions.4 Nov 2026 · 6 min read
For organizersEvent Planning Checklist for 2027: 90 Days Before to Event DayA working event planning checklist for 2027: dated tasks from 90 days out to event day and the week after, covering budget, approvals, tickets and the door.5 Nov 2026 · 7 min read
