Maryland FIRST RoboticsCreating a diversity and inclusion plan for a Maryland robotics team
Robotics teams are strongest when the people building, programming and competing reflect the communities their events serve. A diversity and inclusion plan for a Maryland team should turn that ambition into changes in who joins, who stays, who leads and how success is shared. The Maryland FIRST network is a useful starting point, supporting FIRST Robotics Competition, FIRST Tech Challenge, FIRST LEGO League and Jr.FLL opportunities across Maryland.
The plan should do more than recruit new members. It should improve access, belonging, voice and recognition while reducing financial, physical, cultural and scheduling barriers. That means welcoming students with disability, neurodivergent learners, multilingual families and young people from different socioeconomic and cultural backgrounds. Ask participants about their experience instead of assuming what they need.
Australian readers will recognise some parallel pressures. Melbourne, Brisbane and regional New South Wales have different travel, school and community conditions, while rural teams may have fewer engineers nearby. Everyday phrases such as “fair go” and “have a go” express opportunity and initiative, but teams should still explain arrangements plainly rather than rely on shared assumptions. Funding commonly combines school support, community grants, not-for-profit fundraising, corporate sponsorship and volunteer labour.
A strong plan therefore joins community outreach to everyday team operations: recruitment, onboarding, mentoring, competition preparation, leadership, sponsor recognition and measurement. Give each action an owner, deadline and budget, and let students help decide what should change. A seasonal document is useful, but a reviewed cycle is better because teams, schools and event needs change throughout the year.
Map barriers and set measurable aims
Begin with a listening and access audit. Ask current members, families, mentors and prospective students what makes participation easy or difficult. Review application sources, drop-off points, travel or kit costs, role allocation, leadership patterns and whether members feel safe speaking up. Use anonymous surveys, collect only necessary demographic information and explain who can see the results.
Turn findings into two or three measurable aims, such as recruiting beyond one school, improving retention after the first event, or distributing technical and leadership roles more evenly. Record a baseline, define the desired change and do not treat one demographic figure as proof of success. Belonging and access need their own evidence.
- Hold an anonymous access and belonging survey before registration closes.
- Map the schools, community groups and referral routes producing applicants.
- Give every goal a student owner, mentor supporter, deadline and measure.
- Reserve budget for transport, kit access, accessibility and uniform support.
Complete these actions before the season fills with urgent build tasks. Name each barrier, check the evidence and assign resources. Review at the first monthly meeting, and let students revise aims that do not match participant feedback.
Compare barriers with practical responses
A practical comparison turns broad concerns into specific, accountable actions. Match each barrier with an observable sign and a response that can be checked.
| Barrier | Observable sign | Practical response |
|---|---|---|
| Cost or transport | Families hesitate when fees, travel or uniform costs are unclear | Publish costs early, offer waivers and travel support, then check uptake |
| Narrow role models | Leadership and technical roles stay with one group | Rotate build roles and pair newcomers with experienced peers |
| Weak belonging | Members feel dismissed, isolated or judged for asking questions | Co-create norms, assign buddies and use structured feedback |
| Accessibility | Instructions, tools or venues are hard to access | Provide captioned materials, accessible workstations, flexible breaks and individual plans |
| Limited local networks | Regional members have few nearby mentors or clubs | Build remote mentoring, regional hubs and school partnerships |
Responses often overlap. A student who lives far from an event, uses a mobility device and does not see peers like them faces more than one barrier; a single response may miss that interaction. Combine financial help with flexible participation, accessible communication with student choice, and new-member support with meaningful roles. Measure the combined change, not merely whether it was offered.
For an Australian adaptation, local Aboriginal and Torres Strait Islander organisations should lead cultural engagement in their communities, with proper resourcing and no recruitment shortcut. A regional Queensland team may need remote mentoring before a city team does. Local realities should set priorities while the method remains consistent.
Widen access through outreach and recruitment
Recruitment is stronger when it reaches beyond students who already fit the typical builder stereotype. Work with libraries, makerspaces, youth clubs, teachers, disability networks and family groups. Describe robotics through engineering, design, art, data, teamwork and problem-solving. The community orientation of Chattanooga library friends also demonstrates the value of connecting robotics with trusted local services rather than recruiting in isolation.
Turn interest into a low-pressure pathway: an open build afternoon, beginner programming session, mentor introduction and clear information about costs and support. Let families meet the team without an application form. In Australia, partnerships with councils, TAFE or university engineering clubs can widen pathways, while regional hubs and online mentoring can reduce travel barriers.
Make selection and onboarding transparent. Explain the time commitment, provide shared tools and accessible materials, and pair each newcomer with a peer. Ask invitees what would help them participate rather than assuming motivation can overcome cost, transport or confidence. Track applications by source and adjust outreach accordingly.
Build an inclusive culture on the robot
Culture comes from repeated behaviour, not a statement posted in the workshop. Co-create a code of conduct covering respect, stereotypes, accessibility, photography, conflict and safe reporting. Rotate responsibility for design reviews, notebooks, programming, driving and presentations so students can try different roles without being typecast. Student-led reviews can reveal who speaks, who is interrupted and who receives praise.
Design meetings and events for different needs. Offer written and visual instructions, captions or interpreters, accessible tools and seating, quiet areas, flexible rest periods and alternatives to live demonstrations. Agree adjustments with students instead of making broad assumptions about disability. Keep medical, sensory and cultural requirements private unless permission is given.
Recognise the invisible work of organising, documenting, welcoming and mentoring. Let students choose how their names and achievements appear, use correct names and pronouns, and celebrate progress without casting one person as an inspiration. Follow major events with a quick belonging check and act on the feedback.
Align mentors, volunteers and sponsors
Mentors and volunteers set expectations students notice. Recruit for communication, curiosity and reliability as well as technical skill, then train them in inclusive practice, disability awareness, cultural humility, safeguarding and conflict resolution. Give mentors a shared feedback method so a nervous beginner is not dismissed as lacking commitment. Students should be able to request another mentor when trust is not working.
Include sponsors without giving them control over students or culture. When seeking Australian partners, point to community grants, school fundraising and corporate sponsorship markets, and ask which access outcomes they will fund. Useful support includes travel bursaries, accessible equipment, outreach places and long-term mentor training rather than only premium robot parts. Recognition can reflect these contributions.
Assign a rotating inclusion lead supported by a parent or mentor, while keeping student voice central. Volunteers, families and sponsors should follow the same team agreements. Check whether access measures, leadership distribution and retention show progress. Anyone who repeatedly undermines the plan should face the same accountability process as any other team member.
Review, report and sustain the plan
Use a short review cycle rather than waiting until the season ends. At 30, 60 and 90 days, check application reach, retention, role distribution, leadership access, participation and survey comments. Report what changed, what did not and the next action. Share results in plain language and invite anonymous feedback, while avoiding unnecessary collection of sensitive information.
Treat setbacks as information. If a goal is missed, identify whether the barrier was cost, timing, communication, facilities or team behaviour, then test one adjustment at a time. Record decisions in meeting minutes and assign responsibility. The plan should evolve through evidence while retaining its commitments to access, equity and student agency.
Start this week by holding one student listening session and choosing a measurable barrier to change. For Maryland program guidance, mentor resources, event information or help connecting with the statewide robotics community, contact Maryland FIRST. Then publish the first action, deadline and review date so the whole team knows what happens next.