Abstract and Speaker Submission Form

A call for papers has a different shape from a registration form. Nobody is paying, nothing is being reserved, and the submission is the beginning of a review process rather than the end of a transaction. What the form has to produce is a record a programme committee can actually allocate and score.

What this form collects

Who is presenting and how to reach them, the abstract itself with a word limit, the format and track that determine which reviewers see it, and the disclosures your accreditation or governance requires. It asks different follow up questions depending on the format chosen, so a workshop proposal is not answering questions written for a poster.

The abstract body is pasted text rather than an attached document, because the template format cannot carry a file upload field. Regform supports uploads, so you can add one in the builder after importing if you need the document itself. In practice many calls for papers run on pasted text anyway, and it produces a more consistent read for reviewers.

Who it is for

Association programme committees, academic and clinical conference organizers, and anyone running a call for speakers where submissions need routing, scoring and a decision rather than simply being collected.

How to adapt it

Tracks and formats are the two fields that do the real work, because they determine who reviews what. Set those to match the programme you are actually building. Cut the disclosure section only if you have no accreditation or governance requirement, and keep the word limit visible in the label where submitters will see it.

Setup checklist

1. Set your word limit and say it out loud. The abstract body is a text area, so enforce the limit in the label and the help text. Submitters who paste 800 words into a 300 word field will not notice until a reviewer complains, and by then the deadline has passed.
2. Match the tracks to your actual programme. Track and format are what route a submission to the right reviewers. Vague options produce a pile nobody can allocate, so use the same track names your programme committee already works from.
3. Route submissions for review. The approval path holds each submission pending until a reviewer decides. Decide up front whether reviewers see author names or work blind, because that shapes what you show them.
4. Close the form on the deadline. Set the cutoff and decide what the page says afterwards. A call for papers that quietly keeps accepting submissions after the deadline creates a fairness problem you will have to adjudicate.
5. Ask for the disclosure properly. Conflict of interest and commercial support are compliance requirements in medical, legal and accredited education contexts. The template asks the question and reveals the detail field only when the answer is yes.
6. Confirm receipt immediately. Academics and practitioners submit close to the deadline and want proof it landed. The confirmation should restate the title, the track and the decision date.

Before you publish

Submit once as an oral presentation and once as a workshop, and confirm the workshop length question appears only for the second. Submit with a declared conflict of interest and check the detail field becomes required. Then read the confirmation email as a submitter would and ask whether it tells them what happens next and when.