One screening module with traceable handover decisions
Real sources · Illustrative request · Sample version
Customer question
A fictional CRO outsources one search-and-screening module; the downstream team handles extraction and analysis.
Can the receiving team see where each record went, why it was excluded and which disagreements remain?
Usable handover means searches, stable record IDs, exclusion reasons and review status. Meta-analysis is outside this module.
Illustrative screening volume
Numbers illustrate handover only, not a completed project. PRISMA 2020 records flow; it does not establish screening accuracy.
Analysis excerpt
| Check | Finding / sample content | Use |
|---|---|---|
| Sample record R0120 | Full-text exclusion: wrong population; source and review fields retained | Receiving team can locate the source and reason |
| Sample disagreement R0084 | Two decisions differ; status remains unresolved | Update decision and rationale after adjudication |
Delivery manifest
| File | Format | Contents |
|---|---|---|
| search-log.docx | DOCX | Databases, database-specific searches, dates and export batches. |
| screening-decisions.csv | CSV | record_id, screening stage, decision, reason and review status. |
| handover-manifest.json | JSON | Field definitions, file versions, unresolved disagreements and PRISMA flow counts. |
This is an illustrative formal delivery manifest. This pack supplies an HTML report, CSV tables and a source register. Agree formal formats, quantities and scope in the quote.
Acceptance criteria
- Acceptance follows the agreed file structure, source locations, missing-value conventions, sampling rules and correction process; screening reasons and disagreements remain traceable.
Sources
- PRISMA 2020: Flow diagram
https://www.prisma-statement.org/prisma-2020-flow-diagram