Station coverage
Loading…
Scouts
Loading…
Missed matches
Loading…
Match coverage
Assign an individual match — supersedes any block for that match only.Enter a match label.
Teams
Every column here is an alliance figure from official results.
Three robots share one score, so a team carried by two strong partners reads
identically to the team carrying them. Robot‑level performance comes from
scouting reports, in the last column — that is the question this table
cannot answer and the reason Recon collects data at all.
Loading…
Ask a robot a question
Routed to whoever is scouting that team, on their prematch card.Questions
Loading…
Pit watch
Evidence, not a verdict. A robot with three shooter issues this
event is shown as exactly that — three reports. Recon does not conclude
“their shooter is unreliable”; that is a call a human makes with the
thread in front of them.
Anyone can report. Changing an issue’s status needs
Anyone can report. Changing an issue’s status needs
pit_scout,
scout_lead, mentor or admin — enforced
by the database, not by this page.
Loading…
Comparisons
Pick teams to compare.Add two or more teams.
Pick list
Loading…
Exports
Get the data out, into the tools your analysis people already use.Google Sheets
Robot media
Discovery produces candidates, never truth. Nothing here is visible
to a scout until an admin approves it, and approving is a separate act from making
an image canonical — one tap must not silently do two things. A wrong robot
photo in prematch is worse than no photo, because the scout will trust it.
Rejections are kept. Without that the next discovery run re-offers the same wrong photograph, forever.
Rejections are kept. Without that the next discovery run re-offers the same wrong photograph, forever.
Loading…
Teams at this event
This list is shared with every team using Recon at this event.
Attendance is a fact about the competition, not about one workspace, so there is one
list and everybody reads it. Adding a late entry helps all of them; that is also why
a team who came from The Blue Alliance cannot be renamed or removed here, and why a
team somebody has already scouted cannot be removed at all.
Loading…
Event
Recon shows the event your assignments point at. If that is last
season’s competition, every match on it already has a result and nothing will
look upcoming — which reads exactly like a broken schedule and is not one.
Loading a real event from The Blue Alliance is still the better path and is unchanged. Create one by hand when no provider carries it: an off‑season, a scrimmage, a practice day.
Loading a real event from The Blue Alliance is still the better path and is unchanged. Create one by hand when no provider carries it: an off‑season, a scrimmage, a practice day.
Match schedule
For events The Blue Alliance does not carry — an off-season,
a scrimmage, a practice day, or an official schedule posted on paper before it
reaches the provider. Typing it in creates the matches, the station‑to‑robot
mapping, any teams Recon has not seen, and the coverage grid scouts claim from.
A match the provider already supplied is never overwritten. If TBA has this event, re‑syncing is how the schedule changes.
A match the provider already supplied is never overwritten. If TBA has this event, re‑syncing is how the schedule changes.
Loading…
Yellow & red cards
Loading…
Match data
Deleting a report hides it. Purging destroys it. Those are two
decisions on purpose, and only the second one is here. A deleted report still counts
as evidence that somebody sat at that station for that match, which is what missed
match tracking reads — so nothing below can reach a report until a human has
deleted it first.
A report somebody was paid for is never destroyed. The database refuses it, and the count below says so.
A report somebody was paid for is never destroyed. The database refuses it, and the count below says so.
Loading…
Members
Roles are granted here and nowhere else. Nobody picks their own at
sign-up and nobody can promote themselves — the database refuses it, not this
page. Every change below is written to an audit trail with your name on it.
Loading…
Who gets in
Loading…
Role history
Every membership change, oldest lastLoading…
Join codes
A join code is a bearer token. Whoever has the string gets in, so
every code grants
scout and nothing more — there is no setting for
that, by design. Promote somebody afterwards, by name. Codes expire and can be
revoked, and revoking one does not remove anyone who already joined.
Show a new scout the app
Every screen they will go through, at phone size, with sample data. Nothing on it is live.
Loading…