November 9, 2026

Literature Review Update Workflow for New Evidence

A literature review update is not a fresh search pasted onto an old draft. It is a controlled revision: you re-enter the review at the point where new evidence could change your selection, your synthesis, or your reporte

Written byWisPaper TeamAI Research Workflow Team
Editorial illustration for Literature Review Update Workflow for New Evidence

A literature review update is not a fresh search pasted onto an old draft. It is a controlled revision: you re-enter the review at the point where new evidence could change your selection, your synthesis, or your reported methods, and you leave a trail that a coauthor, reviewer, or future lab member can follow. The practical question is rarely "how do I find more papers?" It is "what has to change in my review, and how do I show that the change was systematic?"

This guide treats the update as a workflow with decisions and artifacts. It starts with a diagnosis of where your review currently stands, then walks through the steps that produce an auditable method trail, and ends with a readiness check. WisPaper tools appear only where they support a specific step.

What kind of update are you actually doing?

The first decision is scope. An update can mean re-running a search to catch newly published studies, re-screening an existing pool against refined eligibility criteria, or re-synthesizing evidence you already hold. These are different jobs with different artifacts.

Starting stateWhat is missingFirst artifact to produce
Draft manuscript, search run months agoNew records since last searchA dated re-run of the original search strategy
Coauthor flagged a missed paperA check against eligibility criteriaA screening decision with a stated reason
Peer review asks for a broader searchDocumented sources and termsA revised search strategy with sources listed
Lab handoff, method unclearReproducible search recordA search log another person can re-execute
New review from scratchEligibility criteria and sourcesA protocol-level plan before searching

Cochrane's guidance on searching for and selecting studies frames the search around eligibility criteria, multiple sources, combined free-text and subject-heading terms, documented process, staged screening, and linking multiple reports of one study. That framing is the backbone of any update, because it tells you which artifacts you must be able to show.

Which artifacts make the update auditable?

Before you search, decide what you will keep. An auditable update typically needs four artifacts:

  1. A search strategy record — the sources used, the terms and any field tags or filters, and the date each search was run. PubMed's search details show how terms were translated and combined, which makes that record easier to reconstruct.
  2. A screening log — which records were included or excluded and the criterion that drove each decision.
  3. A study-linking note — where multiple reports belong to one study, so your count of studies is not inflated.
  4. A synthesis change log — what conclusion, table, or figure changed and why.

PRISMA 2020 supplies reporting templates, including flow-diagram templates for original and updated systematic reviews, and its checklist covers transparent reporting of search, selection, and synthesis methods. If your review follows a reporting standard, build the update so it can populate those fields rather than reconstructing them afterward.

How do you re-run a search without losing the original method?

Re-running a search is where method trails most often break. The safe pattern is to preserve the original strategy as a record, then create a dated variant.

  • Keep the original terms and sources visible. If you change a term, note the change and the reason.
  • Reuse the same source set where possible. Cochrane recommends using multiple sources, so an update that quietly drops a database weakens comparability.
  • Record filters and limits. Date limits and field restrictions change what a search returns; note them alongside the run date.
  • Capture the translation of terms. PubMed's search details reveal how terms were translated and combined, which helps you explain why a re-run returned what it did.

For the actual retrieval, you can run the strategy in WisPaper search to find academic papers through its scholarly search interface, or use the public WisPaper Scholar Search entry point when you need a starting place for finding papers. Whichever route you use, the search log — not the interface — is the artifact that makes the update defensible.

How should you screen new records in stages?

Staged screening keeps a large update manageable. Cochrane describes screening in stages and linking multiple reports of one study, and both practices matter when new evidence arrives in bulk.

A workable sequence:

  1. Deduplicate the combined records before reading titles.
  2. Title and abstract screen against eligibility criteria, recording a reason for exclusion.
  3. Full-text screen for records that pass, again with a recorded reason.
  4. Link reports so that a trial report, a follow-up, and a secondary analysis of the same study are counted once.

When you need to hold candidate papers while you decide, save or upload them in My Library and organize them there. Keeping the candidate pool in one place makes the screening log easier to maintain and easier to hand to a coauthor.

Where does new evidence change the synthesis, not just the count?

