Systematic Review Literature Management:Keep the Decisions, Not Just the PDFs
A few weeks into screening, the questions start piling up: "Why did I include this paper?" "Where did I write down the reason I excluded that one?" What actually goes missing in a systematic review isn't the PDF files. What goes missing are the decisions you made about those PDFs. This article shows how to structure your literature management so those decisions never get lost.
Published: 2026-07-22
What you're managing is files plus history
In a systematic review, several pieces of information accumulate around every paper: which search it came from, whether it's a duplicate, the title/abstract screening decision, the full-text decision, the reason for exclusion, and — if included — the extracted data and risk-of-bias assessment.
A well-managed review is one where all of that history stays attached to the paper. Even if every PDF is accounted for, the review has failed as a record the moment that history breaks.
Split the work across three layers of tools
In practice, no single tool handles everything. A three-layer division of labor works better.
There's a layer for references and citations (Zotero, EndNote, and the like), a layer for screening decisions (a dedicated review tool or a spreadsheet), and a layer for reading and decision notes — where you open the PDF, check the content, and record why you decided what you did. That third layer is the one most people neglect.
One ID per paper is the first defense against losing papers
Confusion starts once the same paper exists in multiple versions — different filenames, duplicate downloads, records pulled from different databases.
At the deduplication stage, give every paper a single unique ID and link everything that follows — decisions, reasons, extractions — to that ID. It sounds like a small detail, but if this step slips, your PRISMA numbers will stop adding up too.
Record exclusion reasons on the spot, in words
The reasons you exclude papers at the full-text stage will be needed later, both in the manuscript and in the PRISMA flow diagram.
A paper you drop because it "just doesn't feel right" will come back to haunt you months later when you have to justify the call. The moment you exclude a paper, write one short line that maps to your criteria — "population outside age range," "outcome definition doesn't match." That habit will save you during write-up.
Paperfy is a third-layer tool
Paperfy isn't a reference manager or a screening tool. It lives in the third layer — reading and decision notes.
Upload the papers that reach full-text review, and each one gets a single page with its AI summary, figures, tables, and original text. Edit the summary to add your inclusion or exclusion reasoning and what you checked, and the decision stays attached to the PDF — no more "why did I keep this?"
Design for interruptions that last months
A systematic review typically takes months to a year, usually running alongside everything else you do. Your management system has to survive being paused and picked back up.
The hard part of resuming is remembering what was decided and where you left off. If every paper carries its own decision notes, getting back up to speed takes minutes instead of hours.
Make sure the records can't disappear
Finally, something obvious but important: don't keep your screening and extraction tables in a single file on one personal machine.
Back them up to a shared drive and version them according to your team's rules. The record of those hundreds of hours of work is a research output in its own right.
Key takeaways
- Every paper keeps its decision, reasoning, and extraction records attached.
- After deduplication, each paper is tracked under a single ID.
- Exclusion reasons are written down in words, on the spot.
- The project can be resumed within minutes after any interruption.
Never ask "why did I keep this?" again
With Paperfy, your decision notes live on the same page as the PDF for every paper that reaches full-text review — easy to revisit even months later.
Systematic review
Explore This Topic
Read the full cluster for this workflow, from first steps to practical use.
Read Next
These guides continue the same workflow.