>>> Blog
Literature Review Software by Stage: A Map of What Each Kind Does
Your supervisor says Covidence, a colleague swears by Rayyan, the library teaches Zotero, and the person at the next desk does everything in Elicit. These are not competing answers to the same question, and nobody has said so.
Here is the short answer. A review is a sequence of stages and most software is built for one of them: a database finds records, a reference manager keeps them, a screening platform decides which ones stay, and a writing tool drafts what you say about them. The names traded in corridors belong to different stages, and the trouble starts when one kind of tool is asked to do another kind's job.
The map: tools by stage
Each row is one tool and each column is one stage of a review in the order you meet them: search, manage references, screen, extract, appraise, analyse (mapping counts as analysis here), write, and report, which means the PRISMA flow diagram.
Legend: ✓ the vendor documents the stage · ◐ covers part of it · — not offered · n/d the vendor's pages do not say.
| Tool | Search | Manage | Screen | Extract | Appraise | Analyse | Write | Report |
|---|---|---|---|---|---|---|---|---|
| OpenAlex (data source) | ✓ | — | — | — | — | — | — | — |
| PubMed | ✓ | — | — | — | — | — | — | — |
| Scopus | ✓ | — | — | — | — | ◐ | — | — |
| Zotero (free) | — | ✓ | — | — | — | — | — | — |
| Mendeley | — | ✓ | — | — | — | — | — | — |
| EndNote | ◐ | ✓ | — | — | — | — | — | — |
| Covidence | — | — | ✓ | ✓ | ✓ | — | — | ✓ |
| Rayyan | — | — | ✓ | ✓ | ✓ | — | — | ✓ |
| Littview | — | — | ✓ | ✓ | ✓ | — | ✓ | ✓ |
| DistillerSR | ◐ | — | ✓ | ✓ | ✓ | — | — | ✓ |
| EPPI-Reviewer | ◐ | — | ✓ | ✓ | ✓ | ✓ | — | ✓ |
| ASReview (open source) | — | — | ✓ | — | — | — | — | — |
| Colandr (open source) | — | — | ✓ | ✓ | — | — | — | — |
| Nested Knowledge | ◐ | — | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Elicit | ✓ | ◐ | ✓ | ✓ | — | — | ✓ | ✓ |
| Consensus | ✓ | — | — | — | — | — | ✓ | — |
| SciSpace | ✓ | — | n/d | ✓ | — | — | ✓ | — |
| NVivo | — | — | — | — | — | ✓ | — | — |
| MAXQDA | — | — | — | — | — | ✓ | — | — |
| ATLAS.ti | ◐ | — | — | — | — | ✓ | — | — |
| VOSviewer (free) | — | — | — | — | — | ✓ | — | — |
| ResearchRabbit | ✓ | ◐ | — | — | — | ✓ | — | — |
| Connected Papers | ✓ | — | — | — | — | ✓ | — | — |
| PRISMA2020 flow diagram app | — | — | — | — | — | — | — | ✓ |
1.Literature search software
Search is where the vocabulary is loosest: a database, an open index, an AI assistant and a citation map all answer with a list of papers, and they are four different things.
| Kind | What it does at this stage | Tools in the map |
|---|---|---|
| Bibliographic database | You write the query, it returns every record that matches, and you export the set; this is the reproducible search a protocol asks for | PubMed, Scopus |
| Open index | An open catalogue of scholarly works with its own search and API; you meet it more often inside other tools than on its own | OpenAlex |
| AI research assistant | Takes a question rather than a query and returns the papers it judges relevant, from an index of its own | Elicit, Consensus, SciSpace |
| Citation-network tool | Starts from a paper you already have and finds what cites it, what it cites, and what sits nearby | ResearchRabbit, Connected Papers |
| Search from inside another tool | Runs a PubMed or other database query from inside a reference manager, a review platform or a coding tool; the half mark | EndNote, DistillerSR, EPPI-Reviewer, Nested Knowledge, ATLAS.ti |
The assistants and the citation tools are good at finding what you did not know to look for, and the database query is the one you report in the methods; most reviews need both.
2.Literature management tools
A reference manager holds the library: every record you export from a database, every PDF, and the citations you insert while you write.
| Kind | What it does at this stage | Tools in the map |
|---|---|---|
| Reference manager | Keeps records and PDFs, organises them into collections, and puts formatted citations and a bibliography into Word, Google Docs or LibreOffice | Zotero, Mendeley, EndNote |
| Library inside another tool | Keeps the sources you found or uploaded so you can reuse them across projects, without formatting a citation; the half mark | Elicit, ResearchRabbit |
The screening platforms import your export and most remove duplicates on the way in, and none of them replaces the reference manager: the library is still there when the review is over.
3.Systematic review screening software
Screening is the stage the review platforms were built for: the same records in front of two people, a decision from each, and a place to settle the disagreements.
| Kind | What it does at this stage | Tools in the map |
|---|---|---|
| Review platform | Title and abstract, then full text; two or more reviewers, conflicts settled, exclusion reasons kept, and the counts carried forward to the PRISMA diagram; most carry on into extraction and appraisal | Covidence, Rayyan, Littview, DistillerSR, EPPI-Reviewer, Nested Knowledge |
| Screening-only tool | Machine learning reorders the pile as you label, so the relevant records surface first; the rest of the review happens elsewhere, apart from Colandr's extraction stage | ASReview, Colandr |
| AI assistant with a screening step | The AI applies your criteria to each paper and shows its reasons; you accept or override | Elicit |
Four of the platforms are compared feature by feature in the comparison post.
4.Data extraction software for systematic reviews
Extraction turns every included paper into the same set of answers: who was studied, the setting, the method, the findings, whatever your form asks.
| Kind | What it does at this stage | Tools in the map |
|---|---|---|
| Review platform | A form per included paper with the PDF beside it, a record of who answered, and in several of them an AI first pass that you accept or correct | Covidence, Rayyan, Littview, DistillerSR, EPPI-Reviewer, Nested Knowledge |
| AI assistant | Columns you define across a set of papers, each answer tied to a quote or a place in the PDF | Elicit, SciSpace |
| Screening-only tool with extraction | Labels you define, filled from the full text with machine suggestions once about fifty papers have been coded by hand | Colandr |
In the platforms, appraisal is a special case of extraction and lives next door; in the assistants, the extraction table is what later becomes the report.
5.Critical appraisal
Two questions get tangled here, so keep them apart: which checklist to use follows the design of each included study, the subject of the appraisal post; this section is only about where you fill it in.
| Level | What it means | Tools in the map |
|---|---|---|
| Custom questions | You rebuild the checklist yourself as questions with the tool's own answer scales; any checklist, any design, no help from the software | Covidence, Littview, EPPI-Reviewer, Nested Knowledge |
| Pre-built form | The checklist arrives ready to fill, one form per framework, and each tool ships a different set | Covidence (RoB 1), Rayyan (RoB 2, MMAT), Littview (MMAT 2018), DistillerSR (Cochrane risk of bias among others), EPPI-Reviewer (Cochrane risk of bias coding tools, with risk of bias diagrams drawn from them), Nested Knowledge (several, more than one per review) |
| Native logic | The software works out the domain and overall judgements from your answers, as the official RoB 2 spreadsheet does | Rayyan, for RoB 2 |
Pick the framework by study design first, then look at the second row: if your checklist is not on a platform's list, it goes in as custom questions, and the methods section is none the worse for it.
6.Literature analysis software and literature mapping software
Analysis means two jobs that share a word: coding what the included papers say, and mapping how the papers of a field connect to each other.
| Kind | What it does at this stage | Tools in the map |
|---|---|---|
| Qualitative data analysis software | Codes the full texts of the included papers the way it codes interview transcripts: themes, queries, memos, summaries | NVivo, MAXQDA, ATLAS.ti |
| Mapping tool | Draws the network of papers, authors, journals or terms, linked by citation or co-occurrence, so you can see where a field clusters and what you have missed | VOSviewer, ResearchRabbit, Connected Papers |
| Synthesis inside a review platform | Meta-analysis, qualitative synthesis and evidence maps built on the data you extracted in the same tool | EPPI-Reviewer, Nested Knowledge |
| Analysis inside a database | Trends and citation counts over a set of results; the half mark | Scopus |
A statistical meta-analysis is its own job: if your platform does not run one, it happens in statistics software after extraction.
7.Literature review writing software
Writing is the stage the AI research assistants are really selling: give them the papers, get back a draft with citations. A few review platforms now draft from the review's own record instead.
| Kind | What it does at this stage | Tools in the map |
|---|---|---|
| AI assistant | Drafts a report or a passage with citations, from the papers it found or the ones you uploaded | Elicit, SciSpace, Consensus |
| Writing inside a review platform | The draft starts from the review's own records rather than from a prompt: its references, criteria, counts and extracted data are already there, so what you write matches the diagram and the tables | Nested Knowledge, Littview |
A citation plugin is not a writer: Zotero, Mendeley and EndNote insert and format references in your manuscript, which is why they sit under managing references and not here.
8.Creating a PRISMA flow diagram
A systematic review reports its counts in the PRISMA 2020 flow diagram and a scoping review in the PRISMA-ScR version, and the only question is whether the numbers come from the software or from you.
| Kind | What it does at this stage | Tools in the map |
|---|---|---|
| Review platform | Draws the diagram from its own screening record and asks you for whatever it did not see itself, such as a database searched elsewhere | Covidence, Rayyan, Littview, DistillerSR, EPPI-Reviewer, Nested Knowledge |
| AI assistant | Puts a diagram inside the report it writes | Elicit |
| Stand-alone generator | You type every number, it draws the diagram and exports it | PRISMA2020 flow diagram app |
If your review lives in a spreadsheet and a reference manager, the generator is the missing piece.
Which combination do you need
Three kinds of review, three sets of stages. The second column names kinds of tool rather than products, because the map already tells you which products cover which kind.
| Review | Stages required | Tools that cover them |
|---|---|---|
| Narrative review | Search, manage, analyse, write | A database or index; a reference manager; a coding or mapping tool when the literature is large; a writing tool if you want a drafted start |
| Scoping review | Search, manage, screen, extract, report | The same two, then a screening platform with extraction and a PRISMA diagram (PRISMA-ScR for the reporting); appraisal is optional |
| Systematic review | All eight | The same two, then a platform covering screening, extraction, appraisal and the diagram; meta-analysis in the platform or in statistics software; a writing tool if you want one |
FAQ
Three questions come up every time.
Is Zotero a literature review tool? Zotero is a reference manager: it holds the records and the PDFs and puts the citations in your manuscript. It does not search databases, screen or extract. For a narrative review, Zotero and a document are often enough; the moment two people have to screen the same records, you need a screening platform beside it.
Can one tool do the whole review? Not from database to manuscript. Nested Knowledge comes closest, with a mark in every column but reference management; Elicit covers the AI-first path from search to report. Everyone else combines: a database, a reference manager, one platform for the middle stages, and a writing tool if wanted.
What is the difference between a reference manager and a screening tool? A reference manager keeps your library and your citations for as long as you do research. A screening tool holds one review's records for the length of that review, records each reviewer's decision, and produces the counts for the PRISMA diagram. You export from the first into the second, and the first is still there when the review is over.
If you are choosing tools this week: write down which of the eight stages your review has, pick one tool per stage from the map, and check that each hands its output to the next, an export on the way out and an import on the way in. Then write the names into your protocol. The rest is settings.
More from the blog
Systematic Review Protocol: What to Write Before You Screen
Inclusion and Exclusion Criteria: What to Include and What to Leave Out
Critical Appraisal Tools for Systematic Reviews: Which One for Which Study Design
Systematic Review Software in 2026: Covidence, Rayyan, Elicit, and Littview Compared
Can AI Replace Your Second Reviewer? What the Evidence Says
Introducing Littview