Is this just another Trello?

It is the same idea with the season built in: competition dates arrive on their own, tasks carry subsystems, and checklists know they get run at a venue with bad wifi.

Does the checklist work without signal?

Yes. Runs queue locally and sync when the connection comes back, which is the only way a pit checklist is useful.

Can we use it on a phone?

Yes. The whole portal is built for a phone first, because that is what people have in their hands mid-competition.

Why is outreach in here and not with the website?

Because it is work, and work belongs where the rest of the season is planned. An outreach event is a meeting on the same calendar, it can carry tasks, and the log hangs off it. The public site is where you show outreach off; this is where you do it.

What counts as one person reached?

That is your call, and the four channels exist so you never have to make one number carry two meanings. Someone you stood in front of is counted in person. A video play is a view. A newspaper reports its own circulation. A kit has a recipient. Nothing is summed across channels, so a judge reading your submission sees what each figure actually is.

Do the tag suggestions send our data somewhere?

Smart tagging is one switch in team settings, and it is the only thing on this page that calls a model. It sends the title and body of the thing being tagged to Google’s Gemini API on our paid account, and gets back labels picked from your team’s own list. It can never invent a tag, it proposes instead of applying, and it is not allowed near money, cards, member records or your public site. Turn it off and everything else here works the same. The full account of what goes where is on our transparency page.

The whole toolkit What is due, who has it, and what it blocks

Tasks and schedule

Build season fails in the same place every year, not in the CAD, but in the gap between “someone said they would do it” and the night before the qualifier. Tasks, schedule and checklists exist to close that gap.

Try it in the live demo

Free for every team · run by a 501(c)(3)

The blocking chain and the checklist that runs itself, as the portal shows them.

Intake redesign: the blocking chain sample

Machine new intake rollers Intake
Maya R. · due Thu · In Progress
Mount intake to chassis Chassis Blocked by Machine new intake rollers
Build subteam · due Sat · Not Started
Tune the intake handoff in auto Autonomous Blocked by Mount intake to chassis
Devon K. · due Mon · Not Started

Move the first bar on the timeline and the two behind it move with it.

Pre-match checklist — Q31, red alliance sample

Q31 run 3/5

Robot weighed and inspected

Charged battery in, strap tight

Driver station on the field wifi

Auto path selected for this alliance

6× Spare batteries on the cart

started itself 15 min before the match ticks queue with no signal

On screen

The page itself, captured out of the live demo, which anyone can open, without an account.

Open it yourself

Robolyst FTC task board: build-season tasks in Not Started, In Progress, Complete and Cancelled columns, each card tagged by subsystem with a priority, due date and assignee. — The task board, with every card tagged by subsystem and owner.

What teams say

This might be the greatest website our team has ever randomly stumbled upon, its completely changed the way we communicate, setup and record events 10/10

FTC #34228

Cardboard Engineering

Every testimony

One set of work, three views

The same tasks render as a list, a kanban board or a timeline. Students who think in deadlines and mentors who think in dependencies are looking at the same data, not two competing trackers.

Custom statuses per team, so the board matches how you actually work
Dependencies: mark what blocks what, and see the chain before it bites
Tags, subsystems and assignees, with filters across all three views, and a filter you keep rebuilding can be saved
Tags and a subsystem are suggested from the title as you save, so a task filed in a hurry is still filed
Comments with @mentions and an activity trail on every task

A schedule that includes competition

Meetings and competitions live on one calendar, and your events sync from FIRST automatically. You do not type in a qualifier date and then discover it moved.

Subscribe from Apple Calendar, Google Calendar or Outlook and every change follows on its own
Import the school or shop calendar you are already stuck with, and see the clashes before you schedule around them
Recurring meetings you can cancel one week of without unpicking the series
RSVPs and attendance are separate columns, because who said they were coming is not who turned up
Tasks due that day ride on the meeting, so a build session opens with its own agenda

Checklists that run

Pit checklists, pre-match checks and inspection prep are templates you run, not documents you re-copy. A run records who ticked what and what got missed, and works offline for the half of a competition venue where the wifi does not.

Outreach, counted while you remember it

Demos, workshops, camps, media coverage and the kits you gave away are logged against the season the week they happen. Come award season the number is a query, not an archaeology project through a year of camera roll.

Four kinds of reach kept apart: in person, digital, media, and donations. A newspaper’s circulation and thirty kids in a room never add up to one figure
In-person reach breaks down by audience: elementary, middle, high school, adults, educators, other FIRST teams, or your own
Partners you go back to every year, with their contacts, how often they host and how much notice they need
Next season sketched out as plans with target dates and the reach you expect
An outreach event on the calendar carries its own log, so the meeting and the number are one record
Tag a log with the award it supports and the submission is written out of what you already entered

Notifications people don’t hate

Every event has its own channels: the bell in the app, email, a push to a phone, or a webhook into the channel your team already reads. Teams living in Discord or Slack can pipe announcements, task changes and competition results there without anyone remembering to post them.

Team-wide defaults first, then every member overrides their own
Anything set to email can roll into one digest a day instead of arriving one at a time
Quiet hours stop a phone buzzing overnight and leave the bell and the email alone
Push works on a phone with the site saved to the home screen. No app store

Questions teams ask

Is this just another Trello?: It is the same idea with the season built in: competition dates arrive on their own, tasks carry subsystems, and checklists know they get run at a venue with bad wifi.
Does the checklist work without signal?: Yes. Runs queue locally and sync when the connection comes back, which is the only way a pit checklist is useful.
Can we use it on a phone?: Yes. The whole portal is built for a phone first, because that is what people have in their hands mid-competition.
Why is outreach in here and not with the website?: Because it is work, and work belongs where the rest of the season is planned. An outreach event is a meeting on the same calendar, it can carry tasks, and the log hangs off it. The public site is where you show outreach off; this is where you do it.
What counts as one person reached?: That is your call, and the four channels exist so you never have to make one number carry two meanings. Someone you stood in front of is counted in person. A video play is a view. A newspaper reports its own circulation. A kit has a recipient. Nothing is summed across channels, so a judge reading your submission sees what each figure actually is.
Do the tag suggestions send our data somewhere?: Smart tagging is one switch in team settings, and it is the only thing on this page that calls a model. It sends the title and body of the thing being tagged to Google’s Gemini API on our paid account, and gets back labels picked from your team’s own list. It can never invent a tag, it proposes instead of applying, and it is not allowed near money, cards, member records or your public site. Turn it off and everything else here works the same. The full account of what goes where is on our transparency page.

The rest of the toolkit