Chapter 12., Section 5. Organizing a Conference — Main Section | Community Tool Box

• Why organize a conference?

• Who might organize a conference?

• When should you organize a conference?

• How do you organize a conference?

Conferences bring together people with common interests, responsibilities, questions, or goals to share knowledge, discuss issues, build relationships, learn from one another, solve problems, plan action, or strengthen a field or community.

Conferences can be held on almost any topic and can vary enormously in scale. A local gathering may bring together several dozen community members for a day, while a national or international conference may involve thousands of people, hundreds of sessions, exhibitors, continuing education, virtual participation, and several days of programming.

Organizing any conference requires planning, coordination, time, and resources. The larger or more complex the event, the more important it becomes to establish clear responsibilities, timelines, contracts, accessibility plans, technology systems, risk-management procedures, and methods for evaluating whether the conference accomplished its purpose.

What is a conference?

A conference is a gathering of people around a shared subject, field, problem, community concern, or professional interest for purposes such as learning, discussion, collaboration, planning, networking, problem solving, or decision-making.

Conferences may be:

• In person
• Fully virtual
• Hybrid, with both in-person and remote participation
• A single event
• A recurring or annual gathering
• A few hours long
• Several days long

The appropriate format depends on the purpose, intended participants, available resources, accessibility, geography, technology, travel burden, sustainability, safety, and the kinds of interaction the conference is intended to support.

Conferences may include:

• Plenary sessions
• Keynotes or featured talks
• Panels and facilitated conversations
• Workshops and skill labs
• Roundtables
• Research presentations and poster sessions
• Demonstrations
• Case discussions
• Problem-solving sessions
• Lightning talks
• Peer-consultation sessions
• Networking activities
• Exhibits
• Site visits
• Organizational business meetings
• Virtual or asynchronous sessions

A conference does not need to use all of these formats. Its structure should follow from what participants need to learn, discuss, decide, practice, or accomplish.

Academic conferences

Academic conferences commonly provide opportunities for researchers, students, scholars, practitioners, and others to present research or theory, receive feedback, discuss methods and findings, develop collaborations, mentor colleagues, and build professional networks.

Some are organized by professional or disciplinary associations and may also include governance meetings, awards, professional development, or other association business.

Professional association conferences

Professional conferences may combine research, practical methods, regulation and policy updates, professional development, networking, organizational business, and discussion of challenges affecting the profession.

Training conferences

Training conferences emphasize development of knowledge, skills, procedures, or professional practice. They may include workshops, demonstrations, simulations, case discussions, practice sessions, and opportunities for continuing education.

Vendor or product training may also occur at a conference, but participants should be able to distinguish educational content from commercial promotion, and relevant financial or commercial interests should be disclosed.

Issue- or problem-focused conferences

Community groups, coalitions, public agencies, nonprofit organizations, advocacy groups, universities, professional associations, and other organizations may convene conferences to examine a community concern, share evidence and experience, develop strategies, build partnerships, or coordinate action.

People directly affected by the issue should be meaningfully involved when their knowledge and participation are important to understanding the problem or developing solutions.

Why organize a conference?

Conferences require substantial effort, so the purpose should be clear before planning begins.

Reasons may include:

• An issue needs focused examination. A conference can bring together relevant knowledge and perspectives and create time for sustained discussion.
• A field or network needs connection. People may be working on similar issues without knowing one another, using different approaches, or lacking a shared place to exchange lessons.
• New research, evidence, methods, technology, law, regulation, or policy needs to be shared.
• People need opportunities for professional development or continuing education.
• A community or field needs collaborative problem solving or planning.
• Participants need opportunities to build partnerships or networks.
• A field or initiative is developing and needs clearer standards, language, evidence, or direction.
• An organization or network wants a recurring gathering. A well-designed annual or periodic conference can help sustain learning and relationships over time.
• A crisis, major change, or new opportunity requires coordinated attention.
• Participants or community partners have identified a need for training, networking, planning, or exchange.
• A grant, contract, partnership, or organizational responsibility includes convening people.
• People need to coordinate advocacy or community action.

