State Competition

Junior Game Table Design:

4’X8’ board surrounded by 2X4's The size of the actual board will be 45”x 93”

All assets that do not have a defined starting point on the field will be outside the game board. 

While not required, if you would like a game board, it can be purchased at 

https://shop.frecklesgraphics.com/purdue_4h_extension_robotics_pl/shop/home

Junior Rules and tasks FOR 2025

2026 Junior Game Rules: -

Rules of Play

1. At the beginning of the match, your team’s robot must start in the WAITING ROOM. At least one wheel of the robot must be touching inside the WAITING ROOM boundary.
2. The GAME ZONE is the area outside of the WAITING ROOM.
3. The RESOURCE TRAY is a plastic tray that will be placed on the outside of the game table and will hold game pieces for known and/or unknown challenge(s).
4. Robots must be launched from the WAITING ROOM throughout the Before being launched, at least TWO wheels of the robot must be touching inside the WAITING ROOM boundary. The wheel must be attached to the robot at the time of launch and must be within the 13 inch cube of the robot.
5. Each match will be 3 minutes.
6. Time begins when the announcer says “BEGIN” and continues until the announcer says, “TIME.”
7. Any structures built by the team cannot be placed onto the GAME ZONE by human players but are permitted to be placed by the robot so long as it is done autonomously and is permitted by challenge rules.
8. No containers used by game officials to store game pieces can be used by the team/robot.
9. Players may retrieve their robot at any time during the match without penalty.When retrieved, the robot must return to THE WAITING ROOM. Judges will not assist in retrieval.
10. If a player interrupts the robot, the robot must return to THE WAITING ROOM.
11. Possession is defined as a piece that is not touching the playing surface and is under the robot's control.
12. Items in possession of a robot may be retrieved once any part/piece of the robot has broken the plane of the WAITING ROOM boundary.
13. If the robot is in possession of a game piece in the GAME ZONE, and the player retrieves the robot, the game official will return the game piece(s) to its original location/state.
14. A player is not allowed to touch any game piece except when the piece is completely inside the WAITING ROOM boundary, OR if the robot is deemed in the WAITING ROOM AND in full possession of a game piece(s). Once the piece is deemed inside The WAITING ROOM, contestants may remove the game piece from the game table/robot and store it in the RESOURCE TRAY.
15. If a contestant intentionally touches a game piece in the GAME ZONE, the team will be penalized 50 points per occurrence. Judges will issue one warning for the first offense. In such cases, the piece will be returned to its original starting position by contest officials as quickly as possible.
16. All competing team members are allowed around the game table during the competition, and any member may touch the robot if necessary. Once a robot is “touched,” it must be moved back to THE WAITING ROOM
17. Teams not competing must remain at their tables or staging
18. Good sportsmanship is always crucial during practice times. Practice time on the game table may be restricted as build time progresses. 
19. Practice time will be approximately 1 ½ - 2 hours between check-in and the start of matches. You will be assigned a match table and will share practice time with other teams.
20. At the conclusion of the match, it is the responsibility of the team captain to review the score sheet with the judge and then initial at the bottom, signifying agreement of the final match score. Scores are final after this point and cannot be contested.

Equipment Rules

1. Robots must fit in a 13-inch cube at the start of play. They can expand another 5 inches in any direction after being placed on the field, making the robot a maximum of 18 inches long.
2. You can have a maximum of one controller active in a match
3. You can use any sensors necessary to complete your challenges
4. At the start of the match, your equipment may be stored off the table or in the launch area. It may not be in the play area until the timer has started.

Junior Scoring Rules and Rubric

1. After 3 minutes, the match will end. Do not touch your robot until scoring is finalized.
2. Unless otherwise specified, scoring will take place at the end of the match. 
3. If a team cannot run their robot, they can still gain points with their engineering notebook.
4. The referee will document the results of the match with the team captain. The captain will initial the results, and it will become final at that point. 
5. Each team will have two attempts per round. Only the high score will be recorded.  In the case of a tie, the second score will be used to make the final decision.

 Junior 2026 Rubric

Senior 4-H Robotics Delivery Challenge: Autonomous Package Delivery

2026 Senior Rules

Theme:

Design and program an autonomous robot to deliver packages to the correct houses in a neighborhood while avoiding obstacles and protecting property.

Competition Overview

Participants will design and program fully autonomous robots capable of identifying, collecting, and delivering color-coded packages to matching homes on a 4x8-foot game mat. Robots must complete deliveries while avoiding obstacles such as parked cars, dogs, and fire hydrants.

Robots earn points based on accuracy, placement, and adherence to rules of safety and efficiency.

Eligibility

• Open to youth in grades 9–12.
• Teams may consist of 2–4 members.
• Each team must use a single robot per match.
• Robots must be autonomous (no remote control after start).

Robot Requirements

