Academic congress management: running the paper process end to end

In academic congress management, the paper process is a single chain: call, submission, peer review, decision, scientific programme, abstract book and certificates. Building that chain in one system, where each step reuses the data of the step before, rather than in email threads and scattered spreadsheets, noticeably reduces both errors and the secretariat's workload. This guide walks through the decisions you need to make at each step, in order.

Why should the paper process run as one flow?

Most secretariats assemble the process piece by piece: papers are collected with a form tool, sent to reviewers by email, decisions are kept in a spreadsheet, the programme is drafted in a text file and certificates are produced one by one after the event. Data is retyped at every hand-off, and every retyping is a fresh chance for error. A single typo in the submission form, if nobody catches it, travels all the way to the abstract book and the certificate.

In a single flow, a paper is entered once and every later step works from the same record. Reviewer assignment, decision, session slot, book page and certificate are simply different states of the same paper. Correct an author's details and the correction appears everywhere; you can see on one screen which paper is waiting at which stage.

This is not only about efficiency. Traceable scientific committee decisions, protected reviewer identities and timely updates to authors directly shape a congress's academic reputation. In a fragmented process, those guarantees depend entirely on the team's attention and memory.

A paper should be entered once; review, programme, book and certificate should all be states of the same record.

How do you write a call for papers?

A good call answers every question an author might ask before submitting. The theme and sub-themes, accepted presentation formats, abstract length, languages, review method and key dates should all be stated plainly. A vague call is the most common cause of query emails to the secretariat and of submissions in the wrong format.

• State the main theme and the sub-themes under which papers should be submitted.
• List the accepted formats, such as oral, poster or online presentation, and the conditions for each.
• Define the abstract word limit, the number of keywords and the accepted languages.
• Announce in advance how many papers one person may submit and how many authors a paper may have.
• Say whether review will be single-blind or double-blind and how many reviewers will read each paper.
• Publish the submission deadline, decision date and full-paper deadline in a single calendar.

Keeping key dates in one place on the congress website, and showing them from that same source in the call, in emails and on forms, removes the familiar problem of different pages listing different dates. If a deadline is extended, the change has to appear on every channel at the same moment.

If you publish the call in two languages, every sub-theme needs an exact counterpart in both. Those names later become headings in the programme and the abstract book, so consistency at the call stage makes every later step easier.

How should submission be organised?

The submission form is the data source for everything that follows. It should therefore collect not just the abstract but every piece of information the programme and book will need, as structured fields: title, abstract, keywords, sub-theme, presentation format and, for each author, first name, last name, institution, email and whether they are the corresponding author.

Asking authors to type all names into one box, separated by commas, is the most common mistake. It means hours of manual cleanup when building the author index for the book and the names on certificates. Each author should be entered on a separate row with separate fields, in an order the submitting author controls.

A confirmation email after submission, a personal panel where authors can follow their paper's status, and the ability to edit until the deadline all reduce support requests. Closing submission automatically at the deadline turns requests for extra time into a rule that applies equally to everyone.

Under KVKK, Turkey's data protection law, the submission form should state clearly why authors' personal data is processed, and the consents given should be recorded. Check which texts you need with your legal adviser and the current guidance of the Personal Data Protection Authority; this article is not legal advice.

How should peer review be run?

Review is the most labour-intensive and error-prone part of the process. The first decision is the method: in single-blind review the author does not know who the reviewer is; in double-blind review the reviewer cannot see the author's identity either. If you choose double-blind, author names must be removed not only from the form but also from uploaded file names and the abstract text.

Assign reviewers by sub-theme and expertise, balance each reviewer's load and check for conflicts of interest. A reviewer from the author's own institution undermines the point of blind review. Doing these checks by hand across hundreds of papers is close to impossible; letting the system propose assignments for the committee to approve is far more reliable.

