Systematic Review Team Roles: Who Actually Does What

A systematic review draws on genuinely different skill sets across its stages, and understanding what each role actually involves helps a team, even a very small one, structure responsibilities sensibly rather than assuming any single person can competently cover every stage equally well alone.

The lead reviewer or principal investigator

This role owns the overall research question, the protocol's final content, and the review's overall direction and timeline, typically making final judgment calls when other team members disagree and being ultimately accountable for the review's methodological integrity and eventual manuscript. On a small team, this role often also personally handles several other functions described below, but the coordinating responsibility itself is distinct from any single hands-on task.

The information specialist or search strategist

Ideally a medical librarian or someone with genuine database-specific search expertise, this role designs and executes the search strategy, translating the review's PICO question into effective, comprehensive search strings across each relevant database, and documenting the search for reproducibility. Many teams underuse or entirely skip this specialized role, defaulting to a less experienced team member designing the search, which is one of the more common reasons a review's search strategy later draws reviewer scrutiny.

Screeners

At least two people, ideally with relevant subject-matter familiarity, independently screen titles, abstracts, and full texts against the eligibility criteria, with a documented process for resolving disagreements. This role requires sustained attention and consistency across what can be a very large volume of records, and is often the most time-intensive individual role across the whole review.

Data extractors

Also ideally staffed by at least two people working independently, this role pulls structured data from each included study using the piloted extraction form, requiring careful attention to detail and, often, some subject-matter familiarity to correctly interpret how a given study reported its methods and results.

Risk-of-bias appraisers

This role can overlap with data extraction or be handled separately, and requires specific familiarity with whichever appraisal tool the review is using, matched correctly to each included study's design. Given how consequential correct tool selection and application is, having at least one team member with genuine appraisal-tool expertise, rather than everyone learning the tool for the first time mid-review, meaningfully improves consistency.

The statistician or methodologist

For reviews including meta-analysis, a team member with genuine statistical training handles model selection, heterogeneity assessment, sensitivity analyses, and the underlying code, ideally involved from the protocol stage rather than brought in only once raw extracted data is ready to pool, since statistical planning decisions made early affect how data needs to be extracted in the first place.

The writer or manuscript lead

This role drafts the final manuscript, checks it against PRISMA 2020 item by item, and manages revision through peer review, requiring both clear writing ability and genuine familiarity with what a methods-focused reviewer will specifically check. This is sometimes the lead reviewer's own role, sometimes delegated to a team member or external editor with particular manuscript-preparation strength.

Structuring a very small team realistically

A team of two or three people cannot staff every role with a dedicated specialist, and realistically means individuals covering multiple functions -- perhaps one person handling search strategy and statistics, another handling screening coordination and manuscript writing, with both jointly serving as the two independent screeners and extractors the methodology requires. What matters most on a small team is still maintaining genuine independence for the specific steps requiring it, like dual screening, even when the same two people are wearing multiple other hats across the rest of the project.

When to bring in outside expertise

Recognizing which specific roles genuinely benefit from outside expertise your team doesn't have internally -- often the information specialist and statistician roles specifically -- and seeking consulting support for exactly those functions, rather than either attempting every role internally regardless of fit or outsourcing the entire project, is often the most resource-efficient way to strengthen a review's weakest points without unnecessary total cost.

Documenting roles in your eventual manuscript

Beyond internal team organization, documenting who performed which specific role is increasingly expected in author contribution statements, reflecting current ICMJE authorship guidance, and planning this documentation from the start, rather than reconstructing it at submission time, is a small administrative step worth building into your project's ongoing record-keeping from day one.

Role clarity and preventing project delays

A surprising number of systematic review delays trace back not to genuine methodological difficulty but to simple ambiguity about who was actually responsible for a specific task, leaving it undone until someone eventually notices the gap. A brief, written role assignment document, agreed upon at the project's outset and revisited if the team's composition changes, is a disproportionately effective, low-cost safeguard against this entirely avoidable category of delay. Revisiting this document briefly at each major project milestone, not just at the outset, catches role drift as a project evolves and keeps everyone's actual current responsibilities aligned with what was originally agreed, rather than allowing informal, undocumented shifts to accumulate unnoticed over a longer project timeline. Teams that treat this kind of light, ongoing project governance as a genuine priority, not an administrative afterthought, consistently report smoother collaboration and fewer last-minute scrambles than teams that leave role clarity to informal assumption throughout the life of a longer, more complex systematic review project. This kind of light, consistent project governance costs relatively little time to maintain but reliably prevents a disproportionate share of the avoidable friction that otherwise accumulates silently across a longer, multi-person systematic review effort. Ultimately, a systematic review is a genuinely collaborative undertaking, and treating team structure and role clarity with the same deliberate care applied to search strategy or statistical analysis is what allows a group of individuals to function as a genuinely coordinated, efficient review team. That coordination, once established well, tends to make every subsequent stage of the review noticeably smoother than it would otherwise have been. This is a small, deliberate investment that consistently earns back far more than it costs.