Learning Objectives

  • Know the difference between indicative and informative abstracts
  • Understand the five common rhetorical moves used in abstracts
  • Know the four sub-moves commonly used within the introduction move
1

Indicative and Informative Abstracts

Abstracts may be broadly grouped into two types based on how much detail they provide. Select each tab to understand the characteristics of each type and see an example.

Indicative abstracts provide enough information to indicate what the research is about, but do not give full details of the findings. They aim to interest curious readers and encourage them to attend the presentation or read the full paper.

Common in: Promissory conference submissions (particularly in humanities and linguistics), some social science venues, and review articles where the scope rather than the findings is the primary contribution.

Typical signals:

  • "This paper discusses…"
  • "The study examines…"
  • "Preliminary results will be presented…"

Limitation: Reviewers who expect quantified findings may perceive an indicative abstract as incomplete or evasive.

Informative abstracts provide full details of the method and the results. They give readers a complete summary of the research — readers do not need to read the full paper to know what was found.

Common in: Computer science, engineering, medicine, and natural sciences. Informative abstracts are the expected norm at major venues such as ACM, IEEE, and Springer journals.

Typical signals:

  • "We trained a model on 50,000 samples and achieved 94.2% accuracy…"
  • "Results showed a significant difference (p < .001)…"
  • "The proposed algorithm reduces computational cost by 38%…"

Advantage: Readers can quickly assess whether the paper is relevant to their work. Reviewers can evaluate the quality of the findings without reading the full text first.

The same study presented in each style:

Indicative version

"This paper examines the use of biosignals to detect foreign language anxiety in a VR conversation system. The study compares native and foreign language conditions and discusses implications for adaptive language learning technology."

Informative version

"In a within-subjects study (N = 40), L2 conversation elicited significantly higher state anxiety than L1 (p < .001). Six physiological measures — BPM, MeanNN, LF, LF/HF, SampEn, and Saccade Amplitude — showed significant L1–L2 differences, providing usable biosignal proxies for cognitive load and stress in VR language learning contexts."

Notice how the informative version gives readers specific numbers and named measures. The indicative version only tells readers what the paper is about.

2

The Five Rhetorical Moves

Researchers across disciplines have identified a set of recurring rhetorical moves — conventional sections that serve a predictable communicative purpose — in research abstracts. Five moves and four sub-moves are commonly recognised. Expand each item to learn about the move.

The introduction move contextualises the research. It may include up to four sub-moves:

  • Problem: A problem in the real world or in the research field that needs to be addressed ("Access to speaking partners is limited in many contexts…")
  • Research gap: A gap in the existing literature — something not yet studied or resolved ("No previous work has examined biosignal signatures of FLA in VR systems…")
  • Research niche: The specific angle the current research takes to fill that gap ("We focus on consumer-grade PPG and eye-tracking sensors…")
  • Overview: A brief preview of what the paper covers ("This paper presents a VR system and a within-subjects study…")

Not all four sub-moves are required. In computer science, introductions are often very brief or omitted entirely if the research area is well established.

The purpose move states the aim, research question, or hypothesis explicitly. It answers the question "What did you set out to do?"

Example: "We present a VR system in which participants converse with an EVA and examine how native (L1) versus foreign (L2) conversation differentially affects self-reported anxiety, sense of presence, and physiological arousal."

A clear purpose move helps reviewers assess whether the results match the aim. If the purpose is obvious from the result, the purpose move may be omitted — but when in doubt, include it.

The method move describes the procedure, dataset, or design used to produce the results. It answers the question "How did you do it?"

Example: "A pre-study focus group with three experienced language educators informed EVA design and task selection. In a within-subjects study (N = 40), participants completed conversational tasks while physiological data were recorded."

The method move is where rigour is demonstrated. It should include enough detail for readers to assess whether the results are trustworthy. In a short traditional abstract, the method is often compressed; in a structured abstract, it may occupy multiple headings.

The results move reports the findings or the artefact produced. It answers the question "What did you find or create?"

Example: "L2 conversation elicited significantly higher state anxiety than L1 (p < .001). Six physiological measures showed significant L1–L2 differences consistent with heightened stress."

The results move is where substance is demonstrated. Results should be quantified wherever possible. In informative abstracts, this is the most important move. Omitting results is only acceptable in promissory or indicative abstracts.

The discussion move interprets the results and states their implications. It answers the question "What do these results mean?"

Example: "These findings establish: 1) EVA conversation in VR offers a viable paradigm for studying FLA and 2) consumer-grade PPG and eye tracking sensors provide usable proxies for cognitive load and stress."

The discussion move is where significance is demonstrated. It is included when readers might not immediately understand the implications of the results. In short papers, the discussion may be minimal or merged with the results.

3

Classify the Move

Read each sentence and identify the rhetorical move it belongs to.

"We collected a corpus of 500 academic abstracts from ten disciplines and annotated them for rhetorical moves using a validated coding scheme."

Correct! This sentence describes the data collection and annotation procedure — it tells readers how the research was conducted. This is the Method move. The reference to a validated coding scheme also signals rigour.
Not quite — review the material and try again. This sentence describes the data collection and annotation procedure — it tells readers how the research was conducted. This is the Method move. The reference to a validated coding scheme also signals rigour.

"Despite the growing adoption of large language models in education, their effect on learner writing quality in L2 contexts remains understudied."

Correct! This sentence identifies a gap in the existing literature — something that has not been adequately studied. Identifying a research gap is a sub-move of the Introduction move. It answers the question: why is this research needed?
Not quite — review the material and try again. This sentence identifies a gap in the existing literature — something that has not been adequately studied. Identifying a research gap is a sub-move of the Introduction move. It answers the question: why is this research needed?

Review

Before writing your abstract, decide which moves to include. Expand each move below and ask yourself: should I include this in my abstract?

Include it if: the research area is not widely known to your audience, or if you need to motivate the research. Omit it if: the area is well established and your audience will immediately understand why the research matters. In computer science, short or absent introductions are common.

Include it if: the aim is not immediately obvious from the results, or if a clear research question strengthens the abstract. Omit it if: the result and the purpose are essentially the same statement — stating both creates redundancy.

Almost always include it. Omit it only if: the method is universally known to your audience and adds no value. For experimental and empirical work, the method move is essential for establishing rigour.

Always include it for informative abstracts. Omit it only in promissory or indicative abstracts where results are not yet available. For computer science articles, the results move is the most important move in the abstract.

Include it if: readers might not understand the implications of the results without guidance, or if you want to make the significance of the work explicit. Omit it if: the implication is self-evident and the abstract is already at its length limit.

Proceed to Unit 4: Structure of Abstracts when ready.