How to Document Your Literature Search Strategy for a Systematic Review

By Dr. Zubair Khalid, DVM, MS, PhD · 2026-08-27

Quick Answer

• Document every database searched, the exact search date, and the complete search string for each database to meet PRISMA-S reporting expectations.
• Record your search strategy before screening begins, then update the documentation when you modify filters or add terms.
• A complete search log does not guarantee acceptance, but missing database names, dates, or full strings is a common reason for reviewer criticism.

Why Search Documentation Matters in Systematic Reviews

Systematic reviews differ from narrative reviews because they use a transparent, reproducible method to find and select studies. The search strategy is the foundation of that method. If a reader cannot tell which databases you searched, on what date, and with what exact terms, they cannot judge whether your search was comprehensive or biased. Peer reviewers and journal editors increasingly expect this level of detail, and reporting guidelines exist specifically to standardize how search methods are described.

The EQUATOR Network maintains a library of reporting guidelines for health research. These guidelines help authors decide what to include in their manuscripts so that readers can assess the validity of the work. For systematic reviews, the PRISMA statement and its extension PRISMA-S for search reporting are the relevant standards. Using these guidelines during the planning phase, instead of after data collection, saves time and reduces the risk of missing essential reporting elements.

Transparent search documentation also supports research integrity. The Committee on Publication Ethics core practices emphasize that research should be reported honestly and completely. When you document your search strategy in detail, you make it possible for others to verify your work. This aligns with broader expectations for data management and sharing, such as those described in the NIH Data Management and Sharing Policy, which encourages researchers to plan for how their data and methods will be made available.

Core Principles of Search Documentation

Reproducibility as the Primary Goal

A documented search strategy must allow another researcher to replicate your search and obtain the same results. This means recording also the search terms but also the database platform, the interface, the date of the search, and any filters or limits applied. Different platforms can return different results for the same terms, so the platform name matters as much as the database name.

Transparency About Changes

Search strategies rarely remain unchanged from start to finish. You may add new terms after finding relevant articles, adjust filters to capture more results, or limit by language or publication date. Each change should be logged with the date and the reason for the change. This transparency helps reviewers understand how your final search evolved and whether the changes introduced bias.

Completeness of the Record

A complete search record includes the full search string as executed, not a summary or paraphrase. Boolean operators, truncation symbols, phrase searching, and field tags must be recorded exactly. If you used a filter for study design or a date range, record that too. Partial documentation is a common reason for criticism during peer review.

At a Glance: What to Record for Each Database

The PRISMA-S Framework for Search Reporting

PRISMA-S is an extension of the PRISMA statement specifically for reporting literature searches in systematic reviews. It was developed to address the gap between how searches are actually conducted and how they are reported in published articles. The EQUATOR Network lists PRISMA-S among its reporting guidelines, and many journals now require authors to follow it.

PRISMA-S covers multiple aspects of search reporting, including the sources searched, the search strategies used, and the processes for managing the records retrieved. Key elements include listing all databases and registers searched, describing any search engines or websites used, and reporting the full search strategies for each source. The guideline also asks authors to describe how they handled deduplication, how they managed records, and whether they sought input from a librarian or information specialist.

You do not need to memorize every PRISMA-S item. Instead, use the checklist as a planning tool before you begin searching and as a verification tool before you submit your manuscript. The National Library of Medicine provides access to research-method references that can help you understand the underlying principles of systematic searching and reporting.

Building Your Search Documentation Template

Step 1: Create a Search Log Before You Start

Open a spreadsheet or document with columns for each element you need to record. Include the database name, platform, search date, search string, filters, number of results, and notes. Fill in the database and platform columns before you run the search. This prevents the common mistake of recording results without the search details needed to interpret them.

Step 2: Record the Full Search String

Copy the complete search string from the database interface into your log. Do not retype it from memory. Most databases display the search history, and you can copy the exact string from there. If the platform assigns a search session number, record it as well. This number can help you or a librarian retrieve the exact search later.

Step 3: Document Filters and Limits

