Robolyst Robolyst
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.

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
3/5
  • Robot weighed and inspected
  • Charged battery in, strap tight
  • Driver station on the field wifi
  • Auto path selected for this alliance
  • Spare batteries on the cart ×6
started itself 15 min before the match ticks queue with no signal

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
  • Comments 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 a phone calendar so it shows up where people actually look.

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.

Notifications people don’t hate

Per-event, per-channel notification settings: in-app, email or a Discord webhook. Teams already living in Discord can pipe announcements, task changes and competition results there without anyone remembering to post them.

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.

Tasks and schedule is one part of the portal.

The roster, the build schedule, the notebook, the money and your public site run on the same free account. Setting it up takes an afternoon.