Getting Started with Engineering Notebooks

Students working through STEM Labs, classroom engineering challenges, and VEX Robotics Competitions  make decisions throughout the learning process. They brainstorm ideas, test mechanisms, write code, collect observations, solve problems, and improve their designs over time.

The robot shows what the team built. The engineering notebook shows how the team got there.

An engineering notebook helps students capture their thinking as it happens. It gives the team a place to record ideas, explain decisions, track testing, document code changes, reflect on challenges, and plan what to try next. Over time, the notebook becomes a record of the team’s learning and growth.

Notebooking does not need to feel overwhelming. A strong notebook is not about perfect pages or polished writing. It is about helping students make their process visible so they can remember what they tried, learn from evidence, and communicate their work clearly.

This article introduces what an engineering notebook is, why it matters, and how students can turn everyday notes into meaningful documentation of their design, coding, testing, and problem-solving.

Table full of robotics supplies including a laptop showing elements from the game and an open engineering notebook that is breaking down strategies for the game.

What is an Engineering Notebook?

An engineering notebook is a place for students to document their thinking, decisions, tests, and improvements as they move through the engineering design process. It is not just a record of what they built or coded. It shows how they approached a problem, what ideas they considered, what evidence they collected, and how their work changed over time.

Students can use engineering notebooks in many VEX learning experiences, from VEX Robotics Competitions to classroom challenges. In each setting, the notebook helps students capture the process behind their work.

An engineering notebook may include:

  • Goals and ideas — challenge goals, game analysis, brainstorming notes, sketches, and possible solutions
  • Design and code work — robot designs, prototypes, build changes, pseudocode, flowcharts, and debugging notes
  • Testing and observations — test results, driver practice notes, classroom activity notes, and evidence collected during trials
  • Reflections, decisions, and next steps — what students learned, what changed, what they decided, and what they will try next

A strong engineering notebook helps someone else (a teacher, coach, or competition judge) understand the students’ process. It should show more than the final answer, explaining the questions students asked, the problems they noticed, the options they explored, and the reasoning behind their choices.

Engineering notebook sample showing a possible approach and decision matrix. Images are cut and pasted onto the paper showing how students got their images.

The notebook does not need to look the same for every student or team. Some may use short notes and quick sketches. Others may include photos, diagrams, data tables, screenshots of code, or longer reflections. What matters most is that the notebook clearly shows students' thinking and helps students continue learning from their work.

When notebooking becomes part of the routine, it helps students remember what they tried, use evidence to improve, collaborate more effectively, and communicate their process to others. Short, consistent entries can be more useful than long entries written after the fact.

Starting an Engineering Notebook

Getting started with an engineering notebook does not require a perfect template or a fully planned system. The most important step is to begin recording students' thinking as it happens. The goal is to create a routine that helps students record each stage of their process, from the first idea to the next improvement.

Choose a Format

Engineering notebooks can be physical, digital, or a combination of both.

A physical notebook can be easy to bring to meetings, use during building, and keep nearby while students test ideas. A digital notebook can make it easier to add photos, screenshots, links, code snippets, and shared entries from multiple students. 

  • Digital notebook templates for VEX Robotics Competitions can be found in this article.

The best format is the one students can use consistently. If the notebook is easy to access and easy to update, it is more likely to become part of the team’s routine.

Create a Simple Entry Structure

Students do not need to start with long entries. A repeatable structure can help them know what to write without feeling overwhelmed.

A simple entry might include:

  • Goal: What are we trying to do?
  • Work: What did we build, code, test, or discuss?
  • Evidence: What happened when we tried it?
  • Decision: What did we learn or decide?
  • Next Step: What will we try next?

Students can also add visuals when they help explain the work, such as photos, sketches, screenshots, diagrams, or data tables.

Make Notebooking Part of the Routine

Teams do not need to go back and recreate everything they have already done. Start with the next meeting, test, or activity.

4 kids talking with one another. An engineering notebook can be seen in the center with the girl on the right pointing at a tablet. The other students are engaged to see how they documented their process.

Notebooking works best when it happens regularly. Set aside a few minutes during or after each activity for students to record what happened and what comes next. Over time, even small entries create a useful record of the team’s learning, decisions, and progress.

From Journal to Engineering Notebook

A journal often records what happened. An engineering notebook goes a step further by explaining what students learned from what happened. 

The difference is not about writing more. It is about making the thinking visible. Strong entries show how one step of the process leads to the next: a problem leads to an idea, an idea leads to a test, and a test leads to a decision or improvement. And this concept applies to all types of entries, including building, coding, and strategy.

  • A coding entry might explain why part of the code changed.
  • A testing entry might compare results from different trials.
  • A competition entry might describe how a strategy changed after a match. 

The goal is to help other team members or others not on the team understand what the students did and how they used evidence and reflection to improve their work.

Journal Entry Developing Engineering Notebook Entry Stronger Engineering Notebook Entry
"We worked on the drivetrain today."
Engineering notebook sample with a table shown. In the left column is data about what gear train is being tested and the second column has data about how far a bin was pulled.

This notebook shows testing results, but has no details about the goal of the tests or reflective notes to show how the team made a decision.

Engineering notebook sample for a Tug of War challenge. Through the notes you can see sketches of the design of the robot and that they lost the trial. Scribbles are shown below to indicate a reflection.

This notebook labels the challenge, uses labeled sketches to show what was being tested, and includes multiple reflection areas.

 

Student Ownership and Adult Support

An engineering notebook should reflect students' thinking. Students should be the ones recording ideas, explaining decisions, adding evidence, and identifying next steps.

Teachers, coaches, and mentors can support notebooking by helping students build routines. Adults can ask questions, remind students to document while their thinking is fresh, and help them understand what kinds of details make an entry useful. However, adults should not rewrite, polish, or create notebook entries for students.

Helpful questions adults can ask include:

  • What problem are you trying to solve?
  • What did you try?
  • What evidence do you have?
  • Why did you make that decision?
  • What will you test or change next?

The notebook does not need to sound like an adult wrote it. It should sound like the students who are doing the work. When students create and maintain their own notebooks, those notebooks become a stronger record of their learning, problem-solving, and growth.

Additional Notebooking Resources

Resource What it can help with

notebooks.vex.com

Access digital notebook templates for VEX IQ Robotics Competition and VEX V5 Robotics Competition teams.

education.vex.com

Explore STEM Labs and activities that give students opportunities to plan, build, code, test, reflect, and document their work.

builds.vex.com

Find Hero Bot build instructions and other VEX robot builds that can help students get started building and documenting.

code.vex.com

Access the coding environment for VEX platforms, including VEX IQ and VEX V5. Coaches can use this link to help students get started with coding, open the correct version of VEXcode, and begin documenting their coding.

Facilitating Engineering Conversations with Students

Use question prompts to help students explain design decisions, testing, iteration, and problem-solving.

Facilitating Coding Conversations with Students

Use question prompts to help students explain code, debug projects, test changes, and reflect on programming decisions.

For more information, help, and tips, check out the many resources at VEX Professional Development Plus

Last Updated: