IIWII Robotics
  • VEX Engineering Notebooks
    • Overview
    • Notebooking Best Practices
    • Understanding the Engineering Notebook Rubric
      • Engineering Notebook Scoring
      • Engineering Design Process Categories
        • Identify the Problem
        • Brainstorm, Diagram, or Prototype Solutions
        • Select Best Solution and Plan
        • Build and Program the Solution
        • Test Solution
        • Repeat Design Process
      • Additional Categories
        • Innovation/Originality
        • Usability and Completeness
        • Record of Team and Project Management
          • Time Management
          • Team Management
          • Resource Management
        • Notebook Format
    • Parts of a Notebook (Sections)
      • Cover Page
      • Team Overview / Introduction
      • Table of Contents (TOC)
      • Engineering Design Process (EDP)
      • Engineering Notebook Format
      • Game Overview / Analysis
      • Design Brief
      • Notebook Entries
        • General Entry
        • Team Meeting
        • Time Management
        • Resource Management
        • EDP Entries
          • Identify the Problem
          • Research
          • Brainstorm / Evaluation
          • Build / Program
          • Test
          • Repeat Design Process
      • Competition Writeup
      • Innovate Submission
      • Appendix
        • References
    • Engineering Notebook Resources
  • Interview
    • Overview
Powered by GitBook
On this page
  1. VEX Engineering Notebooks
  2. Understanding the Engineering Notebook Rubric
  3. Additional Categories

Notebook Format

PreviousResource ManagementNextParts of a Notebook (Sections)

Last updated 1 year ago

This area is fairly self explanatory. Teams can either get a 5 or a 0(zero) for providing evidence that documentation was done in parallel with their design process.

What this means is that the team has documented their notebook journey from beginning to end in chronological order.

Things to consider in this area.

  • Are pages numbered properly?

  • Are individual entries documented with a date along with an author's, and witness, signature?

  • Does a Table of Contents (TOC) exist?

    • Do the page number correlate to the appropriate entries?

    • Are dates used for corresponding entries?

  • If a team is using volume notebooks, maybe one for build, one for programming, and one for team meetings, do they reference each other in a chronological manner?

    • Volumes may be confusing to someone that is not familiar with your workflow and referencing pages in other volume can be helpful for navigating your journey

It is a good idea to ensure that each entry is signed and dated along with double checking the TOC reflects the proper page reference and date if possible.