Adding studies is the easy part. The harder judgment is whether new evidence changes a conclusion, a subgroup, or the certainty you attach to a finding. Treat synthesis as a separate decision from selection.

Ask three questions of each included new study:

  • Does it fall inside the population, intervention, and outcome boundaries you already set?
  • Does it agree or conflict with the direction of the existing synthesis?
  • Does it change how you group studies — for example, by shifting which reports belong to one study?

Record the answer in the synthesis change log. If nothing changes, say so; a documented "no change" is still part of the trail. If something changes, the log tells your coauthor and reviewers exactly where to look.

How do you keep coauthors and reviewers aligned during an update?

An update usually involves more than one reader. The coordination problem is that each person needs to know which version of the search and screening they are looking at.

A simple alignment routine:

  • Name versions. Date the search log and the screening log so a coauthor can tell which run produced which decision.
  • Separate the question from the papers. When the update spans several sub-questions, keep each one's papers and notes distinct.
  • Answer questions against the saved pool. When a coauthor asks whether a specific paper was considered, you need to query the papers you actually hold rather than re-searching from memory.

For the last step, Library QA lets you ask questions based on papers uploaded to My Library or added from search results. That fits the moment when a coauthor asks what your saved evidence says about a specific outcome, because the answer is grounded in the pool you have already assembled.

How do you verify references before resubmission?

An update often adds new citations, and new citations are where reference errors enter a manuscript. A reference check is a distinct step from a search check.

TrueCite supports BibTeX citation screening: it checks BibTeX against real academic databases to flag hallucinated references. Run it after the synthesis is settled and the bibliography is assembled, so you are checking the references you will actually submit rather than a moving list.

Pair the reference check with a citation-lookup step in your source database. PubMed supports citation lookup, and Google Scholar documents citation export, so you can confirm that each new entry resolves to a real record before it enters the final bibliography.

What changes when the update is a full review or a lab handoff?

Some updates are large enough to need a project structure rather than a single search log. Two situations stand out.

A new review or a major expansion. When the update grows into a new review, you need a place to hold the question, the sources, and the working papers together. Research Projects is the WisPaper area for creating and organizing a research project, which suits a review that will run across multiple search rounds.

A lab handoff. When someone else must continue the update, the handoff artifact is the method trail: the search strategy record, the screening log, the study-linking note, and the synthesis change log. A successor should be able to re-run the search and reach the same candidate pool without asking you what you meant.

For longer research tasks that fit a literature review use case, Scholar Agent is the WisPaper area for extended work of that kind. Use it when the update involves sustained reading and synthesis rather than a single search pass.

How do you know the update is ready?

Readiness is a checklist, not a feeling. The update is ready to report when you can answer yes to each of these:

CheckEvidence you can point to
Search is reproducibleDated strategy record with sources, terms, filters
Screening is traceableLog with include/exclude decisions and reasons
Studies are counted correctlyLinking note for multiple reports of one study
Synthesis changes are explainedChange log tied to specific conclusions or tables
Reporting fields can be completedSearch, selection, and synthesis details ready for your checklist
References resolveCitation screening completed on the final bibliography

If any row is blank, that is the next task. The order matters: fix the search record before the screening log, and the screening log before the synthesis log, because each depends on the one before it.

Which route fits your entry point?

Readers arrive at this workflow at different stages. Match your entry point to a route:

  • You have a draft and a stale search. Start with the search strategy record, re-run the search, then screen in stages.
  • A coauthor flagged a paper. Start with the screening log, decide against eligibility criteria, then update the synthesis log if the decision changes anything.
  • Peer review asked for more. Start with the search strategy record and sources, then document the revised strategy before re-screening.
  • You are handing off. Start with the method trail; confirm a successor can re-run the search before you close the project.
  • You are starting a new review. Start with eligibility criteria and sources, then build the artifacts as you go rather than after the fact.

If you are new to the toolset, the WisPaper homepage introduces WisPaper as an AI research assistant for finding, screening, organizing, and working with academic papers, and English readers can begin from the WisPaper English homepage.

FAQs

Cochrane's guidance recommends using multiple sources when planning searches from eligibility criteria. A single-source update narrows what your search can find and makes the update less comparable to the original review. If you must limit sources, record the limitation in the search strategy record so reviewers can see it.