Emily Huddleston
Robotics Club Coordinator
Room Number:
Email: ehuddleston@bellvillebrahmas.org

Meeting dates, times, and location still need to be confirmed with Mrs. Huddleston.

The Robotics Club gives students hands-on experience designing, building, programming, testing, and improving robots. Members use engineering, technology, math, creativity, and teamwork to solve problems and prepare for robotic challenges and competitions. Contact the Robotics Club coordinator for information about membership, meetings, current projects, competition schedules, and upcoming activities.

Robot design, construction, and programming
Testing, troubleshooting, and design improvements
Team practices and competition preparation
Robotics challenges and competitions
Competition results and team advancement
New robots, equipment, software, and technology
Engineering and problem-solving projects
Team roles and student leadership
Demonstrations, exhibitions, and community events
Awards, recognitions, and member accomplishments
Partnerships with other classes, clubs, or community organizations
Opportunities for students to join or support the team

Covering the Robotics Club Beat

Start Here

Introduce yourself to Mrs. Huddleston and explain that you are covering the Robotics Club for the BVP Newsroom.
Ask when and where the Robotics Club meets.
Ask how she prefers to be contacted and how far in advance interviews and coverage should be arranged.
Request the current club calendar, including meetings, build sessions, demonstrations, competitions, and deadlines.
Ask for the names, grade levels, roles, and contact information of club officers and team members.
Ask what robots, challenges, or competitions members are currently working on.
Ask when reporters may visit build sessions and which activities or competitions may be photographed or recorded.
Check with Mrs. Huddleston and team members regularly for project updates, schedule changes, and competition results.
When you discover a possible story, submit it as a pitch before beginning full coverage unless your teacher tells you otherwise.

Your Responsibilities

Check for Robotics Club updates at least once each news cycle.
Maintain contact with Mrs. Huddleston and the students leading each project or competition team.
Keep track of meetings, build sessions, testing, demonstrations, competitions, and deadlines.
Follow the development of important projects from the original idea through design, construction, programming, testing, and improvement.
Watch for new robots, difficult challenges, major design changes, successful tests, competition results, and student accomplishments.
Pitch promising stories to the newsroom.
Arrange interviews, photography, video, and event coverage in advance.
Confirm names, team roles, robot names, competition categories, dates, locations, results, and awards before publication.
Follow up after demonstrations and competitions to obtain official results, photographs, and student reactions.
Include student voices by asking members about their designs, responsibilities, setbacks, solutions, and what they learned.

Important

A robot that has been designed or assembled is not necessarily finished or ready for competition. Clearly distinguish between an idea, an early prototype, a robot being tested, and a completed competition-ready robot. Confirm the project’s current stage and all competition results with Mrs. Huddleston before publication.

Robotics work may involve tools, electrical components, moving machinery, and equipment that can be damaged if disturbed. Do not touch a robot, controller, computer, tool, or project component without permission. Stay clear while robots are operating, and ask before photographing computer screens, programming code, unfinished designs, or competition materials.

Reporting Your Robotics Club Stories

Possible Story Ideas

Students begin designing or building a new robot
The team reveals a completed robot
Members prepare for an upcoming robotics competition
Students test a robot for the first time
A robot successfully completes a difficult task
A major mechanical, electrical, or programming problem is solved
The team makes an important change to its robot’s design
Members develop a new attachment, mechanism, or piece of code
Students attend a robotics competition, demonstration, or workshop
The team earns an award, placement, or advancement
A student takes the lead on an important part of the project
Members demonstrate a robot for students or the community
The club acquires new equipment, tools, parts, or software
Students partner with another class, organization, or community group
A mentor or technology professional works with the team
New officers or team leaders are selected
The club recruits new members
Students complete their robot before an important deadline
The club attempts something it has never done before
A project reaches an important testing or performance milestone

Signs There May Be A Story

Pay attention when:

A meeting, build session, demonstration, competition, or deadline is approaching
Members begin developing a new robot or project
The robot moves or performs its assigned task for the first time
A test succeeds after repeated failures
A major mechanical, electrical, or programming problem appears
Students discover an unexpected solution
The team makes a major change to its design or strategy
Members work under pressure to meet a deadline
The team prepares to transport or reveal its completed robot
A competition schedule, rule, or project requirement changes
Students are selected for special roles or leadership positions
The team earns an award, placement, or advancement
A student develops an especially creative design or solution
New technology, equipment, or software is introduced
The club demonstrates its work for an audience
Members return from a competition with results, lessons, or an interesting experience

Questions to Ask: The 5 W's and 1 H

You will not necessarily ask every question below. Select the questions that fit your story and ask follow-up questions whenever an answer is unclear or incomplete.

Who was involved?

Which Robotics Club members participated?
Who designed, built, wired, programmed, or tested the robot?
Who led the project or competition team?
Who developed the original idea?
Were teachers, mentors, other organizations, or community partners involved?
Who confirmed the competition results or approved the final design?

What happened?

