Should you include preprints and conference papers in a literature review?

Preprints and conference papers can be valuable sources, especially in fast-moving fields. They can also create uncertainty because review status, version history, and evidence quality may differ from journal articles.

The question is not whether preprints and conference papers are always good or bad. The useful question is whether they fit your review question, field, and method.

This guide explains when to include preprints and conference papers in a literature review and how to handle them responsibly.

A preprint is a manuscript shared publicly before formal peer review or journal publication. It may later become a published article, remain unchanged, be revised, or never be published in a journal.

Preprints can help researchers:

• See new work early.
• Track emerging methods.
• Follow fast-moving debates.
• Identify future published papers.
• Understand developing fields.

But preprints should be labeled clearly. They are not the same as peer-reviewed journal articles.

A conference paper is a research paper presented or published through a conference. In some fields, conference papers are major scholarly outputs. In others, they may be preliminary or less central.

Conference papers vary by:

• Peer-review process.
• Length.
• Detail.
• Publication venue.
• Field norms.
• Whether a later journal version exists.

The review should treat conference papers according to field expectations, not a single universal rule.

Include preprints when early evidence is important and your review protocol allows them. This is common in fast-moving areas where journal publication lags behind research activity.

Preprints may fit when:

• The topic is new.
• Published literature is limited.
• The field expects preprint sharing.
• The preprint contains important methods or data.
• You clearly label its status.
• You check for newer versions.

Do not include preprints only because they are easier to access.

Exclude preprints when the review requires peer-reviewed evidence or when the preprint lacks enough detail to assess.

Reasons to exclude may include:

• Peer-reviewed studies are required.
• The preprint is outside scope.
• Methods are unclear.
• A newer journal version exists.
• The source has been withdrawn.
• The claims are too preliminary for your purpose.
• The review question has high-stakes implications.

If preprints are excluded, state that in the criteria.

For criteria design, see inclusion and exclusion criteria for literature reviews.

Include conference papers when they are important scholarly outputs in the field or when they provide evidence not available elsewhere.

Conference papers may fit when:

• The field values conference publication.
• The paper includes enough method detail.
• It presents relevant results.
• It is part of a major research thread.
• The review includes conference proceedings.
• A later journal version is not available.

This is especially relevant in areas where conferences move faster than journals.

Version checking is essential for preprints and conference papers. A source may have a preprint, conference version, and later journal version.

Check:

• DOI.
• Title changes.
• Author list.
• Publication date.
• Preprint server.
• Conference proceedings.
• Journal version.
• Corrections or retractions.
• Withdrawn status.

If a later peer-reviewed version exists, decide which version the review should cite.

For source-status checks, see how to check whether a paper has been corrected or retracted.

Label source status clearly in notes and, when relevant, in the review text. Readers should know whether evidence comes from a preprint, conference paper, journal article, or report.

Record:

• Source type.
• Version.
• Peer-review status.
• Publication venue.
• Date accessed if needed.
• Later version status.
• Inclusion reason.
• Evidence use.

This protects the review from treating all sources as equal.

Preprints can add recent evidence, but they may need cautious wording. If a claim depends mainly on preprints, say so.

Use careful language:

• "Early preprint evidence suggests..."
• "Conference papers in this area report..."
• "Peer-reviewed evidence remains limited..."
• "A later journal version should be checked before final citation..."

The wording should match the source status and evidence strength.

For evidence weighting, see risk of bias vs study quality.

AI can help identify source type, check for possible later versions, summarize methods, and compare preprints with published papers. It should not decide source status without verification.

Use AI to ask:

• Is this source a preprint, conference paper, or journal article?
• Does a later version appear to exist?
• What method and evidence does it report?
• Does it support my claim?
• What status should I verify manually?

Then check publisher pages, DOI records, and official source pages.

Turn the advice into a repeatable workflow by defining the decision you need to make, the evidence required for that decision, and the record that will prove how the decision was made. In literature review work, the problem is rarely one missing tool. The problem is usually that search, reading, checking, and writing happen in separate places without a shared rule.

Use a short operating routine:

• Name the review question or subquestion.
• Define the source set you are working from.
• Decide what counts as enough evidence for the next step.
• Apply the same criteria to every paper in that step.
• Mark uncertain cases instead of forcing a clean answer.
• Keep source locations for claims that may enter the final review.
• Review the workflow after each major search, screening, or writing session.

This routine keeps the work moving without making the review careless. It also gives supervisors, collaborators, and future you a way to understand why the source set changed.

Record the pieces that would be hard to reconstruct later. You do not need a diary of every click, but you do need enough detail to explain the path from question to source to claim.

For this topic, the most useful record usually includes scope, sources, decisions, verification, and next actions. Add the date, tool or source used, reviewer status, and next action. If AI assisted the step, write down what it helped with and what a human checked.

The record should distinguish discovery from evidence. A tool may help find a paper, but the paper itself must support the claim. A summary may help triage a source, but the original source should support any statement that appears in the literature review.

Before writing, check whether the workflow has produced usable evidence or only useful notes. Notes help you think. Evidence supports a sentence.

Ask:

• Which claim will this source support?
• Is the claim narrower than the evidence?
• Have methods, sample, outcome, or concept details been checked?
• Are limitations visible?
• Are conflicting papers handled rather than ignored?
• Is the citation real, current, and relevant?
• Can another reader understand how this source entered the review?

If the answer is unclear, keep the point in notes rather than moving it into the draft. This is the small pause that prevents AI-assisted research from becoming polished but weak writing.

WisPaper can help researchers find and inspect academic papers when building a review source set. Deep Search, Scholar Agent, and Inspiration Discovery support natural-language academic search, while paper cards show source labels, summaries, authors, publication details, and preview images.

Those source labels and paper details can support first-pass triage, especially when researchers need to separate journal articles, conference papers, and other source types for closer checking. Saved or uploaded papers can be kept in My Library, and Library QA can answer questions based on the user's own paper set.

WisPaper can help organize source inspection, but researchers should verify version status, peer-review status, and citation suitability before final use.

Try WisPaper