Robolyst Robolyst
For event directors, volunteers and program delivery partners

Run your FTC events, from the first queue call to the recap

The event manager runs the queue, inspection and the pits on the day. Pit scouting gives every team one QR code and the whole event one report. The region dashboard puts every FIRST Tech Challenge event in your region on one table, with photos, recaps, advancement and the teams that did not come back. The region website gives every event a public page, and the people who sign up get a newsletter. One request covers all four.

Event manager

For event directors and the volunteers working the day

A dashboard for everyone working the event

Each event gets its own dashboard for the people working it. Add volunteers by email before the event, or show a join code at check-in that lasts ten minutes. Give each one a role: lead queuer, queuer, lead inspector, inspector, pit admin, FTA or field tech. Roles of your own are defined once for the region and work at every event in it.

Each person sees the tools their role needs and nothing else. A lead queuer can add queuers and a lead inspector can add inspectors without waiting on you. Access ends a week after the event, so nobody carries it into the next season.

Open the sample event

The queue moves on one button

The lead queuer moves each match a step: queuing soon, now queuing, on deck, on field. Teams in that match get an alert on their phones or in their Discord, every pit TV updates, and queuers check teams in by tapping their numbers. A second press inside four minutes is refused, so a double tap does not skip a match. Replays and breaks go into the schedule where they happen. If FIRST has not published the schedule yet, import the FTC Live export.

Teams tap "ready for inspection" on their pit page and join the line themselves. Take next hands an inspector the team that has waited longest, and two inspectors pressing at once get different teams. A team that has not passed shows struck through at the queue until it does.

The FTA keeps field notes per team, so a connection problem in Q12 is on the card when that team plays Q30. A request for a CSA or a reinspection reaches the people who handle it. Both exports are ready for the event report.

Queue Harbor Qualifier
Q14 scheduled 1:46 PM
  1. Queuing soon
  2. Now queuing
  3. On deck
  4. On field
14231 18806 9052 not here3311
Send Q14 to on deck
Inspection 27 of 32 passed
  • 9052 Inspecting Inspector 2
  • 22104 Waiting 4 min
  • 7034 Waiting 2 min
  • 16090 Passed
Take next
Drawn with sample data.

Every team gets a page from its pit sign

Print one QR sign per team. Scanning it opens that team’s page for the event: queue alerts on the phone, your announcements and approved parts requests, its place on the pit map and its spot in the practice field line. Teams on Robolyst get the same alerts through their team, with no sign needed.

The pit admin posts up to four announcements at once, each with its own expiry. Parts requests wait for approval before every team sees them. The practice line puts a team that lost a match to a field fault at the front.

Pit B7 14231 Scan for queue alerts, announcements and your pit sheet
14231 · Harbor Qualifier Pit B7
Now queuing: Q14 Red alliance with 18806
Lunch break moves Q30 to 1:15. Field 1 practice reopens at 12:45.
Practice field 2 3rd · ~6 min
Pit sheet Filled in
Drawn with sample data.

Pit displays, with a ticker you run from your phone

Open robolyst.org/display in the browser of any TV and it shows a six-character code. Scan it or type it on your phone, pick the event, and the screen starts. Left on its default it follows the event by itself: the queue and rankings during quals, the full table before alliance selection, each alliance’s next match in the playoffs. Or build a template from panels: rankings, the schedule with the latest results, event photos with an upload QR, the pit scouting QR with coverage, and an announcements ticker. Two panels sit side by side and the rest rotate on a timer you set.

Templates belong to the region, so the same boards come back at every event, and an edit reaches every screen on it within seconds. Screens stay paired between events. Move the whole set to the next venue from the region dashboard, and press Identify to find which TV is which.

To post to the ticker, type up to 140 characters on your phone. Tag it as info, heads up or good news, and keep it up for 15 minutes, an hour or the rest of the day.

The TV never signs in, and nothing private is on the screen.

Harbor Qualifier

1:42 PM

Rankings 1 to 6 of 32
1142313.4
290523.1
Alliance selection starts at 2:15 in the main gym.
Ticker 3 screens
Message for every display at this event Alliance selection starts at 2:15 in the main gym. 50/140
InfoHeads upGood news
Stays up for 1 hour Send
Drawn with sample data.

Pit scouting

For any event, run from its event dashboard

One QR code per pit, one report for the event

