A ResearchCollab field guide

From 300 papers to a critical, defensible review

A seven-stage method for building a literature review that survives your supervisor, your examiner, and peer review — with the AI shortcuts that are safe to take and the ones that will cost you.

Free to read in full 24 pages · about 35 minutes 9 templates by email

Why this guide exists

It is week six. You have 340 papers in a folder, roughly forty of which you have actually opened. Your notes live in three places and agree with none of them. Then your supervisor reads your first draft chapter and writes the sentence every researcher gets at least once: this is descriptive; where is your critique?

That comment is not really about writing. It is about process. A review reads as descriptive when it was built by collecting papers and summarising them one at a time, which is what almost everyone does the first time, because nobody teaches the alternative until you have already got it wrong.

This guide teaches the alternative. It walks through seven stages, and at each stage it tells you what artefact you should end up holding. Produce those artefacts as you go and the review largely writes itself, your methods section is already documented, and the gap you claim at the end is one you can actually defend.

Want the whole method? The complete 24-page playbook is free to read as well: The Literature Review Playbook.

The nine templates, free

The guide is the instructions. The templates are the work. Tell us where to send them and they arrive in a minute.

✓ On the way — check your inbox.

No sign-up needed to keep reading this page.

Stage 0Framing the question

A vague question produces an unmanageable result set and a review with no spine. Your question needs a structure that names its component concepts, because those concepts become your search blocks, your inclusion criteria, and eventually your themes.

What you should have at the end A one-sentence question, a structured framework, and written inclusion and exclusion criteria.

Criteria written after screening has begun are not criteria; they are rationalisations. Date and language limits are the two most frequently challenged decisions in any review, so if one exists for capacity reasons, say so and list it as a limitation. An examiner will accept a declared constraint far more readily than an unexplained one.

Stage 1Building a search that holds up

A search has two jobs that pull against each other: find everything relevant, and stay small enough to screen. The way you resolve that tension has to be visible to someone else, which is why the search is built in blocks rather than typed as a sentence.

What you should have at the end A documented search string per database, plus citation chaining and grey literature.
Record the count per database, per attempt The single most common gap in a methods section is the result count for each source on the date it was run. It takes five seconds to write down and cannot be recovered later, because databases are updated continuously and the same string will return a different number next month.

Stage 2Screening without losing the thread

Screening is where a review is most often quietly compromised, because it is repetitive, it happens under fatigue, and every decision is invisible unless you record it. The process itself is simple. The discipline is in the logging.

What you should have at the end A deduplicated library, a screening log with reasons, and a completed flow diagram.

Stage 3Appraising what you found

This is the stage most often skipped, and skipping it is what turns a review into an annotated bibliography. Appraisal is the difference between reporting that three studies found an effect and being able to say that two of them were at high risk of bias and the third was not.

Stage 4Extraction and synthesis

The single biggest upgrade available to most reviews is replacing free-form notes with one consistent extraction table covering every included study. Free-form notes force you to re-read everything when you sit down to write. A table lets you read across studies, which is where synthesis actually happens.

Stage 5Finding and testing the gap

Most reviews describe what has been studied clearly, then arrive at what is missing almost by accident in the last fortnight of writing. Gap finding is its own stage, run against your evidence table rather than against memory.

Weak gapMore research is needed on mobile health interventions for diabetes.
The same gap, made defensibleOf the 43 studies reviewed, 38 relied on self-reported adherence, and only 4 followed participants beyond six months. The consistent short-term effect reported across this literature may therefore reflect reporting behaviour rather than sustained adherence, a possibility no included study was designed to distinguish.

Stage 6Writing the review

The structural mistake that generates the descriptive comment is organising by paper. Smith found X, then Jones found Y, then Patel found Z. Each sentence is accurate, and the paragraph argues nothing. Strong reviews are organised by claim, with studies cited as evidence inside them.

Using AI without compromising the review

The difference between safe and unsafe AI use is not about capability. It is about whether the output can be verified cheaply. Terminology suggestions are checked the second you run them. A fabricated citation may not be caught until your viva.

The failure that ends careers, briefly Language models produce citations that look correct in every respect — plausible authors, plausible journals, a correctly formatted DOI — and do not exist. Every reference must resolve to a paper you have opened.

Take the method with you

The Literature Review Toolkit

Everything on this page as a printable guide, plus the nine editable templates — the ones that turn the method into artefacts you can hand to a supervisor.

Playbook · 24pp PDFQuick Start Checklist · 1pp 3 worksheets · Stages 0–16 templates · Stages 1–4

✓ On the way — check your inbox.

One email with the files. Unsubscribe in a click.

Scroll to Top