top of page
Lesson 13: Log Book & Abstract

The Inventor's Logbook is a compilation of all of your materials in one place.  It is used to show the progression from initial idea to finalized project.  A physical logbook is needed for face to face competitions.  When face to face is not possible, a digital version should be submitted.  The logbook will contain all materials from the unit including handouts, notes, research, and sketches. 

Task 1: Compile Your Log Book

Compile all materials that your team has used for your project including handouts, notes, research, and sketches, in a notebook.    If you are preparing a digital logbook, check with your teacher for specific directions on what format/program should be used (such as Google Slides, Office 365, etc.).  The logbook should be organized with the following tabs to document your team's application of the  Design Thinking Process.  All of the materials you have used during the unit should be filed in the logbook behind the appropriate tab. 

Log Book Table of Contents


Tab 1:  Statement of the Problem

  • Problem Statement

  • Survey Results

    • Data

    • Comments


Tab 2:  Interviews

  • List by person

Tab 3:  Research

  • Any relevant research conducted that helps explain your problem or solution

  • Similar Ideas on the Market

  • Patent Search Results


Tab 4:  Ideation & Sketches

  • Brainstorming notes

  • List of materials used or needed for manufacture

  • Sketches of Ideas

  • Pictures of Prototypes

Tab 5:  Test

  • Photo & Test Summary


Tab 6:  Iteration

Tab 7:  Communication

  • Tri-Board design/photo

  • Pitch Script

Task 2: Write an Engineering Abstract

Your team will work together to  write an engineering abstract - a short summary, 250 characters or less, of your invention research project.  The abstract will be added to your Log Book, Tri-Board, and is required to enter your project in the Online Qualifier at Georgia Tech.

Your abstract should have the following five pieces

  • Introduction:  This is where you describe the purpose for creating your invention. How is your invention or new procedure better, faster, or cheaper than what is already out there?

  • Problem Statement:  Identify the problem you solved.

  • Procedures:  What was your approach for researching the problem? 

  • Results:  What were the results if your survey? Be specific and use numbers to describe your results. 

  • Conclusions:  State how your invention contributes solving the problem.


Things to Avoid

  • Technical terms that most readers won't understand.

  • Abbreviations or acronyms that are not commonly understood unless you describe what they mean.

  • Abstracts do not have a bibliography or citations.

  • Abstracts do not contain tables or graphs.

Why Is an Abstract Important?

Your InVenture project abstract lets people quickly determine if they want to learn more about your project. It's like an advertisement for what you've done. If you want judges and the public to be excited about your project, then write a compelling abstract!

Since an abstract is so short, each section is usually only one or two sentences long. Every word is important to conveying your message. Carefully choose your words and don't be afraid to reinforce a key point by stating it in more than one way. 

How to Meet the Word Limit

It is harder to write a short description of something than a long one. For your first draft, don't be overly concerned about the length. Just make sure you include all the key information. Use the "Word Count" tool to see how many characters you have used. 


Then start crossing out words, phrases, and sentences that are less important than others. Look for places where you can combine sentences in ways that shorten the total length. Put it aside for a while, then come back and re-read your draft. With a fresh eye, you'll probably find new places to cut. Before you know it you will have a well-written abstract.

Locker Hammock Log Book
Winner of Best Logbook Award an National Invention Convention
1alumihive abstract.PNG

Complete the abstract for your team's project and place it in your logbook.

bottom of page