Manuel B. Garcia

Manuel B. Garcia serves as the Senior Director for Educational Technology and Digital Learning at FEU Institute of Technology, Manila, Philippines. Read More

Contact Info

1607, FEU Tech Building,
P. Paredes St, Sampaloc,
Manila, Philippines
mbgarcia@feutech.edu.ph

Follow Me

How Do You Document Search Changes Without Pretending They Were Planned From the Beginning?

Literature searches often evolve as researchers learn the terminology and structure of a field. Good reporting does not require pretending otherwise: preserve what changed, when it changed, why it changed, and how the final search was conducted.

632
Documenting Literature Search Changes Guide 632 of 899
01 · The Question

What Should You Report When Your Final Search Is Not the Search You Started With?

You begin with one set of keywords. After screening several hundred records, you discover an important synonym. A database's subject headings work differently from what you expected. Citation searching reveals terminology from another discipline. One concept produces mostly irrelevant results, so you refine it.

By the end, your search is considerably better than version one.

The temptation is to report only the polished final strategy, as though you had designed it perfectly before seeing the first record. That creates a cleaner methods section, but it can erase information that matters for understanding how the evidence base was constructed. Transparent documentation should preserve the difference between what was planned and what was learned during the search.

02 · The Short Answer

Keep a Search History That Separates Plans From Later Decisions

In Brief

Document meaningful search changes by preserving the earlier strategy, recording what changed, when and why it changed, and retaining the exact final searches that were actually run rather than rewriting the final strategy as though every decision had been planned from the beginning.

The level of detail should match the review type. Systematic reviews require particularly reproducible search reporting, while more iterative review approaches may legitimately evolve during searching. In either case, transparency means describing the process accurately rather than creating retrospective methodological neatness.

03 · What You Need to Know

What a Transparent Search Record Should Preserve

Search documentation and search reporting are related but different

Cochrane makes a useful distinction between documenting a search and reporting it. Documentation is the internal record you maintain while conducting the review. Reporting is the information eventually presented to readers.

Good reporting depends on good documentation because memories of exactly which terms, filters, dates, platforms, and iterations were used become unreliable surprisingly quickly. Search interfaces also change, and databases may use different syntax even when the underlying concepts are the same.

For Cochrane intervention reviews, documenting the search process in enough detail to permit correct reporting is a mandatory methodological expectation. The guidance specifies that records should capture the sources searched, when they were searched, who conducted the search, and which terms were used, with searches reproducible to the extent possible.

Preserve the exact searches you actually ran

Do not reconstruct a search months later from memory if the original database output or search history can be retained.

For each important database or information source, useful records may include the database name, platform, date searched, exact search strings or line-by-line strategy, controlled vocabulary, fields searched, filters, limits, and number of records retrieved. What is appropriate varies across databases and review methods.

Cochrane recommends copying and pasting or exporting exact database strategies rather than retyping them, partly to reduce transcription errors. PRISMA 2020 asks systematic-review authors to present full search strategies for all databases, registers, and websites searched, including filters and limits.

That final reproducible strategy is essential. It is not always the whole history.

Keep versions when the strategy changes materially

If an early exploratory search is discarded after five minutes because of a spelling error, maintaining an elaborate methodological diary would add little value. Documentation should be proportionate.

More consequential changes deserve a record. Examples include adding or removing a major concept, substantially changing terminology, introducing a date or language restriction, changing databases or other information sources, adding a search method such as citation searching, or revising a strategy because known relevant studies were being missed.

Record What to capture Why it matters
Search version The exact strategy before and after an important revision Shows what actually changed
Date When the search or revision occurred Establishes the sequence of methodological decisions
Rationale Why the revision was necessary Distinguishes conceptual refinement from unexplained post hoc adjustment
Evidence informing the change For example, missed benchmark papers, newly discovered terminology, or excessive irrelevant retrieval Explains what prompted the decision
Consequence Where useful, what changed in retrieval or coverage Helps assess whether the revision materially altered the evidence pool

State why the search changed, not merely that it changed

“Search terms were refined during the review” provides little information. What did you learn that required refinement?

Perhaps screening showed that an established synonym had been omitted. Perhaps a subject heading had changed. Perhaps a term was so ambiguous that it retrieved large numbers of irrelevant records. Perhaps citation searching identified terminology used in an adjacent discipline. Perhaps the search failed to retrieve known eligible studies.

These explanations make the methodological logic visible.

They also help distinguish legitimate iteration from changing search terms in ways that could introduce confirmation bias.

Do not rewrite chronology

Suppose your original strategy omitted an important synonym. After screening, you discovered the term and reran the search with it included.

A final methods section that presents only the improved strategy without any indication that the search developed may be adequate for some limited reporting purposes, depending on the review type and what exactly is being reported. But where the change represents a consequential departure from a protocol or materially affects how the evidence was identified, describing the revision gives readers information needed to evaluate the process.

