[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"content-en-blog\u002Fabstract-submission-form-example":3},{"seo":4,"title":7,"description":8,"category":9,"publishedAt":10,"author":11,"sections":12,"cta":80,"related":83},{"title":5,"description":6},"Abstract Submission Form: Fields and Examples","Which fields an abstract submission form needs, which to drop, and a worked example with the field types, limits and help text organisers can copy.","Abstract submission form: fields, examples and best practices","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.","planning","2026-02-10","Eventumbot",[13,16,29,32,35,46,49,59,68,71,74,77],{"heading":14,"body":15},"Start from what the committee will use","Every field is a cost for the author and a decision for the committee. Ask of each one: who reads this, and when? If the answer is nobody, remove it. Optional fields left empty by most authors are a sign that they were never needed.",{"heading":17,"body":18,"items":19},"Example form","This is a typical structure for a peer-reviewed meeting. Adapt the limits to your call.",[20,21,22,23,24,25,26,27,28],"Title (text, up to 20 words). Help text: use sentence case, no abbreviations in the title.","Track (single choice). One track per abstract; the chair may move it later.","Presentation preference (single choice: oral, poster, no preference).","Abstract text (long text, 250 to 300 words, counter visible). Suggested structure: background, methods, results, conclusion.","Keywords (up to 5). Used for reviewer matching.","Authors (repeatable block: name, email, affiliation, presenting author yes or no, corresponding author yes or no).","Optional file (PDF, up to [size] MB) only when figures are essential to review.","Statements (checkboxes): the work is original; ethics approval where relevant; consent to publish the abstract in the book of abstracts.","Conflicts (free text, optional): people the authors would like excluded from reviewing.",{"heading":30,"body":31},"Write help text for the mistakes you have seen","The best help text answers the question authors emailed you last year. Put the rule next to the field: the word limit beside the counter, the file format beside the upload button. Do not rely on a PDF linked from an announcement.",{"heading":33,"body":34},"Test as an author before launch","Ask two colleagues who have not seen the form to submit a dummy abstract, including one with five authors and one with special characters in the title. Check what the confirmation email says, whether the author can edit before the deadline and what a withdrawn abstract looks like to the committee.",{"heading":36,"body":37,"items":38},"Field types and when to use each","The type of a field decides how clean the data is later. Free text is flexible and hard to sort; a choice list is rigid and easy to sort. Use the strictest type that still fits the question.",[39,40,41,42,43,44,45],"Short text: title, keywords, name. Set a character limit and show it.","Long text: the abstract itself. Show a live word count and state whether formatting is allowed.","Single choice: track, presentation preference. Prevents “oral or poster” typed into a title box.","Multiple choice: topics that may overlap, for example a maximum of three topic codes.","Repeatable block: authors. Each author is a small set of fields, not a comma-separated line.","File upload: only when the file is used in review, with type and size limits stated.","Checkbox: statements the author must confirm, each on its own line so consent is unambiguous.",{"heading":47,"body":48},"Word limits, counters and what authors actually do","A word limit that the system does not enforce will be exceeded. Decide whether the limit is hard, so the form refuses longer text, or soft, so it warns. Count words, not characters, unless your publication needs characters. Test the counter with text containing Greek letters, chemical formulae and line breaks, because these are what break it. Say whether references count toward the limit and whether figures or tables are allowed, and whether authors may format text or must paste plain text. If you print a book of abstracts, plain text saves hours of clean-up.",{"heading":50,"body":51,"items":52},"Common form mistakes and how to fix them","These are the problems that show up in almost every first-time call.",[53,54,55,56,57,58],"Too many mandatory fields, so authors type “n\u002Fa”. Keep mandatory only what the committee will read.","Affiliation as one free-text line, which produces ten spellings of the same university. Use separate fields or a list.","No way to save a draft. Authors lose text when a session expires; offer draft saving or a warning.","Ambiguous roles. “Presenting author” and “corresponding author” need one-line definitions beside the field.","Confirmation email that does not repeat what was submitted. Include the title, authors and a link to edit.","Editing closed too early or never. State until when authors may change the abstract.",{"heading":60,"body":61,"items":62},"Data the programme will need later","Some information is not needed to review an abstract but is needed to schedule it. It is tempting to collect everything at submission. Resist that: authors whose abstract is rejected have wasted effort, and the answers will be out of date by the time the programme is built. Collect the following after acceptance, in a short follow-up form.",[63,64,65,66,67],"Confirmed presenter and their email address.","Days the presenter cannot attend.","Audio-visual or accessibility needs.","Preferred format if you offered a choice between oral and poster.","Consent for recording, if you record sessions.",{"heading":69,"body":70},"A thirty-minute form review","Before the call opens, gather the programme chair, one committee member and someone from the secretariat for half an hour. Walk through the form field by field and ask of each one who reads it, when, and what would go wrong if it were empty. Then submit a dummy abstract together and read the confirmation email aloud. Finish by writing down the three fields you removed or changed. This short meeting finds more problems than any amount of solo proofreading.",{"heading":72,"body":73},"Make the form usable for every author","Authors submit from many countries, on many devices and often in a second language. Label every field in plain words, put the instruction next to the field rather than in a separate document, and write error messages that say what to fix (“The abstract has 342 words; the limit is 300”) rather than “Invalid input”. Check that the form can be completed with the keyboard alone and that colour is not the only signal for an error. Say clearly which language abstracts must be written in. If authors may submit in another language, decide in advance who will review those abstracts, or you will discover the problem after the deadline.",{"heading":75,"body":76},"What to do about resubmissions, withdrawals and duplicates","Three situations arise in every call, and each needs a rule that is written on the form page before the first submission. First, an author submits the same abstract twice, by accident or to try a different track. Decide whether the system blocks duplicates or a person merges them, and tell authors which abstract counts. Second, an author wants to withdraw. Allow it until a stated date, record the reason in one line and keep the record so that the committee can see what happened. Third, an author submits a new version after the deadline because they spotted an error. Decide in advance whether you allow corrections of typing errors after the deadline, who approves them and how you keep the reviewers from seeing two versions. A clear rule turns each of these from an argument into a routine.",{"heading":78,"body":79},"Keep the record complete for review and programme","The abstract record collected here also feeds review and the programme. Presenting author, track and presentation preference should be structured fields, not text in a free box, or someone will retype them later.",{"label":81,"to":82},"Explore abstract management","\u002Ffeatures\u002Fabstract-management",[84,86,88,91],{"label":85,"to":82},"Abstract management",{"label":85,"to":87},"\u002Fglossary\u002Fabstract-management",{"label":89,"to":90},"Abstract submission checklist for conference organisers","\u002Fblog\u002Fabstract-submission-checklist",{"label":92,"to":93},"Abstract review rubric: scoring criteria and examples","\u002Fblog\u002Fabstract-review-rubric"]