Everything the team uses to run itself, in one place.
This page is for the team. Ask a lead if you do not have the passcode.
That passcode did not match. Try again.
Everything behind this page has its own login as well. Nothing secret is stored here.
Email your forms in. Consent and release forms have to be signed and on file before you can compete, and they are what holds people up every single year. Sign them in the FIRST Dashboard, then send anything on paper to the team email. Do it the day you get them, not the week of the tournament.
Links that are not set up yet show as unavailable rather than sending you nowhere.
The calendar below is the same one on the public calendar page, and it is the source of truth. If it is not on there, it is not happening.
Times come from what students picked on the interest form. Once they are fixed they go on the calendar, and any change gets posted in Discord first.
Not fixed yet. The standing days and times land here, and on the calendar, as soon as they are.
Qualifiers run December through March, almost always Saturdays and mostly east of Worcester. Plan on the whole day, early call time through the evening.
Dates get added as FIRST publishes them.
Kickoff is September 12, 2026. Event registration closes weeks ahead of each qualifier, and consent forms have to be in before a student can be on the field.
Miss those and no amount of robot fixes it.
Make the team calendar public in Google Calendar, then paste its embed URL into
calendar.embedUrl in assets/js/config.js. It fills in here and on
the public calendar page at the same time.
Not a rule, but it is the order that wastes the least material and the least time.
Strategy first, against what the game actually scores. Arguing on paper is free. Arguing in aluminium is not.
CAD the mechanism before anything gets cut or printed. Onshape runs in a browser and is free for students, so there is nothing to install and nothing to lose.
Cut, print, assemble, wire. Check the inventory before ordering anything, because we usually already own it.
The robot code is our copy of the FTC SDK, on GitHub. Clone it, open the folder in VS Code, and commit as you go: small commits, real messages, on a branch rather than straight onto main.
Drive it, break it, measure it. Then put the decision and the numbers in the engineering notebook in the team Drive while you still remember why you made them. Judges read that notebook, and it is how the Inspire Award gets won.
All free. Onshape needs no install at all, and you do not need every one of these on day one.
The one worth ten minutes before your first meeting.
Setting this up: on YouTube hit Share → Embed, copy the
src="…" URL (it looks like youtube.com/embed/…) and
paste it into portal.videoEmbedUrl in assets/js/config.js.
Quick jumps to the pages everyone else sees.
The passcode is a speed bump, not a lock. This page stays out of search results and the passcode keeps it out of casual view, but a determined person could still read these links out of the page source. Every tool behind them has its own login. Keep passwords, personal details, and anything genuinely sensitive off this page.