A conference may also strengthen the sponsoring organization's visibility and relationships, but visibility should be a result of useful work rather than the primary reason for convening people.

Who should organize a conference?

Many types of organizations can organize conferences, including:

• Professional and academic associations
• Government agencies
• Coalitions and networks
• Nonprofit and community organizations
• Schools, colleges, universities, and other educational institutions
• Advocacy and community-organizing groups
• Community members and other groups with a direct stake in the issue

The key question is not what type of organization is convening the event but whether it has, or can assemble, the knowledge, relationships, resources, authority, and operational capacity needed to do so responsibly.

When should you organize a conference?

A conference may make sense:

• When you want to educate or inform a field, community, professional group, policymaking audience, or the public
• When you want people with relevant knowledge and experience to address a shared problem
• When significant new work or evidence needs to be shared
• When people need renewed connection, learning, or reflection around difficult work
• When a recurring gathering provides enough value to justify the time and cost

Before deciding to organize one, ask:

• What result are we trying to achieve?
• Is a conference the best way to achieve it?
• Could a smaller workshop, working group, webinar, community meeting, online forum, publication, or other approach accomplish the same goal more effectively?
• Do we have enough time, money, staff, technology, relationships, and expertise?
• Can we make the event accessible and reasonably affordable to the people we want to involve?
• Are other organizations already planning something similar?

How do you organize a conference?

Conference planning is detailed work. A useful planning system should identify tasks, responsible people, deadlines, dependencies, budget implications, decisions, risks, and current status.

Lead time varies. A small local conference may be organized relatively quickly, while a large event involving venue contracts, international travel, continuing education, major speakers, sponsorship, accessibility services, streaming, or hundreds of sessions may require many months of preparation.

Conference organization generally involves:

• Creating the organizing structure
• Planning the conference
• Publicizing the event, recruiting presenters, and registering participants
• Running the conference
• Following up and evaluating the event and organizing process

Creating an organizing structure

Put together an organizing team.

Include people who collectively understand the conference's purpose, intended participants, program content, operations, budget, accessibility, communications, technology, safety, community relationships, and other major responsibilities.

Depending on the event, responsibilities may include:

• Program and speaker selection
• Participant and community engagement
• Accessibility and language access
• Venue and lodging
• Virtual or hybrid technology
• Registration and attendee services
• Communications and marketing
• Sponsorship and exhibitors
• Budget and finance
• Contracts and procurement
• Safety and emergency planning
• Volunteers and staffing
• Continuing education
• Evaluation and follow-up

For recurring conferences, document what was learned each year. Maintain timelines, vendor information, contracts, accessibility notes, budgets, program decisions, risk plans, evaluation findings, and other information that can help future organizers.

Appoint a coordinator or project lead

A conference usually benefits from one clearly identified coordinator or a small coordinating team responsible for keeping the overall project aligned.

The coordinator should not personally perform every task. Their role is to maintain the overall view of the event, understand who is responsible for each area, track decisions and deadlines, coordinate across teams, and make sure unresolved issues reach the appropriate decision-maker.

A professional event planner may be useful for a complex event, but the sponsoring organization still needs people who understand the conference's purpose, participants, content, accessibility responsibilities, and organizational values.

Establish a communication and project-management system

Use systems appropriate to the size of the event. These may include:

• Shared project plans
• Task-management software
• Shared calendars
• Collaborative documents
• Messaging platforms
• Video meetings
• Defined approval and escalation procedures

Clarify which decisions individual leads can make, which require committee approval, who makes final decisions when quick action is necessary, and who serves as backup when a key organizer is unavailable.

Planning the conference

Agree on the purpose and desired results.

Possible goals include:

• Training and professional development
• Networking and relationship building
• Recognition and renewal
• Sharing research, evidence, policy, or other new information
• Improving practice
• Advocacy
• Increasing attention to an issue
• Problem solving
• Decision-making and planning
• Launching a new initiative or direction