Every team scans a QR code at its own pit and fills in one short sheet about its robot. The answers land on a single report every team at the event can read, next to live rankings and OPR. Teams stop sending scouts from pit to pit to ask the same twenty questions.

There is no app and no account. The questions follow this season’s game: drivetrain, auto, teleop, endgame, plus an optional robot photo. The same code reopens the sheet after a repair or a new auto. If the pit Wi-Fi drops, the phone keeps the answers and sends them when it reconnects.

How it runs

  1. 1

    Request access

    We email a private link to the address you enter. Opening it adds you to the event’s dashboard.

  2. 2

    Open the link a few days out

    Registered teams are already listed. Add walk-ins by team number.

  3. 3

    Print the pit signs

    One letter page per team, any printer. Hand them out at check-in or tape one to each pit table.

  4. 4

    Watch it fill in

    The Pit signs tab shows which teams have a sheet, so you know who to nudge before quals start.

Who sees what

ItemWritten bySeen by
Pit sheet answers and robot photoThe team itself. Another team can fill a blank sheet, and the team’s own answers replace theirs.Everyone, on the event’s scouting report and the team’s Robolyst page
Your event dashboardYou and your event staffOnly signed-in staff you added, each limited by their role. Access ends a week after the event.
Each team’s pit codeThe team at that pitAnyone who scans it can edit that team’s sheet. You can turn a pit code off or reissue it.

Try it first

Coverage you can watch

On the event dashboard you see how many teams on the roster have a sheet and when the last sheet came in. The usage log splits sheets by source, a team’s own pit code against another team or a volunteer, and counts them per day in the event’s timezone. If the count is still low on Friday night, you know which pits to visit before quals.

A filled-in event report
Pit signs Harbor Qualifier
32 pit codes Made by the pit admin 27 sheets from them
Print pit signsMake pit codes

27 of 32 teams have filled in their sheet for this event

Usage log last sheet 6 min ago
22 Team's own pit code
5 Another team or a volunteer
DayOwn codeOthers
Fri Nov 1492
Sat Nov 15133
Drawn with sample data.

Region dashboard

For program delivery partners, and event directors for their own event

Every event in your region on one table

Sign in and the dashboard opens on your region, with a row for every event this season: team count, pit scouting coverage, photos and where the recap stands. Each row opens that event’s own dashboard, where its scouting, displays, photos and recap are run.

Coordinator dashboard · Sample Lakeshore Region Program delivery partner access to every event in the region.
Overview Scouting Photos Recaps Advancement Teams Location page Embeds
DateEventTeamsPit scoutingPhotosRecap
Nov 8Lakeshore League Meet 228 28/2864Published
Nov 15Harbor Qualifier32 27/3241Draft
Nov 22Ridgeline Qualifier30 12/30After the event
Dec 6Cedar Valley QualifierNo roster yetAfter the event
Drawn with sample data.

A photo queue you review, and upload links for photographers

Photos uploaded from a public event page wait in your queue. Approve them, fix the credit or caption, or reject with a reason that stays on the record. A rejected file is deleted. Reviewers get an email when something is waiting.

Photos you upload yourself go live straight away. So do photos sent through an upload link, which is how a venue photographer adds photos without an account. Give the link a label, a credit, a photo limit and a last day, then print its QR code. Location data is stripped from every file before it is stored.

Each event dashboard has the same queue for that event alone, so a volunteer with photo review can work it on the day.

Photo queue 3 pending
PendingApprovedRejected
  • Alliance 1 lifting the trophy Harbor Qualifier · Team 14231 · event page Approve Edit Reject
  • Pit 14, intake rebuild Harbor Qualifier · J. Ortega · event page Approve Edit Reject
  • Opening ceremony Lakeshore League Meet 2 · Team 9052 · event page Approve Edit Reject
Upload links 1 live
Venue photographer Harbor Qualifier · until Nov 18

41 of 200 photos

Drawn with sample data.

One recap, three places to put it

Once the event ends, its dashboard gets a Recap tab. Write a short intro and pick up to four photos. Publishing gives the event a public recap page with the winners, the teams advancing, the awards and the numbers.

The tab draws social images, square or story sized, as PNGs or one zip. It also writes the newsletter email in plain text or HTML. A draft stays private until you publish it.

CHAMPIONS Harbor Qualifier
14231 Cedar Bots18806 Harbor Hex
1080 × 1080
Email copy Harbor Qualifier recap

