Pipeline Failures at the Venue: Wifi, Batteries, and Sync

Match day is hostile

Venues have unreliable or prohibited wifi, the field network is reserved for robots, outlets are scarce, and you have minutes between matches. A scouting system that only works in your lab will fail here. Design offline-first and bring a field kit.

Failure 1: Networked sync dies

Apps that sync over wifi or a cloud server stall when the venue wifi is saturated or blocked. Fix: go QR-based. QRScout and ScoutingPASS encode each match into a scannable QR code, so transfer needs no network at all: a scout’s device shows the QR, a central laptop with a webcam scans it, and tab-separated values drop into your sheet. This sidesteps venue connectivity entirely. If you must use a server, run it on a local hotspot/router you control , never the venue wifi, and keep QR as the fallback.

Failure 2: Dead batteries

A tablet dies at match 30 and a station goes dark. Fix kit:

• Charge every device the night before; bring battery packs and a power strip.
• Carry paper backup sheets at every station so a scout keeps recording on a dead device and you transcribe later.
• Stagger device use so not every tablet drains at once.

Failure 3: Scan/transfer jams

QR scanning can fail: glare on a screen, a too-dense QR, a webcam that will not focus. Fixes:

• Keep forms lean. A huge form makes a dense QR that scans poorly; only collect metrics you will actually use.
• Bring a dedicated scanning laptop with a known-good webcam and test it at home.
• Have a manual-entry fallback: if a QR will not scan, read the values off the screen into the sheet rather than losing the match.

Failure 4: Spreadsheet/aggregation breakage

A broken formula or a shifted column silently corrupts your agg and rank tabs mid-event. Fixes:

• Freeze the schema before the event; do not edit column layout once data is flowing.
• Keep the raw-data tab append-only; do all derived work in separate tabs so a formula mistake never touches source rows.
• After each batch, sanity-check one team’s numbers by hand.

A pre-event checklist

1. Run a full mock match cycle at home: fill a form, generate a QR, scan into the live sheet, see it appear in rank.
2. Confirm the schedule is pre-loaded so scouts pick teams, not type them.
3. Pack: charged devices, battery packs, power strip, scanning laptop, webcam, and a stack of paper backups.
4. Assign stations and a single data-lead who owns the laptop and the sheet.

The difference between teams that have data in elims and teams that do not is almost never analytics sophistication; it is whether the boring infrastructure held up under venue conditions.

Key takeaways

• Design offline-first: QR-based transfer (QRScout/ScoutingPASS) needs no network and beats venue wifi, which is unreliable or prohibited.
• Carry a field kit: charged devices, battery packs, a tested scanning laptop, and paper backups at every station.
• Freeze your spreadsheet schema, keep raw data append-only, and run a full mock cycle plus a packing checklist before every event.

This lesson was adapted from learnfrc.com.