Conference organisers are not looking for evidence that you can do really clever writing (save that for your article abstracts), they are looking for evidence that you can give an entertaining presentation.
Third, conference abstracts written in the future tense are off-putting for conference organisers, because they don’t make it clear that the potential presenter knows what they’ll be talking about.
But even then, they’re more likely to re-arrange their programme than to accept a poor quality abstract.
And you can’t take it for granted that your abstract won’t face much competition.
The abstract also contains information about your conclusion. Mikael Berndtsson and colleagues advise, "A typical [informative] abstract is about 250-500 words.
This is not more than 10-20 sentences, so you will obviously have to choose your words very carefully to cover so much information in such a condensed format." (Mikael Berndtsson, et al., "Thesis Projects: A Guide for Students in Computer Science and Information Systems," 2nd ed.
An abstract is a brief overview of the key points of an article, report, thesis, or proposal.
Positioned at the head of a paper, the abstract is usually "the first thing that individuals read and, as such, decide whether to continue reading" the article or report, wrote Dan W.
For example, we knew that the Creative Research Methods conference, like all general methods conferences, was likely to receive a majority of abstracts covering data collection methods.
So we stated up front, in the call for papers, that we knew this was likely, and encouraged potential presenters to offer creative methods of planning research, reviewing literature, analysing data, writing research, and so on.