Universities and scholarly associations
Separating scientific decisions from conference administration
A speaker asks for a slot, a sponsor asks for a talk and the administrator is unsure who may say yes.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
Draw a line between decisions about content (what is accepted, who speaks, what the programme says) and decisions about operations (deadlines, systems, rooms, communications). Content decisions belong to the scientific committee. Operations belong to the organising team.
Write the hand-off points down: the committee decides, the administrator records and communicates. If the administrator can change who speaks by changing the schedule, the line is not clear enough.
Decision rights at a glance
Use this table as a starting point and edit it to match your constitution or university rules.
| Decision | Scientific committee | Administration | Notes |
|---|---|---|---|
| Programme themes and tracks | Decides | Records | Changes after publication need committee approval. |
| Abstract acceptance and format (oral, poster) | Decides | Notifies authors | Administrator never alters an outcome. |
| Keynote and invited speakers | Decides | Handles invitations and logistics | Fees and travel follow the budget owner. |
| Session chairs and timing within sessions | Decides | Confirms and circulates | Last-minute swaps are logged. |
| Room allocation and schedule layout | Approves final programme | Proposes and tests clashes | See the room checker for clash tests. |
| Review deadlines and submission system | Sets review standards | Runs the system and reminders | Extensions need an agreed rule. |
| Any sponsor involvement in content | Decides, with the association's policy | Records and informs sponsor | Commercial terms sit outside the committee. |
Hand-off points that need names
- Name who confirms the final accepted-abstract list and the date it is frozen.
- Name who answers an author who disputes a decision, and in what form.
- Name who approves any change to the published programme after release.
- Agree how the administrator tells the committee about scheduling constraints, such as room limits.
- Record each decision, its owner and its date in a decision log.
Conflict of interest
Reviewers, session chairs and committee members may submit or sponsor work. The association or university should set the rule for how this is handled.
The administrator's role is to apply the rule consistently, for example by blocking a conflicted reviewer from seeing a submission, not to decide whether a conflict exists.
When schedule and science collide
Rooms, timing and speaker availability sometimes force a content question. A keynote can only come on day two, or a workshop needs the biggest room.
The administrator brings the constraint and two or three options to the committee chair. The committee chooses. If the committee prefers a change that the venue cannot support, the multi-room allocation checker shows the options on paper first.
Questions for the committee at the start
- Who may approve a late abstract or a withdrawn presentation?
- What is the appeal route for an author?
- Who speaks to the media or the sponsor about content?
- Who has the final say if the committee chair and the administrator disagree on timing?
- What is recorded in writing, and where?
Worked example · Fictional example
A fictional society clarifies its line
Fictional organisation and figures, for illustration only.
The Persatuan Ilmiah Fiktif receives 220 abstracts for a two-day meeting and has space for 90 oral presentations. Its administrator sends decision emails after the committee signs off the list.
A senior member asks the administrator to move his paper from poster to oral. The administrator replies that only the committee chair can do so and logs the request.
The committee decides against it, and the administrator informs the author. Afterwards the society adds a one-page decision-rights table to its meeting procedures.
Use this yourself
Decision-rights checklist
Copy this and fill in the owner against each line. Anything with no owner is a risk.
- Who accepts or rejects abstracts, and who tells authors?
- Who may change a speaker, session or timing after the programme is published?
- Who sets and applies the conflict-of-interest rule?
- Who answers disputes or appeals from authors?
- Who decides whether a sponsor may take any part in content?
- Who approves programme changes forced by room or venue limits?
- Who communicates changes to delegates, and who approves the wording?
- Where are decisions recorded and who keeps the log?
Handle it in-house, or bring in help?
Your team can usually handle this when
- The committee already has written rules and a trusted administrator.
- The programme is small and changes are rare.
- Roles are clear from earlier editions.
Outside planning help earns its fee when
- Many abstracts, parallel sessions and several people who feel entitled to change the programme.
- Sponsors or senior members push for content changes.
- A new administrator inherits unclear practice.
Want the decision rights written and run?
If decisions are being made in emails and chat messages, a conference project lead can set up the decision-rights table, keep the log, bring scheduling constraints to your chair with options and make sure each decision is communicated to the right people. The committee decides the science and the project lead handles the process.
Questions organisers ask
Can the administrator reorder the programme?
Only within rules the committee has approved, such as adjusting times to fit rooms. Changing who speaks or in which format is a committee decision.
How do we handle late abstracts?
Agree a rule before the deadline: who may grant exceptions and on what basis. Record each exception.
What should be written down?
Each decision, who made it, the date and who was told. A simple log is enough.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.