---
title: "Organising a Conference"
source: The Turing Way
source_url: https://github.com/the-turing-way/the-turing-way
licence: CC-BY-4.0
domain: data-and-analysis
subdomain: turing-way
date_added: 2026-04-25
---

(cl-mec-organising-conferences)=
# Organising a Conference

*Recommendations listed in this subchapter also apply to longer collaborative events like sprints and hackathons.*

Event planning and organisation involves many roles, tasks and responsibilities, which can be challenging, especially for online/hybrid conferences or other collaborative events that have a large target audience.

This document lists the various tasks for organising such events, which will be useful for people who do not have any former experience or professional support available to them.
In this subchapter, we discuss different aspects of conference organisation, which are listed in chronological order and divided into sets of tasks and responsibilities "before", "during" and "after" the meeting.
Though created for longer events, these detailed task lists can be used for planning smaller events that have fewer logistical requirements.

Though we assume 'virtual first' approach for inclusive events, these recommendations have been drawn from in-person conference planning, and hence can be used for remote or in-person meetings with changes to adapt to a physical location.

(cl-mec-organising-conferences-before)=
## Before the event

The different subsections are marked as "Earlier-phase", "Mid-phase", and "Later-phase", based on their importance at the different phases of organisation.
A few subsections are marked as "Relevant for all phases", as those aspects should be taken care of in all stages of event organisation.

### The organising committee for the event

***Earlier-phase***
- To make organising truly inclusive, include different stakeholders from the community, organisation, and members from diverse backgrounds in the committee.
- If the organising committee has members across different time zones, the event can be held in a distributed manner.
- Have 1-2 committee chairs who can capture the overview of the entire team's work.
- Divide the full committee into smaller subcommittees by different tasks and responsibilities.
- Identify chairs for the subcommittees and allow members to join more than one subcommittee.
- Have a common place for documentation and interaction channels to keep communication transparent.

### Website for the event (preplanning)

***Earlier-phase***

*If possible, create a subcommittee dedicated for designing the website and maintaining online communication*

- Take accessibility aspects into account (font size, colour, background).
- State everything clearly and in simple words.
- Provide contact details of people with clearly stated roles and responsibilities.
- Grant edit rights to more than one member in the committee (or subcommittee) across different time zones.
- Have clearly defined sections for different information, such as:
  - General information and format of the event.
  - Draft schedule.
  - Theme and target audience.
  - Details about the tools that will be used for connecting.
  - Sponsors (if any).
  - Registration details and deadline (if already available).
  - Call for proposals and guidelines for submitting content.

### Community participation and accessibility

***Relevant for all phases***

- Choose a Code of Conduct that captures your organisation and community values.
- Describe your community participation guidelines.
- Create possibilities for people to ask for support to attend your event.
- Create a reporting guideline for any questions, concerns or breaches of the Code of Conduct.
- Describe how you intend to create an inclusive event, for example, will there be a sign language interpreter or live transcription.
- Consider allocating a budget that can be dedicated to addressing transportation needs for attendees who benefit from accessibility support. 
- Create one single location for all the information (like an A-to-Z) regarding the events.
- Host a few community calls in different stages of planning to involve the audience in the process.
- Invite volunteers who can help you troubleshoot some specific issues.
- Allow flexibility for the participants to join the call from anywhere (including from home).
  - Clearly state what are the size limits for the groups that join remotely (or if individual participation is preferred even when joining from the same location).

### Communication channel

***Relevant for all phases***

- A dedicated Slack or Gitter channel within the organisation account for the event.
- Have a private channel for the organisers.
- If working in subcommittees, create channels for the subcommittees to post relevant progress.
- Create a channel for the community where they can receive updates and engage with each other regarding the event.
- Create appropriate channels for the registered participants (general, introduction, social, program).
- Have an announcement channel that can be used for announcing important information by the committee members.
- If the organisation account is not open for others to join, then create an open channel for participants.
- Create a social media account on X/Twitter for announcements, branding, improving visibility and wider outreach.
  - Assign 1-2 volunteers or committee members who can handle social media in collaboration with the committee.

### Storing and sharing information within the organising committee

***Relevant for all phases***