• Platform: Teams may use LEGO SPIKE Prime, VEX IQ, VEX V5, Arduino, Raspberry Pi, or similar systems capable of full autonomy.
• Size limit: Robot must start within a 13"x13"x13" cube and expand another 5 inches in any direction after being placed on the field, making the robot a maximum of 18 inches long.
• Power: Battery-powered only, no external power or tethers.
• Sensors: Any onboard sensors may be used (color, distance, camera, gyro, etc.).
• No Wi-Fi, Bluetooth, or remote-control during run (except to start the program).

Game Field Description

• Field size: 4 ft x 8 ft mat with printed “neighborhood” layout.
• Elements include:
  • Truck zone: Starting area containing all packages for delivery.
  • 4–6 houses: Each marked with a distinct color.
  • Driveways, yards, sidewalks, and mailboxes for each home.
  • Obstacles: Parked cars, dogs, fire hydrants, trees, and curbs.

Note: Layout and obstacle placement will be consistent for all teams during a given round.

Game Objective

Deliver as many packages as possible to the correct colored homes accurately and safely within the time limit.

Delivery Rules:

• Packages are color-coded to match the target house.
• Packages begin at the truck zone and must be autonomously delivered to the correct home.
• Some houses will have a return package (marked differently) that must be picked up and returned to the truck.

Match Format

• Each team has 2 minutes and 30 seconds to complete as many deliveries as possible.
• Robots must start completely inside the truck zone.
• Teams may touch or reset their robot only by forfeiting a 10-point penalty and returning it to the truck zone.
• Robots must be autonomous from start to finish (only one start button press allowed).

 Scoring System

Time Efficiency Bonus

If a team finishes all deliveries (either all packages delivered and/or returned) before the 2-minute 30-second limit, they receive bonus points based on the time remaining:

Competition Rounds

1. Practice Round: 1 official practice run per team.
2. Qualifying Rounds: 2 matches; best score counts.

Finals: Top 3–5 teams advance for a single championship match.

Judging & Tie-Breakers

Judges will evaluate based on:

