PRISMA protocol missing evidence: supervisor demands fix

How long will fixing a PRISMA protocol really take?

The short answer is that a thorough revision of a systematic‑review protocol that has been flagged for “missing evidence” typically consumes between 12 and 18 hours of focused work. In practice that translates to roughly two full working days if you can dedicate eight solid hours each day, plus a few additional hours for polishing and checking compliance with the PRISMA‑2020 checklist.

If you are staring at a five‑day deadline, you should budget the first 24 hours for a diagnostic sweep and a revised search‑strategy draft, the next 12–14 hours for expanding the evidence base (adding databases, grey‑literature sources, and updating search strings), and the final 4–6 hours for documentation, peer‑review by a colleague, and a final compliance audit. Anything less than this window will likely leave gaps that your supervisor will notice again.

What are the concrete stages and how much time does each normally require?

Why does this process often stretch beyond the initial estimate?

Many students underestimate the research‑gathering phase because they assume that adding a database is a simple tick‑box. In reality, each new source requires a separate Boolean construction, field‑specific syntax, and a brief validation run to confirm that key seed articles are captured. That validation step alone can double the time you thought you needed.

Rewriting the search strategy from scratch is another common time sink. When the original protocol is missing evidence, the supervisor usually expects a more exhaustive keyword map, which means you must revisit the conceptual framework, extract additional synonyms from the literature, and test combinations iteratively. The trial‑and‑error loop often consumes several hours that students don’t anticipate.

Formatting and checklist compliance are deceptively tedious. The PRISMA‑2020 checklist asks for explicit statements about each information source, date of the last search, and the exact search strings. Missing a single line item forces a back‑and‑forth with the supervisor, adding days to the timeline.

What does a realistic student timeline look like?

Consider Maya, a second‑year PhD student in a UK public‑health programme. She received the “missing evidence” note on a Monday morning and had a Friday deadline. Her timeline unfolded as follows:

• Monday (2 h): Read supervisor comments, listed all PRISMA items flagged, and created a quick audit spreadsheet.
• Monday‑Tuesday (6 h): Conducted a scoping search in Scopus and CINAHL, added OpenGrey, recorded hit counts, and saved export files.
• Wednesday (4 h): Refined Boolean strings, ran pilot searches, and documented the final syntax in a Word table.
• Thursday (3 h): Updated the PRISMA checklist, wrote a “Changes Made” paragraph, and sent the draft to a senior lab mate for feedback.
• Friday (2 h): Integrated peer comments, ran a Turnitin similarity check, proofread, and submitted before the 5 pm deadline.

Maya’s total effort was about 17 hours, spread across five calendar days. She missed the “two‑day” ideal only because her institution’s library required a manual request for full‑text access to some grey‑literature items.

Is the workload genuinely heavy, or can I cut corners?

The answer is honest: the workload is genuinely heavy when the protocol is missing evidence in the inclusion criteria. You are being asked to demonstrate that your search is comprehensive enough to capture all relevant studies, which is the cornerstone of systematic‑review credibility. Cutting corners—such as omitting a major database or glossing over the PRISMA checklist—will almost certainly trigger another round of revisions, extending the timeline further rather than shortening it.

What’s the minimum‑viable plan if I’m short on time?

If you truly have only a few hours left, focus on three non‑negotiables: (1) add at least one additional bibliographic database that covers a distinct discipline (e.g., if you started with PubMed, add Scopus or Web of Science); (2) update the PRISMA checklist so every “Information sources” line is filled in with the new database name and the date of the last search; (3) write a concise “What changed” paragraph that directly references each supervisor comment. Anything beyond those three items—such as a full grey‑literature sweep or a second peer‑review round—should be postponed until after the deadline.

What terminology does my supervisor actually expect?

The supervisor’s phrase “missing evidence” is shorthand for several PRISMA‑2020 items. Specifically, the checklist expects you to list:

• All databases searched (including platform names, e.g., “Embase via Ovid”).
• Any additional sources of grey literature (conference proceedings, trial registries, dissertations).
• The full Boolean search strings for each source, presented line‑by‑line.
• Eligibility criteria that are explicitly linked to the search terms (e.g., “Population: adults ≥18 y, Intervention: community‑based nutrition programs”).

If any of those boxes are empty, the reviewer will flag “missing evidence.” Use the exact headings from the PRISMA checklist when you rewrite the protocol; that signals you are addressing the precise concern.

What technical dead‑ends should I watch for?

When you add a new database, the syntax often changes. For example, Embase uses “/exp” for exploded terms, while PubMed requires “[MeSH Terms]”. A common failure mode is copying a PubMed string verbatim into Scopus, which yields zero hits or an inflated result set. Double‑check each platform’s field tags and Boolean operators before you run the final search.

Another pitfall is the export format. Some libraries only allow RIS or CSV exports, and the reference manager you use (EndNote, Zotero) may truncate long author lists, leading to incomplete citation records. Verify that the exported files contain the full set of fields required for the PRISMA “Study selection” flow diagram.

How can I keep integrity concerns at bay?

Similarity‑detection tools treat a systematic‑review protocol as a highly structured document. Because many sections (e.g., the PRISMA checklist) contain boiler‑plate language, the overall similarity score can appear higher than expected. To mitigate this, paraphrase any copied guidance in your own words, and cite the original source (e.g., “PRISMA‑2020 checklist, Page 3”).

If you used an AI‑assisted drafting tool, ensure that every generated sentence is reviewed for factual accuracy and that you retain a record of the prompt‑response exchange. This documentation can be useful if an audit is requested by your department’s research integrity office.

What step‑by‑step time plan can I start tonight?

Begin with a rapid “gap analysis”:

1. Open the supervisor’s email and highlight every phrase that mentions evidence, databases, or inclusion criteria.
2. Open your current protocol side‑by‑side and tick off which highlighted items are already addressed.
3. For each unchecked item, write a one‑sentence note describing what is missing (e.g., “No search of Scopus for conference abstracts”).
4. Prioritize the notes: first add a database that covers the biggest disciplinary gap, then address any grey‑literature source, finally refine the Boolean strings.
5. Allocate a timer: 45 minutes per database addition, 30 minutes per Boolean refinement, and 20 minutes for checklist updates.
6. After each block, save a version with a timestamp (e.g., “protocol_v2_2026‑11‑03”).
7. When you reach the final hour, run a quick plagiarism check, scan the PRISMA checklist for empty rows, and send the draft to a peer for a 15‑minute read‑through.

Following this disciplined micro‑schedule keeps you moving forward without getting stuck on any single component for too long.