Maryland FIRST RoboticsHow to start a robotics team at a Title I school in Maryland
A robotics team can make STEM learning more accessible at a Maryland Title I school while giving students a reason to solve problems together. The first version need not be large or expensive. It needs curious students, an adult mentor with time, and a school leader who can connect the activity to student priorities. A clear plan also tells families what commitment, costs and support are involved.
Title I designation brings federal support for eligible school needs under the Every Student Succeeds Act, but it does not automatically fund a robotics programme or make every purchase allowable. The district’s finance team, curriculum office and Title I coordinator should confirm how a proposal fits the school’s plan. With that alignment, robotics can support STEM access, engagement and learning goals; without it, a well-intentioned club may struggle to survive the school year.
Build a case the school can support
Begin with a meeting involving the principal or delegate, a teacher, the Title I coordinator, a parent or caregiver, and one student. Ask what the school wants to improve, which students need more access to engineering, and how an activity will be supervised. A one-page proposal can describe the learning purpose, participants, meeting frequency, adult roles, likely costs and evidence of student benefit. That is stronger than a general request for a robot.
Check the district’s rules before naming vendors or promising equipment. Costs may need to run through purchasing, a purchasing card or a school account; others may be eligible for a grant or sponsorship, while extracurricular purchases require especially careful review. Maryland FIRST can guide teams on starting, mentoring, coaching and volunteer roles, while the school handles approvals and safeguarding. If the team wants engineering briefs to support reading and communication, Bookert’s education resources can be investigated alongside classroom literacy goals.
Choose the FIRST pathway that fits
As the nonprofit operational partner for FIRST in Maryland, Maryland FIRST supports FIRST Robotics Competition, FIRST Tech Challenge, FIRST LEGO League and Jr.FLL for students from about age four to eighteen. Match the programme to students’ ages, available mentors, equipment and desired challenge rather than competition size. Younger learners may begin with Jr.FLL or FIRST LEGO League; older students may be ready for FIRST Tech Challenge or FIRST Robotics Competition. Check current season requirements and regional offerings before choosing.
This comparison starts a school conversation; it is not a promise of cost or placement. A smaller platform can make engineering and programming easier to teach, while a full competition team offers deeper fabrication and project management. Either path can build belonging, persistence and communication.
| Programme | Student fit | Main build focus | Support to plan early |
|---|---|---|---|
| FIRST Robotics Competition | Older students, usually grades 7–12 | Full-size competitive robot, strategy and team engineering | Experienced mentors, workshop access and transport to events |
| FIRST Tech Challenge | Older students, usually grades 7–12 | Smaller robot, software and iterative design | Computing or mentoring support and a smaller parts inventory |
| FIRST LEGO League | Elementary and middle-school students | LEGO-based robot, programming and core engineering concepts | Shared equipment, adult facilitation and age-appropriate event tasks |
| Jr.FLL | Younger learners | Simple models, teamwork and early STEM habits | Playful sessions, family participation and close adult guidance |
Whichever pathway is chosen, run a small pilot first: six to eight students, one or two mentors and one meeting time protected for a full term. Let the pilot reveal which tools, adult skills and student supports are genuinely needed before the team orders a complete season of materials.
Plan a first season that can survive school reality
Work backwards from the first event. Identify registration and kit deadlines, practice dates, venue and travel time. Include weekly build sessions, safety training, family information, fundraising and reflection in the calendar. Maryland schools commonly start in August or September, with competitions later in the year. Many Australian schools begin in January or February, so a comparable launch may belong at the start of Term 1, with fundraising beginning over the previous holiday.
The budget should show more than a kit: registration and event fees, parts, tools, software, travel, meals, accessibility supports, replacement equipment and contingency. Seek specific contributions from the parent association, foundations, businesses, alumni and community groups. The Maryland FIRST grant writing guidance helps teams present a clear budget, timeline and student benefit to a sponsor or funder.
Assign responsibilities early. One adult can coordinate administration, another technical instruction, and families can share transport, event support and equipment care. Give every student a role in design, build, programming, documentation or outreach. Maintain a roster, emergency procedures and a plan for missed sessions; a calm, organised meeting is more valuable than a large unsupported group.
Keep access and inclusion at the centre
A Title I setting makes affordability and participation central. Offer shared laptops, team shirts and basic materials so appearance does not determine belonging, and make the first session useful to students with no coding experience. Avoid requiring families to buy personal kits unless a grant covers them. Include transportation, meal support and accessible event arrangements in the funding request where possible.
For older students wanting a technical pathway without the scale of full FIRST Robotics Competition, FIRST Tech Challenge offers iterative design, software and team problem solving. It is a useful route when a school needs clear information about the current programme, registration and event pathway. Pair technical mentoring with a teacher who connects the work to mathematics, computing and school priorities.
Australian readers may recognise much of this planning model. Melbourne, Sydney, Brisbane and Canberra have school communities, makerspaces and businesses that can supply mentors or sponsors, while regional and remote schools often rely on remote mentoring and shipped parts. Local conversations turn on a “parent roster”, “signing the permission form” and fundraising through a “sausage sizzle”. Councils and community foundations can be approached much as a Maryland team approaches a county education foundation. These parallels help, but calendars, funding rules and safeguarding expectations still need local checking.
Use events to learn, recruit and sustain
Treat the first competition as a working session with learning goals, not a final test of worth. Students can record what the robot did, what changed between trials and where a teammate improved the design. Invite families and younger students to a school demonstration, then explain how the event supports the next grant. A design log gives stronger evidence of learning than a trophy photograph.
Recruit mentors as a community rather than relying on one expert. A university student, local engineer, teacher, tradesperson and FIRST alumnus can contribute different skills. Give mentors a role description, contact and schedule, and complete the school’s safeguarding and training requirements. Give sponsors a brief covering students served, learning goals, budget and recognition; clear expectations protect relationships and help renewals.
Measure the programme before expanding it. Track attendance, retention, student leadership, skills demonstrated, mentor hours, costs and feedback from families and teachers. A successful first year may mean a stable meeting, a small competition roster and a second cohort of mentors, not a large robot. Use those records to request renewed Title I consideration where allowable, a new grant and a place on the district’s annual activity calendar.
The most useful first step is a 30-minute meeting with a school leader, a teacher, one student, one family member and one potential mentor. Leave with a chosen age pathway, meeting time, safeguarding plan and list of costs to verify. Run a six-week pilot, gather evidence and decide whether the team is ready for a full season.
Contact Maryland FIRST for team-starting resources, mentoring information, programme guidance, volunteering opportunities and current competition and event details. Set the first meeting, invite one student, one family member and one mentor, and begin with a small, well-supported pilot designed to grow into a lasting programme.