The aim is not confession. Iterative refinement can be methodologically appropriate. The issue is whether the written record accurately represents what happened.

Planned methods and actual methods should be distinguishable

Protocols and registrations provide a useful reference point because they record intended methods before the review is completed. PRISMA 2020 includes an item asking authors to indicate where a protocol can be accessed and to describe and explain amendments to information provided at registration or in the protocol.

If the final search differs from the planned search, identify the relevant difference rather than silently replacing the planned method with the final one.

Planned method What you intended to search or do before the relevant methodological adaptation occurred.
Implemented method What you actually searched or did, including justified refinements and deviations made during the review.

A rigorous report can contain both. They are not competing versions of the truth.

Document sources beyond bibliographic databases too

Literature identification may involve more than database searching. Reference-list searching, forward citation searching, trial registers, websites, organizations, expert contacts, and other sources can contribute relevant records.

Cochrane specifically notes the importance of planning how searches of sources other than databases will be recorded because activities such as reference-list searching and forward citation searching may occur later in the review process. Decisions about search iterations can also be preserved in appendices and used in future updates.

For an iterative search, this matters because later search methods can otherwise become invisible. A reader may see a final set of included studies without knowing that some were discovered through a substantially different route from the original database search.

Record restrictions and filters carefully

Date, language, document-type, study-design, and other restrictions can materially change what a search retrieves. When such limits are used, their rationale may matter as much as the syntax.

Cochrane advises review authors to justify restrictions on publication date and format and cautions against language restrictions because of the risk of excluding relevant studies. PRISMA 2020 asks authors to report filters and limits as part of the full search strategy.

If a restriction was added after searching began, preserve when and why it was introduced rather than allowing it to appear retrospectively inevitable.

Do not document so little that the search cannot be reproduced

Statements such as “Google Scholar and several databases were searched using relevant keywords” are not reproducible descriptions.

For systematic reviews, readers should be able to see which sources were searched, when they were searched, and the actual strategies used. Search reproducibility is imperfect because database content and interfaces change, but that does not remove the obligation to document what was done at the time.

Do not document so much that the important decisions disappear

The opposite problem is possible too. A search diary containing every typo, test query, and minor syntax adjustment can become enormous while obscuring the decisions that actually shaped retrieval.

A useful internal record can be detailed, while the published explanation focuses on consequential changes. Supplementary materials can carry full strategies and technical detail when the main article cannot reasonably accommodate them.

Watch Out

Transparency does not mean turning the methods section into a minute-by-minute transcript of database use. Preserve enough detail to reconstruct consequential decisions and reproduce the implemented searches, while distinguishing substantive changes from ordinary technical experimentation.

Good documentation makes later updates much easier

A clear search history is useful long after publication. When a review is updated, previous strategies may need to be rerun or modified because database indexing, controlled vocabulary, interfaces, or understanding of the original search has changed.

Cochrane's guidance on review updates recognizes that experience from the original search may justify modifying sources or search terms. Without an accurate record of the original search and its development, updating becomes partly an exercise in methodological archaeology, which is rarely anyone's favorite research method.

04 · A Practical Example

How to Record an Iterative Search Without Rewriting Its History

Hypothetical Example

A search for studies of AI-assisted formative feedback

A researcher develops an initial database strategy around generative AI, formative feedback, and higher education. Screening reveals that relevant studies frequently use terminology that was absent from the original search.

Version 1 The researcher saves the exact initial strategy, database, platform, date, filters, and number of records retrieved.
Problem identified Several known relevant records use “automated feedback” and related terminology and are not reliably retrieved by the original strategy.
Revision The missing terminology is incorporated, the strategy is tested again, and the exact revised search is saved as Version 2.
Rationale recorded The search log states that the terms were added after screening because relevant terminology not represented in the original strategy had been identified.
Final reporting The review reports the implemented search strategy in reproducible form and, where appropriate to the review methodology, identifies the substantive refinement rather than implying that Version 2 existed from the beginning.

Nothing embarrassing occurred in this example. The search improved. The methodological record simply preserves how it improved.

05 · What Researchers Often Get Wrong

Common Mistakes When Reporting Search Changes

Misconception

“A rigorous review should make it look as though nothing changed.”

No. Rigorous research can involve justified methodological adaptation. Concealing meaningful changes removes information readers may need to evaluate the review.

Misconception

“I should report every test query I ever ran.”

Not necessarily. Distinguish ordinary search development from consequential changes that affect conceptual coverage, sources, limits, or reproducibility. Internal records can be more detailed than the published narrative.

Misconception

“Reporting the final keywords is enough for a systematic review.”

