In October 2024, the American Association of Biological Anthropologists closed its call with 755 abstracts. Each one went to two members of the programme committee, and the reviews were due 16 days later. Small subcommittees then turned the accepted work into sessions, and authors heard back in mid December, three months before the meeting in Baltimore (AABA Vice President’s Report, March 2025). The committee had been recruited the previous spring, giving the organisers time to prepare the review process before submissions arrived.
A conference programme committee (program committee in American usage) is the group that decides what an event’s programme contains. It writes or approves the call for abstracts, organises the review, makes the acceptance decisions and shapes accepted work into sessions. At scientific congresses it is usually made up of volunteers from the field. At business conferences it often appears as an advisory board.
An effective committee needs a clear remit, a scoring rubric, conflict rules and deadlines agreed before the call opens. This guide explains how to assign those responsibilities, work backwards from the event date and move from abstract review to a finished programme.
What does a programme committee do?
The programme committee is responsible for content. Define its remit alongside the other committees so everyone knows who decides on submissions, logistics and the local programme.
| Committee | Owns | Typical members | Main output |
|---|---|---|---|
| Programme committee | Content: call, review, selection, sessions | Experts from the field, track chairs | Accepted abstracts grouped into sessions |
| Organising committee | Delivery: venue, budget, registration, logistics | Office staff, PCO, a board representative | A congress that runs on the day |
| Local organising committee | The host city: local speakers, social programme, venue contacts | Members from the host region | Local support and the social programme |
| Advisory board (business conferences) | Themes and speaker suggestions | Senior practitioners, sometimes sponsors | A shortlist of topics and speakers |
PCO stands for professional congress organiser, the agency many associations hire for delivery. One more term causes confusion: some association boards have a standing “programme committee” that oversees member services all year. That is a governance body. The event committee is the one tied to a call for abstracts.
In practice the programme committee answers four questions. Which topics does the call invite? Which submissions are accepted? In what format does each accepted piece appear? Which sessions do they form? The Association for Computational Linguistics lists its programme chairs’ duties in roughly that order, from selecting the committee and writing the call through overseeing review and selection to building the programme (ACL policy on programme co-chair duties).
Keep delivery decisions with the organising team, while making sure the committee knows the room capacity and budget constraints that affect the programme.
Who sits on the committee
Once the remit is clear, the roles follow from it. Most committees have four layers, whether they handle 80 submissions or 8,000:
- Programme chair or co-chairs: own the call, the timeline and the final decisions. Usually a respected volunteer from the field, appointed by the board for one or two editions.
- Track or area chairs: each owns one topic area. They assign reviewers, read the reviews in their area and propose decisions for the borderline cases.
- Reviewers: score submissions against the rubric. Most are unpaid, which is why their number and workload decide whether the timeline holds.
- Staff liaison from the office: owns the system, the deadlines and the reminders. This person manages the administration and helps volunteers keep to the agreed schedule, without taking part in content decisions.
Many associations add one or two seats on purpose: an early career member, someone from the previous committee for continuity, or a member from the host region. The AABA recruits openly. For its 2025 meeting, regular members applied through a web form, and 55 were selected (AABA Vice President’s Report, March 2025). An open call widens the pool beyond the chair’s personal network, which is where many programmes quietly narrow.
How many reviewers do you need?
Reviewer capacity depends on both workload and the proportion of invited reviewers who take part. Take the Thermal Hydraulics Division of the American Nuclear Society. For the 2025 annual meeting it reviewed 78 submissions with 44 reviewers, who returned 215 reviews: 4.9 per reviewer and 2.75 per paper, against a target of two. Only about 21 per cent of its reviewer pool took part, close to its historical average of 20 per cent (ANS Thermal Hydraulics Division, Program Committee Report, June 2025).
Use participation data from your own previous events wherever possible. Multiply expected submissions by the reviews each abstract needs, then divide by a workload volunteers will accept. That gives the active reviewers you need. Divide again by your expected participation rate to get the list you have to invite. As a worked example: 400 abstracts with two reviews each and ten reviews per person need 80 active reviewers. At a participation rate like the one in the ANS report, that means asking around 400 people.
Estimate this capacity early enough to recruit additional reviewers before the call closes.
The timeline: work backwards from the event date
The same backwards logic applies to dates. A programme committee runs on fixed points, and the first of them comes surprisingly early. The AABA’s 2025 cycle is a well documented example: the meeting ran from 12 to 15 March 2025, and the call for committee members opened eleven months before.
A real cycle, worked backwards
From committee call to final programme in eleven months
- 11 months Recruit the committee Call for committee members opened on 17 April 2024 and closed on 1 July.
- 6 months Open the call Symposium proposals closed on 6 September, the abstract portal opened on 15 September.
- 5 months Close and review Abstract deadline 15 October, reviews due 31 October: two reviewers per abstract in 16 days.
- 3 months Build sessions and notify Subcommittees of three to four members formed the sessions by 4 December. Authors were notified on 16 December.
- 3 weeks Finalise the programme Late breaking abstracts closed on 1 February, and the programme was final on 21 February 2025.
Notice how short the review window is. Sixteen days works only because the committee, the rubric and the reviewer assignments were in place before the first abstract arrived. A larger congress with external reviewers needs more slack, and four to six weeks for review is a safer rule of thumb. The same report also records a lesson worth copying. After a change of submission system, some authors said they never received their decision, so the next cycle will notify authors several times.
Business conferences usually run a shorter cycle, because the call is smaller and often framed as a call for speakers. The order of steps stays the same. How early invited speakers need confirming, and what they cost when you invite rather than select, we cover in our guide on how to get speakers for your B2B conference.
How abstract selection works
With people and dates in place, the selection itself follows five steps. Each one has an owner and a rule agreed before the call opened, so submissions can be assessed consistently.
- Screening: the office checks formal criteria such as word count, template and required sections before any reviewer sees the abstract. The ANS report explicitly reminds authors to follow the summary template, because incomplete submissions waste reviewer time.
- Assignment: track chairs give each abstract to two or three reviewers with matching expertise and no declared conflict.
- Scoring: reviewers rate each abstract against a short rubric, for example relevance to the call, originality, quality of method or evidence, and value for this audience. They also recommend a format: talk, poster or lightning talk.
- Decision by band: clear accepts and clear rejects follow the scores. The middle band goes to discussion in the committee meeting.
- Session building: track chairs group accepted work into sessions with a common thread and propose session chairs.
Keep the rubric to four criteria and publish it with the call. Authors write better abstracts when they know what is being scored, and reviewers disagree less when the scale is the same for everyone.
Why the middle band needs a discussion
Review scores are useful, but they do not always produce consistent decisions. In 2014 the NeurIPS machine learning conference sent 166 submissions to two independent committees. The two committees disagreed on 43 of those papers, about 26 per cent, and of the 43 papers one committee accepted, the other accepted only 22 (Cortes and Lawrence, 2021). Re-examining the data seven years later, the authors concluded that the review was good at spotting weak papers and poor at identifying the strongest ones.
Use scores to identify submissions with a clear consensus and those that need discussion. Reserve committee time for conflicting reviews and borderline cases, checking the reasoning behind the scores before making a final decision.
Blind or open review?
What reviewers can see changes their scores too. At the WSDM 2017 conference, reviewers who could see author names were more likely to recommend papers from famous authors, top universities and top companies than reviewers in the double blind condition. The odds multipliers were 1.63, 1.58 and 2.10 (Tomkins, Zhang and Heavlin, PNAS 2017). Double blind review of abstracts costs almost nothing: ask authors to keep names and affiliations out of the abstract text, and let the system hide the submitter. For invited symposia, open review is fine, because there the name is part of the offer.
What the evidence says about review
Three numbers every programme chair should know
Conflicts of interest and sponsored content
Blind review protects against reputation bias. Conflicts of interest need a rule of their own, because reviewers are often colleagues, co-authors or competitors of the people they score. The simplest version: reviewers declare conflicts before assignment, and the track chair routes those abstracts to someone else. Typical conflicts are the same employer, recent co-authorship, a supervisor and student relationship, or direct commercial competition.
Medical education shows how strict this can get. The ACCME Standards for Integrity and Independence govern accredited continuing medical education in the United States. They require providers to collect, from everyone who controls content, all financial relationships with ineligible companies over the previous 24 months. Owners and employees of those companies are excluded from roles such as planner or faculty, with limited exceptions (ACCME toolkit, 2020). A trade association conference does not need that regime. But a written disclosure question with a 24 month window costs nothing and settles most arguments before they start.
Business conferences face a different version of the problem: the sponsor who expects a speaking slot. Keep paid slots outside committee scoring and label them clearly in the programme. Mixed into the call, they damage trust in every acceptance. The committee decides the content, and the commercial team sells visibility. Both are legitimate, as long as attendees can tell which is which.
From accepted abstracts to a programme
After selection, the committee needs to coordinate three handovers with the organising team.
The first is the decision letter. A rejection with two sentences of reviewer feedback gives an author a reason to submit again next year. Even when you use a template, explain the decision as clearly as the review process allows. Where an abstract was solid but did not fit a talk slot, offer an alternative. A poster or a block of lightning talks gives good work a place without stretching the room plan.
The second is session building. Track chairs group accepted abstracts into sessions, but the number and width of those sessions should already be fixed by the rooms you have. Our guide to conference session types shows how plenaries, parallel sessions, workshops and posters fit together, and why the room plan should set the parallel width before acceptance letters go out.
The third is the agenda itself, including the breaks and meeting windows the committee rarely thinks about. How much of the day should stay free of sessions is the subject of our guide to conference agenda planning. If you are still choosing the tool for submissions, reviewer assignment and conflict handling, the guide to conference management software compares what the different system types cover.
Once the committee has built the sessions, Converve’s programme module publishes them so that every attendee can build a personal agenda from parallel tracks, register for sessions with limited seats and keep their booked 1:1 meetings in the same schedule. How this works alongside an association congress is shown on our page for associations.
Frequently Asked Questions
What does a program committee do at a conference?
A programme committee (program committee in American usage) decides the content of a conference. It writes or approves the call for abstracts, organises peer review, decides which submissions are accepted and in which format, and groups accepted work into sessions. Logistics such as venue, budget and registration belong to the organising committee.
What is the difference between a programme committee and an organising committee?
The programme committee owns content: the call, the review, the selection and the sessions. The organising committee owns delivery: venue, budget, registration and logistics. At association congresses a local organising committee often handles the host city and the social programme as well.
How many reviewers should each abstract have?
Two to three reviews per abstract is common. The AABA sent each abstract to two committee members for its 2025 meeting, and the ANS Thermal Hydraulics Division aimed for two and averaged 2.75 (AABA, March 2025; ANS, June 2025). Plan for low participation: only about 21 per cent of the ANS reviewer pool took part.
When should the call for abstracts open?
For a scientific congress, around six months before the event is common, with the committee recruited several months earlier. The AABA opened its abstract portal six months before its March 2025 meeting and its committee call eleven months before. Business conferences with a smaller call for speakers can run shorter cycles.
Should abstract review be blind?
For open calls, double blind review is the safer default. At the WSDM 2017 conference, reviewers who saw author names gave famous authors 1.63 times the odds of a positive recommendation (Tomkins, Zhang and Heavlin, PNAS 2017). Asking authors to leave names and affiliations out of the abstract text is usually enough.
Agree the review process before opening the call
Set the committee’s remit, review criteria and conflict rules before inviting submissions. Estimate reviewer capacity from realistic workload and participation figures, and allow time to discuss cases where the reviews disagree.
A documented process helps the chair explain acceptance decisions and gives the organising team a clear basis for building the programme. If you want the finished programme, session registration and 1:1 meetings to run in one personal agenda for every attendee, get in touch with Converve.