• Relevance to the congress theme should be scored as a separate criterion.
• Clarity of method and whether the findings are adequately reported should be asked separately.
• The reviewer's recommendation should be one of accept, accept after revision or reject.
• Comments for the author and notes for the committee only should be kept in separate fields.
• If the reviewer suggests a different presentation format from the author's choice, the reason should be given.

The decision belongs to the scientific committee; the reviewer's recommendation is one input to it. The acceptance, revision or rejection letter that follows should pass on reviewer comments without any identifying details. A paper returned for revision goes back to the author, who uploads a new version, and the process continues on the same record.

How do you build the scientific programme?

Placing accepted papers into the programme means solving three constraints at once: room capacity, session length and the fact that a speaker cannot be in two places at the same time. Two papers by the same author landing in different rooms at the same hour is the problem most often spotted after the programme is published.

Grouping sessions by sub-theme, giving every session a chair and planning oral and poster sessions separately produces a programme people can actually read. A scheduler that detects room and speaker clashes on its own lets you run that check before publication.

The programme keeps changing after publication: a speaker cancels, a session moves to another room. Generating it from one source keeps the website, the PDF and the session file attendees add to their own calendars showing the same up-to-date information.

Online presentations add another layer to the programme. Sessions with remote speakers, their connection details and technical rehearsal times should be defined within the programme itself, and session chairs should know in advance who will be in the room and who will join remotely. In mixed sessions, leaving a short buffer before each talk keeps a connection delay from pushing back the whole session.

How do you prepare the abstract book and certificates?

The abstract book is the congress's permanent academic record. Abstracts of accepted and presented papers are published in order of sub-theme or session, with a table of contents and an author index. If structured data was collected at submission, most of the book can be generated automatically, leaving editorial review as the remaining task.

If there will be a full-paper book, give authors a template, collect full texts against a separate deadline and open that submission only for accepted papers. Whether the book will carry an ISBN and under which licence it will be published should also be announced with the call.

Certificates look like the last small job, yet they draw some of the most complaints: misspelled names, forgotten co-authors, certificates for papers that were never presented. Generating attendance and author certificates in bulk from registration and paper data, and tying access to payment and attendance status, prevents these mistakes.

The work does not end when the congress does. The abstract book, programme and committee lists should be published on a permanent archive page of the congress website, and the paper files stored as an orderly archive. Being able to reach all past editions of a recurring congress from one address signals continuity, which reassures both returning authors and researchers attending for the first time.

Frequently asked questions

How many reviewers should read each paper?

A common practice is to have every paper read by at least two reviewers, with the committee adding a third when opinions diverge. Decide the number at the call stage, based on the expected volume and the size of your reviewer pool, and announce it.

Should a paper go into the programme if no author has registered?

Many congresses make registration by at least one author a condition for inclusion. State the rule in the call and check it in the system before the programme is finalised, so that papers nobody will present stay out of the book and the programme.

Should posters be reviewed differently from oral papers?

The scientific criteria should stay the same; a poster does not mean a less rigorous review. The difference lies in fit with the format: some work suits visual presentation, other work suits discussion. Letting reviewers recommend a format with a reason gives the committee flexibility when building the programme and makes it easier to explain to authors why their work was accepted as a poster.

When should the abstract book be published?

The abstract book is usually published during the congress or right after it. A full-paper book can follow weeks or months later, once authors have had time to revise; putting that timeline in the call sets clear expectations.

What can be reused for next year's congress?

Sub-themes, the review form, the reviewer pool, document templates and the site structure can all carry over to the next year. Past programmes and abstract books should stay in an archive that remains accessible on the congress website.

The first step for your next congress

For your next congress, start by drawing the current process on paper: which steps a paper passes through, where data is retyped at each step, and which errors appear at which hand-off. That map shows on its own what needs to be automated.

Once every step from call to certificate runs on the same data, the secretariat is freed from technical chores and can spend its time protecting scientific quality. At Bir Web Ajans we build this whole flow on Nova CongressPort, which gives each congress its own domain and its own database.