Define results clearly enough that they can later be evaluated. "Hold a successful conference" is not a useful outcome by itself. A better goal might involve increasing participants' knowledge, producing a shared action plan, establishing new partnerships, identifying policy recommendations, or training a specified group in a particular competency.

Identify the intended participants

Identify whose participation is necessary or useful to the conference's purpose.

Depending on the event, this may include:

• Practitioners
• Researchers or students
• Residents and community members
• Program participants
• People with relevant lived experience
• Advocates
• Public officials
• Funders
• Service providers
• Employers or businesses
• Professional associations
• Members of the sponsoring organization
• The general public

Involve intended participants in planning when their perspective will improve the event. Surveys, interviews, advisory groups, focus groups, partner consultation, community conversations, and previous-event data can help identify what people actually need rather than relying on assumptions.

Set the date, length, and delivery format

Decide whether the event will be in person, virtual, or hybrid and how long it needs to be.

Consider:

• The amount of content and interaction required
• Participant work and caregiving schedules
• Relevant religious observances
• School and academic calendars
• Elections or major public events
• Professional conferences that compete for the same audience
• Travel costs
• Weather and severe-weather risk
• Venue availability
• Accessibility-service availability
• Technology
• Organizational capacity

A recurring conference may benefit from predictable timing, but don't continue a date or format automatically if it creates unnecessary barriers.

Plan the program and format

There is no single standard structure. A keynote followed by breakout sessions may work well for one conference but be unnecessary for another.

Possible conference-wide activities include:

• Plenary talks
• Panels
• Facilitated conversations
• Community or participant presentations
• Performances or demonstrations
• Whole-group planning
• Awards or recognition
• Organizational business

Choose featured speakers because they add something meaningful to the conference. Relevance, expertise, communication skill, lived experience, credibility, and fit with the audience may matter more than fame.

Document speaker expectations, including:

• Topic and session length
• Compensation or honorarium
• Travel and lodging
• Additional conference participation
• Accessibility requirements
• Presentation-material deadlines
• Commercial or financial disclosures where relevant
• Recording, streaming, photography, and reuse permissions

Plan conference sessions

Session types may include:

• Research or practice presentations
• Poster sessions
• Workshops
• Skill labs
• Panels
• Roundtables
• Peer consultation
• Demonstrations
• Lightning talks
• Case discussions
• Interactive problem-solving sessions
• Networking sessions
• Virtual or asynchronous content

Sessions may also be organized into thematic tracks so participants can follow related content.

Whether to offer several simultaneous sessions depends on the conference's purpose, participant numbers, room or platform capacity, accessibility, presenter availability, and how important it is for everyone to hear the same content.

Continuing education

If you plan to offer continuing-education credit, identify the relevant professional or credentialing requirements before advertising it.

Determine:

• What type of credit participants need
• Which organization approves or accepts it
• Which sessions qualify
• Required learning objectives and assessments
• Attendance verification requirements
• Recordkeeping requirements
• How certificates or records will be issued

Don't use "CEU" as a generic term for any continuing-education credit. Describe the credit accurately and confirm that the intended licensing or credentialing bodies accept it.

Sponsors and exhibitors

Sponsors and exhibitors may provide financial or in-kind support, useful products or services, or information relevant to participants. Their involvement should be governed by clear policies.

Consider:

• Sponsorship levels and benefits
• Separation between sponsorship and program-selection decisions
• Disclosure of sponsored content
• Commercial conflicts of interest
• Attendee-data access
• Lead collection and consent
• Exhibit-space accessibility
• Appropriate products or organizations for the conference

Registration information should not automatically be transferred to exhibitors or sponsors simply because they financially support the event.

Site visits and field experiences

Site visits can be valuable when seeing a program, community setting, facility, or natural environment directly contributes to the learning objectives.

Plan them with attention to:

• Consent and privacy of people who live, work, or receive services at the site
• Accessibility
• Transportation
• Safety
• Group size
• Confidentiality
• Disruption of normal operations

Address conference logistics

Logistics turn the program plan into an event people can actually attend and use.

Location and venue

For in-person events, evaluate the geographic location and site together.

Consider:

