Skip to content
Free planNo credit card requiredStart writing

Screening decision log template with exclusion reasons and conflict rules

Copy this screening decision log to record every reviewer's decision, the final decision and its reason. It comes with a ranked list of exclusion reasons and written rules for settling disagreements between reviewers.

Copying the log is free. In the Systematic Review workspace, screening, conflicts, agreement statistics, the CSV of decisions and the decision log as Word or PDF cost 0 credits; the free plan holds one review of up to 50 records.

A screening decision log records who decided what about each study in a systematic review, why, and how disagreements were settled. This template gives you the columns, a ranked taxonomy of exclusion reasons and disagreement rules for your protocol. It is for reviewers who screen in spreadsheets or must explain their screening to an examiner or journal.

Fill the log as you screen with the screening forms. Its counts feed your PRISMA flow diagram.

The decision log (copy this)

One row per record per stage. Paste the header into a spreadsheet and freeze the first row.

Record IDStageReviewer AA reasonReviewer BB reasonAgree?Final decisionFinal reasonResolved byDateNote
TA / FTInclude / Exclude / MaybeInclude / Exclude / MaybeY / NA+B / third reviewer

TA is title and abstract; FT is full text. Keep the record ID the same as in your reference manager or screening tool, so the log can be matched to the export.

Add two small tables beside it:

  • Reports not retrieved. Report ID, how you tried to get it, date. These are not exclusions.
  • Excluded studies that look eligible. For PRISMA 2020 item 16b, list studies a reader might expect to see included, with the reason each was excluded [1].

The exclusion reason taxonomy

Use one short list for the whole review and check reasons in this order. The first criterion a report fails is its main reason, so each excluded report is counted once.

OrderReasonUse it whenExample
1Duplicate reportA second copy of a record you already haveThe same trial in PubMed and Embase, missed by deduplication
2Wrong publication typeEditorial, letter, commentary, protocol, conference abstract (if excluded in your protocol)A conference abstract with no full paper
3Not in an included languageOnly if your protocol limits languagesA study published only in a language you excluded
4Outside the date rangeOnly if your protocol limits datesPublished before your start year
5Wrong populationParticipants differ from the criteriaStudents in a simulated shift
6Wrong intervention or exposureThe intervention or exposure differsA nap taken before the shift
7Wrong comparatorNo eligible comparison groupTwo nap lengths, no no-nap group
8Wrong outcomesNo eligible outcome measured or reportedReports only satisfaction, not alertness
9Wrong study designDesign not in your criteriaCase series, cross-sectional survey
10Wrong settingSetting outside the criteriaLaboratory study with no work duties
11No usable outcome dataMeta-analysis only: outcome reported without data you can poolMeans without any measure of spread

Ordering the cheap checks first (duplicate, publication type, language, date) means most reports are excluded on facts that need no judgment. "Full text not available" is missing on purpose: a report you could not get is "not retrieved", a separate box in the diagram. For why reasons must sum to the total, see PRISMA flow diagram mistakes.

For other review types, swap in their criteria: a scoping review uses wrong population, wrong concept, wrong context and wrong source type; a qualitative evidence synthesis adds "not qualitative data" and uses sample and phenomenon of interest in place of population and intervention.

Rules for settling disagreements (adapt for your protocol)

Cochrane requires a process for resolving disagreements to be set out in advance [2]. Copy and edit these rules.

  1. Independent first. Each reviewer decides without seeing the other's decision.
  2. Title and abstract: lean to inclusion. If either reviewer includes or marks Maybe, the record goes to full text. Only records both reviewers exclude are excluded.
  3. Full text: discuss. The two reviewers meet, reread the criteria and the relevant passage, and agree a final decision and one reason.
  4. Third reviewer. If they still disagree, a named third reviewer decides. Their decision is final.
  5. Criteria problems get fixed, not argued. If the same disagreement recurs, clarify the criterion in a dated protocol amendment and recheck earlier decisions.
  6. Measure agreement. Report percent agreement and Cohen's kappa per stage, calculated on decisions before resolution.
  7. Keep the trail. Never overwrite the original decisions; add the final decision in its own column.

A filled log (invented)

These rows are invented for illustration.

Record IDStageABAgree?FinalFinal reasonResolved by
R014TAIncludeIncludeYInclude
R027TAExcludeMaybeNInclude (to FT)Rule 2
R027FTExclude: wrong comparatorExclude: wrong designNExcludeWrong comparatorA+B, rule 3
R033FTIncludeExclude: wrong outcomesNIncludeThird reviewer
R041FTExclude: wrong populationExclude: wrong populationYExcludeWrong population

