For most conferences, the abstract is the only thing reviewers read before deciding whether you present. It is also what attendees read when they choose which session to attend. A good abstract is short, specific and easy to judge. This guide gives you a structure that works across most fields, then the details that make the difference.
Read the call for papers first
Before you write anything, read the call for papers closely and note:
- the word or character limit, and whether the title and author list count towards it;
- the themes or tracks, and which one fits your work best;
- whether the abstract must be structured (with headings such as Background, Methods, Results, Conclusions) or written as one paragraph;
- whether you can include references, figures or tables;
- the presentation type you are applying for: oral, poster, or either;
- the deadline and time zone. Many conferences close submissions at midnight in their own time zone or at "anywhere on Earth".
Abstracts that ignore the format are often rejected before anyone reads the content.
A structure that works
Most strong abstracts answer five questions in this order, in roughly these proportions:
- Why does this matter? (one or two sentences) State the problem and why someone in your field should care.
- What was missing? (one sentence) What is not yet known, or what does not work well enough today?
- What did you do? (two or three sentences) Your approach, data, sample or method, with enough detail to show it is sound.
- What did you find? (two or three sentences) Your main results, with numbers where you have them. "We found a significant improvement" is weak; "accuracy rose from 71% to 86% on the test set" is strong.
- So what? (one or two sentences) What your result changes, who can use it, and what comes next.
If your work is still in progress, say so clearly and describe the results you will present by the conference date. Reviewers accept work in progress more readily when the method is clear and the timeline is realistic.
Write for a tired reviewer
Reviewers often read dozens of abstracts in one sitting. Make their job easy:
- Put your main finding in the abstract's first half, not the last sentence.
- Use the words people in your track would search for, so your abstract is easy to classify.
- Prefer short sentences and active voice: "We surveyed 412 nurses" rather than "A survey was conducted".
- Define abbreviations the first time you use them, and use as few as possible.
- Avoid claims you cannot support in a 15-minute talk or a poster.
The title
A good title says what you studied and, if possible, what you found. Compare "Machine learning in healthcare" with "A screening model that detects early sepsis from routine ward observations". The second tells the reviewer exactly what to expect and helps attendees find your session.
Common reasons abstracts are rejected
- The topic does not fit the conference or the chosen track.
- There are no results, and no clear plan for when there will be.
- The method is vague or the sample is not described.
- The abstract repeats the background and says little about the new work.
- It goes over the word limit, or the format is wrong.
- The same work has already been presented or published, and the conference asks for original work.
Before you press submit
- Ask a colleague outside your immediate project to read it and tell you, in one sentence, what you found. If they cannot, revise.
- Check every author's name, affiliation and order. These are often printed exactly as submitted.
- Save a copy of the final text and the confirmation email.
- Note the dates for acceptance decisions, early registration and, if relevant, full paper submission.
You can find conferences that are still accepting abstracts on our open calls for papers page, sorted by the closest deadline.
Written by the International Conference editorial team. Event dates and rules change, so always confirm details on the official event or government website.