Skip to content

A Duetone product

ReviewsDue

No passwords. No bidding. Just reviews. ReviewsDue runs a conference’s peer review, from the first submission to the final program.

A reviewer’s workspace in ReviewsDue: the submitted paper’s PDF on the left, the review form with an overall rating and a detailed review on the right.

One place for everyone in the review

The user manual covers each role, and a skill for your own AI assistant can answer how-to questions from it. The assistant never sees papers, reviews or your account.

Matching without bidding

Reviewers upload a few of their own papers instead of bidding, into a personal library they can reuse in every conference, and ReviewsDue checks that they are listed as an author.

It scores how closely each reviewer’s work matches each submission, with Latent Semantic Indexing or SPECTER2 semantic embeddings, as the chairs choose, then proposes an optimal assignment that respects conflicts, declined papers and every reviewer’s load limits. Chairs review the proposal, with every addition and removal listed, before anything is saved.

The Assign Reviewers grid: papers with their required, assigned and completed reviews, and below them the committee with each reviewer’s similarity to the selected paper, load and remaining capacity.

Conflicts of interest, found automatically

ReviewsDue checks each committee member’s co-authorship against every paper’s authors, using public OpenAlex, Crossref and DBLP records and papers published through ReviewsDue, matched by ORCID iD. Co-authors on committee members’ signature papers are checked too.

A name or co-author name match is only a possible conflict: it goes to review and keeps no one away until it is confirmed. Authors can confirm or decline possible conflicts when they submit. Chairs triage the uncertain ones one after another, and can look up any person to see their conflicts with the evidence. A dismissal is remembered until new evidence appears. Double-blind tracks never reveal authors to committee members.

Chairs can also turn on institutional conflicts, and committee members and authors can declare a conflict with each other.

The Conflicts page open on one committee member: the summary of what was checked, a conflict with an author on a paper, each source’s result, and the shared works behind it with their authors.

Every role, every phase, every track. Nothing left to chance.

A conference is thousands of small questions about who may do what, and when. ReviewsDue answers each one with an explicit rule in a tested lifecycle table, and when the answer is no, it says why.

Each answer also weighs who is acting (12 roles, from conference chair to site admin), the track’s phase (6 phases, from registration to decisions released), and the track’s own settings (7 groups), on every track.

Allowed moveAllowed edit in placeRefused, with its reasonOne square: one action, from one state
List all 43 lifecycles
  • Account deletion: 25 answers, 13 refusals
  • Assignment: 84 answers, 54 refusals
  • Author claim: 117 answers, 88 refusals
  • Author identity: 25 answers, 17 refusals
  • Bulk email: 128 answers, 96 refusals
  • Conference request: 30 answers, 21 refusals
  • Conflict: 72 answers, 15 refusals
  • Conflict check: 96 answers, 63 refusals
  • Conflict lookup: 49 answers, 37 refusals
  • Conflict resolution: 70 answers, 53 refusals
  • Data export: 42 answers, 31 refusals
  • Decision: 80 answers, 56 refusals
  • Decision notices: 50 answers, 25 refusals
  • Delegate proposal: 20 answers, 13 refusals
  • Delegation: 56 answers, 31 refusals
  • Email: 207 answers, 128 refusals
  • Expertise file: 990 answers, 891 refusals
  • Expertise upload: 56 answers, 42 refusals
  • Format check: 60 answers, 14 refusals
  • Invitation: 54 answers, 38 refusals
  • Matching: 312 answers, 161 refusals
  • Meeting plan: 6 answers, 0 refusals
  • Meeting tracker: 28 answers, 8 refusals
  • Paper file: 84 answers, 61 refusals
  • Paper in round: 28 answers, 15 refusals
  • Paper text: 120 answers, 87 refusals
  • PDF check: 84 answers, 44 refusals
  • Plan upgrade: 25 answers, 20 refusals
  • Program: 132 answers, 81 refusals
  • Rebuttal: 20 answers, 13 refusals
  • Reminder wave: 12 answers, 7 refusals
  • Request email: 63 answers, 34 refusals
  • Review: 4 answers, 1 refusal
  • Review round: 15 answers, 7 refusals
  • Session titles: 42 answers, 34 refusals
  • Shepherding: 77 answers, 52 refusals
  • Signature paper: 32 answers, 20 refusals
  • Submission: 72 answers, 52 refusals
  • Survey: 63 answers, 47 refusals
  • Text analysis: 153 answers, 119 refusals
  • Text signal: 128 answers, 71 refusals
  • TPC meeting: 20 answers, 14 refusals
  • Withdrawal request: 20 answers, 7 refusals

Built for large programs

Track chairs, area chairs, TPC members, reviewers and authors each get a dashboard of what is due.

Running a conference or workshop?

Request a conference on reviewsdue.com. It is free for up to 100 submissions, and authors and reviewers never pay.