Thirty-two teams, 60 qualification matches and a final that went to a third match.

Winners 14231 Cedar Bots, 18806 Harbor Hex
Advancing to the Lakeshore Championship 14231, 18806, 9052, 7788
Read the full recap with photos
Copy subjectCopy plain textCopy HTML
Drawn with sample data.

Which teams did not come back

Partners get three lists for any of the last five seasons. Lapsed teams competed the season before and have not registered. Registered, no event yet lists teams that signed up but are on no event roster. Rookies are in their first season. Retention is shown as a share of last season’s teams.

Each list exports as a CSV with the team’s city, last event, seasons competed and website.

Lapsed Competed in 2024, not registered for 2025
TeamNameCityLast eventSeasons
11745Pine Street RoboticsWestbrookHarbor Qualifier, 20244
16302GearhoundsMillportLakeshore League Meet 1, 20242
21877Static ShockCedar FallsRidgeline Qualifier, 20241
Export CSV
Drawn with sample data.

Your name on the location page

A display name, contact email, website, logo and up to six featured photos, shown as a Region partner panel on the location page of every state your region ran events in.

Region partner sample
Lakeshore FIRST Tech Challenge ftc@lakeshore.example
Drawn with sample data.

Advancement, slot by slot

For each championship your region feeds: slots filled, teams advanced, slots still to award, and the teams still in contention on an upcoming roster.

Lakeshore Championship 4 of 12 filled
  • Nov 15 Harbor Qualifier 4/4 Done
  • Nov 22 Ridgeline Qualifier 0/4 Awaiting results
  • Dec 6 Cedar Valley Qualifier 0/4 Upcoming
Drawn with sample data.

Region embeds for your own site

Upcoming events with a countdown, the advancement tracker, a photo strip, champions and a leaderboard. Paste one snippet. The dashboard counts the views.

Open the Region hub template
Region hub embed · sample
Champions Harbor Qualifier 14231 · 18806 League Meet 2 9052 · 3311
Drawn with sample data.

A bot for your state Discord server

Add the Robolyst bot to the region’s server from the Discord tab. Every event you follow gets a live thread, a digest goes out each week, and members on a roster are verified for their team. The tab lists your teams with nobody in the server yet.

What the bot does
Drawn with sample data.

Region website

For program delivery partners and the webmasters they add

A website for your region, built from blocks

Start from the Region hub kit and the site already has six pages: Home, Events, Teams, Volunteer, FAQ and Contact, written with your region’s name in them. Each page is a stack of blocks you reorder and edit in place. There is a hero, the next event with a countdown, a map of your teams, volunteer roles, an FAQ, sponsor logos and a newsletter signup, along with the blocks Robolyst team sites already use.

Choose one of seven looks for the whole site, from Classic to Brutalist, and set its accent colour. The site stays a draft until you publish it, and a preview link lets someone check it on a phone first.

Every region site gets a free is-a.team address. Connect a domain you already own, or ask for one and we register it and pay for it.

See connecticutftc.org, built this way
lakeshoreftc.org Published
Lakeshore FTC HomeEventsTeamsVolunteerFAQContact
FIRST Tech Challenge, right here in Lakeshore Students in grades 7 to 12 design, build and program a robot, then compete in alliances. View local events Get involved
Next up Harbor Qualifier Sat, Nov 15 · Westbrook High School
9 days14 hrs22 min
Look ClassicDraftingMatchdayBroadsheetScrapbookGridBrutalist
Drawn with sample data.

A page for every event, with results as they happen

Every event FIRST lists for your region gets its own page on the site, with nobody building it. Before the event it shows the date, the venue, a countdown and the volunteer link. On the day, rankings, matches, the playoff bracket and awards fill in as FIRST publishes them, and a page left open refreshes itself every minute. An event with two divisions is one page with a switch between them.

The Event info tab holds what FIRST does not publish: a description and hero photo, the day’s schedule, documents like the team packet, a contact email, how many volunteers you still need, and links for registration, volunteer sign-up and the photo album. Scrimmages and outreach days that FIRST never lists can be added by hand. Hiding an event takes it off the site and off its Robolyst page. FIRST’s record is untouched.

An event director fills in their own event from its event dashboard, so the page can be right before you get to it.

