The Abstract Is Not First
- Nolan P. Comparetto
- Feb 14
- 3 min read
I need to say this nicely, but I also need to say it clearly.
Writing the abstract first is like writing a book report about a book you have not read yet. You can try, but you are basically guessing, and then you have to rewrite it anyway. That is why I say it all the time.
The abstract is not first.
What An Abstract Actually Is
An abstract is a short summary of your entire report. It tells the reader what you did, why you did it, how you tested, and what you found. It is the preview of the whole season.
If you have not written the report yet, you do not actually know what the final story is. That is not a you problem. That is just how time works.
What Happens When You Write It First
When teams write the abstract first, one of two things happens.
Option one, the abstract is vague. It turns into a paragraph of general statements like “We built an ROV and improved it.” That does not help, and it does not show your real work.
Option two, the abstract is specific, but it is wrong later. The team changes the design, tests something new, or learns something unexpected, and now the abstract does not match the report.
Either way, you rewrite it. So why do it twice.
The Better Way To Do It
Write the abstract last, but think about it all season.
Here is my actual process.
First, collect the data.
Second, write the sections of your report as you go.
Third, when the report is complete, write the abstract as the final step.
The abstract becomes easy when you already have the evidence.
Nolan’s Four Sentence Abstract Formula
If you want a simple way to write it, use this structure.
What the project was and why it mattered
What you built or changed and what your approach was
How you tested or measured performance
What results you found and what you concluded
That is it. Four sentences. Done.
The Cheat Code
The cheat code is that the abstract should sound like your report. If your report is full of testing, data, and iteration, your abstract should mention that. If your report includes a real world project or outreach, your abstract should mention that too.
An abstract is not a place to be fancy. It is a place to be accurate.
Why This Matters In Real Life
Judges read the abstract first. Teachers read the abstract first. Sponsors read the abstract first. If your abstract is vague or does not match your report, you lose people right away.
Your abstract is your first impression. Make it match your work.
Nolan Final Word
Write the abstract last. Save yourself time, stress, and rewrites.
If you feel like you have to start somewhere, start with the thing that makes the abstract easy later.
Collect the data. Then let the report tell you what the abstract should say.
SeaSiders Shoutout
Quick shoutout to the SeaSiders, one of the Manvel Junior High Warriors SeaPerch teams in Manvel, Texas, because they said this and I cannot believe I did not say it first.
"You cannot write a book report about a book you have not read yet. So you should not try to write the abstract before you write the rest of the Technical Design Report."
That sentence should honestly be printed on a sticker and placed on every laptop during report season.
Come find us at the 2026 International SeaPerch Challenge and grab some stickers. If you see a laptop with an “Abstract Is Not First” sticker on it, that team just saved themselves at least two rewrites. If you are still writing your abstract first, it is ok, we still love you, but we are also going to hand you a sticker and gently roast you with kindness.
Comments