Note every filter you applied, including date ranges, language restrictions, and study design filters. Record whether the filter was applied at the database level or during screening. Database-level filters affect the search results directly, while screening filters affect which records you include after seeing the results.

Step 4: Log Changes as They Happen

When you modify your search, add a new row to your log instead of overwriting the previous version. Record the date of the change, the reason for the change, and the new search string. This creates an audit trail that shows how your search developed and helps you report the final version accurately.

Step 5: Save Your Search in the Database

Most databases allow you to save your search strategy to a personal account. This is useful for retrieving the search later and for sharing it with coauthors or reviewers. The National Library of Medicine resources describe how to use PubMed's saved-search features, and similar functions exist in other major databases.

Recording Databases, Dates, and Search Strings

Database Names and Platforms

Record the official database name and the platform you used to access it. For example, Medline can be searched through PubMed, Ovid, or EBSCOhost, and each platform may return different results for the same query. The platform matters because it affects how the search is interpreted and which records are retrieved.

Search Dates

Record the exact date of each search. Literature changes continuously, and a search run in January may return different results in March. If you update your search before submission, record the new date and the results from the updated search. Some journals ask for the date of the last search, so keeping this information current is important.

Full Search Strings

The search string must be recorded exactly as it was executed. This includes Boolean operators, parentheses, truncation symbols, phrase quotes, and field tags. If you used a combination of subject headings and free-text terms, record both. The National Library of Medicine provides guidance on how to construct and document searches in biomedical databases.

Documenting Filters, Limits, and Search Modifications

Common Filters and Their Documentation

Filters for publication date, language, and study design are common in systematic reviews. Each filter must be recorded with the exact parameters used. For example, if you limited your search to English-language articles published after 2010, record that limit and the date you applied it. If you used a validated search filter for randomized controlled trials, record the filter's name and source.

Handling Search Modifications

When you add terms or change your search, record the modification in your log. Note the date, the reason, and the new search string. This is especially important when you add terms after finding relevant articles through citation searching or reference lists. Reviewers may ask why certain terms were added late in the process, and your log provides the answer.

Peer Review of the Search Strategy

Many systematic review protocols include a peer review of the search strategy before the search is executed. This review can be done by a librarian or information specialist who is not part of the review team. The National Library of Medicine resources describe the value of librarian involvement in systematic review searching. If you have your search peer reviewed, document the reviewer's name, the date, and any changes made as a result.

Practical Implementation Steps for Your Review Team

Assign a Search Documentation Lead

One person on the review team should be responsible for maintaining the search log. This person records the searches, updates the log when changes are made, and verifies that the final manuscript includes all required search details. Having a single owner reduces the risk of missing or inconsistent documentation.

Use a Shared Document

Store the search log in a shared location that all team members can access. This could be a cloud-based spreadsheet or a document in your project folder. The log should be version-controlled so that changes are tracked and previous versions are preserved.

Schedule Documentation Checkpoints

Plan to review your search documentation at key points in the review process: after the initial search, after screening, and before manuscript submission. At each checkpoint, verify that all databases are listed, all search strings are complete, and all dates are recorded. This prevents last-minute scrambling to reconstruct search details from memory.

Coordinate With Your Data Management Plan

If your review is funded by NIH or conducted at an institution with data management requirements, your search documentation may be part of your data management plan. The NIH Data Management and Sharing Policy describes expectations for planning how research data and methods will be managed and shared. Your search log is a methodological record that should be preserved and made available when appropriate.

Records and Measurements: What Your Search Log Should Contain

Common Failure Patterns in Search Documentation

Missing Database Names

A frequent problem is listing databases without specifying the platform. Writing "Medline" without noting whether you used PubMed, Ovid, or EBSCOhost makes replication impossible. Reviewers may ask for clarification, and the omission can delay publication.

Incomplete Search Strings

Some authors summarize their search strategy instead of providing the full string. For example, writing "we searched for terms related to diabetes and exercise" does not allow replication. The full string with Boolean operators and field tags must be provided.

