How to Recruit FRC Team Members (and Actually Keep Them)

Most teams don't actually lose members during build season. They lose them in the three or four months before it even starts, the gap between the club fair sign-up sheet in September and the robot actually needing hands in January. If your roster looks thin by winter break, the fix isn't a better pitch at the fair. It's what happens in the first ten minutes of the first meeting, and what you hand a new member to do before they leave it.

Club fair tactics that actually convert sign-ups

A robot sitting still on a table is furniture. A robot doing something, an intake spinning, a drivetrain doing slow circles on the ground in front of your booth, is what actually stops foot traffic. If you're bringing last year's robot or a practice chassis, run it. Let people drive it if you can supervise safely: someone who got to hold the controller for thirty seconds is far more likely to show up to the first meeting than someone who watched from six feet away.

Staff the booth with students, not just a mentor. FIRST's own Robotics Competition Mentor Guide says it directly in its Team Recruitment section: "Students are more likely to be interested in participating if they see and hear from their peers." An adult explaining what FRC is reads like a pitch. A sophomore explaining why they stayed reads like an invitation.

Freshmen and sophomores are worth targeting specifically. Chief Delphi threads on recruiting students describe the same logic over and over: underclassmen haven't locked themselves into other clubs yet, and you get more seasons out of them before they graduate. Cross-recruiting from adjacent programs, math team, marching band, other STEM clubs, comes up often too. Members of those groups already show up early and show up on time, and that habit carries straight over to a robotics team.

Whatever sign-up method you use, get real contact info on the spot, a phone number or an Instagram handle, not just a school email nobody checks. Then actually reach out within a day or two with the date, time, and room for the first meeting. A booth conversation with no follow-up is a wasted conversation.

Stack the fair with the other channels the Mentor Guide lists: posters around the school and in local businesses (FIRST has flyer templates on its Team Management webpage), a mention in the school newsletter, and a short assembly presentation with a video and a live demo if your school allows it.

A first meeting that doesn't scare people off

Don't open meeting one with 45 minutes on the org chart, the season calendar, and the safety rules. That's the fastest way to lose someone who came in curious. Spend the first ten or fifteen minutes on a walk-through of the shop with real parts and last year's robot in front of them, then get their hands on something immediately: stripping wire, a short CAD exercise, sorting the parts bin. People come back for what they got to touch, not for what they got told.

Keep the scope small on purpose. Nobody needs the entire season, the subteam structure, and the full competition schedule in one sitting. Cover what they need for this week and let the rest come later. Before anyone leaves, collect their contact info and a rough sense of which subteam interests them, so the very next meeting isn't a cold restart.

One more thing worth knowing if you're the mentor running that first meeting: FIRST's Youth Protection Program strongly recommends against any single adult being alone with youth participants, and the Safety Manual expects mentors to lead by example on safety from day one. Have at least one other adult or an experienced student in the room.

Give rookies real work in week one

The biggest reason rookies vanish by their third meeting is that nobody gave them a job. "Go find something to do" is not a job.

You can't hand a freshman a band saw solo on day one, and you shouldn't try to. The Safety Manual is explicit that anyone operating shop equipment needs "both the knowledge and experience to operate shop equipment safely," and it bars gloves near rotating machinery like drill presses and band saws specifically because they can get pulled in. That's a real constraint, not an excuse to sideline someone for a month.

It's also not the whole picture. FIRST's own Guided Experience training, a free 12-module course built for onboarding new members, has a whole module for exactly this problem. Module 4, "Fabrication Tools and Safety," walks new members through a safety quiz, a guided tour of the shop's tools, and then a team activity where they actually build something: a battery cart, using the tool training they just got. That's the model worth copying even if you don't use the official course: pair the safety orientation with an actual, tangible build on day one, not a lecture with no output.

Beyond that, a brand-new member can do real work immediately under the same safety rules: label and inventory the parts bin, strip and crimp wire on a practice board under supervision, run a CAD tutorial, build out a scouting spreadsheet, or shadow a veteran on the drivetrain while wearing the same ANSI-rated safety glasses and closed-toe shoes everyone else has on. None of it requires solo power tool access, and all of it is a real contribution a rookie can point to by the end of the meeting.

Pair every rookie with a specific veteran by name before they leave. The Mentor Guide calls this out by name as one of the best ways to run extra team training: partnering rookie and veteran students so new members always have someone specific to learn from, instead of a general invitation to ask questions of whoever's nearby.

Why teams lose members by December

Here's the part most teams get backwards: the drop-off usually isn't a build season problem. Build season, the stretch from Kickoff through your first event, is when a team is at its most hands-on and most obviously worth showing up for. The danger zone is the three or four months before that, September through December, when a rookie who signed up at the club fair is waiting for the robot to start and mostly getting administrative meetings instead.

Look at what FIRST's own season calendar in the Mentor Guide actually lists for that stretch. September is recruiting and a team safety meeting. October is inventory, tool prep, and early award submissions. November is signup deadlines, event registration, and event payment. December is finalizing shop hours, kickoff plans, and pre-season purchasing, and for teams that plan ahead, a mock kickoff to rehearse the format before the real one, which is also its own lesson in the Guided Experience course. Almost none of that is robot-building, because build season doesn't officially start until Kickoff in January (see the 2027 season calendar for the exact date). If the only thing a new member experienced between September and December was two hours of paperwork talk and a bake sale, they had no reason built in to come back for January.

Chief Delphi threads on team recruitment and retention describe the fix consistently: give the fall its own payoff instead of treating it as dead time before the "real" season starts. Running last year's robot at a nearby offseason event, or letting rookies rebuild and drive an old robot, gives new members something concrete to work toward before winter break. Teams that skip this and go quiet from September to January are the ones whose fall rookies simply don't show up again once Kickoff arrives. For the fuller playbook on what to do with that stretch, see the LearnFRC offseason guide.

One separate, bigger risk worth naming: long-running Chief Delphi threads on teams that folded outright point to the same root cause again and again, a key mentor or teacher leaving, not a shortage of student sign-ups. That's a mentor pipeline problem, and it deserves its own plan rather than getting lumped in with a thin roster of students.

The takeaway

Recruiting gets people to show up once. Retention is a September-through-December decision, not a January one. Run a robot that moves at the club fair, keep the first meeting short and hands-on, hand every rookie a named task and a named partner before they leave it, and give the fall semester a real, tangible payoff instead of three months of waiting for Kickoff. Do those four things and most of your December attrition disappears before it starts.