Skip to main content

Published 2026-03-24

Reviewer invitation email templates for conferences

Reviewers say yes to clear, small requests. These three templates cover the invitation, the reminder and the thank-you, with the details that make a quick answer possible.

What a reviewer needs to decide

A reviewer wants to know four things before answering: how many abstracts, by which date, on which topics, and what happens if they must decline. Put them in the first three lines and link to a one-click response.

Invitation

Send it before the submission window closes, so reviewers can block time.

Subject: Invitation to review for [Conference name] Dear [Name], The scientific committee of [Conference name] ([dates], [city]) would be grateful if you could review up to [number] abstracts in [topic area]. Review period: [start date] to [end date] Time needed: about [minutes] minutes per abstract Format: online, scored against a five-criterion rubric Please accept or decline here: [link]. If you know of a conflict of interest with a submission, you will be able to declare it before scoring. Thank you, [Programme chair]

Reminder

Send one reminder to people who have not replied and a separate one to reviewers who accepted but have not finished. The second message should state the number of abstracts still open and the exact deadline.

Subject: [Conference name]: [number] abstracts still awaiting your review Dear [Name], Thank you for agreeing to review. You have [number] abstracts open, and the review period closes on [date]. If you cannot finish, please tell us by [earlier date] so we can reassign them: [link]. [Programme chair]

Thank-you

A short thank-you after the decisions are issued costs nothing and increases the chance that the reviewer accepts next year. Say what the review contributed: the number of abstracts accepted, the number of sessions built.

Who to invite and how many

Invite more people than you need, because a share of them will decline or go quiet. A practical rule is to invite about one and a half times the number of reviewers you need, and to keep a reserve list of another ten per cent. Choose people by topic first, then check workload and conflicts. Avoid inviting only the most senior names: mid-career researchers often review faster and more carefully, and being asked is a recognition that they value. Where possible, ask the track lead to name the invitees, since a personal request from a colleague has a much higher acceptance rate than a message from the secretariat.

Instructions email at the start of review

When the review period opens, send accepted reviewers a short message with everything they need. Do not assume they remember the invitation.

Subject: [Conference name]: your review assignments are ready Dear [Name], Thank you for agreeing to review for [Conference name]. You have been assigned [number] abstracts. 1. Log in at [link] and open “My assignments”. 2. For each abstract, first check whether you have a conflict of interest. If you do, mark it and skip the abstract. 3. Score the five criteria and select a recommendation. 4. Write one short comment for the author. Use the confidential field for remarks meant only for the committee. Deadline: [date and time, time zone]. Rubric and examples: [link]. Questions: [address] Thank you, [Programme chair]

Handling declines and silence

A decline is a normal answer, not a failure. Reply within a day, thank the person and ask whether they can suggest a colleague. For people who do not answer, send one reminder after five days and a second, shorter one after ten. If there is still no reply, treat it as a decline and move on; chasing a fourth time costs more than replacing the person. Record every outcome in the same place as the assignments so that the chair sees at a glance how many reviewers are confirmed, pending and lost.

Subject: Re: Invitation to review for [Conference name] Dear [Name], Thank you for letting us know, and no problem at all. If you can suggest a colleague who works on [topic], we would be grateful for a name and an email address. Best wishes, [Programme chair]

A review timeline you can copy

Reviewers respond better to a schedule they can see in advance. This is a compact version for a five-week review.

Week 0 Invitations sent; replies requested within 7 days Week 1 Reminder to those who have not replied; assignments prepared Week 2 Assignments open; instructions email sent Week 3 First reminder: “Please start your first three abstracts” Week 4 Reminder with the number of abstracts still open Week 5 Deadline; final reminder two days before; reassign missing reviews the next day

Say thank you in ways that matter

Reviewers work without payment and often without credit. Small gestures help, and none of them need a large budget. Thank each reviewer individually after the decisions are sent. Where your rules allow, offer a certificate of reviewing, a reduced registration fee or a mention in the proceedings. Tell reviewers how their scores were used, for example how many abstracts were accepted and how many sessions were built. The people who feel that their work was noticed are the people who accept again next year.

Handling reviewers’ personal data

Reviewer lists contain names, emails and expertise. Treat them as personal data. Send invitations individually or through a mail merge, never by copying everyone in one message. Tell reviewers what you store, why and for how long, and give them a contact for questions. Do not publish the list of reviewers of individual abstracts, and be careful about publishing the full committee list without agreement. If you use a platform to send messages, check where it stores data and what your organisation’s policy requires.

Subject lines that get opened

The subject line decides whether an invitation is read. Name the meeting and the request in the first words, keep it short, and avoid urgency that is not real. “Invitation to review for [Conference name]” outperforms a vague “Request for help”. For reminders, put the number of open abstracts and the date in the subject, since these are the facts the reviewer needs. Avoid capital letters and exclamation marks, which push messages towards spam folders, and always send from an address that a reviewer can reply to.

Practical tips

A few habits improve response rates.

  • Address the reviewer by name and mention their area, not a mass-mailing greeting.
  • Offer an easy way to decline and suggest a colleague.
  • Set an earlier internal deadline than the public one.
  • Keep a reserve of reviewers for unexpected withdrawals.
  • Record acceptances and declines in the same place as assignments.

Keep reading

  • Peer review
  • Abstract review rubric: scoring criteria and examples
  • How to manage peer review for academic conferences
  • Peer review