A literature review is not a list of summaries. It is an argument about what a field knows, how it knows it, and where the gaps are — built from other people's papers. This workflow takes you from a blank page to a structured draft in six repeatable steps.
Who this guide is for
This guide is for students facing the chapter or assignment that sounds simplest and stalls longest: 'review the literature'. It suits a dissertation chapter, a standalone review paper, or the background section of a project report. The workflow assumes no special software beyond a search engine, a reference manager and a spreadsheet or document for your matrix — though it works even better with them.
Step 1: Frame the question before you search
One sentence: what exactly are you reviewing the literature about, for what population, setting or system, and to answer what question? Every inclusion decision later gets easier with this sentence pinned above your desk. Reviews that skip this step collect papers the way magpies collect foil.
Step 2: Build a real search strategy
List the key concepts in your question, then brainstorm synonyms for each.
Combine synonyms with OR and concepts with AND; test the string in Google Scholar and one subject database.
Record every search — database, date, string, results count — in a search log. Examiners and future-you will thank you.
Follow citations backwards (references of good papers) and forwards (the 'Cited by' link) to catch what keyword searches miss.
Here is a search string doing honest work, for a review on feedback timing in undergraduate science courses: ("formative feedback" OR "feedback timing" OR "delayed feedback") AND (undergraduate OR "higher education") AND (science OR STEM). Notice the pattern: synonyms for one concept grouped with OR inside brackets, concepts joined with AND, exact phrases in quotes. Paste it into Scholar for a first sweep, then adapt it to your subject database's own syntax — most databases have the same logic with slightly different symbols, and their help pages show the local dialect.
A review is a web, not a pile: the connections between papers are the argument.
Step 3: Screen with written criteria
Decide your inclusion and exclusion rules before screening: date range, language, study types, settings. Apply them first to titles and abstracts, then to full texts. Keep a simple count of what fell out at each stage — that count becomes the methods paragraph of your review.
Step 4: Extract into a synthesis matrix
Create a table with one row per paper and columns for question, method, sample, key finding and limitations. Fill it as you read. Patterns that are invisible across twenty PDFs become obvious in one table: who agrees, who contradicts, which methods dominate, and which questions nobody has asked.
Handy tip
Add a final column: 'So what for my study?' If a paper cannot fill it in one line, it probably belongs in the background section, not the core review.
What a synthesis matrix actually looks like
Paper
Method
Key finding
Limitation
Study A
Survey of 212 undergraduates
Students preferred feedback within a week
Self-reported preference, not measured learning
Study B
Randomised trial, two cohorts
Delayed feedback improved retention on delayed tests
Single institution, one subject area
Study C
Interviews with 18 lecturers
Workload, not belief, drives feedback delays
Small sample; no student data
An illustrative example with placeholder studies. Even in miniature the pattern jumps out: preference and learning point in different directions, and the lecturer study explains why practice lags both. That tension is a theme — and themes are what your review is made of.
One more writing habit separates synthesis from summary: the theme sentence. Every paragraph of a themed section should survive having its first sentence read aloud on its own — 'Evidence on timing is split between what students prefer and what testing shows.' If a paragraph's first sentence is a paper's name ('Smith et al. (2021) studied…'), you are summarising again. Useful stems: 'Across the quantitative studies…', 'Where X and colleagues found…, Y's team reported the opposite pattern…', 'The interview studies add a complication the trials cannot see…'
Hundreds of papers go in; one structured story comes out.
Step 5: Organise by theme, not by paper
Group your matrix rows into three to five themes — by finding, method or debate, never 'Paper 1 says… Paper 2 says…'. Each theme becomes a section that opens with the overall picture, presents the strongest evidence on each side, and closes with what remains unresolved.
Step 6: Write the gap, then the review
Draft your concluding gap paragraph first: what the field does not yet know, and why it matters. Then write each theme section so it points at that gap. A review structured this way reads as an argument with a destination — which is exactly what examiners reward.
Pro tips from people who mark reviews
Write something every week of the search, even if it is only the methods paragraph and the matrix. Reviews stall when reading and writing are treated as separate phases.
Keep a 'parking lot' document for fascinating papers that do not fit your criteria. Parking them formally stops them haunting your inclusion decisions — and they often seed your next project.
Put your search log and criteria in front of your supervisor early. An hour of correction at step 2 is cheaper than a rewrite at step 6.
Start your reference manager on day one and never type a reference by hand. The review that ends with a weekend of bibliography repair is a rite of passage you are allowed to skip.
Troubleshooting: where reviews go wrong
Drowning in results (thousands of hits). Your concepts are too broad or your criteria too kind. Tighten in this order: add a date range, require the concept in the title or abstract, then narrow the population. Record each tightening in the search log — the funnel is a finding, not a failure.
Finding almost nothing. Work the synonyms harder (ask how the field itself names the thing — check the keywords of the two closest papers), remove one AND concept at a time, and snowball: the reference list of one good paper is a pre-screened library on your exact topic.
Themes will not emerge. Your matrix is probably sorted by paper. Re-sort it by finding — group the rows that agree, then the rows that contradict, then the rows using different methods. Themes are agreements, disagreements and methods wearing a trench coat; sorting exposes all three.
The draft reads like a shopping list of studies. Apply the deletion test: remove any paragraph that could not move to a different position in the chapter without breaking the argument. Survivors are synthesis; the rest is summary wearing synthesis's clothes — rewrite those around claims, not papers.
None of these steps requires talent, only sequence. Question, search, screen, extract, organise, argue: run the loop once and the next review takes half the time.
Frequently asked questions
How long should a literature review be?
Long enough to establish the conversation and the gap — no longer. As a rough guide, in a dissertation the review chapter commonly runs at about a tenth to a fifth of the total length, but your institution's handbook and your supervisor's expectations outrank any rule of thumb.
How many sources do I need?
There is no magic number, and markers can tell the difference between coverage and padding. A focused undergraduate review might rest on 25–40 well-chosen sources; a doctoral review may engage hundreds. Stop when new searches stop changing your themes — that point is called saturation, and it, not a count, is the real finish line.
What is the difference between a narrative and a systematic review?
A narrative review (this workflow, used flexibly) selects and interprets literature to build an argument. A systematic review pre-registers a protocol, searches exhaustively against it, and reports every decision so another researcher could reproduce the result. Systematic reviews are the standard for clinical and policy questions; narrative reviews suit theory-building and dissertation chapters.
Can I use AI tools during a literature review?
For discovery help — suggesting synonyms, mapping a field's vocabulary, summarising a paper you then read properly — most universities allow it. The screening decisions, the reading and every word of the writing must be yours, and every source must be one you have actually opened. Disclose tool use if your institution asks.
When do I stop searching and start writing?
You do not, quite — the steps overlap. But the signal to shift your centre of gravity to writing is saturation: the same names and findings keep recurring, and new papers slot into existing themes instead of creating new ones.
The Fundora Editorial Team is a small group of educators, researchers and tech writers. We test the tools and methods we recommend, prefer free options, and update our guides when things change.
Your thesis topic will live with you for months, so choose it properly. Learn how to brainstorm widely, test ideas against interest, feasibility and contribution, and narrow a vague interest into a question you can actually finish.
A research proposal is a promise and a plan. Learn the sections reviewers expect, how to frame a sharp question, write a methodology that survives scrutiny, and the feedback loop that turns a draft into an approval.
Research papers are not novels. Learn the three-pass method — skim, read, interrogate — with time budgets, a comparison table and the five-question note that makes papers stick.
22 October 2026· 8 min read
The Fundora Letter
Never miss a post
One useful guide, every Sunday — the week's best study, research and AI-tool guides, delivered quietly to your inbox. No spam, no selling your address — unsubscribe any time.
Signups are handled by Brevo, our email service — your address is stored on Brevo's servers so we can send the letter. It is never sold, and every issue has an unsubscribe link.
Fundora uses cookies to analyse traffic and improve your experience. Learn more