How ReadCube Supports Systematic Literature Reviews and PRISMA Reporting

Updated

ReadCube supports a systematic review from first search through PRISMA reporting inside one platform. Its literature-review tools cover dual-reviewer abstract and full-text screening with automatic conflict flagging, custom data-extraction forms, AI Autofill that pre-fills extraction fields with links to the source for you to confirm, and PRISMA flow diagrams and audit trails that build automatically and export in the required format. This fits teams running a structured review who want screening, extraction, and reporting records in a single system rather than spread across separate tools.

Screening at every stage with dual reviewers

ReadCube runs abstract and full-text screening with independent reviewers. Each reviewer screens separately, and when their decisions disagree, the conflict is flagged automatically so the team can review and resolve it. This keeps the dual-reviewer requirement visible in the workflow instead of relying on manual comparison of spreadsheets.

The practical setup is: assign reviewers to a shared library, have each complete screening independently, then work the flagged conflicts until resolved. The expected result is a screening record where every included or excluded study has two independent decisions and a documented resolution.

Consistent data extraction with custom forms

You can define the exact fields your review needs, then extract across every study using the same form. This is the mechanism that keeps extraction consistent: the form fixes what gets captured, so each study is read against identical questions rather than ad hoc notes.

AI Autofill and source-linked confirmation

AI Autofill answers your extraction questions for you, with each answer linked to the source passage. You confirm the result rather than accept it blindly. The workflow is: define fields, let Autofill pre-fill, then check each answer against its linked source before confirming. The audit value comes from that link — every extracted value traces back to a specific passage.

PRISMA reporting and audit trails

PRISMA flow diagrams and audit trails build automatically from the review work and are export-ready in the required format. Because screening decisions, conflicts, and extraction records live in the same platform, the reporting step draws on the actual review history rather than a reconstruction.

Where the rest of the workflow fits

The review tools sit alongside the platform's broader capabilities, which matter for the search and reading stages:

Stage What ReadCube provides
Discovery Access to 123M+ indexed papers from the Dimensions research database; AI builds structured queries from plain-language descriptions
Reading and annotation Highlight, underline, draw, notes, and sticky comments directly on the PDF
Organization Tags, custom fields, and Smart Lists for large, shareable libraries
Monitoring Saved recurring searches with daily, weekly, or monthly alerts; AI filters new results against your criteria
AI use checks An AI Access Indicator flags, per paper, whether publisher terms permit AI use

The AI Assistant answers questions from your library and trusted databases, with each answer linked to the exact passage in the source, and can compare up to 20 papers at once to surface patterns, gaps, and contradictions.

What to check before committing

  • Review type fit. The screening, extraction, and PRISMA features are described for systematic-style reviews; confirm they match your protocol's specific requirements.
  • AI permissions. The AI Access Indicator exists because publisher terms vary per paper — check flagged restrictions before relying on AI extraction for a given source.
  • Team access. Shared libraries keep collaborators on the same evidence; confirm how your team will be set up before screening begins.
  • Pricing and plan limits. The site links to a pricing page but the supplied material does not state costs or plan restrictions, so check current terms directly at about.readcube.com/pricing before deciding.

For a team already running dual-reviewer screening and PRISMA reporting, the main draw is consolidation: screening conflicts, extraction forms, source-linked AI answers, and the PRISMA diagram all derive from one review record.