Writing a conference abstract and getting it accepted are two different problems. Once the text is ready, the submission itself runs through a dedicated abstract-management platform with its own account setup, submission form, review workflow, and deadlines — and a surprising share of avoidable rejections come from mishandling that process, not the writing. This guide covers the mechanics: what an abstract-management system actually does, how the review timeline typically runs from submission to decision, and how abstract acceptance connects to presenter registration and the final program.
What an abstract-management system does
Most societies and conference organizers no longer collect abstracts by email. They use a dedicated abstract-management platform — common examples include Ex Ordo, Oxford Abstracts, EDAS, EasyChair, ConfTool, and OpenConf — that handles the submission form, reviewer assignment, scoring, and notifications in one system. These platforms typically provide:
- A structured submission form with required fields (title, author list, affiliations, topic/track selection, word-count-limited abstract body, keywords, and often a separate field for disclosures or funding).
- Track or session-type routing, where the submitter selects a topic area, presentation format (oral, poster, workshop), or session type, which determines which reviewer pool and review criteria apply.
- An automated reviewer-allocation engine that matches submissions to reviewers by declared expertise or track, and enforces a review-load cap per reviewer.
- Configurable blind review. In single-blind review, reviewers see author names but authors don’t see reviewer identities; in double-blind review, neither side is identified. Which model applies is set by the organizer, not the submitter, and it can change what you’re allowed to put in the abstract text itself — double-blind tracks commonly require the submission to omit author names, institutional affiliations, and identifying acknowledgments from the abstract body, with that information collected separately in the submission form’s metadata fields instead.
- Status tracking and notifications, so submitters can see whether an abstract is in draft, submitted, under review, or decided, usually with automated emails at each transition.
Because the platform enforces the submission form’s structure programmatically, formatting problems that a human editor might tolerate — going over the word limit, leaving a required field blank, uploading the wrong file type — often produce an immediate validation error or a hard block on submission, rather than a note back from an editor later. For guidance on the word limits, structure, and content that go into the abstract text itself before you reach this stage, see CASRAI’s guide to conference abstract format, word limits, and a template.
Creating an account and starting a submission
Nearly every abstract-management platform requires the submitting author to create an account before starting a submission, separate from any conference-registration account. Points worth confirming before you begin:
- Submitting author versus presenting author. Many systems let one person submit on behalf of a different presenting author, but require the presenting author’s name, affiliation, and (often) a separate confirmation or registration step later. Get this distinction right at submission — changing the designated presenter after acceptance can require organizer approval and isn’t always permitted.
- Co-author entry. Most forms require every co-author’s name, affiliation, and email at submission time, not just the corresponding author. Some platforms send co-authors an automated confirmation request; an unconfirmed co-author can hold up processing.
- Saving drafts. Most systems allow saving an incomplete submission and returning to it, but the abstract only enters the review queue once formally submitted — a saved draft sitting past the deadline is not counted as submitted.
- Late submission windows. Some conferences run a separate, shorter late-breaking abstract track with its own deadline, word limit, and review process, distinct from the standard track. Check whether a “late” option is actually a different track with different rules before assuming it’s simply an extension.
The review timeline: submission to decision
Timelines vary by conference size and field, but the sequence is broadly consistent across abstract-management platforms:
- Submission deadline closes and the platform locks further edits (some systems allow limited post-deadline corrections for typos, but not substantive changes).
- Reviewer assignment runs, either automatically via the platform’s matching engine or manually by track chairs, typically within one to a few weeks of the deadline.
- Review period, during which assigned reviewers score and comment on each abstract against the conference’s stated criteria (originality, methodological soundness, relevance to the meeting’s scope, clarity). This is usually the longest phase, often several weeks, and is where most of the gap between submission deadline and notification date comes from.
- Track chair or program committee adjudication, where reviewer scores are aggregated and borderline cases are discussed, sessions are assembled, and format (oral versus poster) may be assigned based on both the abstract’s score and the number of oral slots available — a strong abstract can still be placed as a poster purely because oral slots are limited.
- Notification. Accept, reject, or occasionally accept-with-required-revisions decisions go out through the platform, usually with reviewer comments attached and a firm deadline for the presenting author to confirm.
The gap between submission deadline and notification is worth planning around directly: for annual society meetings this commonly runs 4-10 weeks, but it is set independently by each conference and can run longer for larger meetings with multiple review rounds. Check the individual conference’s own published timeline rather than assuming a standard interval — travel funding requests, institutional approvals, and visa applications for international travel often have their own lead times that only start once you have a firm acceptance in hand, so a late notification date can create real downstream scheduling pressure.
How abstract acceptance links to presenter registration
Acceptance of an abstract is not the same as being registered to attend, and conflating the two is one of the more common ways a confirmed presenter ends up dropped from the final program. The mechanics organizers typically enforce:
- Presenter registration is usually mandatory and separate. Most conferences require the presenting author (specifically the presenting author, not just any co-author) to complete full conference registration and payment by a stated deadline after acceptance — commonly a few weeks — or the abstract is withdrawn from the program regardless of its review score.
- The confirmation step is where this gets linked. Some abstract-management platforms integrate directly with the conference-registration system, so confirming your presentation slot also generates or requires a registration record; others treat them as fully separate systems, and it is the presenter’s responsibility to complete both.
- Presenter substitution has its own approval path. If the original presenting author can’t attend, most societies require formal notice to the organizers (not just handing the slides to a co-author informally) so the program listing, badge, and any presenter-specific access reflect who is actually presenting.
- No-show policies exist and are tracked. Repeated no-shows by a submitting author or institution can affect standing for future submissions to some societies, since it affects program integrity and scheduling for other presenters.
Because these are organizer-specific policies rather than a fixed standard, the authoritative source is always the individual conference’s own author instructions and registration terms — abstract-management platforms enforce whatever rules a given organizer configures, and those rules differ meeting to meeting.
Frequently asked questions
Can I submit the same abstract to more than one conference?
Policies vary by organizer. Because a conference abstract is generally a preliminary, non-peer-reviewed disclosure rather than a full publication, submitting materially the same abstract to multiple meetings is not treated the same way as duplicate journal publication, but many societies explicitly prohibit or require disclosure of concurrent submission in their author instructions. Check the specific conference’s submission policy rather than assuming it’s permitted.
What happens if my abstract is accepted but I can’t get travel funding or a visa in time?
Contact the organizers as soon as the conflict is apparent — most abstract-management systems have a formal withdrawal or substitution process, and organizers generally prefer early notice (which lets them offer the slot to a waitlisted submission) over a late no-show.
Do I need to resubmit through the same account if a co-author changes after submission?
No, but most platforms require the submitting author (or an organizer, in some cases) to edit the co-author list within the system of record rather than communicating the change informally by email, so the program, badges, and CE/credit records stay accurate.
Is peer review for a conference abstract as rigorous as journal peer review?
No. Conference abstract review is typically faster and less rigorous than journal peer review, often a single review round with a shorter scoring rubric focused on relevance and clarity rather than a full methodological review, and it commonly happens while the underlying research is still in progress.