No Search Dates

Omitting the date of the search is a common error. Without a date, readers cannot assess the currency of the search or understand why certain recent articles may be missing. Journals increasingly require search dates as part of the methods section.

Unreported Filters

Filters for language, date, or study design are sometimes applied but not reported. This is problematic because filters affect which records are retrieved and can introduce bias. All filters must be documented with their exact parameters.

Overwriting Search Versions

When authors modify their search and overwrite the previous version, they lose the audit trail. This makes it impossible to report how the search evolved and may lead to inconsistencies between the methods and the results. Always preserve previous versions of your search.

Limitations of Search Documentation

Database Coverage Gaps

Documenting your search does not compensate for gaps in database coverage. No single database covers all relevant literature, and even comprehensive searches may miss important studies. Your documentation should describe which databases you searched and acknowledge the limitations of that coverage.

Language and Publication Bias

Search filters for language and publication type can introduce bias. If you limit to English-language articles, you may miss relevant studies published in other languages. Documenting these limits is necessary, but it does not eliminate the bias they introduce.

Indexing Delays

Databases index articles at different speeds, and recent articles may not appear in your search results even when they are published. Your search date defines the cutoff, but articles published before that date may still be missing if they have not been indexed yet. This is a limitation of the search process itself, not of your documentation.

Changes in Database Interfaces

Database interfaces change over time, and a search that worked on one date may not work identically on another date. This is why recording the platform and the exact search string is important, but even with complete documentation, replication may not be perfect if the interface has changed.

Welfare and Safety Context for Research Integrity

Protecting Participant and Researcher Welfare

Systematic reviews often synthesize evidence from studies involving human participants or animals. Transparent search documentation supports the ethical conduct of research by ensuring that the evidence base is complete and that conclusions are based on all available studies, not a biased subset. The Committee on Publication Ethics core practices emphasize the importance of honest and complete reporting in all research.

Avoiding Duplicate Publication

Clear documentation of your search and your review methods helps prevent duplicate publication. If your search strategy is transparent, other researchers can see what you have covered and avoid unnecessary duplication of effort. This is particularly important in fields where multiple systematic reviews on the same topic are common.

Supporting Data Sharing

The NIH Data Management and Sharing Policy encourages researchers to plan for data sharing from the start of their projects. Your search documentation is part of the methodological data that should be preserved and shared. Making your search strategies available supports reproducibility and allows other researchers to build on your work.

Professional Escalation Criteria

When to Consult a Librarian or Information Specialist

If you are uncertain about how to construct a comprehensive search or how to document it properly, consult a librarian or information specialist early in your project. These professionals have specialized training in systematic searching and can help you build and document your search strategy. The National Library of Medicine provides access to resources that describe the role of librarians in systematic reviews.

When to Seek Peer Review of Your Search

If your review covers a complex topic or involves multiple databases, consider having your search strategy peer reviewed before you execute it. This review can identify missing terms, incorrect Boolean logic, or inappropriate filters. Document the peer review process and any changes made as a result.

When to Escalate to Your Institution or Funder

If you encounter disputes about search documentation within your review team, or if you are uncertain about compliance with funder or institutional requirements, escalate the issue to your institution's research office or your funder's program officer. The NIH Grants and Funding website provides information about grant requirements and expectations, and your institution may have additional policies.

Building a Search Documentation Audit Trail for Peer Review

The Peer Review Verification Problem

Even a complete search log does not guarantee that reviewers will accept your methods. Reviewers often ask for verification that the search was actually run as described, that the results counts match the screening flow, and that no undocumented changes occurred between the initial search and the final manuscript. A search documentation audit trail addresses this problem by creating a verifiable chain of evidence that connects your planning documents to your executed searches and your final report.

The EQUATOR Network reporting guidelines emphasize that methods should be described so completely that another researcher could replicate them. However, replication is only possible if your documentation can withstand scrutiny. An audit trail goes beyond the basic search log by adding verification steps, version control, and cross-checks that demonstrate your search was conducted exactly as reported.

