To write a conference abstract, check the submission rules, identify one clear contribution and summarise the question, approach, findings and significance within the word limit. If the work is ongoing, state its status accurately and submit only to a category that accepts it.
An abstract has to make a research project understandable in a small space. You may know months of background, several methodological complications and a list of possible implications. The reviewer needs a focused account of what your submission contributes to this particular conference.
This guide includes a copyable structure, two original fictional examples and a checklist for the submission form. Use the examples to understand the writing choices, then replace them with your own verified research.
Check the conference rules first
Allan Gaw’s Writing an Effective Abstract study guide, hosted by the University of Edinburgh, stresses following the organiser’s instructions. It discusses title, background, methods, results and conclusion as common components. The conference’s own requirements take priority over any general template.
| Rule to check | Why it matters |
|---|---|
| Submission category | A research paper, poster, workshop, panel and work-in-progress submission may ask for different information. |
| Word or character limit | Check what is counted, including headings, references and the title. |
| Required structure | Some events require named headings; others request a single paragraph. |
| Review arrangements | Follow instructions for author names, affiliations and anonymous review. |
| Results requirements | Find out whether completed findings are necessary or ongoing work is eligible. |
| Theme and audience | Make the connection to the relevant track clear. |
| Deadline and time zone | Record the actual cutoff, not just the calendar date. |
| Submission process | Check fields, file type, keywords, declarations and confirmation steps. |
Save these requirements beside the draft. An abstract written for one event may need substantial changes for another. Reusing the wording without checking the new brief can leave you answering the wrong question.
Choose one message before you write
Write a private sentence completing this prompt: “The contribution of this submission is…” Be specific enough that a reader can tell what is new or useful. A topic such as doctoral productivity is not yet a contribution.
A more focused message might concern a particular planning practice, population or methodological comparison. Your final claim needs to match the evidence you have. If you cannot support the proposed message, narrow it before trying to make the wording more persuasive.
The guide to finding a research gap can help you explain how your work relates to what is already known. For an abstract, select only the part of that context needed to understand your contribution.
A copyable conference abstract structure
The following prompts are an original drafting aid. They do not prescribe the headings or exact proportions your conference requires.
| Part | Drafting prompt |
|---|---|
| Context | What specific problem or debate does the submission address? |
| Question or aim | What did you investigate, argue, design or analyse? |
| Approach | What material, participants, sources or methods did you use? |
| Findings or contribution | What did the work establish? For eligible ongoing work, what is completed and what remains planned? |
| Significance | What can the audience take from this contribution, within its limits? |
For a short abstract, start with one or two sentences for each part and then edit to the required length. This is easier than compressing a whole introduction. Move quickly from context to your own work.
The shape varies by discipline. A humanities proposal may describe a corpus, interpretive approach and argument rather than participants and experimental results. A design submission may explain the artefact, evaluation and contribution. Keep the function of each part while using appropriate disciplinary language.
Example 1: a completed-study conference abstract
Fictional teaching example. The study, participants, interview material and findings below are invented to demonstrate structure. They are not evidence about doctoral students and must not be presented as real research.
Title: How doctoral students use weekly plans when research tasks change
Doctoral research often involves tasks whose scope changes as evidence emerges, creating a practical challenge for weekly planning. This study examined how doctoral students revise their plans when an intended task becomes uncertain or dependent on feedback. We conducted semi-structured interviews with 18 doctoral students across three departments at one university and used thematic analysis to examine their accounts of planning and revision. Participants described three recurring practices: defining a small observable output, keeping a separate list of tasks awaiting input, and reviewing unfinished work before setting the following week’s priorities. Their accounts also suggested that a plan could become unhelpful when incomplete tasks were repeatedly carried forward without reconsidering their scope. The analysis identifies planning as an ongoing process of interpreting research uncertainty, rather than simply allocating hours. Because the study draws on self-reported practices at one institution, it does not establish whether these practices improve completion rates. The presentation will discuss how these findings could inform conversations about realistic research planning in doctoral supervision.
This example gives the reader a concrete aim, material, approach and finding. It includes a limit that directly affects interpretation. The final sentence names what the presentation will discuss, without using that promise as a substitute for the completed study’s findings.
| Component | Where it appears |
|---|---|
| Context | The opening sentence identifies a planning problem specific to changing research tasks. |
| Aim | The second sentence asks how students revise plans. |
| Approach | The interview sample, setting and analytic approach are stated. |
| Findings | The abstract names the practices identified and the problem of repeatedly carrying tasks forward. |
| Limit and significance | The ending bounds the claim and explains the supervision relevance. |
If this were your real project, you would verify every detail against the study records and analysis. You would also check that the language accurately reflects the analytic approach and any requirements your discipline has for reporting it.
Example 2: an eligible work-in-progress submission
Fictional teaching example. The following project and progress details are invented. Use this type of wording only when the conference explicitly accepts work in progress, proposals or an equivalent category.
Title: Designing a study of energy measurement in small research scripts
Researchers interested in reducing computational energy use need comparisons that make workload and measurement choices explicit. This work-in-progress project is developing a protocol for comparing two implementations of the same data-processing task on a single machine. The current stage includes a defined workload, a draft recording procedure and a list of potential sources of measurement variation. The next stage will pilot the protocol, assess whether repeated runs produce sufficiently stable measurements, and revise the procedure before collecting comparative data. No comparative energy results are available at submission. The proposed presentation will examine the protocol’s design choices, including the treatment of background activity and the relationship between runtime and energy measures. Feedback is sought on whether the planned comparisons address the research question and which sources of variation should be prioritised. The contribution is a protocol under development, with conclusions about energy differences reserved for the subsequent analysis.
This abstract gives the project a purpose while making its status explicit. It states what exists now, what is planned and what feedback would be useful. It does not invent results or imply that an unfinished comparison has already established an energy saving.
Some conferences would reject this because they require completed findings. Others have a dedicated development category. Eligibility comes from the call for submissions, not from how confidently you word the abstract.
Write the findings before polishing the introduction
For a completed study, draft the findings section from your analysis first. What can you actually say? Keep the unit of analysis, comparisons and uncertainty visible where they matter. Then write the question and methods needed to understand those findings.
This order can reveal mismatches. An introduction may promise a broad account of all doctoral experience while the study supports a narrower conclusion about one setting. Fix the scope before cutting words.
For an argument-led paper, identify the argument and the evidence used to develop it. Avoid ending with “the implications will be discussed” if you can state the actual implication. Reviewers need enough substance to understand what they would be accepting.
Your literature review matrix can help you select the context, but an abstract rarely has room for a catalogue of related studies. Include references only as the submission rules permit.
Edit for specificity and space
On the first editing pass, remove background that does not help the reader understand your question. Replace broad statements about a topic’s importance with the specific problem your work addresses.
On the second pass, check verbs and claims. “Explores” may accurately describe an exploratory project; “demonstrates” requires a stronger basis. Make sure the level of certainty stays consistent from findings to conclusion.
On the third pass, remove repetition and empty phrases. Keep information that identifies your material, approach and contribution. Cutting those details can create a smooth paragraph that says very little.
| Less informative wording | More specific drafting direction |
|---|---|
| This important study investigates an important issue. | Name the issue and what is being investigated. |
| A range of methods was used. | Identify the relevant design or analytic approach. |
| Interesting findings emerged. | State the finding that supports the contribution. |
| Results will be presented. | For completed research, include the main result now. |
| This proves the approach works everywhere. | State what the evidence supports in the studied setting. |
The right-hand column gives directions, not sentences to paste unchanged. Choose terms that fit your discipline and your actual work.
Give the abstract a useful title
A title should help a reader identify the subject and contribution. Name the material, relationship, argument or setting when that information is central. Avoid a clever phrase that only becomes understandable after reading the abstract.
Check whether the conference has a title length limit. Keep specialist abbreviations out unless your intended audience is likely to recognise them and the instructions allow them.
Ask a colleague to read just the title and tell you what they expect the submission to cover. If their expectation differs substantially from your abstract, adjust one or both.
Get feedback with a focused request
Send the abstract and the relevant submission instructions to a supervisor or colleague. Ask whether the contribution is clear, whether the claims match the evidence and whether any essential information is missing.
A reader outside your immediate project can identify unexplained terms. A subject specialist can catch methodological or interpretive problems. Their feedback serves different purposes, so tell each person what you need.
If feedback pulls the draft in different directions, return to the brief and the central contribution. The guide to turning supervisor feedback into an action plan can help you separate changes you can make now from questions to resolve.
Check the submission form before the deadline
Count the words using the final text, then check the submission system’s count if it provides one. Character limits and the treatment of headings can differ from your document editor. Leave enough time to resolve a discrepancy.
Paste the text into the form and review the preview. Check italics, symbols, line breaks and any structured headings. Verify the author order, affiliations and corresponding-author details with the people involved.
Complete required declarations accurately and obtain any necessary co-author agreement. Save the submitted version and confirmation. Do not assume an unfinished form has been submitted merely because the text is saved.
Frequently asked questions
How long should a conference abstract be? Follow the event’s stated limit. There is no universal length, and a template from another conference may have different requirements.
Can I submit without results? Only if the relevant category permits the stage of work you have reached. Make that stage clear. Do not replace missing findings with predictions written as facts.
Should I include citations? Follow the instructions. If references are allowed, use only what the reader needs and check whether they count towards the limit.
What comes after acceptance? Check the assigned presentation format and practical requirements. For an oral talk, the guide to your first conference presentation covers preparation. If meeting new researchers feels daunting, networking as an introvert offers a starting point.
Begin with the submission rules and the contribution you can support. Build the abstract around those two anchors, then check that every sentence helps a reviewer understand the work.
Featured image: Kelly Sikkema on Unsplash.