← Back to all articles

Competition Guides

FLL Challenge Ireland: the robot game is not the whole score

How Irish teams can balance robot performance, innovation, design explanation and Core Values.

3 Oct 20263 min read
Article cover image

Editorial overview

The visible centre of FIRST LEGO League Challenge is the autonomous robot game, but the Irish programme makes clear that this is only one part of the work. Teams also develop an innovation solution, explain their robot design and demonstrate Core Values in how they collaborate. At a regional tournament, students present these elements and then put the robot onto the competition field.

That balance changes how a team should organise. If every meeting is spent chasing robot points, the innovation project becomes a rushed presentation and only one or two students understand the design. If the team spends too long discussing a broad social problem, it may never build a testable solution. Strong teams create one schedule for all outputs and make technical decisions visible to everyone.

CompeteMap sees Challenge as a substantial engineering season for students aged 11–16 in Ireland. It suits teams that can meet consistently and an adult coach who is comfortable letting students own imperfect decisions. Registration includes the season Challenge Set, a regional tournament place and support resources, but teams also need access to compatible LEGO Education equipment. The greatest value comes from iteration and shared explanation, not from adults delivering a polished machine.

Quick Facts

FieldDetails
ProgrammeFIRST LEGO League Challenge Ireland
Typical studentsAges 11–16, from schools, clubs and volunteer groups
Team sizeUp to 10 students with an adult coach
Main elementsRobot Game, Innovation Project, Robot Design and Core Values
EquipmentCompatible LEGO Education robot kit and coding device
EventRegional tournament with judged presentations and robot matches

For current dates, eligibility and registration details, see the FLL Challenge Ireland competition page.

Plan four strands from the beginning

Assign leads for robot, project, documentation and presentation, but rotate students so knowledge does not become trapped. Use one weekly review to connect the strands. The innovation project may reveal a user need that influences the team's presentation style; robot testing may provide a useful example of how the team responds to failure.

For the Robot Game, prioritise reliable missions before complicated combinations. Record starting position, attachment, code version and success rate. For the Innovation Project, define the problem narrowly, consult people who understand it and show how feedback changed the idea.

Make student ownership visible

Every student should be able to describe at least one decision and one revision. Practise answering “Why did you choose this?” rather than memorising a script. Core Values are not a slogan section; judges can see whether the team listens, includes members and handles pressure constructively.

Key Takeaways

  • Do not let robot points consume the Innovation Project and judged explanations.
  • Build reliability before adding complex mission combinations.
  • Keep a shared record of decisions, tests and revisions.
  • Confirm the current kit, fee and tournament arrangements on the official Irish pages.

Sources checked

EXPLORE NEXT

Not sure where to start?

Find the right competition
View all articles →

Comments

Join the conversation

Share a question, note, or update.

No comments yet.