Designing a Three Layer Audit Trail

A robust audit trail has three layers that work together to provide complete verification. The first layer is the planning record, which captures your intended search strategy before execution. The second layer is the execution record, which captures what actually happened when you ran the search. The third layer is the verification record, which documents the checks you performed to confirm that the execution matches the plan and that the final report matches both.

Layer 1: The Planning Record

Before you run any search, create a planning document that records your intended approach. This document should include the research question, the databases you plan to search, the preliminary search terms, and any filters you intend to apply. Date this document and store it separately from your execution log. The planning record serves as a baseline that reviewers can compare against your final reported search.

The planning record also helps you identify gaps before you start. For example, if your research question involves a specific intervention and you have not included terms for that intervention in your preliminary search, the planning record makes that gap visible. The National Library of Medicine research-method references describe how structured planning improves the quality of systematic searches.

Layer 2: The Execution Record

The execution record is your search log with one addition: each entry must include a verification signature. This signature can be the initials of the person who ran the search, the date and time of execution, and a confirmation that the recorded search string matches the string actually executed. This signature turns a passive log into an active audit trail.

For each database search, record the following verification elements:

Layer 3: The Verification Record

The verification record documents the checks you performed to ensure consistency across your planning record, execution record, and final manuscript. This layer is often missing from search documentation, which is why reviewers request clarifications. A verification record answers common reviewer questions before they are asked.

Create a verification checklist that you complete at each documentation checkpoint. The checklist should confirm that every database listed in your methods section appears in your execution record, that every search string in your appendix matches the execution record, and that the results counts in your PRISMA flow diagram match the counts in your search log. Discrepancies must be resolved and documented before submission.

Implementing Version Control for Search Documentation

Version control is essential for maintaining an audit trail, but many review teams rely on informal file naming that leads to confusion. Implement a structured version control system for your search documentation using a simple naming convention that includes the date, version number, and status of each document.

For example, name your search log file as follows: search_log_20240315_v1_draft.xlsx, then search_log_20240318_v2_revised.xlsx, and finally search_log_20240401_v3_final.xlsx. Store previous versions in an archive folder instead of deleting them. This preserves the full history of your documentation and allows you to show reviewers exactly when and how your search evolved.

The NIH Data Management and Sharing Policy describes expectations for managing research data throughout the project lifecycle. Version-controlled search documentation aligns with these expectations by ensuring that methodological records are preserved, organized, and available for sharing when appropriate.

Cross Checking Search Results Against Screening Records

A common point of reviewer criticism is inconsistency between the number of records reported from each database and the number of records that enter the screening process. Your audit trail should include a cross check that reconciles these numbers.

For each database, record the total results count from your search. Then record the number of records exported to your reference management tool. Then record the number of records after deduplication. These three numbers should be traceable in your audit trail. If the numbers do not match, investigate the discrepancy and document the reason. For example, some records may have been excluded during export because they were duplicates within the database itself, or the export may have failed for a subset of records.

This cross check serves two purposes. First, it ensures that your PRISMA flow diagram is accurate. Second, it demonstrates to reviewers that you have verified your own work instead of relying on memory or estimates.

Using the Audit Trail During Manuscript Preparation

When you prepare your manuscript, use the audit trail to generate the search reporting elements required by PRISMA-S. The verification record tells you which databases to list, which search strings to include in your appendix, and which dates to report. The execution record provides the exact wording for your methods section. The planning record helps you describe how your search evolved and why you made specific modifications.

The Committee on Publication Ethics core practices emphasize that research should be reported honestly and completely. An audit trail supports this by making it difficult to accidentally misreport your search methods. When you can trace every reported element back to a dated, verified record, you reduce the risk of errors that lead to rejection or post-publication criticism.

Troubleshooting Common Audit Trail Failures

Missing Verification Signatures

If your execution record lacks verification signatures, you can still reconstruct some evidence. Check your database search history if you were logged in, review your email notifications from database alerts, or consult your reference management tool for import timestamps. Document what you can verify and clearly mark what cannot be verified.

