New Hampshire Science and Engineering Exposition (NHSEE)

Writing an abstract
The judges (and anyone else interested in your research) will be looking for a high quality abstract that explain what you did, why you did it, how you did it and what you found in a few words. Writing a good abstract can take work, and you’ll find as you continue in science or engineering this skill will help you tremendously. ISEF requires that your projects have an abstract and we’d like to help you make yours a good one.

The NHSEE Quick Guide to Abstracts should help you in planning and writing your abstract. You have 250 words (ISEF rule) to draw your reader into your paper and convince them to read the whole thing. Check out our guide and make your abstract a great one.

A Quick Guide to Abstracts

What is an abstract?

An abstract is a brief, written description of your project that explains your project’s purpose, procedures, data, and conclusions. It is a self-contained summary that tells the reader why they should care about your project and what you found out. The abstract is concise, but complete—it communicates the essence of your project.

How do I write an abstract?

ISEF limits abstracts to 250 words, so you need to be succinct—focus on the big picture. Here are a couple of templates:

Science Experiment. For a science experiment, start with an introductory statement about why you are doing your project. What are you trying to find out, and why should your readers care? Then, state your question/problem and your hypothesis. Next, summarize your methods. You don't have a lot of space, so only mention the key points of your procedures. Then give the highlights of your data and data analysis, followed by your conclusions. The very last part of the abstract should discuss the applications and implications of your project.

Engineering Project. The abstract for an engineering project will be similar, but there will be a few changes. Start with an introductory statement about why you are doing your project. What problem are you trying to solve? What need are you trying to address? Why should your readers care? Then, state your design goal and describe your initial design. Next, summarize your iterative process of designing, testing, rebuild, and retesting. You don't have a lot of space, so only mention the key points of your process. Then give the highlights of your data analysis from tests of prototypes, followed by your final designs. The very last part of the abstract should discuss the applications and implications of your project.

Are Abstracts Important?

Yes, very! Abstracts are an incredibly important part of technical communication. Scientists, engineers, and mathematicians have to wade through a vast amount of literature. They don't have time to read all of it, so they use abstracts to decide if an artic le is worthwhile. If the abstract is interesting and relevant, a scientist might read the accompanying article. If the abstract isn’t, a scientist stops reading and moves on.  Just like scientists, science fair judges read your abstract and may make preli minary judging decisions based on your abstract. A good abstract is like a good first impression it goes a long way.

Do you have any other tips?

• An abstract isn't an email or text message, so use complete sentences and proper English. Leave out the LOL's, TTYL's, @'s and w/o's.
• Have someone proofread your abstract.
• Focus on the big stuff; don't include nitty gritty details.
• Do include numbers. For example, instead of “the sedimentary rocks were less dense than the metamorphic rocks”, try, “the sedimentary rocks were 10% less dense than the metamorphic rocks.
• Sell your project. You don't have a lot of space, but you want to make sure that your reader doesn't leave asking, “So what? Why should I care?”.

Source: