For teams

Run reviews like releases.

Roles, comments, two-person sign-off, and an audit trail—all built into the same end-to-end review platform. Designed for HEOR consultancies, HTA agencies, guideline committees, and Cochrane-style review teams.

Built for the teams shipping 100-day JCA dossiers, NICE submissions, and Cochrane updates — where one slip in the audit trail kills the submission.

  • 4 rolesPermission controlled
  • 5 milestonesSign-off gates
  • 2-personApproval rule
  • 1 inboxFor mentions, sign-off & digests
Built into the platform

Six capabilities. One coherent team product.

01

Roles & permissions for accountable review work.

Four roles — admin, lead reviewer, reviewer, viewer — control who can edit, review, approve, or observe. Private projects stay invisible to anyone outside the team — including search engines and people who guess at URLs.

  • Admin can invite, promote, delete, and approve sign-offs.
  • Lead Reviewer edits protocol, assigns workload, adjudicates conflicts.
  • Reviewer submits screening decisions and extraction reviews — read-only on protocol.
  • Viewer is read-only across the team — useful for stakeholders, methodologists, and auditors.
What they can doAdminLead reviewerReviewerViewer
Invite, promote, and deleteCan doNot statedNot statedRead-only
Approve sign-offsCan doNot statedNot statedRead-only
Request sign-offNot statedCan doNot statedRead-only
Edit protocolNot statedCan doRead-onlyRead-only
Assign workloadNot statedCan doNot statedRead-only
Adjudicate conflictsNot statedCan doNot statedRead-only
Submit screening decisionsNot statedNot statedCan doRead-only
Submit extraction reviewsNot statedNot statedCan doRead-only
Can doRead-onlyBlank: not stated for that role
02

Comments & @mentions on every object.

Threads anchor on analyses, studies, individual screening decisions, extracted outcomes, and extraction reviews. You can only @mention people on the same review, so a stray name from another team never sends a notification by accident.

Thread anchored on an extracted outcomeOpen
  • One level of replies per thread, collapsed for readability.
  • Authors edit their own comments; admins and lead reviewers can soft-delete inappropriate content while preserving audit history.
  • Resolve threads when the discussion is finished; re-open any time.
  • Read and write access gated by the same team-role permissions as the parent analysis.
03

Unified notifications & email digest.

Every team event lands in one bell-icon inbox: @mentions in comments, invitations, adjudication pings, sign-off requests, and the living-review digest. One pipeline, one set of preferences.

One inbox, five kinds of event
  • @mention in a comment
  • InvitationSends immediately
  • Adjudication pingSends immediately
  • Sign-off request
  • Living-review digest
  • Per-user preferences route each kind to immediate email, digest email, or in-app only.
  • Digest cadence is daily, weekly, or off — picked per notification kind.
  • Safe defaults: invitations and adjudication requests send immediately; informational events are opt-in.
  • Notification access is strictly per-user — you only ever see and act on your own.
04

Two-person protocol sign-off.

Five strict milestones — protocol locked → screening locked → extraction locked → analysis frozen → manuscript locked — let Cochrane- and HTA-style reviews enforce each stage before the next opens. The two-person rule is built in: whoever requests sign-off can never be the same person who approves it.

  1. RequestA lead reviewer requests sign-off with a milestone and optional notes.
  2. SnapshotThe system freezes the protocol, eligibility, and extraction form as an immutable snapshot.
  3. DecideEvery admin on the team is notified; one admin approves or rejects.
  4. LockOnce locked, edits to that stage are blocked until an admin reverts the milestone.
05

Workload assignments & conflict adjudication.

Split studies across reviewers per phase (abstract / full text) and slot (A / B). Auto-balance round-robins deterministically — refresh the page and you see the same preview before you commit.

Review mode, picked per analysis
AIMeTwo decisions per study, compared.
  • Per-reviewer “my queue” view stays fast even on 50,000-study reviews.
  • Pick the review mode per analysis: single, dual AI + me, or dual two humans.
  • Per-study peer-status badges — Agreed, Awaiting peer, or Conflict — visible without opening the study.
  • Conflict adjudication shows a field-by-field diff between reviewer submissions.
06

Versioned protocols & audit-ready exports.

Every sign-off snapshots the analysis state into an immutable version. Every signed-off version is listed in chronological order, and you can diff any two consecutive versions side-by-side to see exactly what changed in the protocol, eligibility, or extraction form.

Signed-off versions, in order
  1. v1Protocol lockeddiff v1 ↔ v2
  2. v2Screening lockeddiff v2 ↔ v3
  3. v3Extraction locked
  • PRISMA flow updates automatically as studies move through the pipeline.
  • Source-linked audit trail: every effect estimate traces back to the originating PDF snippet.
  • Sign-off events, role changes, and adjudication decisions are all logged.
  • Sign in with Google or Microsoft — no extra account or password to manage.
Organisations

One home for your institution’s evidence.

An organisation is one home for an institution’s workspaces, people and reviews, set up from the Teams page.

Guests are invited by an owner or admin, need a sponsor, and their access is time-limited.

Invitations
Owners and admins invite people by email.
Archiving
Owners and admins archive workspaces.
Audit page
Downloads as a spreadsheet.
Data page
Retention, whether data may be used for AI training, archive and closure.
Personal plans
Personal plans and review slots are unchanged. Your personal library stays as it is when you join an organisation.
Evidence library

Publish signed-off reviews to the people who rely on them.

The organisation publishes signed-off reviews, with a curator’s attestation, to invited readers.

  1. Signed-off reviewPublishing starts from a review that has been signed off.
  2. Curator’s attestationEach published review carries a curator’s attestation.
  3. PreviewCheck the review before publishing it.
  4. Published to invited readersThe organisation publishes to the readers it invites.
  5. “Ask the library”Readers get an answer with references.

Ask the library

Answers come only from published reviews, with references. Pick an example question to see where the answer appears.

Reader asksWhat does our published evidence say about this intervention?
Drawn only from this organisation’s published reviews.
How teams use it

From kickoff to manuscript, on a single timeline.

The same five milestones every Cochrane- and HTA-style review already uses, but enforced by the platform instead of a shared spreadsheet. Every milestone snapshots the protocol so a regulator can replay the review months later from the same inputs.

Two-person sign-off across five milestonesSelect a milestone to step the review forward.
  • GDPR-compliant
  • Sign in with Google / Microsoft
  • Full audit trails
  • BYOK on Enterprise
  • Server-enforced role permissions

Bring your team. Ship your next review.

Free tier runs the full pipeline on one real review. Team plans start at 3 seats with 7 pooled reviews per seat per month.

Talk to sales