A science fair abstract is a short summary of your entire project, written in 250 words or less. It covers why you did the project, how you did it, what you found, and what it means. Most science fairs require one, and at the highest levels of competition, like the International Science and Engineering Fair (ISEF), the abstract follows a strict format with four labeled sections: Purpose, Procedure, Results, and Conclusions.
What Goes in Each Section
Every science fair abstract follows the same basic structure, whether you’re entering a local competition or a national one. Think of it as telling the story of your project in miniature. Here’s what each section needs:
Purpose: This is your opening. Start with one or two sentences of background that explain why this topic matters or what gap in knowledge you noticed. Then state your specific research question or the problem you set out to solve. Judges look for a “clear and focused purpose” that “identifies contribution to field of study,” so don’t be vague. Instead of writing “I wanted to learn about water pollution,” try something like “Agricultural runoff increases nitrogen levels in local waterways, yet few low-cost monitoring options exist for small farms. This project tested whether a simple colorimetric sensor could detect nitrogen concentrations above EPA thresholds.”
Procedure: Summarize how you conducted your investigation in two to four sentences. Hit the key steps and mention any important methods or tools, but skip minor material details unless they directly shaped your results. If you used a specific type of sensor, a particular software program, or a notable technique, include it. If you used beakers and graduated cylinders, don’t bother listing them. One critical rule: only describe work you personally did. If a mentor performed a procedure (like a surgical step or running specialized lab equipment), leave that out of the abstract entirely.
Results: Report the key findings that support your conclusions. Use specific numbers, percentages, or comparisons rather than vague statements. “The sensor detected nitrogen at concentrations above 10 mg/L with 94% accuracy across 60 trials” is far more useful than “The sensor worked well in most tests.” Don’t include every data point you collected. Pick the results that directly connect to your research question. No tables, charts, graphs, or images belong in the abstract.
Conclusions: Keep this to one or two sentences. State what your results mean, whether your hypothesis was supported, and if relevant, note a real-world application or implication. This is where you can use present tense to express a broader takeaway: “Low-cost colorimetric sensors offer a viable option for on-farm nitrogen monitoring, potentially reducing delayed detection of runoff contamination.”
Getting the Word Count Right
The ISEF limit is 250 words, and most regional and state fairs follow the same guideline. That’s roughly one page double-spaced. With so little space, every sentence has to earn its place. A common mistake is spending too many words on background and running out of room for results and conclusions, which are the parts judges care about most.
A good rule of thumb for distributing your words: about 50 to 60 words for the purpose, 60 to 80 for the procedure, 60 to 80 for results, and 20 to 40 for conclusions. These aren’t rigid limits, but they keep you from going lopsided. If your purpose section is 120 words long, you’ve buried the most important parts of your project.
Choosing the Right Tense and Voice
Use past tense when describing what you did and what happened: “I measured,” “the samples showed,” “growth rates decreased.” Use present tense for general truths and your conclusions: “These results suggest,” “nitrogen levels above this threshold pose a risk.”
You don’t need to write everything in passive voice to sound scientific. “I tested three concentrations across 20 trials” is clearer and more engaging than “Three concentrations were tested across 20 trials.” Active voice tends to be easier to read, and when you’re working with a tight word count, it’s often shorter too. Use passive voice when the action matters more than who did it, but don’t default to it for every sentence.
What to Leave Out
Science fair abstracts have a surprisingly long list of things that don’t belong:
- Acknowledgments. Don’t thank your teacher, mentor, or parent in the abstract.
- Bibliography or references. The ISEF abstract specifically does not include a bibliography.
- Work done by others. If your mentor ran an instrument, performed a medical procedure, or did preliminary analysis before you joined the project, that stays out of the abstract.
- Unnecessary data. If a result doesn’t connect directly to your conclusion, cut it.
- Visual elements. No graphs, tables, images, or special formatting.
What Judges Actually Score
Understanding the judging criteria can help you write a stronger abstract. At ISEF, science projects are evaluated on five areas: Research Question (10 points), Design and Methodology (15 points), Data Collection and Interpretation (20 points), Creativity and Potential Impact (20 points), and Presentation (35 points). Your abstract isn’t scored separately, but it’s the first thing judges read, and it shapes their initial impression of every one of those categories.
Judges want to see that your research question is testable, that your methods are well designed with defined variables and controls, that you collected enough data to support your conclusions, and that the project shows creativity or real-world impact. Your abstract should signal all of these qualities in miniature. If your method involved a control group, mention it. If you ran enough trials for statistical confidence, say how many. If your project addresses a practical problem, make that clear in the purpose or conclusion.
Writing It Step by Step
Don’t try to write the abstract from scratch in one pass. Start by finishing your project completely, because you need to know your results and conclusions before you can summarize them. Then follow these steps:
First, write one sentence for each section answering the core question: Why did I do this? How did I do it? What did I find? What does it mean? This gives you a four-sentence skeleton that captures the entire project. Read it aloud. If someone unfamiliar with your work could understand the basic story, your structure is solid.
Next, expand each sentence into a short paragraph. Add your background context to the purpose, your key methods to the procedure, your specific numbers to the results. Then do a word count. If you’re over 250, start trimming. Cut adjectives first (“very significant results” becomes “significant results” becomes just the numbers). Remove any sentence that repeats information already stated elsewhere.
Finally, read the abstract as if you know nothing about the project. Does it make sense on its own? Could you explain what the student did and why it matters? If any section leaves you confused, rewrite it with plainer language and more specific detail. Have a friend or family member read it too. If they can summarize your project back to you after reading the abstract, you’ve done the job right.