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. Parts of a Notebook (Sections)

Competition Writeup

PreviousRepeat Design ProcessNextInnovate Submission

Last updated 1 year ago

At the conclusion of every competition it is a good idea to review what took place and do a recap to evaluate what went right and what went wrong. This is also an opportune time to review how the team performed against others and how well the team worked with one another.

There are various aspects that a team may want to review and include in a post competition writeup. Most importantly for consideration is how well the team and robot performed in matches and any observation of what could be improved upon moving forward.

The example being used contains the following Match Results

  • Top 10 Rankings

  • Links to Match Video (sometimes matches can be linked directly if timestamps can be used)

  • Match Overviews

  • Alliance Selection Consideration Table

  • Skills Review

  • What was learned

  • What needs to be worked on

While not included in this write up it may be good to review other competitors' robots to see if there are any worthwhile ideas to pursue. This could be placed in its own entry if desired.