- Use a common, and if possible, single resource management system (like GitHub, Google drive, website) that is easily searchable for storing **organisation related documents**.
- Establish a common location for storing and sharing documentation.
- All organisers should have access to all documentation used for planning and organisation.
- Create a single page summary for the organisers listing the available resources with their links.
- Have meetings periodically to list and create an overview of the immediate task(s), check with people who these tasks are delegated to and plan the next steps to take before the next meeting.
- Maintain notes from each call and share with all the members in the organising committee.

### Budget

***Mid-phase***

- Allocate sufficient budget for organising this event (for example for the tools, equipment and childcare).
- The first place to confirm your budget and support for handling it is your organisation.
- Looking for sponsorship early on is always a good idea.
  - In the early phase, even though not all the information is sorted, use the website to attract sponsors.
- Decide how big your event should be based on the available resource (such as online communication tools, assigned budget of the event, size of your community).
- Calculate how much to make the registration fee if no sponsorship is gained.

### Participation support grants

***Mid-phase***

- Allocate part of your budget for the participation support grant that can be requested by the applicants for the following support:
  - Free or subsidized childcare during the event so that the participants can attend the event without worrying about taking care of their children.
  - Software cost or subscription fee if the one being used by the event is not freely available.
  - Hardware or equipment for facilitating participation, such as headsets, microphones, webcams (create a list of hardware that can be funded by the support grant).
  - High-speed internet for the duration of the event.
  - Other aspects that may improve the quality of participation of the applicants.
- Consider the possibility of waiving the registration fee for people from a low-income organisation/country.
- Create a rubric for selection.
- Share the application form before the registration deadline.
- Communicate clearly how many participation support grants are available and what they include.
- Send decisions to participation support grant applicants as soon as possible so that they can decide if they can register to attend the event.

### Event theme and duration

***Mid-phase***

