What does “automated reminders” actually mean? The four levels of deadline chasing
Every conference platform can send email, so a feature list that says “automated reminders” tells a program committee nothing about the week before a deadline. What matters is whether the software goes and finds the people who have done nothing — the reviewer who has not scored, the speaker who has not uploaded, the author who has not confirmed — and chases them, on a schedule you chose, without a staff member remembering to. This page gives that a scale, reports what the August 2026 research found across the category without naming anyone, and ends with the four questions that tell the levels apart.
The four levels
Level 4 — Chases non-completers on your schedule, in the venue’s time, once a day per person
The system finds the people who have not done what they were asked — the reviewer with unscored abstracts, the speaker without a file, the author who has not confirmed — and emails them on a days-before schedule the customer sets, evaluated in the event venue’s timezone, folded into one message per person per day across everything they owe, and stopped automatically the moment the task is done.
Level 3 — Chases non-completers automatically, on the vendor’s schedule
The system chases people who have not acted, on a deadline-relative schedule, but without the refinements above: the schedule is fixed by the vendor, the hour is the server’s, or one person can receive several reminders in a day.
Level 2 — Emails when something happens
Confirmation when a submission arrives, notice when a review is assigned, a decision letter when one is sent. Useful, and not chasing: nothing goes to the person who has done nothing.
Level 1 — Staff compose and send
Reminders exist as an email template. Working out who is late, and sending, is a human task.
What the research found
Of the twenty-three vendors whose documentation was assessed, thirteen do not document chasing people who have not acted at all: their reminders, where they exist, go to everyone or are sent by staff. Eight document chasing non-completers on a deadline-relative schedule. Of those, four let the customer set the days-before schedule rather than fixing it, and one documents all four criteria below. A vendor whose documentation is not public is counted as unproven, not as absent — the same rule this site applies everywhere.
Two patterns recur and are worth knowing before a demo. A vendor’s marketing may describe reminders “when you are waiting on someone” while its help center shows a template that goes to every reviewer regardless of whether they have finished; and a vendor may describe automated reminders while its help center instructs staff to chase reviewers by hand. Neither is dishonest — “reminder” is a wide word — but a committee that has been burned by it will want the help-center page, not the brochure.
The four questions
- It chases the people who have not acted, not everyone on the list.
- The customer sets the days-before schedule, per event, and can see the setting.
- The schedule is evaluated in the venue’s timezone, not the server’s.
- One reminder per person per day across everything they owe, stopped when the task is done.
Ask each as a demonstration rather than a question: have the vendor show the setting, show a reminder that went to someone who was late, and show that the same person was not reminded about something they had already done.
Where Rostrum sits
Rostrum chases at level four: it finds non-completers across reviews, speaker files and confirmations, sends on the days-before schedule you set per event, evaluates the schedule in the venue’s timezone, sends one message per person per day covering everything they owe, and stops the moment the task is done. The mechanics are in the manual, and every setting and its default is in the product catalog.