SixSides

We're going to the Games - SixSides is the official app of the World Police and Fire Games Perth 2027. Read the announcement

Blog

Association Conferences: How to Plan Delegate-Led Side Events

Chris Igos
Association Conferences: How to Plan Delegate-Led Side Events

How to Plan Delegate-Led Side Events Around an Association Conference

An Australian professional association is preparing for a three-day national conference. The formal programme is already taking shape, but several professional networks and special-interest groups have started asking whether they can organise their own breakfasts and dinners while everyone is in the same city.

The conference team sees the potential. These smaller gatherings could give delegates more time to discuss specialist issues, reconnect with professional networks or meet people with similar interests. But recognising those gatherings also creates practical questions about visibility, scheduling and responsibility.

Should every independently organised breakfast appear in conference communications? Who manages registrations if a dinner fills up? What happens if a host changes the venue? How can delegates tell the difference between an activity delivered by the association and one simply listed alongside the conference?

The answer is not for the conference team to organise everything itself.

Delegate-led side events can create additional opportunities for professional exchange around an association conference, but organisers need clear boundaries between enabling participation and taking responsibility for independently hosted activities.

1. What Counts as a Delegate-Led Side Event?

Not every activity happening around a conference has the same relationship with the organiser.

A useful first step is to distinguish three broad types of activity.

Official Conference Activities

These are planned, delivered or formally commissioned by the conference organiser or its delivery partners.

They may include plenary sessions, workshops, official receptions, conference dinners or other activities within the organiser's programme. The organiser is clearly responsible for how these activities are presented and delivered.

Recognised or Listed Delegate-Led Side Events

These are independently hosted gatherings that the organiser chooses to acknowledge or make visible to conference participants.

For example, a regional professional network might organise a breakfast before the conference day begins. A specialist working group might arrange a dinner to discuss an issue that matters to people attending the conference.

The conference organiser may choose to list the activity without becoming responsible for booking its venue, managing its RSVPs or delivering the gathering.

Fully Independent Gatherings

Some delegates will make their own arrangements without any involvement from the conference team.

Colleagues may organise dinner together. An existing network may meet privately. An organisation may invite selected guests to an activity that it does not ask the association to promote.

These gatherings do not necessarily need to become part of a formal side-events programme.

The distinction matters because recognising an activity, promoting it and delivering it are different levels of organiser involvement.

Listing a gathering can make it visible to delegates without necessarily making it part of the organiser-delivered conference programme.

A gathering can be useful without becoming an official conference event, and an organiser does not need to list every activity taking place around the conference.

For a broader perspective on how organisers can support participation without controlling every interaction, see Why Events Need Community Hosts, Not Just Agendas.

2. Five Decisions Organisers Should Make Before Listing Side Events

If an association decides to recognise delegate-led gatherings, the strongest approach is to make a few clear decisions before invitations start arriving.

Decision 1: Decide Which Gatherings to Recognise

A side-events programme does not need to become an open noticeboard for anything happening near the conference.

Organisers can establish criteria that reflect the event and the professional community it serves.

Useful questions might include:

  • Does the gathering have a clear connection to conference participants or the wider professional community?
  • Is the host clearly identified?
  • Is the purpose understandable?
  • Are any eligibility or invitation conditions transparent?
  • Is there enough information for delegates to make an informed decision about attending?
  • Is the organiser comfortable including the activity in conference-related information?

The criteria should be proportionate.

A small breakfast discussion probably does not need the same submission process as an official conference session. But the organiser still needs enough information to understand what it is choosing to make visible.

Equally, being independently hosted should not automatically make an activity suitable for conference promotion.

The objective is not to maximise the number of side events. It is to make appropriate delegate-led opportunities visible where doing so adds something useful around the main conference.

Decision 2: Define Host and Organiser Responsibilities

This is one of the most important decisions to make before anything is listed.

If a delegate or professional network is hosting a gathering independently, potential host responsibilities may include:

  • securing the venue
  • managing RSVPs
  • communicating capacity
  • handling applicable costs
  • providing accurate event details
  • communicating changes or cancellations
  • responding to attendee questions
  • delivering the gathering itself

The conference team may choose to take responsibility for a narrower set of tasks, such as establishing listing criteria, identifying appropriate programme windows, reviewing submitted information and maintaining a consistent place where recognised gatherings can be found.

The exact arrangement will depend on the association, the conference and any agreements involved.

Organisers should describe that arrangement accurately rather than assuming that calling an activity “independent” automatically resolves questions about responsibility.

This article is not a legal guide, and responsibilities relating to liability, insurance, safety, venues or privacy can depend on the particular circumstances and jurisdiction.

The practical principle is:

Be clear about what the conference team has agreed to do and what remains with the independent host.

Decision 3: Protect the Main Conference Programme

Side events should sit around the conference rather than unnecessarily compete with the experience delegates registered to attend.

That does not require a universal timetable rule.

A multi-day conference may have sensible opportunities for breakfasts before the formal programme, dinners after scheduled sessions or periods deliberately left open for smaller gatherings. A shorter event with a tightly packed programme may have very little appropriate space.

The useful question is:

Where can additional participation happen without undermining the main conference experience?

That may mean avoiding side-event listings during a keynote, major conference reception or other programme moment the organiser expects delegates to attend.

It can also mean giving hosts enough scheduling guidance that several recognised activities are not unintentionally competing for the same narrow window.

The aim is not to control every delegate's calendar. It is to make the relationship between the official programme and recognised side events understandable.

Decision 4: Make Side Events Discoverable and Understandable

Once an organiser chooses to recognise a side event, delegates need enough information to decide whether it is relevant to them.

A useful listing may show:

  • gathering title
  • host or organising group
  • purpose or discussion theme
  • date and time
  • meeting location
  • intended participants
  • capacity or eligibility conditions
  • RSVP or host contact details
  • any cost to attend
  • whether the activity is independently hosted or part of the official programme

The organiser does not necessarily need to become the registration system for the gathering. A listing could simply direct interested delegates to the host's own RSVP process.

What matters is that somebody viewing the conference information can understand what the gathering is, who is hosting it and how participation works.

Decision 5: Review Whether the Approach Was Worthwhile

A side-events programme should not continue automatically simply because it existed once.

After the conference, organisers can review whether the approach was useful and manageable.

Questions might include:

  • Were the listing criteria clear?
  • Did hosts understand their responsibilities?
  • Did the gatherings fit reasonably around the programme?
  • Could delegates find enough information to decide what was relevant?
  • Were there recurring questions or misunderstandings?
  • How much administrative work did the approach create for the conference team?
  • Would the same model make sense next year?

The aim is not to prove that side events increased retention, attendance or engagement unless there is evidence to support those conclusions.

The more practical question is whether the arrangement created useful participation opportunities without introducing disproportionate confusion or workload.

3. Why Listing a Side Event Is Different From Hosting It

Consider a group of environmental practitioners that wants to hold a breakfast during a national association conference.

The association agrees that the gathering is relevant to conference participants, includes it in a side-events listing and links delegates to the host's RSVP form.

That gives the gathering visibility.

It does not automatically mean the association is negotiating with the café, managing the guest list, taking payments, answering dietary questions or notifying participants if the independent host changes the venue.

Those tasks may remain with the host if that is how the arrangement has been structured.

The distinction changes if the association becomes more directly involved. A jointly delivered, officially affiliated or association-managed activity may create a different set of responsibilities.

The important point is not to create distance from delegate initiative. It is to make the organiser's actual role clear.

Visibility does not have to mean operational ownership.

That allows a conference team to recognise relevant activity around its event without automatically becoming responsible for delivering every gathering that takes place alongside it.

4. Example: Side Events Around an Australian Association Conference

Imagine a fictional national environmental management association preparing for a three-day conference in Melbourne.

The conference attracts professionals from consultancies, government, infrastructure organisations, research institutions and specialist environmental groups.

As the event approaches, three delegate-led gatherings emerge.

A regional practitioners' network wants to organise a breakfast for people working outside metropolitan areas. A special-interest group plans a dinner focused on a shared professional challenge. An established private network also intends to meet during the conference but does not need wider promotion.

Recognition

The conference team decides that relevant delegate-led gatherings can be submitted for inclusion in a side-events listing.

The regional breakfast and specialist dinner are submitted because their hosts want other delegates to be able to discover them. The private network gathering remains independent and does not appear in the listing.

Programme Timing

The team identifies breakfast and evening periods that sit around the main programme.

This gives hosts useful guidance while protecting the core conference sessions from unnecessary competition.

Host Responsibility

The side-event hosts secure their own venues, manage RSVPs, communicate capacity and costs, and notify attendees if anything changes.

The association reviews the submitted information and provides visibility through its conference information. It only takes on the responsibilities it has explicitly agreed to.

Discoverability

Each listed event includes its purpose, host, time, location, intended participants and RSVP information.

Delegates can see that these are independently hosted opportunities rather than official programme sessions.

Review

After the conference, the organising team looks at the questions it received, the amount of administration involved and whether the distinction between side events and official activities was sufficiently clear.

It does not claim that the gatherings improved retention or generated measurable community growth.

It simply decides whether the model was useful enough to repeat and what should change next time.

The important lesson is that the association can make room for delegate initiative without becoming the host of every gathering.

5. A Real Australian Example: Philanthropy Australia Conference 2026

Philanthropy Australia used a comparable approach around its September 2026 conference.

Its published material described Side Events as delegate-led gatherings organised alongside the main conference programme. Breakfast and dinner opportunities were identified around the core programme, and delegates interested in opening their gatherings to conference participants could submit event details for consideration.

Philanthropy Australia also promoted listed side events online and provided venue guidance to help hosts identify possible local meeting places.

The published Side Events programme included different participation conditions. Some gatherings provided broader RSVP opportunities, while others were invitation-only or otherwise limited.

That distinction is useful.

A side event can be recognised within the wider conference experience without every gathering needing the same audience, format or participation conditions.

This example should not be treated as a universal model, nor does the existence of the programme establish particular engagement, retention or commercial outcomes.

It simply shows one way an Australian association has created space around a flagship conference for delegate-led activity.

Official sources:

Philanthropy Australia — Side Events: Extending Connection Beyond the 2026 Conference Program

Philanthropy Australia Conference — Side Events

6. When Is a Side-Events Programme Worth Considering?

Not every association conference needs a formal side-events programme.

A more structured approach may make sense when delegates are already organising gatherings, the conference brings several professional networks together, there is sensible space around the main programme and the organising team can manage a basic listing or recognition process.

It may be unnecessary when interest is limited, the conference programme leaves little room, or the administrative work would outweigh the likely usefulness.

That distinction matters because adding more activities does not automatically create a better event.

Sometimes the most appropriate approach is simply to acknowledge that delegates will make their own plans.

At other conferences, a clear framework can make existing delegate initiative easier to navigate without asking the organiser to deliver everything itself.

The organiser's goal should be purposeful participation, not the largest possible side-events calendar.

Where SixSides Fits

SixSides is a community-first event engagement platform designed to support stronger connection, participation and community interaction around events.

Delegate-led gatherings are one possible part of that wider participation experience. Helping delegates understand what opportunities exist and discover relevant people, conversations and activities can contribute to a more connected conference community.

But SixSides should not be positioned as the operational manager of independently hosted side events.

The conference organiser still needs to decide which gatherings it will recognise, what information it requires, what responsibilities it is willing to accept and how recognised activities relate to the official programme.

SixSides can support the broader community and participation layer around the conference without replacing those organiser decisions.

Final Thought

Association conferences naturally bring together people who have reasons to meet beyond the formal agenda.

The organiser does not need to design and deliver every breakfast, dinner or specialist conversation that emerges from that opportunity.

What it does need is clarity.

Which gatherings will be recognised? What remains independent? Who is responsible for delivery? When can the activities take place without competing unnecessarily with the main programme? And how will delegates understand what is available?

Supporting delegate-led side events does not mean an association must organise every gathering. It means making deliberate decisions about which activities to recognise, what responsibilities to accept and how delegates can understand their opportunities to participate.

Make Space for Delegate Initiative Without Owning Every Gathering

A side-events approach works best when organiser involvement is deliberate and proportionate.

Clear programme boundaries, host responsibilities and participation information can give delegates room to create useful professional gatherings without requiring the association to turn every conversation around the conference into another event it has to manage.

SixSides can support the wider participation and community experience around those moments while the organising team remains responsible for defining how independently hosted gatherings fit alongside its conference.

Give your event a community that lasts

A branded app where members show up before day one and stay long after the close. We'll walk you through it.