Skip to content

Structuring a paper

Compressing a whole paper into 250 useful words

Four moves — background, method, result, implication — with the result sentence doing most of the work.

An abstract states the problem, what you did, what you found, and what it means, in that order. Write it last, from the finished paper. Give a sentence or two to background and method, and the largest share to results — with actual findings in them, not a promise that findings will be discussed.

THE PROCESS

Step by step

Write it after the paper is done

An abstract drafted before the results exist becomes a description of your intentions. Wait until the argument is settled, then write the abstract from the finished text. It takes about twenty minutes at that point and several frustrating hours before it.

Pull one candidate sentence from each part

Take the sentence that best states the problem from your introduction, the design from your methods, the headline finding from your results, and the main implication from your discussion. Lay those four sentences out on their own. You now have a skeleton that is guaranteed to match the paper.

Set up the problem in one or two sentences

Start close to your question, not at the edge of the field. One sentence of context and one that names the unresolved issue is usually enough. If your first sentence would work at the start of any paper in your discipline, cut it.

Compress the method to what a reader needs to judge it

Name the design, the population or material, the sample size, and the main analysis. Leave out instrument settings, software versions, and recruitment detail — a reader deciding whether to open the paper needs to know the shape of the evidence, not how to reproduce it.

Put the findings themselves in the results

This is the sentence people actually read, so it has to carry content: direction, size, and the comparison the effect is relative to. Include the key numbers if the field expects them. Two or three sentences here is a reasonable share of a 250-word abstract.

End on an implication you can defend

Say what follows for theory, practice, or the next study, sized to the evidence you have. One sentence is normally enough. If the closing line could be attached to a paper with the opposite finding, it is too general to keep.

Cut to the limit without losing a move

When you are over the word count, trim the background first, then the method, and only then the implication. Delete throat-clearing phrases such as “it is well established that” and “the purpose of this study was to”. Never solve a word-count problem by removing the results.

Choose keywords the title does not already contain

Keywords are for retrieval, so repeating words already in the title wastes them. Add synonyms, the method name, the population, and the broader field term someone might search from a neighboring discipline. Check whether your journal requires terms from a controlled vocabulary.

The four moves and how much room each one gets

Almost every research abstract does the same four things: it establishes the problem, states what was done, reports what was found, and says what that means. The moves are stable across fields; only the proportions shift. In a 250-word abstract, a workable split is roughly 15 percent background, 25 percent method, 45 percent results, and 15 percent implication.

Those proportions are the whole discipline of abstract writing. Most weak abstracts are top-heavy — three sentences establishing that the topic is important, two on method, one vague line about results. Reversing that balance is usually the single largest improvement available, and it costs nothing but rearrangement.

The move structure also tells you what to cut when you are over the limit. Background compresses well because readers of the abstract already know the field. Results compress badly, because there is nothing else in the abstract a reader can substitute for them.

  • Background — the unresolved problem, in one or two sentences.
  • Method — design, sample, and the main analysis, without procedural detail.
  • Results — direction, size, and comparison; the largest share of the words.
  • Implication — what changes for theory, practice, or the next study.

Why the results sentence decides everything

Search engines, conference committees, and readers scanning a table of contents all make their decision on the results sentence. An abstract that says “results are presented and their implications discussed” has told the reader nothing and given them no reason to open the paper. It is the most common and most expensive fault in academic abstracts.

Weak: “Differences between the two groups were analyzed and the results are discussed in relation to existing theory.” Stronger: “The intervention group improved on the accuracy measure while the control group did not, and the difference persisted at the three-month follow-up.” The stronger version names direction, comparison, and durability — and a reader who stops there has still learned something true.

Confidentiality is occasionally a real constraint, particularly for conference abstracts submitted before analysis is complete. Even then, state the direction of the preliminary finding rather than deferring entirely. Committees reject abstracts with no findings far more often than they reject abstracts with modest ones.

Structured abstracts, and what the headings change

Many journals, especially in medicine and psychology, require labeled sections: Background, Methods, Results, Conclusions, sometimes with Objective or Design as separate headings. The content is identical to an unstructured abstract; the labels simply make the moves explicit and enforce the proportions for you. Use the exact labels the journal lists, since they vary — some ask for Purpose, others for Objective or Aim.

Structured formats punish padding, because a sentence of general context sitting under a Results heading is immediately visible. If your journal allows either format, drafting in the structured version and then removing the labels is a reliable way to produce a well-balanced unstructured abstract. Going the other way is harder, because an unstructured draft hides its imbalance inside the transitions.

