Sign in to scout.
Signing in decides who you are. What you can do is decided by your team — the first person into a new workspace becomes its admin, everybody after that is a scout until an admin says otherwise. Nobody picks their own role.
Signed in.
Your account is fine, but an admin removed you from the team, so there is nothing here for you to open. A join code will not undo that — an admin has to add you back. Talk to whoever runs scouting for your team.
Your account is real, but it is not in a team workspace yet, so there is nothing you are permitted to see. Enter the join code your scout lead gave you.
No code? An admin or mentor on your team can make one from the console. They can also add you directly — a code is the convenient route, not the only one.
Your station
Scouting partner
Next assignment
Upcoming
Practice matches, replays, or a robot you need to watch that Recon has no assignment for.
Stations are never auto-assigned. Scouts move seats, and an app that insists it knows where you sit produces wrong-robot data.
For a practice match, a replay, or a robot the schedule does not have. It is recorded as a manual match and stays labelled that way — it never becomes an official result.
The event is —. Observations from a custom match are analysed with every other report for that robot; only the match itself is marked manual.
Watch items & questions
Starting position
No zone selected — the report submits either way.
Driver performance
Tracking confidence
Quick chips
Notes
Submit
Watch items & verification
Team intel
On this device
Delivered
What the robot is built to do. One profile per robot per event — a robot gets rebuilt between events, so last month's answers are not this weekend's robot.
Robot photo
Notes
Robot problems and repairs across this event. Anyone can report one; the pit crew works them.
Your event
Leaderboard this event
Predictions
Profile
Preferences
Your quick chips
Notifications
Session
Offline
Event data
Sync
Prototype
This is an integration harness, not the production client. It talks straight to
PostgREST with a user JWT so RLS does the authorization. Feature-by-feature
REAL/DEMO/PENDING status is in prototype/FEATURE_STATUS.md.
Scout lead
Station coverage, the scout roster, and per-match assignment. Everyone can read it;
changing coverage needs scout_lead, mentor or
admin.
A walkthrough of every screen, at phone size, with sample data — for showing somebody the flow without borrowing their phone.
Open the previewYour reports
Strategy
One page per robot: photo, official record, what your scouts observed, FUEL history, breakdowns, match log and an evidence summary. Desktop-shaped — it is a workbench, not a phone screen.
Open the strategy desk