- Identify your target audience within your community and organisation.
- Invite community members to suggest ideas and collectively choose the most relevant theme.
- Identify the most suitable time zone and the duration of the event.
- Avoid scheduling your event on national holidays or religious and cultural days, you may also want to consider avoiding other days and timings that would make attendance difficult for your desired audience.
- Use a standard time with a link to different time zones (like [arewemeetingyet](https://arewemeetingyet.com)) when communicating about the event.
- Add the exact date, time, location (if any!) and choice of tool that will be used for communication.

### Define timeline and invite applications

***Mid-phase***

*Establish a timeline for organising and planning the conference and share on the website*
- Deadline for abstract submission.
- Deadline for abstract selection notification and program announcement.
- Deadline for application for participation support grant (equipment and internet cost).
  - Include application for participation support grant in the registration (such as equipment for remote joining, internet cost, childcare).
- Deadline for registration.
- Deadline for announcing the selected participation support grant awardees.
- Deadline for registration cancellation.
- Establish a rubric for selection of the talks and sessions.
- Invite abstracts for talks and sessions and share rubrics for selection.

### Create a registration form

***Mid-phase***

It is important to consider what information you need to collect and how you will do this in the registration form.

For more details, see the next sub-chapter on registration forms. 

### Community suggestion and feedback forms

***Mid-phase***

*Choose a standard platform to manage all your forms, for example, [Surveymonkey](https://www.surveymonkey.com/) or [Google forms](https://www.google.com/forms/about/), with a statement on how you ensure the security of the data collected*.

- Theme suggestion form.
- Speakers suggestion form.
- Participation support application form.
- Sponsorship interest form for those who need grants to facilitate their participation.
- Abstract submission form for talks (options for the keynote, long, short, lightning talks).
- Abstract submission form for workshop, up-skilling or breakout session (options for the different lengths of the session).
- Ideas and leaders for social events.
- Form to collect community vote on the submitted sessions and social activities.
- Final feedback form for participants (can be created in the later stage before the event).
- Feedback form for the chairs, helpers, speakers and notetakers (can be created shortly before the event).

### Program

***Later-phase***

*Agree as a committee and what the rough agenda for the event's program will be. Create slots for keynotes, breakout discussions, workshops, poster and lightning talk session.
Provide designated time slots for social events in the main program.
Make sure that after each talk/session there is 5 minutes break to allow people to log in to the right online call link, switch rooms, and ask any logistics-related questions.
Provide plenty of breaks, and treat those breaks as virtual coffee sessions.*

- Identify speakers and sessions for the event from the selected abstracts for the talks and community voted sessions.
- Create a well-balanced agenda that covers the intended theme of the event.
- If the sessions are supposed to run in parallel, create an agenda based on the session topic/theme.
- In addition to the talks, have plenty of slots for breakout discussions, short workshops and other opportunities to exchange skills.
- Provide new and interesting topics that are not selected for long talks as an opportunity to present their idea in short or lightning talks.
- Instead of having a live lightning talk and poster presentation, invite submission of pre-recorded lightning talks and talks on posters that can be assembled in a gallery (for example, a YouTube playlist) that can be accessed by everyone.
  - For poster sessions, create a gallery of posters online that can be browsed easily.
    * Use [F1000 Research](https://f1000research.com/posters/8-400), [Zenodo](https://zenodo.org/), [Figshare](https://figshare.com/) or [Open Science Framework (OSF)](https://osf.io/meetings) to ensure that a DOI is assigned to each submission and allows browsable collections.
      Other options are Flicker, Unsplash and Google photos.
    * Share link of each poster with their online video in the shared document.
  - Decide the length of these talks (recommended length is 1.5-2 minutes),
  - Create a designated slot in the program to ensure that people take time to check out these talks and posters.
- Share program and agenda with everyone (via the website) on time.
- Make sure that your online program is kept up to date.
- Invite volunteers from the community to chair sessions.
- Share speaker's and session guidelines with the selected participants.
- Share the chair's guidelines and protocols with the selected participants.
- Treat social events in your program as seriously as any other session; discuss this with the organising committee and agree on social events that are good fits for your community.
  - Confirm leaders for these social activities.
- Create shared documents for all the selected talks, sessions and social events to be shared with the participants.
  - Save all the shared documents in one location (or create a common location with their link) so all the participants can browse them during and after the event.

### Documents and tools for participants

***Relevant for all phases***

- Establish a dedicated location for all the shared documents for different sessions with participants so that they can access and edit online during the event.
  - Use a standard template that can be similar for all the sessions with minor adaption.
- If using a tool that is available only upon subscription, make sure that all the participants have access.
- Share a how-to guide to ensure that everyone knows how to use the tool.
- If possible, offer help with installation and testing of the tool.
- Remind everyone to arrange a microphone or headsets.
  - If possible, provide a grant to buy necessary equipment such as headphones, webcams, and/or high-speed internet.
- Share the participation guidelines, code of conduct and contact information of people who can help with any issues regarding the meeting.
- Send a reminder with the links to the document(s) and other important resources to all the participants a week and a day in advance.
- Create slides or presentations that might be needed from the organiser's side (welcome, wrap up).

### Organise a pre-event community call
*Often referred to by different names such as installation party, coffee-hours or set-up test fest*

***Later-phase***

- Organise a pre-event call for the organising committee to cross-check if all the materials for the event are sorted and have been made available to everyone.
- Arrange a conference call(s) with volunteers, speakers, session leads and chairs to communicate the guidelines and discuss their responsibilities during the event.
- Create a collaborative document to collect questions from participants, document answers and share it with those who can't attend the call.
- Arrange a separate conference call(s) with the participants to answer their questions related to the event and also use collaborative notes to share the main discussion points.
- Test the technical infrastructure with everyone and help set up any software that is needed during the event.
- Share important contact details (committee chairs, code of conduct contact person) with everyone.
- Keep this meeting informal and have as many helpers as possible who can help individuals in breakout rooms.

### Storing and sharing information with the participants

***Later-phase***

- Use a common, and if possible, single resource management system (like GitHub, Google Drive, or a website) that is easily searchable for sharing **information with the participants**.
- Create a single page summary for the participants of the available resources with their links.
- Clearly communicate where and how participants can access information and documents.
- If not using a free platform, provide access to the participants.
  - This can be communicated in the registration confirmation email and the pre-event community call.
- Send out short emails with updates and reminders that point the participants to these resources (as people tend to look for all the information right before the event).

### Branding and promotional materials

***Relevant for all phases***

- Use the organisation logo for promoting this event only if agreed by the organisation leadership, otherwise invite logo designs from the community.
- Use social media to engage with the community.
  - Reach out to them as frequently as possible during the decision making.
- Use online store to sell swag to allow people to buy them before or during the event.
  - If the overall budget is low, this can be used for inviting small donations from the community.
  - If you have sufficient budget, send these to your organising committees before the event, and to the speakers and volunteers after the event as a *thank you* gift.
- Design online posters and flyers to share with your community members who can help you promote the event in their networks.

### Designated venues for participation

*If there are physical office locations, or co-working spaces accessible for most members*

- Reserve conference room(s) (or similar venues) with high-speed internet.
- Share details on how members can access this venue.
- When possible, use individual cameras to simulate remote participation so that others joining remotely don't feel left out.
- If the reserved location has a webcam and microphone, check that they work properly.
- Plan the seating arrangement so that people are facing to the main screen/camera.
- Test the screen with different light intensity.
- Arrange all the required materials and equipment, like extension cords or power strips.
- Create a form to collect dietary requirements, interest in participating in a social event, mobility-related requirements and other location-specific requests.
- Arrange for beverages/snacks for the breaks, and ensure that the catering service will label the food for contents/allergens.
- If organising any location-specific social event, run that in parallel to the remote social event.
  - Book social event venue, transfer, and catering and communicate them clearly.

(cl-mec-organising-conferences-during)=
## During the event

### Kicking off the event

*Checklist for the designated chair of the opening session*

- Start the video call, or any communication channel 30 minutes before the event to check that everything works.
- Share links to the documents and other resources for the event on the chat system like Slack.
- Remind attendees of the community participation guidelines and the Code of Conduct.
- Introduce the organising committees and the Code of Conduct contact person for the event.
- Introduce the format of the meeting and when the breaks are scheduled.
- Explain the basic protocols for participation.
  - Muting microphone when not speaking.
  - Using a chat system during the meeting - if there is one.
- Remind the guidelines for participating in discussions.
  - Raise hand - on chat, or virtually (like in [Zoom](https://zoom.us/)) or physically.
  - Other ways to involve others in the discussion equitably.
- Ask everyone to write down their name, contact (X/Twitter, email) and other relevant information.
  - Provide a place to write down pronouns, but keep that optional.
- Start the meeting with an icebreaker question.
  - Create opportunities for everyone to share something personal (about their hobby, or experiences) on the document or verbally.
- Communicate the ways to have inclusive discussions.
- Remind everyone if the video will be recorded.
- Provide an agenda with the names and contact information of the session chairs.
- Remind session chairs of their guidelines in private and make sure that they have all the information and support they need.
- Provide everyone with a way to keep track of sessions and time, for example, a shared link to [cuckoo.team](https://cuckoo.team) clock.
- Share how participants can ask for help with troubleshooting, event information or feedback about the event.

(cl-mec-organising-conferences-after)=
## After the event

- Consider how you will ensure that everyone is able to access return transport safely if your conference is hosted in-person or hybrid.
- Create a debrief document to capture what went well and what could be improved in future events.
- Create a small overview blog post to share the main highlights from the event with the community/participants immediately.
- Collect any additional documents or information mentioned by others/speakers during the events.
- If the event sessions and talks were recorded, process and publish the recorded videos within a defined time frame.
- Send thank you emails to everyone with the link of the complete notes and all the relevant information.
- Send a feedback form to all the participants with the thank you email.
- Settle all the invoices from the event.
- Host a post-event community call to thank people and share the lessons learned.

## Resources

- The *Checklist for running a meeting* is a summarised version of the [Gallantries (Galaxy+The Carpentries handbook)](https://galaxy-carpentries.github.io/gallantries/handbook) which is an expanded version of [The Carpentries workshop checklist](https://docs.carpentries.org/topic_folders/hosts_instructors/hosts_instructors_checklist.html).
- The *Checklist for running a longer event such as a conference or sprint* is a summarised version of the debrief document written by the [chairs of the 1st CarpentryCon conference](https://2018.carpentrycon.org/) organisation committee.
