ReviewerBase / A proposal for nonprofit infrastructure

Peer review is in danger.
Let’s fix it.

One shared reviewer network for journals and conferences. Coordinate expertise, availability, and review recognition — with credits earned for reviews and spent on submissions.

Help make it happen

01 / The problem

More papers.
Too little time
to review them.

  • Reviewers get little recognition. Essential review work goes unrewarded, while requests pile up.
  • Low-quality submissions consume scarce attention. AI makes them easier to produce at scale while authors aim to maximize their output.
  • Journals and conferences struggle to recruit reviewers. Exhausted reviewers, rejected review requests, slow processes.
  • Authors pay the price. Long waits and rushed, low-quality reviews undermine useful feedback and fair decisions.

This pressure is already changing policy: ICLR’s 2027 submission policies address submission volume and low-quality, AI-generated content.

We can let peer review deteriorate, or design a better system. ReviewerBase aims to do the latter!

02 / Our proposal

Share the reviewer pool.
Choose how to participate.

01

One shared reviewer database

A common pool for journals and conferences across the publishing system, with expertise, availability, and contact preferences maintained by reviewers. Review requests go through ReviewerBase, without giving venues reviewer email addresses. Venues can use discovery, availability, and review recognition without adopting credits.

02

Optional credits for reviews and submissions

Participating venues can award credits for confirmed reviews and accept them for submissions. A credit is a credit, wherever it was earned: venues accepting credits count them equally across the network. Venues can set their own submission requirements, with shared safeguards governing credit issuance. The goal is to attach costs to submissions and remunerate reviews at the same time.

The intended effect: more reviews, fewer low-quality submissions. Where venues adopt credits, reviewing earns submission capacity; requiring credits gives authors a reason to not submit low-quality work.

03 / Expected benefits

What changes?

For reviewers

  • Set how many reviews you take on, for which venues, and on which topics. Pause or opt out easily.
  • More fitting and targeted review requests by journals that value your time.
  • Receive recognition for confirmed reviews, whether or not a venue uses credits.
  • Receive submission credits where a journal or conference opts into the credit system.

For journals & conferences

  • Find reviewers by topic, current availability, and willingness to respond.
  • Assess relevant reviewing track records through permission-controlled information.
  • Recognize contributions and optionally reward reviewers through a shared workflow.
  • Optionally use credit requirements to discourage low-effort submissions and encourage more reviewing.

For the publishing system

  • More available reviewers will shorten waits and give each paper more attention.
  • Fewer low-quality submissions will leave more time for substantive, fair reviews.
  • Review work counts across venues, sharing the burden beyond individual journals and conferences.
  • We might finally achieve balance between submission and reviews.

04 / Conditions for this to work

Connect existing systems.

Integrations with ORCID and editorial platforms so contributors do not have to maintain another isolated record.

Design against abuse.

Prevent fake reviews, duplicate credits, and unlimited credit issuance. Protect confidential data and provide fair entry routes for researchers without review opportunities.

Keep it nonprofit.

Community governance should protect the system from control by a single publisher or commercial owner. Nonprofit status needs transparent rules and oversight.

05 / Questions

Before you take part.

These are proposed principles. We will agree on detailed policies with pilot participants.

Can a venue join without using credits?

Yes. Reviewer discovery, availability, invitation preferences, and review recognition are useful on their own. Credits are an optional layer; venues retain control over their editorial policies.

Why not pay reviewers directly?

We do not rule out payments. Paying reviewers is hard to coordinate without shared reviewer infrastructure. Once our infrastructure is in place, monetary payments can easily be built on top, allowing journals to offer real money for reviews. However, there is also a gaming risk, which is why it is not part of our core concept right now.

What if I have not had opportunities to review?

A lack of credits should not exclude newcomers or researchers with limited review opportunities. Credit pilots need fair entry routes, such as waivers, before introducing submission requirements. The exact arrangements remain open.

Who confirms that a review was completed?

An authorized representative of the journal or conference confirms completion under a disclosed policy. Records identify the confirming venue and prevent duplicate credit claims. Confirmation establishes that a review took place, not provide an objective rating of its scientific quality.

How will you prevent low-quality reviews submitted just to earn credits?

When acknowledging a review, editors can provide a non-public quality score. These scores help guide future review requests, so reviewers who consistently submit low-quality reviews are invited less often.

How can reviewers be contacted?

Review requests go through ReviewerBase, without sharing reviewers’ email addresses. Reviewers can manage their availability and contact preferences, respond to invitations, and pause new requests. This helps venues respect reviewers’ capacity while protecting their contact data.

Who can see my information?

Researchers should control their availability, contact preferences, and participation. Access to reviewing activity should be permission-controlled. Confidential reports should remain with the relevant venue wherever possible, and personal contact details should not become a commercial product. Specific access and retention rules still need to be defined.

06 / The project

Help shape what comes next.

Contact: thomas.wolgast@openscientia.org

We are validating the idea by asking researchers and venues to express interest. If a certain number of reviewers and institutions participate, we will build it.

ReviewerBase is a concept for nonprofit, community-governed infrastructure. You can express interest below or contact Thomas directly to share feedback.

07 / Take part

This needs reviewers.
And the venues
they review for.

The more researchers, journals, conferences, and institutions participate, the more useful the shared pool and the credit system become.

Express interest in updates, help define the rules, or discuss joining as a partner.

Help build ReviewerBase.

We are looking for supporters. Only your email address is required.

What interests you? (optional)

By submitting, you agree that we may store your details to record your interest and contact you for the purposes you select. You can withdraw at any time.