Conference abstracts follow their own conventions and often have tighter limits — sometimes 150 words or fewer — with a submission portal that counts characters rather than words. Read the call for abstracts before drafting; a rejected submission is usually a formatting failure, not an intellectual one. Where review is blinded, check that the abstract text does not name your institution or your cohort.

What does not belong in an abstract

An abstract has to stand alone, because it will be read detached from the paper in search results and databases. That rules out anything that depends on the surrounding text: citations in most formats, references to figures or tables, undefined abbreviations, and phrases such as “as described above”. Reading the abstract aloud with the paper closed is a quick way to catch anything that dangles.

It also rules out material that is not in the paper. An abstract is a proportional representation of the article, not a trailer for it. If the abstract mentions a secondary analysis, the paper has to report one; if the abstract claims a practical implication, the discussion has to argue for it. Reviewers notice the mismatch quickly.

Abbreviations deserve particular care. A term you use once does not need shortening at all, and one you use four times should be spelled out at first mention within the abstract itself, then again at first mention in the body — the two texts are indexed separately, so each has to be self-sufficient. If a term would need explaining twice for the sake of two uses, write it out instead.

Word limits, keywords, and how indexing uses them

Most journals cap abstracts somewhere between 150 and 300 words — check the one you are submitting to, because the limit is enforced at desk-check and the fix is rushed if you leave it. Some count the structured headings toward the total, and some count numbers and units in ways that surprise you. Paste your draft into the submission form early to find out.

Title and abstract carry almost all of the retrieval weight for your paper. Words that appear in both are strongly weighted, so the terms a reader would search for should appear naturally in the first two sentences rather than only in the keyword field. This is a reason to write plainly, not a reason to stuff terms in.

Keywords should extend the title rather than echo it. Include the method, the population, the theoretical framework, and at least one broader term that a researcher from an adjacent field would use for the same thing. If the journal draws on a controlled vocabulary such as MeSH, select from that list even when your own phrasing feels more precise.

FAILURE MODES

What goes wrong, and what to do instead

Writing “results will be discussed” instead of reporting the results.

State the finding: direction, magnitude, and what it is being compared with. Even a preliminary result stated plainly beats a placeholder.

Spending the first three sentences establishing that the topic matters.

Cut to one sentence of context and one that names the unresolved problem. Readers of an abstract already accept that the field exists.

Using abbreviations or citations the abstract never explains.

Spell out every abbreviation on first use inside the abstract, and avoid citations unless the journal explicitly permits them. The abstract has to work when it appears alone in a database.

Pasting sentences verbatim from the introduction and discussion.

Rewrite them for the compressed context. Sentences built for a paragraph carry setup that wastes words once the paragraph is gone.

Claiming more in the abstract than the paper actually supports.

Match the hedging in your discussion. If the paper says “may contribute to”, the abstract cannot say “demonstrates”.

Discovering the word limit after the abstract is written.

Check the author guidelines before drafting and write to that number. Trimming from 400 words to 200 damages structure; writing to 200 does not.

Questions writers ask about this

How long should an abstract be?

Most journals cap abstracts at 150 to 300 words, with 250 the most common ceiling — check the guidelines for the specific journal, since the limit is enforced automatically at submission. Thesis abstracts are usually set by the university, often around 300 to 500 words. Conference abstracts are typically shorter and sometimes counted in characters.

What tense should an abstract be in?

Use past tense for what you did and found — “participants completed”, “accuracy improved”. Use present tense for the problem statement and for the implication, since both describe things that are still true. A mixed abstract is correct; a uniformly present-tense one usually reads as a proposal.

Can I use “we” in an abstract?

In most fields yes, and it is often clearer than the passive alternative — “we recruited 84 participants” rather than “84 participants were recruited”. A few journals still prefer impersonal constructions. Scan the abstracts in a recent issue and follow what you see there.

Should I write the abstract first or last?

Last, without exception for the final version. You can sketch a working abstract early to keep yourself honest about the argument, but rewrite it once the results are settled. Abstracts written first tend to describe the study you planned rather than the one you completed.

What is the difference between an abstract and an introduction?

The abstract summarizes the entire paper, including the results and conclusion, and stands alone. The introduction sets up the problem and stops at your research question — it deliberately does not reveal the findings. They overlap only in the background move, and even there the abstract version should be shorter.

One workspace
for the whole paper

Draft with structure, cite as you write, and keep a verifiable record of how the document came together. Copyeditor is in beta — apply and we’ll reach out as spots open.

Apply for beta

*Beta opens this season — starting with students and researchers.

The Copyeditor writing workspace