• Travel time and cost
• Public transportation
• Parking and accessible drop-off
• Lodging
• Physical accessibility
• Accessible stages and presentation areas
• Restrooms
• Quiet or low-stimulation space where feasible
• Lactation or other private space where appropriate
• Service-animal access
• Room acoustics and assistive listening
• Lighting and visibility
• Wi-Fi and power
• Hybrid-event infrastructure
• Emergency exits and evacuation accessibility
• Severe-weather plans
• Food service
• Cost and contract terms

Don't assume that a venue marketed as a conference facility automatically meets all of your accessibility or technology requirements. Verify the features you need and include important responsibilities in the contract.

Virtual and hybrid platforms

Virtual participation requires its own planning.

Consider:

• Platform accessibility
• Captioning and interpretation
• Screen-reader compatibility
• Authentication and participant access
• Privacy and security settings
• Streaming quality and bandwidth
• Moderation
• Breakout rooms
• Chat and Q&A
• Recording
• Presenter technical support
• Participant technical support
• Backup plans for outages

Use access controls appropriate to the event and avoid sharing meeting credentials more broadly than necessary.

Food

Food planning should reflect the length of the event, venue, budget, and participant needs.

Consider:

• Food allergies
• Dietary restrictions
• Religious or cultural dietary needs
• Clear labeling
• Accessible food-service arrangements
• Water availability
• Enough time for meals and breaks
• Applicable food-safety requirements

Lodging

If participants or presenters will travel, provide clear information about available lodging, negotiated rates, reservation deadlines, accessibility, transportation between lodging and the conference, cancellation terms, and who is responsible for payment.

If scholarships or travel assistance are available, describe eligibility and application procedures clearly.

Fees and financial access

Registration fees should be based on the actual event model rather than on historical examples from other conferences.

Consider:

• Venue and technology costs
• Staff and contractor costs
• Accessibility services
• Presenter expenses
• Food
• Materials
• Insurance
• Registration and payment fees
• Evaluation and follow-up
• Sponsorship and grants

Reduced fees, scholarships, sliding scales, sponsored registration, virtual access, student rates, or other approaches may reduce financial barriers when resources allow.

Signage, wayfinding, and information

Participants should be able to find rooms, registration, accessible routes, restrooms, meals, exhibits, emergency exits, transportation, and other important locations.

Use:

• Clear physical signage
• High-contrast readable text
• Accessible digital schedules and maps
• Mobile or web updates
• Information desks
• Email or text notifications when useful

Don't rely on color alone to communicate important information.

Participant identification

Name badges may help participants and staff identify one another, but collect and display only information appropriate to the conference.

Consider allowing participants to choose:

• Preferred name
• Organization or role, where relevant
• Pronouns, if they wish to share them
• Whether particular professional or personal information is displayed

Staff and volunteers should be clearly identifiable through methods that don't rely only on color.

Safety, health, and emergency planning

Develop an emergency plan appropriate to the conference and venue.

Address:

• Medical emergencies
• First-aid and AED availability
• Emergency-service contact procedures
• Fire and evacuation
• Accessible evacuation
• Severe weather
• Shelter-in-place
• Power or internet outages
• Security threats
• Harassment or threatening behavior
• Lost persons where relevant
• Public-health concerns when applicable
• Staff communication and escalation

Organizers should not casually dispense medications from a conference first-aid kit. Coordinate emergency medical response with the venue and qualified responders appropriate to the event.

Code of conduct and participant concerns

Consider adopting a conference code of conduct that explains expectations for respectful behavior and how participants can report harassment, discrimination, threats, or other serious concerns.

Identify:

• Who receives reports
• How urgent concerns are escalated
• What confidentiality can and cannot be promised
• How the organizers coordinate with venue security or emergency services when necessary
• What responses may follow serious violations

Contracts and coordination

Material obligations should be documented regardless of whether the conference is large or small.

Contracts or written agreements may address:

• Dates and spaces
• Prices and payment schedules
• Food and beverage
• Lodging blocks
• Technology and internet
• Accessibility responsibilities
• Cancellation and force majeure
• Insurance
• Recording and intellectual-property rights
• Data handling and privacy
• Security
• Service levels and support
• Refunds