1. Highest score achieved
2. Fastest time to complete all deliveries (if tied on points)
3. Engineering Design Notebook ( – Required – worth 525 points.  Rubric on website, including judge interview.

Safety & Conduct

• Robots must not launch, throw, or eject parts or packages.
• Youth participants must do all programming.
• Coaches may assist in setup but not in operation.
• Respect for judges, other teams, and materials is mandatory.

Robotics Engineering Notebook - All Levels

Adapted from the University of Idaho Extension “All about the FTC Engineering Notebook”.

Engineering Notebook Rubric

Why an Engineering Notebook?

An engineering notebook is a working document. It is where ideas, sketches, and team thoughts are recorded in addition to the final production information about your team and robot. It is a journal your whole team will use to help everyone know what’s going on, where you record your testing data, and it is a record of your abandoned ideas and prototypes. 

• Engineering notebooks show the thought behind your strategy, designs, innovations, and organization. They show how each team member contributes and how your team overcomes obstacles. These things are hard to see at an event when you are there with a finished product.
• Your engineering notebook is the primary reference for your team. It records all thoughts at meetings and events, all ideas for robot design, all changes to the code (although the actual code does not need to be included), and game strategy. A notebook is a tool for the entire team to communicate together. It should be used as a reference for the team and the judges.
• An engineering notebook is a tool to show how your team works, what you do, and the concepts you explore with your sponsors and potential sponsors.
• Judging your notebook will include written content and a short, one-minute presentation to the judges.  All members must participate and be able to talk about what is in the notebook. 

Should I follow this formatting guideline?

The short answer is yes; some of the guidelines are presented as optional. Still, by closely following the guidelines, you make your engineering notebook easier for the judges to understand and make it eligible for all awards

If you plan to use a handwritten notebook, it is a good idea to divide the sections before you start writing or decide if you want to use multiple small notebooks to document your season. Remember that your meeting discussions are as important as your engineering, game strategy, and programming thoughts when considering the awards. Showing how your team uses all of its strengths to overcome engineering challenges is critical, including all aspects of the team. You also have the option of using an electronic notebook. These can be easier to use if you are meeting in different places; as long as you have access to it, no one will forget to bring the notebook. While the judges do not differentiate between a handwritten notebook and a printed one, there are pros and cons that each team should consider.

 Sample template for online Engineering Notebook

Now that you have decided on your notebook/notebooks get a sharpie and put your TEAM NAME and COUNTY on the notebook. This is one of the most important things you can do! It not only helps the judges find your notebook in the mountain of engineering notebooks at a tournament, but it lets those same judges know you care about your notebook and can follow basic instructions. No matter how nice your cover is, if a judge has to hunt to find your team name and county, it does not leave them with a good impression – even before they look inside. Remember, the judge is your advocate for being considered for awards; you want them to have a positive impression of the team in every way possible.

Requirements of Your Engineering Portfolio/Notebook:

• The portfolio should be organized in a logical manner.
• The engineering portfolio must have engineering content. The engineering content could include entries describing examples of the underlying science, mathematics, and game strategies in a summary fashion.
• The engineering portfolio must provide examples showing the Team clearly understands the engineering design process, including an example of lessons learned.
• The portfolio should inspire judges to ask about detailed engineering information.
• The portfolio format is less important but enables the judges to understand the Team’s design maturity, organizational capabilities, and overall Team structure.
• The portfolio should reference specific experiences and lessons learned and should capture the summary of the status of the Team and their Robot design.  The engineering design process should be evident.
• The portfolio could summarize experiences and lessons learned with concise tables of outcomes.
• The portfolio could summarize how they acquired new mentors and/or acquired new knowledge and expertise from their mentors.
• The portfolio should contain a summary of the overall Team plan.
• The portfolio could contain information about the plans to develop skills for Team members.
•  

Getting Started

Everything is going into this notebook, but it’s a blank page or screen right now. So how do you get going?

• Make sure your Team Name and County are on the cover – both are required
• The next thing you need to do is set aside the first page for your team summary. You will want to do a draft of this page. It is the first impression you give to the judges! They will see your team summary before they even meet your team! Alternatively, you can fix your team summary to the backside of the front cover.
• Label the next page "table of contents" As you set the sections, you will start filling this in! This will help keep your notebook organized, and where you will highlight key pages you want the judges to look at.
• Divide the sections. You are welcome to organize the engineering notebook into more categories if you like, but remember, the chronology and connectedness between everything you do are important to the judges, especially strategy, design, build, and programming all work together to make your season.
  • You want a Team Profile section where each team member is introduced, preferably with pictures.
  • Your Engineering Section will be the bulk of your notebook. It will include all your team meeting notes, designs, programming thoughts, strategy ideas, and reflections. Each meeting will need its own page; you will want additional pages for your engineering notes.
• Add your first meeting to the table of contents, and create an entry in the Engineering section. In your tasks column, include setting up your engineering notebook and your contribution policy; remember, EVERY team member should contribute to the notebook! Don’t forget the team reflections at the meeting – this is a good place to make a contribution by having each team member present take a pen (never use a pencil!)

Stick with your notebook policy for every meeting! Everything needs to be in the notebook.

What do You Mean When You Say Everything Goes in the Notebook?

Add the meeting to the entry to the table of contents for every meeting, and then write your tasks and reflections. Every credible idea discussed should be included in the notebook – even those ideas that don’t work out. Do not self-censor your notebook! If you use a whiteboard to draw out ideas, take pictures, or have a team member sketch the ideas into the notebook. Make sure you leave space on meeting pages for photographs of what was happening – OUTLINE THEM IN INK and follow the picture inserting guidelines; pictures occasionally fall out.

 If you wonder if you should include something in the engineering notebook, do! Judges love the little bits of information that make your journey real, like; ideas you discard because they are out of budget, when you sacrifice strategy because of a programming limitation, drawings sketched on napkins, the inconsequential details of a meeting – like celebrating a team member or coach’s birthday. However, judges don’t need to know if the cake was good. 

Tournament Time

You’ve done well, brought your engineering notebook to all team meetings, and it’s been a great resource for your team over the season. You’ve saved it from near-fatal disasters. Your team has poured their heart and designs into it. Maybe you’ve even shown it to a few potential sponsors? But it is tournament time, and that’s when the engineering notebook transforms from a working document for the team to keep their thoughts, ideas, and designs into the written transcription of what makes your team special. 

Now is the time to go back and flag pages for the judges. What entries really tell your team’s story and show their strength? Where are your PTC or other design sketches? Where are the best pages to learn about the team’s innovative idea? Great! You have your flags and highlighted your table of contents for the judges.

• Look at the front cover, is your TEAM NAME and COUNTY there and easy to read? Make it bolder if you need to – if you can, put it on the binding too.
• Is your team summary on the first page or fixed securely to the inside of the front cover?
• Is your table of contents completely filled in with key entries highlighted for the judges?
• Does every team member have a bio and photo in the Team Section?
• Does your Engineering section have all your meetings, designs, notes, and reflections?

Have the key entries been flagged for the judges?

• Your Bill of Materials is fixed into your notebook and added to the table of contents so the judges can find it quickly. Did you print a second copy for inspection?
• Page-by-page:
  • All pictures have ink borders with the page number on the back of the photo; should it fall out?
  • All white space is removed?
  • Every page has a page number. It’s okay if the numbers restart for each section?
  • Are all corrections are crossed out a single time and dated?
  • Everything fixed to the pages is secure and not coming loose?

Review this document again. Remember to turn in your notebook when you check in at the tournament. The longer the judges have with your notebook, the more they can get from it. The judges should receive your notebook shortly after they arrive. You can still feel free to point out key passages in the judging room, don’t use all your time flipping pages – your flags can help you here.

After the tournament, remember to pick up your engineering notebook!

Engineering Notebook Rubric - All Levels