A live dashboard that watches every batch from warehouse to line and back — plus every device inside, with its own condition status.
Every batch is built for a purpose — who carries it, who uses the iPads, what they're for. Picked at creation, painted on the card.
The proctor receives a Student batch and hands the iPads to students at specific seats. Each device is bound to a line and a seat — the unit walks to the testing room and stays there for the exam.
An iPad with myProctor pre-installed, given to a proctor or tech user who doesn't have iOS, prefers not to install on personal device, or just hasn't installed it yet. One device per staff member.
Same idea as Staff, but reserved for Admin, Manager, TCA, ATCA users — the senior layer that runs and supervises events. Tracked separately so the dashboard can tell coordination devices from front-line devices.
Floating pool of iPads for any TCA-managed need — replacements, walk-ins, troubleshooting, last-minute swaps. Not pre-bound to a person or seat. The flexibility valve in the inventory system.
From the moment a batch is created until it returns or is voided. Color is the language — one glance and you know.
The batch exists in the warehouse, labeled and ready. Counted as In Store.
Custody transferred to a proctor, staff, or TCA. Counted as With User.
Mid-return. Counted as Partially Returned until the last device comes back.
Round-trip complete. Counted as Returned; ready to redeploy or close out.
Created but never deployed — wrong contents, mistaken event, abandoned plan. Counted as Cancelled.
A batch is a unit, but each device inside has its own condition flag. The dashboard rolls them up so the warehouse knows what came back fine and what didn't.
Operational. No issues found in the physical check or in use.
Physical damage — cracked screen, dented case, broken port. Needs repair.
Looks fine, behaves wrong — frozen app, battery won't hold, intermittent issue.
Unaccounted for at hand-back. Triggers an investigation, not a panic.
Swapped out mid-event for a fresh device. Original is retired; replacement inherits the slot.
Three quiet design decisions that keep the dashboard honest.
The batch has a lifecycle. Each device inside has a condition. The dashboard counts both, separately — so a batch can be "Returned" while one of its iPads is "Damaged."
Blue means stored. Orange means active. Yellow means in transition. Green means closed. Red means voided. Used everywhere — list rows, filter chips, audit log.
Every swipe — hand out, hand back, mark damaged, replace — propagates through Firestore to the dashboard immediately. No refresh, no batch jobs, no overnight reconciliation.