Use appropriate legal or procurement review when the size, financial exposure, complexity, or risks justify it.

Publicizing the conference

Choose communication channels used by the intended participants.

These may include:

• Conference and organizational websites
• Email
• Social media
• Professional associations
• Community and partner organizations
• Universities and schools
• Newsletters
• Event platforms
• Earned media
• Community outreach
• Printed materials or traditional media where useful

Conference communications should clearly state:

• Purpose and intended audience
• Dates and format
• Location or virtual access
• Registration cost
• Accessibility information
• Continuing-education information
• Key deadlines
• Contact information

Registration

Pre-registration helps organizers estimate attendance, room or platform capacity, food, materials, staffing, accessibility services, and other needs.

Online registration may be the primary method, but provide an accessible alternative when people cannot reasonably use it.

Collect only information needed for legitimate conference purposes.

Registration may include:

• Name and contact information
• Session choices where required
• Accessibility or communication requests
• Dietary needs
• Continuing-education information
• Travel or lodging information where legitimately needed
• Consent or preferences concerning photography, recording, directories, or future communications where applicable

Explain how registration information will be used and protected. Use secure payment and registration systems when collecting fees or sensitive information.

Confirmation should include the information participants need to plan effectively, including cancellation and refund terms.

Recruiting presenters

Presenters may be invited directly or selected through a call for proposals.

A call for proposals should explain:

• Conference goals and themes
• Intended participants
• Available session formats
• Selection criteria
• Deadlines
• Accessibility expectations
• Presenter compensation or registration policies
• Required disclosures
• Recording or publication terms

Review proposals consistently. Depending on the conference, reviewers may consider relevance, evidence, originality, practical usefulness, learner engagement, accessibility, representation of perspectives, and fit with the overall program.

Running the conference

Before the event begins, brief conference staff, volunteers, presenters, and venue personnel on their roles and escalation procedures.

Conference staff should know:

• Where important services are located
• How to reach organizers
• Accessibility procedures
• Emergency procedures
• How to handle lost items
• Where to direct registration problems
• How to report safety, harassment, or security concerns
• How to obtain technical support

Final logistics

Confirm:

• Presenters, times, and locations
• Track scheduling and reasonable travel time between sessions
• Room and platform capacity
• Accessibility arrangements
• Captioning and interpretation
• Technology
• Session hosts or moderators
• Meal, break, and gathering spaces
• Exhibitor placement and accessible traffic flow
• Registration, information, accessibility support, and emergency-service locations
• Transportation and parking information
• Printed and digital materials
• Volunteer and staff schedules

Check-in

Design check-in to be fast, secure, accessible, and understandable.

Depending on the conference, options may include:

• Digital pre-check-in
• QR or barcode check-in
• Staff-assisted registration
• Printed alternatives
• Separate help for accessibility or registration problems

Have clear procedures for walk-in registration, capacity limits, payments, session availability, and replacement credentials.

Support presenters

Make sure presenters understand:

• Where and when they are presenting
• Technology available
• Accessibility requirements
• Session length
• Moderator or host responsibilities
• Recording or streaming status
• Where to obtain technical help

Provide logistical support based on actual needs and contractual commitments rather than a person's status or fame.

Prepare for disruption and emergencies

No plan can predict every problem, but organizers can anticipate common ones.

Develop contingency plans for:

• Speaker cancellation
• Weather
• Transportation disruption
• Power failure
• Internet or platform failure
• Room or lodging errors
• Over-capacity sessions
• Medical emergencies
• Accessibility failures
• Security concerns
• Harassment or threatening conduct
• Public-health concerns

Identify who has authority to make urgent decisions and who serves as backup.

Collect feedback and assess outcomes

Conference evaluation should be planned before the event.

Depending on the conference, evaluation may examine:

• Participant experience
• Learning or professional-development outcomes
• Accessibility
• Safety and belonging
• Program relevance and quality
• Networking and relationship development
• Technology and virtual participation
• Affordability and participation barriers
• Venue and services
• Registration and communication
• Speaker and presenter support
• Sponsor and exhibitor experience
• Organizer workload and processes
• Achievement of the conference's stated goals

Session feedback may be collected through mobile or web forms, QR codes, email, conference platforms, interviews, facilitated discussions, or other accessible methods.

Avoid treating participant satisfaction as the only measure of success. If sessions have learning objectives, use appropriate learner assessment where practical. If the conference is intended to produce action, partnerships, plans, or other outcomes, evaluate whether those results occurred.

Clean up and protect information

At the end of the event:

• Return equipment and materials
• Secure or dispose of confidential materials appropriately
• Collect lost property according to a defined process
• Close temporary accounts or credentials
• Secure attendee and continuing-education records
• Remove unnecessary exported registration lists
• Store or delete recordings according to consent, contracts, and retention policy
• Settle financial obligations

Follow up

After the conference:

• Send promised resources
• Issue continuing-education documentation accurately and promptly
• Thank presenters, volunteers, partners, sponsors, and venue staff
• Complete invoices, reimbursements, and financial reconciliation
• Share appropriate summaries or outcomes
• Assign owners and deadlines for action items or commitments made during the conference
• Debrief the organizing team
• Review participant feedback and outcome data
• Document recommendations for the next event

Evaluation

Evaluate several dimensions of the conference.

Sessions and presentations. Consider relevance, accuracy, evidence, accessibility, clarity, facilitation, usefulness, engagement, and achievement of stated objectives. Do not base decisions mainly on whether a presenter was entertaining or personally persuasive.

The overall participant experience. Ask whether participants could access the event, find relevant content, build useful connections, participate meaningfully, feel safe and respected, navigate technology and logistics, and obtain the information or learning they came for.

The venue and technology. Review accessibility, transportation, lodging, food, room quality, internet, audiovisual systems, hybrid delivery, technical support, staff responsiveness, emergency systems, and whether contracted services were delivered as promised.

The organizing and staffing systems. Consider whether roles were clear, communication was effective, staffing was adequate, workloads were sustainable, decisions were made efficiently, and people had appropriate backup when problems arose.

The planning process. Examine:

• Whether enough staff, volunteers, and expertise were available
• Whether planning began early enough
• Whether intended participants and other relevant perspectives had meaningful input
• Whether attendance, budget, staffing, accessibility, and other estimates were reasonably accurate
• What worked particularly well
• What should change and how

Conference outcomes. Return to the original purpose. Did the conference actually contribute to the learning, partnerships, planning, advocacy, problem solving, professional development, or other results it was designed to support?

Some results will not be visible immediately. When longer-term outcomes matter, consider follow-up months later to learn whether participants used what they learned, formed partnerships, implemented plans, or continued work that began at the conference.

In Summary

Conferences can bring together people, knowledge, experience, and relationships in ways that are difficult to reproduce through other formats. They may support learning, professional development, problem solving, advocacy, networking, planning, field building, or community action.

Successful conferences begin with a clear reason for convening people. Organizers should identify the intended participants and desired results before deciding on the venue, speakers, program, technology, or promotional strategy.

Planning should address both the visible program and the systems behind it: staffing, budgets, contracts, accessibility, registration, communications, technology, privacy, safety, lodging, food, sponsors, presenters, continuing education, and contingency planning.

Accessibility should be built into the event from the beginning rather than addressed only after someone encounters a barrier. The same is true of privacy, cybersecurity, emergency planning, and participant safety.

During the event, staff should be prepared to answer questions, solve problems, support presenters, address access needs, communicate changes, and respond to emergencies without losing sight of the conference's purpose.

Finally, the conference should not end when the final session closes. Follow through on commitments, protect participant information, complete financial and administrative work, evaluate both the experience and outcomes, and preserve useful lessons for future organizers.

A successful conference is not simply one that attracts a large crowd or receives enthusiastic evaluations. It is one that uses people's time and resources responsibly and creates meaningful progress toward the purpose for which they were brought together.