Event info Harbor Qualifier
Schedule 7:30 Team load-in and inspection9:15 Opening ceremony9:45 Qualification matches2:15 Alliance selection
Documents Team packet PDF · 1.2 MB
Volunteers still needed 12
lakeshoreftc.org/events/USLKHQ
Harbor Qualifier Live Westbrook High School · Q24 of 40
#TeamRPW-L-T
1142313.45-0-0
290523.14-1-0
377882.84-1-0
4188062.63-2-0
Refreshes every minute
Drawn with sample data.

A newsletter for the people who signed up on your site

Visitors sign up from the newsletter block on any page and choose what they want to hear about: volunteering, students and families, or coaches and teams. A list you already have comes in as a CSV.

Write the email in Markdown, add an image, and attach an event card with the date, the venue, how many days are left and a volunteer button. Send yourself a test, then send it or schedule it for later. Pick topics and the dashboard counts who it will reach before you press send. It goes out from notify@robolyst.org under your region’s name, and every copy carries a one-click unsubscribe.

Each send keeps its numbers: delivered, opens, clicks, bounces, complaints and unsubscribes. Tick one box and the email also goes into a public archive on the site.

Newsletter draft
Subject 12 volunteers short for Harbor
To VolunteeringStudents and familiesCoaches and teams 214 people
9 days away Harbor Qualifier Sat, Nov 15 · Westbrook High School Sign up to volunteer
Send me a test Schedule From notify@robolyst.org as Lakeshore FTC
Last send: kickoff recap Sep 8
1,186 Delivered642 Opens119 Clicks6 Bounces0 Complaints4 Unsubscribes
Drawn with sample data.

Sponsors, in levels you name

Add a sponsor once with its logo and link and put it in a level. Every sponsor block on the site shows it, highest level first.

Sponsors sample
Gold
Harbor MachiningLakeshore Credit Union
Silver
Cedar Valley RotaryWestbrook HardwarePine St. Dental
Drawn with sample data.

A contact form with a shared inbox

Whatever comes through the site’s contact form lands in the Messages tab. Replies go out under the region’s name, and answers come back to the region’s contact email, so no volunteer has to hand out a personal address. Spam is set aside where it cannot clutter the list.

Messages 2 open
  • Our middle school wants a team next fall Open Starting a team · D. Reyes
  • Can I judge at Ridgeline? Replied Volunteering · M. Chen
  • Is the Harbor gym wheelchair accessible? Open Events · K. Patel
Drawn with sample data.

A Webmaster role for whoever runs the site

Give a volunteer the Webmaster role from the Team tab. They get the site, Event info, the newsletter, sponsors and messages. Event dashboards, retention lists and access grants stay closed to them.

Webmaster role
  • Website and domain
  • Event info
  • Newsletter
  • Sponsors
  • Messages
  • Event dashboards
  • Retention lists
  • Access grants
Drawn with sample data.

Access

Granted by hand, to an email, for one region

Access by email, scoped to your region

Access is a grant on an email address for one FIRST region code. It can be set up before you have a Robolyst account. Sign in with that address and everything on this page opens for your region.

There are two roles. A program delivery partner sees every event in the region, plus the team lists, the location page and the region embeds. An event director lands on the dashboard for their own event. The region dashboard shows them that event and nothing else in the region. Either one adds the volunteers who work the day, each with a role of their own.

Past those two, a partner can hand out narrower region roles from the Team tab: Webmaster for the website, Event lead for every event dashboard, Photo moderator for the queue, or a role of their own built from the same permissions.

Volunteers sign in with their own account. Add them by email from the event dashboard, or show a join code at check-in. Each one gets a role, sees only that event, and loses access seven days after it ends. You can revoke it sooner.

A grant lasts until September 1 after the season and can be revoked at any time. Every action taken from the dashboard, or through one of its links, is written to an audit log for the region.

Who can do what

ToolProgram delivery partnerEvent directorEvent staff
Region overviewEvery eventTheir event
Event dashboard: staff, queue and inspectionBy role
Pit signs, coverage and usage logBy role
Photo queue and upload linksBy role
Feature a photo
Pit displays and the tickerBy role
Recaps
Advancement
Retention lists and CSV
Location page partner panel
Region embeds
Region website and domain
Event info for the websiteEvery eventTheir eventBy role
Newsletter, sponsors and messages

An event director's rows cover their own event. Event staff see the tools their role allows, for the one event they work.

Request access

Choose your role and region and list your events. Access is granted by hand to the email you enter, and we reply there once it is set up.