Maryland FIRST RoboticsHow to organize a robotics showcase for local Maryland legislators
A robotics showcase gives Maryland legislators a direct view of youth engineering, not merely a polished robot demonstration. The strongest events pair an engaging exhibit with a precise civic purpose: showing how local students learn, identifying barriers to participation, and making a realistic request for support.
For Australian readers, the Maryland setting can feel unfamiliar because legislative responsibility is divided among federal, state and local bodies. The same planning discipline transfers well, however: identify the decision-maker, frame the request clearly, and make every technical detail accessible to someone who has never programmed a robot.
Begin with three intended outcomes: increased awareness of FIRST programs, a better understanding of STEM workforce needs, and at least one follow-up action involving funding, mentoring, legislation or school access. An event without a defined outcome may generate warm applause but no durable commitment.
The tone should be welcoming, non-partisan and evidence-led. Students should be treated as capable presenters, while adults handle logistics, safety and documentation. Maryland FIRST, the nonprofit operational partner for FIRST in Maryland, supports teams for ages 4 to 18, so the event can connect hands-on LEGO-based learning with advanced competition when age groups are linked thoughtfully.
Set a civic purpose that fits the program
First, write a one-page brief naming the audience, two or three key messages and the decision you want the visitors to consider. A useful request is specific: support for regional teacher training, a competitive robotics grant, accessible workshop space or a meeting with education officials. Avoid asking legislators to endorse one team or one commercial product.
Then map local stakeholders. Include the relevant Maryland General Assembly members, county council or education-board representatives, and officials connected with economic development or workforce planning. Program leads can coordinate through Maryland FIRST Robotics, which supports the statewide FIRST network and can help connect outreach to teams, mentors and volunteers.
Build a timeline around real-world calendars
Work backwards from the event date, allowing ten to twelve weeks for invitations, sponsor confirmation, robot preparation and rehearsals. Assign one owner to every task, keep a shared budget, and set firm deadlines for receiving bios, consent forms, accessibility information and final demonstration requirements. Hold a short planning call each week rather than relying on scattered messages.
Check the Maryland General Assembly calendar and each invited officeholder’s schedule before fixing the date. Australian calendars add another layer: many families travel during the December-to-February school holiday period, and public holidays can affect interstate or international guests. If Australian students are visiting, avoid the busiest holiday weeks and build in a buffer for jet lag, weather and changed school timetables.
Create a one-page run sheet covering arrival, parking, room setup, robot transport, demonstrations, questions, emergency contacts and teardown. Rehearse the transitions as well as the demonstrations. A backup activity using a recorded robot run, a LEGO hand-off challenge or a design display protects the programme if a mechanism fails on the day.
Invite decision-makers with a personal purpose
Build the guest list from the civic purpose, not from a generic mailing list. Research each candidate’s education, technology, manufacturing, youth or regional-development interests, then send a short invitation that references the local team and explains what the visitor will see and decide. Personalised invitations are more likely to be accepted and forwarded.
Australian audiences should keep the levels of government distinct. Parliament House in Canberra represents the federal Parliament, state MPs act in state parliaments, and councils govern local areas; Maryland’s state legislators similarly operate alongside county and municipal governments. Invitations should therefore identify the exact office, committee or portfolio being sought, including whether the ask concerns state funding, local implementation or future legislation.
Prepare a simple ground rule: disagreement may be direct, but it must remain respectful of people. For facilitator training, a framework for respectful exchange illustrates why clear listening and response rules matter, although its focus is Jewish dialogue in Israel rather than youth robotics. Give students a short briefing on handling tough questions without improvising hostile answers.
Turn the robots into a clear civic story
Organise the floor into short, guided stations. One team can explain drivetrain design, another coding and sensors, a third safety testing, and a fourth the customer or community need behind the project. Include younger FIRST LEGO League or Jr.FLL teams so officials can see how engineering interest develops over time, then use FIRST Tech Challenge or FIRST Robotics Competition robots to show advanced prototyping and teamwork.
Give each visitor a three-minute journey: watch a demonstration, hear a student explain one design choice, and see one measured result such as task completion time, obstacle distance or repeated reliability across trials. Explain why the design changed, not merely which parts were used. A visible iteration often communicates engineering judgement better than a long technical speech.
Australian organisers will recognise community centres, public libraries and school halls as practical venue types. A Maryland equivalent should offer step-free access, reliable internet, power for charging, safe robot transport and a quiet room for guests with sensory needs. Australian speech is often relaxed, so a brief “have a yarn” before formal remarks can help overseas visitors settle in, while printed speaker notes keep the programme itself disciplined.
Secure sponsorship, mentors and practical support
Start with a budget based on real figures: venue hire, equipment transport, printing, insurance, accessibility, catering, photography and contingency. Seek in-kind support from local engineering firms, universities, community colleges, makerspaces and retailers before assuming every cost will be paid in cash. Mentor volunteers can supervise students, check machines and keep visitors moving, protecting the students’ presentation time.
Australian companies often assess community grants through measurable impact, tax invoices and brand visibility. If an Australian business considers supporting a Maryland event or an exchange delegation, finance teams should review foreign-payment, GST and exchange-rate implications first. Keep sponsorship promises modest and documented, and separate philanthropic support from any commercial display so the event remains credible with public officials.
Use media to extend the conversation
Issue a concise media brief before the event and a short report afterwards. The Maryland FIRST guide to drafting a press release is a useful starting point for turning a student achievement into a community story. Include verified numbers, a strong quotation from a student, named partners and one clear request; avoid jargon and unsupported claims.
Public invitations should state the purpose, schedule, accessibility arrangements and how to register. In Australian cities such as Sydney and Melbourne, multilingual outreach is often essential for broad participation, so Maryland organisers can likewise work with libraries, schools and community associations to reach families beyond existing robotics circles. Obtain consent before using children’s photographs or names.
The communication plan can be organised around three moments:
| Stage | Main audience | Core message | Evidence to retain |
|---|---|---|---|
| Before | Officials, sponsors, families | The event connects local learning with community needs | Confirmations, registrations and media replies |
| During | Visitors, students and partners | Students apply engineering through teamwork and iteration | Attendance, demonstration results and consented images |
| After | Offices, sponsors and the public | Specific support can expand STEM access | Meeting notes, commitments, survey responses and a named follow-up owner |
Run the day for trust and measurable follow-through
On the day, use a clear check-in desk, named room hosts, a scheduled microphone check and separate arrival and departure routes for equipment. Give every volunteer the same short briefing, including pronunciation names, accessibility priorities and the correct response if a robot behaves unexpectedly. Record attendance and note each visitor’s comments, but do not treat photographs as a substitute for evaluation.
Measure more than foot traffic. Count student presentations, officials attending, relevant community partners and concrete commitments, then conduct a brief survey with visitors and participating families. A two-week follow-up meeting should confirm which questions require a written response and who will deliver it. This turns a positive visit into an accountable civic relationship.
Actions for a memorable showcase
- Put one clear, publicly beneficial request on every invitation and sign.
- Let students explain design choices while volunteers handle technical support.
- Ask visitors for one specific action, then assign an owner and deadline.
- Send personalised thanks with photographs, results and the promised next step.
Start with a 60-minute planning session this week. Confirm the date, assign the civic-purpose owner, shortlist ten invitees and begin sponsor outreach; a focused team can turn one public robotics event into a durable partnership with Maryland decision-makers.