No. PRISMA 2020 asks for full search strategies for all databases, registers, and websites searched, including filters and limits. Reproducibility requires considerably more than a short keyword list.

Misconception

“Admitting that a search changed makes the review look biased.”

Not necessarily. Search development can legitimately be iterative. Explaining the rationale for a change often makes it easier to distinguish appropriate refinement from result-driven adjustment.

Misconception

“I can reconstruct the search later when I write the paper.”

That is risky. Exact syntax, filters, platforms, dates, and intermediate decisions are easy to forget. Record them when the search is conducted rather than relying on retrospective reconstruction.

06 · What This Means for You

Keep a Small Search Audit Trail From the Beginning

You do not need sophisticated software to create a useful search history. A structured spreadsheet, research log, reference-management note, or review platform can work if it preserves the necessary information consistently.

A simple decision framework

If you run an important database search
Save the exact strategy, source and platform, date, relevant limits, and retrieval information appropriate to the review.
If you materially revise the strategy
Keep the earlier version and record what changed and why rather than overwriting it.
If the change follows something learned from retrieved studies
State what was learned and why it justified the revision.
If the implemented method differs from a protocol or registration
Identify and explain the amendment according to the reporting requirements appropriate to the review.

Be especially transparent when a search modification changes which kinds of evidence become visible. If a revision was made after you had already seen the direction of findings, document the rationale carefully and consider whether the change could have been influenced by those findings.

The same principle applies beyond search terms. If your inclusion criteria changed after results became visible, preserve that methodological history as well.

Ultimately, a good audit trail helps you answer a deceptively simple question: could another researcher understand not only what search you ended with, but how the consequential decisions that produced it were made?

07 · A Quick Checklist

What to Record When Your Literature Search Changes

For each consequential search revision, check that you recorded:
The database, register, website, or other information source involved.
The platform and date of the search where relevant.
The exact strategy or sufficient technical detail to reproduce the implemented search.
The previous version when the strategy changed materially.
What changed and the methodological reason for changing it.
Any filters, limits, or restrictions introduced or removed.
Whether the revision differed from a protocol, registration, or other previously stated method.
Enough information for the final report to distinguish planned methods from important later refinements.
08 · Frequently Asked Questions

Frequently Asked Questions About Search Documentation

Do I need to save every version of every search?

Not necessarily. Preserve the exact implemented searches and retain versions associated with consequential conceptual or methodological changes. Minor experimentation, syntax corrections, and abandoned test queries generally do not require the same level of published documentation.

What information should I record for a database search?

For a systematic review, this commonly includes the database and platform, date searched, complete strategy, fields, controlled vocabulary and text terms, filters or limits, and other information needed to understand and reproduce the search. Follow the reporting guidance appropriate to your review.

Should I report that I added keywords after reading papers?

If the addition materially changed the search, particularly in a review requiring transparent and reproducible methods, document the refinement and its rationale. Discovering useful terminology from retrieved literature is not inherently problematic.

What if my final search is much better than the one in my protocol?

Use the methodologically appropriate improved search, but identify and explain relevant amendments rather than silently replacing the planned strategy. The protocol and final review serve different purposes: one records intentions and the other should accurately report what was done.

Where should full search strategies appear?

For systematic reviews, detailed strategies are commonly provided in supplementary material or another accessible location, depending on the journal and review framework. PRISMA 2020 recommends presenting full strategies for all databases, registers, and websites searched.

Should citation searching and website searching be documented too?

Yes, when they form part of the review's evidence-identification process. Record enough information about non-database sources and methods to explain what was searched or consulted and, as far as practicable, permit the process to be understood or reproduced.

Does documenting a change prove that it did not introduce bias?

No. Transparency does not remove bias. It allows you and your readers to examine the rationale, timing, and potential consequences of the decision rather than having the decision disappear from view.

09 · The Bottom Line

Report the Search You Actually Conducted, Including How It Evolved

The Bottom Line

Document search changes by preserving exact search versions, recording consequential revisions and their rationale, and distinguishing planned methods from later refinements rather than presenting the final strategy as though it existed unchanged from the beginning.

An evolving search is not inherently a weak search. In many contexts, iteration is necessary. What strengthens the methodological record is making that evolution traceable enough for readers to understand what was done, why important changes occurred, and how the final evidence base was identified.

10 · Sources and Further Reading

Sources and Further Reading

11 · Cite this Guide

How to Cite This Guide

This guide is intended to be read, shared, and used in research, teaching, and academic work. If you draw on its ideas, explanations, or other content, please acknowledge the source by citing the guide. Doing so gives appropriate credit and helps your readers locate the original resource.

Has the Field Guide helped your research?

If a guide helped clarify a question, inform a research decision, or move your work forward, I would love to hear about your experience. Your story may also help other researchers discover the Field Guide.

Share Your Experience
Takes only a few minutes