R027 shows the fixed order at work: both reviewers excluded it, for different reasons, and the earlier criterion in the order, comparator, became the main reason.

How to keep the log in AI for Research

The Systematic Review workspace records decisions as you screen and keeps the log for you.

  1. Share the review's project with your co-reviewer as can edit, or tick Use the AI as a second reviewer. Each record then needs two decisions.
  2. Screen with I, E (with a reason from the list) and M. The list is set by the review type and uses the reasons in the taxonomy above, plus "full text not available"; the order of checking is yours to apply.
  3. Open the Conflicts view. Each record where you disagree shows both decisions; choose Include or Exclude to set the final decision.
  4. Read the Agreement panel: Cohen's kappa with its label, percent agreement and the number of records compared, for each stage.
  5. On the Report tab, download All records and decisions (CSV): one row per record with the title and abstract decision, the full-text decision, the final decision and its reason, plus extraction columns.
  6. For the appendix, or for a team that screens in another tool, download the decision log as Word or PDF from the same tab, with the screening form and the exclusion-reason list. No credits.
Log columnWhere it is in the workspace
Each reviewer's decisionOn each record, under the abstract
Agree?Conflicts view; kappa and percent agreement in the Agreement panel
Final decision and reasonRecord state; "Final decision" and "Reason" columns in the CSV
Duplicates removed"Duplicates removed" list on the Search tab, with the match (DOI, PubMed id or title)
Counts by reasonPRISMA 2020 diagram on the Report tab

What the template and the workspace do not do

  • The CSV holds final decisions, not every vote. Each reviewer's own decision is shown on the record but is not a column in the export, and the date of each vote is not shown. Copy decisions into this log if your methods need them.
  • Decisions are not blinded. Once your co-reviewer has decided on a record, you see their decision under the abstract, so rule 1 depends on deciding before you look.
  • Reasons come from a fixed list per review type. You cannot type a custom reason. Use the note column of your own log for detail.
  • Resolving a conflict offers Include or Exclude. There is no third-reviewer role; a project editor resolves, and you record who did.
  • Reports not retrieved are not tracked separately. They are excluded as "full text not available"; move them to the not-retrieved box in your final diagram.

Who it is for

Review teams with two or more screeners, PhD candidates who must defend each exclusion in a viva (AI tools for PhD students), and clinical teams preparing a review for a journal (AI for medical research). The full workflow is on the systematic review software page.

Learn more

Sources

  1. Page MJ, McKenzie JE, Bossuyt PM, et al. The PRISMA 2020 statement: an updated guideline for reporting systematic reviews. BMJ. 2021;372:n71. https://doi.org/10.1136/bmj.n71
  2. Lefebvre C, Glanville J, Briscoe S, et al. Chapter 4: Searching for and selecting studies. In: Higgins JPT, Thomas J, et al. (eds). Cochrane Handbook for Systematic Reviews of Interventions, version 6.5. Cochrane, 2024. https://www.cochrane.org/authors/handbooks-and-manuals/handbook/current/chapter-04

Last updated 2026-11-13

Questions

More in the help center.

What is a screening decision log?

A screening decision log is a table with one row per record and stage, holding each reviewer's decision and reason, whether they agreed, the final decision, who settled any disagreement, and when. It is the audit trail behind your PRISMA flow diagram, your agreement statistics and your table of excluded studies, and it lets an examiner or peer reviewer check any single decision.

What are the most common exclusion reasons in a systematic review?

At full text, most exclusions fall under wrong population, wrong intervention or exposure, wrong comparator, wrong outcomes, wrong study design, wrong setting and wrong publication type, such as conference abstracts or editorials. Language and date limits, duplicate reports of the same study and missing outcome data for pooling make up most of the rest. Use the same short list throughout so counts can be summed.

Do I need to give exclusion reasons at title and abstract stage?

No. PRISMA 2020 asks for reasons for reports excluded at full text, not for every record excluded at title and abstract. Many teams still tick a reason during title screening because it speeds up discussion of disagreements, but you only need to report the number excluded at that stage. Every full-text exclusion needs one main reason.

How do you resolve disagreements between reviewers?

Write the rule in your protocol before screening. A common rule: at title and abstract, any record that one reviewer includes goes to full text; at full text, the two reviewers discuss each conflict with the criteria in front of them, and a third reviewer decides if they still disagree. Record who resolved each conflict and the final reason.

What if a study fails more than one criterion?

Give it one main reason so your exclusion counts add up to the total excluded. Check criteria in a fixed order, for example publication type, population, intervention, comparator, outcomes and design, and record the first one the study fails. State that order in your methods so readers know why a survey of students was counted under population rather than design.

Start free

No credit card needed. Upgrade when you need more.