Academic conference planning resources

Committees fail when two people think a task is theirs or nobody does. This guide defines the usual roles in an academic conference and what each one owns.

A good form collects what the committee will use and nothing else. This article lists the fields that earn their place and shows a worked example you can adapt.

The call for papers is a public announcement, not a submission form. This template covers what authors need to decide whether to submit, in the order they look for it.

A scientific meeting is planned backwards from its opening day. This timeline shows what has to be decided, and when, so that the call, the review and the programme do not collide.

What to lock before a call for papers opens, from topics to file rules.

A decision letter is the most-read message you will send. These templates cover acceptance, conditional acceptance and rejection, with the practical details authors need next.

A conflict of interest that is found after a score exists is a problem. One that is declared and enforced before assignment is a routine. This is how to set that up.

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.

How committees assign, conflict-check and decide without losing the audit trail.

Reviewers who score without shared anchors produce numbers that cannot be compared. A short rubric, agreed before the call closes, makes scores usable and decisions explainable.

Poster presenters need clear rules early. This guide gives organisers a ready structure for size, format, logistics and judging, and what to decide before accepting posters.

The book of abstracts is the record of what was presented. This template covers the front matter, the entry format and the checks that keep it accurate.

Parallel sessions save time and create clashes. This guide shows how to group abstracts, avoid conflicts between talks people want to see and keep the schedule editable.

A programme is a set of sessions, each with a chair, a room, a time and a list of presentations. This template shows the structure and an example day you can adapt.

An accepted abstract is not a presenter until someone has registered. This guide shows how to match the two lists, remind people on time and decide what happens to no-shows.

A fee table should reflect who attends and what they get. This guide explains the categories, deadlines and inclusions that most scientific meetings need, and how to keep them clear.

Most conference email problems come from sending too much, too late or to the wrong group. This plan sets out the messages, their timing and their audience.

A conference website answers a small set of questions in a predictable order. This checklist lists the pages that matter and the content each should carry.

When a scientific meeting needs more than one language on the public site.

Attendees need the same programme in the place they are standing. This article compares an app with a website by the tasks that matter, and shows when each is enough.

A chatbot is only as good as the answers behind it. These examples show the questions attendees ask most, how to word the answers and which ones should go to a person.

Success depends on what the meeting was for. This guide lists metrics for each stage, defines them precisely and shows how to compare editions without misleading numbers.

A survey is useful when its questions lead to decisions. This guide lists the questions worth asking each group and how to keep the survey short enough to be answered.

What changed in event technology — and why the scientific record still needs an owner.

How chatbots and voice interfaces change attendee communication at meetings.