Timing 200 Runners Across Multiple Devices: The Setup That Actually Works
"Can I Split the Timing Across Multiple Phones?"
This question lands in our inbox almost every week — usually from a PE teacher or sport coordinator about three weeks out from their athletics carnival, fun run, or cross country day. They've got 150, 200, sometimes 400+ runners. One person at the finish line scanning everyone is theoretically possible, but it gets slow at scale and there's no margin for error.
The instinct is right: split it up. Two finish-line stations time twice as fast. Four stations time four times as fast. The question is how to split it without ending up with four separate, unmergeable result sets.
This guide walks through the two ways to do that with Run Lap Tap, depending on whose devices you've got.
First, the Honest Constraint
Run Lap Tap doesn't support two devices scanning into the same live event at the same time. Pro entitlements are tied to your Apple ID and events sync between your devices via iCloud, but iCloud sync isn't designed for "two phones writing to the same event in the same second." If two devices tried to scan into one shared event in parallel, they'd race each other and you'd lose laps.
The way to scale isn't to multi-device a single event. It's to split your runners into groups, give each group its own event, and have one device per event. Then merge the results at the end.
Once you get used to that pattern, it's actually faster and more reliable than the multi-writer-on-one-event setup people imagine. No collisions, no sync conflicts, rock-solid timing per station.
The setup branches based on one question: are the helping devices on the same Apple ID as you, or different Apple IDs?
Option A — All Devices on Your Apple ID (the Easy Path)
If you've got more than one iPhone or iPad of your own — or you can sign your Apple ID into a colleague's device for the day — this is the simplest setup.
Why this works
Your Pro subscription is tied to your Apple ID, not to a specific device. Sign that Apple ID in on three devices and all three get Pro. No extra cost.
Your roster syncs automatically via iCloud to every device on that Apple ID. Build it once on your main device; the others pick it up within seconds. No CSV exports, no AirDrop, no manual steps.
The workflow
- Sign your Apple ID into every device you want to use for timing. Settings → [your name] → iCloud, make sure Run Lap Tap is enabled on each device.
- Open Run Lap Tap on each device. Within a few seconds you should see your existing rosters appear on the new devices.
- Build (or check) your full 200-runner roster on whichever device is easiest. It'll sync everywhere.
- Assign QR codes in the app, then print bibs from the QR Bib Labels screen.
- On each device, create a separate event for the group that device will time:
- "Cross Country – Group A (1–50)"
- "Cross Country – Group B (51–100)"
- "Cross Country – Group C (101–150)"
- "Cross Country – Group D (151–200)"
- Each device scans only its own group. Helpers can use any recording method — Tap, Bib keypad, QR scan, or NFC wristband — whichever suits their station.
- Finish each event when the last runner crosses. Results sync back to all your devices.
- Export each event to CSV (or PDF) and combine them in Excel or Numbers for one ranking list.
That's it. No extra subscriptions, no permission tangles.
Option B — Different Apple IDs (Borrowed Helpers)
If your stations are run by colleagues on their own iPhones — and you don't want to share your Apple ID with them — the roster won't auto-sync across, because each Apple ID has its own iCloud. The fix is a CSV export.
Why this matters
Run Lap Tap's CSV export preserves every runner's QR code and NFC tag ID, not just their name. That means if you scan a runner's QR bib on your phone and on your colleague's phone, the app on both phones recognises the same runner. The codes are portable.
The workflow
- Build your roster + assign QR codes on your device.
- Open the roster → tap the ⋯ menu → Export Roster.
- A CSV file is generated. Share it via AirDrop, email, or any file-share method to each helper.
- Each helper imports the CSV on their phone (Rosters tab → New Roster → Import CSV). All 200 runners appear with the same QR codes you printed.
- From here it's the same as Option A: each helper creates a separate event for their group, scans only their group, exports results at the end.
- You collect the per-station CSVs and merge them in Excel/Numbers.
The cost difference
In Option A, your one Pro subscription covers everything because it's all your Apple ID. In Option B, each helper's device needs its own way to handle more than 30 runners in their event, since the free tier caps event size at 30 runners.
Two ways to handle that:
- Race Pass ($6.99 one-off per device) — unlocks unlimited runners for one event, perfect for race day. Cheapest per-station option for a single big day.
- Helper's own Pro subscription — if they'll use it across multiple events through the year.
For a single carnival, a Race Pass per helper device is the simple call. For 4 stations × $6.99 = under $30 total, you've timed a 200-runner carnival across four parallel stations.
Worked Example: 200 Runners, 4 Stations, One Result Sheet
To make this concrete, here's how a real cross-country day at a primary school might run.
Setup (the day before):
- One teacher (you) builds the roster of all 200 students with QR codes assigned. Bibs printed on the single-bib layout.
- You've got three colleagues helping on the day: two with their own iPhones (different Apple IDs), one borrowing your spare iPad (your Apple ID).
On the day:
| Station | Device | Apple ID | Pro source | Group |
|---|---|---|---|---|
| 1 (you) | iPhone | yours | your Pro | Years 3–4 (50) |
| 2 (colleague A) | their iPhone | theirs | their Race Pass | Years 5–6 (50) |
| 3 (colleague B) | their iPhone | theirs | their Race Pass | Year 5 (50) |
| 4 (helper) | your iPad | yours | your Pro (auto) | Year 6 (50) |
You shared the roster CSV to colleagues A and B in the morning. The iPad helper (using your Apple ID) didn't need the CSV — your roster auto-synced overnight via iCloud.
Each station runs as its own event. Mass starts get staggered by 5 minutes per group so there's no traffic at any one finish line. Total runtime: about 90 minutes for the whole school instead of 4 hours for a single-station setup.
After: Four CSVs into Numbers, sort by total time per age group, podium ribbons pre-printed Monday morning.
Common Pitfalls
- Don't sign the same Apple ID into devices owned by people who'll keep using those devices after the carnival. They'll have your iCloud data forever. Sign in for the day, then sign out and remove the Apple ID. Or use Option B with their own Apple IDs and a Race Pass each.
- Each station's runners must be disjoint. A runner can only finish once per event. If a runner from Group A wanders into Station 2 by mistake, their time won't get recorded. Brief the helpers and use clearly-visible bib number ranges per station.
- Don't try to import the roster CSV on a device that already has a roster with the same runners. It'll create duplicates. Either start clean or delete the existing roster first.
- Sync isn't instant. If you make a roster change at 8:55 AM and your colleague's device imported the CSV at 8:30, they won't see your last-minute change. Decide on the roster the night before.
Roadmap Note
We're tracking a feature request to build the per-event results merge into the app itself — so you wouldn't need Numbers at the end. It's on the list for a future release. In the meantime the CSV export gives you everything you need in about 60 seconds of spreadsheet work.
The Bottom Line
You don't need to wait for "true multi-device race timing." With one Pro subscription on your Apple ID, you can run as many devices as you've got — they sync automatically, share the same roster, and each runs its own slice of the field. With colleagues on different Apple IDs, a Race Pass per device + a roster CSV does the same job for about $7 per station for the day.
The trick is letting go of the "one event timed by many" instinct and embracing the "many events timed by one device each" pattern. It's faster, more reliable, and gives you cleaner data to work with afterwards.