What robot, project, challenge, or competition was involved?
What was the robot designed to do?
What responsibilities did each team member have?
What mechanical, electrical, or programming work was completed?
What problem did the team encounter?
What solution did students develop?
What changed from the original design?
What did the robot accomplish?
What should happen next?

When did it happen?

When did students begin the project?
When was the robot built, programmed, or tested?
When did the breakthrough or problem occur?
When is the competition or demonstration?
What deadlines must the team meet?
When were the results officially announced?
When will the robot be tested or used again?

Where did it happen?

Where does the Robotics Club meet and work?
Where was the robot designed, built, or tested?
Where was the competition or demonstration held?
Where will the team compete next?
Where can students see the robot or learn more about the club?
Where can interested students sign up or become involved?

Why does it matter?

Why was this robot or project created?
Why did the team choose this design?
Why was the challenge difficult?
Why was a design or programming change necessary?
Why is this accomplishment important to the team?
Why should other students care about the project?
What did members learn from the experience?
How could this technology be useful outside the competition?

How did it happen?

How was the robot designed?
How were responsibilities divided among team members?
How was the robot built, wired, and programmed?
How did students test its performance?
How did the team identify and solve problems?
How many versions or design changes were required?
How was the project funded?
How was the team evaluated or scored?
How can other students become involved?
How will the team improve the robot before its next test or competition?

Questions for Robotics Club Members

What is your role on the team?
Which part of the robot or project did you work on?
Why did you choose that role?
What was the most difficult problem you encountered?
How did you help solve it?
What changed between the original design and the current version?
What skills did you learn?
What part of the project are you most proud of?
What did you learn from testing or competition?
What still needs improvement?
What happens next?
How can other students become involved?

Questions for Competition Team Members

What challenge or event did the team enter?
What was the robot required to do?
How did the team prepare?
How was the robot evaluated or scored?
What worked well during competition?
What did not work as expected?
Did the team have to make repairs or adjustments?
What result or placement did the team receive?
Did the team qualify or advance?
What will the team change before competing again?

Questions for the Coordinator or Mentor

What is the purpose of this project or competition?
What rules or design limitations apply?
How were student roles assigned?
Which parts of the work were completed by students?
What technical skills are students developing?
What was the team’s greatest challenge?
Have the competition results been officially confirmed?
What safety rules apply during construction and testing?
What comes next for the robot or team?
Is there anything about the robot, project, or results that people might misunderstand?

People You May Need to Interview

Depending on the story, consider interviewing:

Robotics Club coordinator Emily Huddleston
Club officers or team leaders
The student who developed or proposed the idea
Students responsible for mechanical design and construction
Students responsible for wiring and electronics
Students responsible for programming
Students responsible for testing and troubleshooting
The robot’s driver or operator
Members of a competition team
Students who earned an award or recognition
Teachers whose classes connect with the project
Technical mentors or community partners
Competition judges or event organizers, when available
Students watching or participating in a demonstration

Do not interview only Mrs. Huddleston or a team leader. Include the students who designed, built, programmed, operated, and repaired the robot.

For team stories, identify each student’s specific contribution. Do not give one person credit for work completed by the entire team.

What You Need to Collect

Before writing or producing the story, collect:

The complete and correctly spelled names of everyone involved
Each student’s grade level
Each student’s official position, role, or responsibility
The official name of the robot, project, challenge, or competition
The date, time, and location
The purpose of the robot or project
An understandable description of what the robot was designed to do
The materials, equipment, software, or technology used
A description of how the robot was designed, built, programmed, and tested
The problems students encountered and how they addressed them
Important changes made to the original design
The project’s current stage of development
Official competition scores, placements, awards, or advancement results
The name of the person who confirmed the results
Important build, registration, testing, or competition deadlines
Information about project costs or funding when relevant
What happens next
At least one useful quote from a student who worked on the robot
At least one useful quote from Mrs. Huddleston
Quotes from students with different team responsibilities when appropriate
Photographs or video of designing, building, programming, testing, or competing
Identification of everyone shown in photographs
The names of important robot parts or mechanisms shown
Relevant designs, sketches, schedules, programs, score sheets, or official announcements
Confirmation that photography and video were permitted

Before You Leave

Ask yourself:

Do I have the correct spelling of every name?
Do I know each student’s grade level and team responsibility?
Do I have the robot’s or project’s official name?
Can I clearly explain what the robot was designed to do?
Do I know exactly what happened?
Do I know when and where it happened?
Did I distinguish between an idea, prototype, test model, and completed robot?
Did I identify which students designed, built, programmed, tested, or operated it?
Did I explain the problem and the solution clearly?
Did I verify technical explanations with someone who understands the project?
Have all scores, placements, awards, and advancement results been confirmed?
Did I interview more than one member when the project involved a team?
Do I have strong quotes—not merely “It was fun” or “I’m excited”?
Do I know what happens next?
Do I have usable photographs or video?
Did I identify everyone shown in my photographs?
Did I receive permission before approaching or recording an operating robot?
Did I avoid touching or moving equipment without permission?
Is there another builder, programmer, operator, mentor, or team member I should interview?

The Bellville Herd

NEWSROOM

A Brahma Video Productions Student Newsroom