Decide the question before you search
Almost every stalled review began with a topic rather than a question. A topic has no end point, so reading continues indefinitely and every article feels relevant. A question can be answered, which means you can tell when you have enough.
Convert your topic into a question with boundaries in it: a population, an intervention or exposure, and an outcome. Not nurse burnout, but whether scheduled debriefing reduces reported burnout in hospital nurses. The second one tells you what to search for and, crucially, what to exclude.
Write it at the top of a blank document before opening any database. Everything that follows either serves that sentence or gets left out, and having it visible stops the drift that consumes weekends.
Search once, properly, on Saturday morning
Use your library's databases rather than a general search engine, because you are paying for them and because the filters are the point. Set the date limit your rubric requires, restrict to peer-reviewed, and search on the concepts in your question rather than on the whole sentence.
Two hours here replaces two days of scattered reading later. Aim to finish the morning with somewhere between twelve and twenty candidates: enough to see a pattern, few enough to actually read. If you have ninety, your question is too broad and needs narrowing before you go further.
Then screen ruthlessly by abstract before reading anything in full. Most candidates will not survive that screen and that is a success rather than a loss. You are looking for the eight to twelve that genuinely speak to your question.
- Question written down first, with population, intervention and outcome in it
- Library databases, date-limited and restricted to peer-reviewed
- Twelve to twenty candidates by lunchtime, not ninety
- Screen by abstract before reading a single full text
- A matrix built as you read, one row per source
- Organised by argument, never by author, before any prose is written
The matrix is the whole trick
Build a table as you read, one row per source, with columns for the citation, the population, the method, the key finding, and any limitation you noticed. Fill a row immediately after reading each article, while it is still fresh, rather than intending to come back.
This does two things. It stops you rereading, which is where most of a weekend disappears, and it makes the patterns visible: when you look down the finding column you can see which studies agree, which disagree, and where the gap is. That view is impossible when your notes are prose scattered across a document.
The matrix also becomes your evidence when somebody asks how you selected sources, and on Sunday it is the thing you write from. You will not open the articles again.
Organise by argument, not by author
The most common structural failure in student reviews is a series of paragraphs each summarising one study. Smith found this. Jones found that. Patel found something else. It is thorough, it is exhausting to read, and it demonstrates none of the synthesis the rubric is asking for.
Instead, look down your matrix and name the two, three or four things the literature collectively says. Those become your sections. Each section then draws on several sources at once, comparing them, noting where they disagree and why that might be.
The test is simple: if a paragraph cites only one source, it is a summary rather than synthesis, and it probably belongs inside a paragraph that cites three. That single rule transforms most student reviews.
Sunday: write, then verify
Write from the matrix rather than from the articles. This feels like cheating and it is exactly right: you already did the reading, and going back into the full texts is how Sunday afternoon disappears. Take each argument section in turn and write it from the rows.
Then verify. Open every source once more and check two things: that it exists as you have cited it, and that it actually says what you have attributed to it. This is not optional any more, because references that look perfect and describe nothing real have become common, and faculty now check.
Finish by reading the whole thing against the rubric row by row, pointing at the sentence that satisfies each criterion. If you would rather somebody else ran that final check, that is what feedback is for, but the check itself takes five minutes and it is the highest-value five minutes in the process.
Questions people actually ask
How many sources does a course-length review need?
Whatever your rubric says, and if it doesn't say, eight to twelve substantive sources is a reasonable range for a course assignment. More is not automatically better: a review that synthesises ten sources well beats one that summarises thirty. If you're finding ninety candidates, the question is too broad rather than the field being large.
How do I know when to stop searching?
When new results keep returning the same studies you've already found. That saturation point is a real signal and it arrives sooner than people expect on a well-bounded question. If it never arrives, the question needs narrowing, because an unbounded topic will keep producing new material indefinitely.
What if the studies contradict each other?
That's the most interesting thing you can find, and it's what synthesis is for. Say so explicitly, then look at why: different populations, different measures, different time frames. A review that identifies and explains disagreement demonstrates far more than one presenting a tidy consensus that the evidence doesn't actually support.
Can I use AI tools to find sources?
To generate search terms and suggest directions, yes, and it's genuinely useful for that. Not to produce citations, because fabricated references look flawless and are now common enough that faculty check. Whatever you use to find things, every source in your list has to be one you personally opened and read.