Inconsistent Results Counts

If your search log shows a different results count than your screening records, investigate the source of the discrepancy. Check whether you applied additional filters during export, whether the database updated between your search and your export, or whether you accidentally searched a different date range. Document your findings and correct the records.

Lost Planning Documents

If you did not create a planning record before searching, you can still create a retrospective planning document that describes your intended approach based on your protocol or registration. Clearly label this document as retrospective and explain why it was created after the search. This is less ideal than a prospective planning record but still provides useful context for reviewers.

Professional Escalation for Audit Trail Issues

If you discover significant gaps in your audit trail that cannot be resolved, escalate the issue before submission. Consult a librarian or information specialist who can help you assess whether your documentation is sufficient for the journals you are targeting. The National Library of Medicine provides access to resources on systematic review methods that can help you evaluate your documentation.

If the gaps are substantial, consider whether you need to rerun your searches to create a verifiable execution record. This may be necessary if your original searches were not saved and cannot be retrieved. Rerunning searches is time consuming but preferable to submitting a manuscript with unverifiable methods.

For disputes within your review team about the accuracy of the audit trail, escalate to your institution's research integrity office or your funder's program officer. The NIH Grants and Funding website provides information about grant requirements and expectations that may apply to your documentation practices.

Frequently Asked Questions

What is the minimum information I need to document for each database search?

Record the database name and platform, the exact search date, the full search string as executed, all filters and limits, and the number of results retrieved. This information allows another researcher to replicate your search and assess its comprehensiveness.

How do I record a search string that I modified during the review process?

Create a new row in your search log for each modification. Record the date of the change, the reason for the change, and the new search string. Do not overwrite previous versions, because the audit trail is important for transparency.

Do I need to document searches of sources other than databases?

Yes. If you searched clinical trial registries, preprint servers, or websites, document those searches as well. PRISMA-S includes reporting requirements for all sources searched, beyond bibliographic databases.

How do I document a search that was peer reviewed by a librarian?

Record the librarian's name, the date of the review, and any changes made to the search as a result. This information may be requested by reviewers or editors and demonstrates that your search was independently checked.

What should I do if I cannot retrieve the exact search string from a database?

If you did not save the search string at the time of the search, you may be able to retrieve it from the database's search history if you were logged in. If you cannot retrieve it, you must disclose this limitation in your manuscript and describe the search as accurately as possible.

How does search documentation relate to data management plans?

Search documentation is part of the methodological record of your research. The NIH Data Management and Sharing Policy describes expectations for managing and sharing research data and methods, and your search log should be preserved and made available when appropriate.

Should I document the number of results from each database separately?

Yes. Recording the number of results from each database separately helps reviewers understand the contribution of each source and allows you to report the total number of records screened accurately.

What if my search documentation is incomplete when I am ready to submit?

If you discover missing information at the submission stage, you must disclose the gaps honestly. Do not fabricate search details. Describe what you can verify and acknowledge the limitations. The Committee on Publication Ethics core practices emphasize honest reporting, and fabricated search details would constitute misconduct.

Related Articles

• Scientific Literature Review: A Reproducible Search and Synthesis Workflow
• Meta-Analysis vs Systematic Review: What's the Difference?
• How to Write an Experiment Report: A Practical Template
• Scientific Literature Review Format: A Reproducible Structure for Researchers
• Meta-Analysis vs Systematic Review: Choosing the Right Synthesis Method

References and Further Reading

• Research Methods Resources. National Library of Medicine.
• EQUATOR Network. EQUATOR Network.
• Core Practices. Committee on Publication Ethics.
• NIH Grants and Funding. National Institutes of Health.
• ORCID for Researchers. ORCID.
• Data Management and Sharing Policy. National Institutes of Health.
• NCBI Literature Resources. National Center for Biotechnology Information.
• PubMed. National Library of Medicine.

This article is educational and does not replace institutional policy, professional advice, or applicable safety and regulatory requirements.