The outcome
For a lot of associations, the annual conference isn’t an event. It’s a third of the year’s revenue and the moment members judge whether the membership is worth it. Get it right and renewals lift, sponsorship deepens, and members talk about the program for months. Get it wrong and the rest of the year is uphill.
The work that determines whether a conference goes well sits with the program team: which speakers, which streams, which themes, what flow makes the days work. The work that determines whether it goes wrong is administrative: managing 200 sessions across six audience groups and four streams, updating the running order when a speaker drops out, getting the right registrations against the right sessions, ensuring the dependencies between optional items are enforced.
When the administrative layer runs itself, the program team gets to focus on the program. The event fills because registrations are easy and the right invitations reach the right members. The content team manages the running order through a drag-and-drop interface rather than reformatting a spreadsheet. The next year’s event is built from the previous year’s template rather than rebuilt from scratch.
What the conference experience looks like to the member
The member receives a personalised invitation. The link recognises them. They see the conference site, with their member pricing applied automatically, and they choose their track. If they want the full conference, dinner is included. If they only want day one, dinner is offered as a paid extra. The dependency rules between optional items are baked in, so the member can’t accidentally book themselves into a workshop they’re not eligible for or duplicate-pay for an item already in their bundle.
Once registered, they get a personal program. The streams they’re attending. The sessions they’ve selected. The dietary preferences they noted last year, pre-filled. They can change their mind about a session up to a cutoff, online, without contacting the office.
On the day, their badge prints itself from the data the AMS already holds. The session room knows which sessions they’re attending. The post-conference CPD record updates automatically.
What the conference experience looks like to the team
The program team builds the program. The events team builds the registration. Neither team builds a spreadsheet that has to track them both.
A new session is created in the AMS, and a content stub is generated automatically in the website CMS, ready for the program team to add the abstract, learning outcomes, and speaker bios. The session is automatically categorised, by stream, by audience group, by topic, by day, so it appears in the right places across the site. When the session moves time, every page that references it updates. When a speaker is replaced, every reference to that speaker updates.
Registration health is visible in real time. Numbers by stream, by member category, by session. Underperforming sessions can be promoted, overperforming sessions can be moved to a larger room, and the team makes those calls during the registration window, not after.
Critically, next year’s event is faster. The structured content from this year is reusable. The pricing logic is reusable. The registration flow is reusable. What changes is the program. What doesn’t change is the rest.
Why this was hard before, and why it isn’t now
A serious conference is a content management problem dressed up as an events problem. The program lives in twenty places: the website, the email campaign, the printed program, the mobile app, the badge, the speaker bios, the session room signage, the social media schedule. Keeping all of those in sync, while also handling complex registration logic, was the work of a team and a sprawling spreadsheet.
The shift came when structured content became reusable. Define a session once, with all its attributes, taxonomies, and relationships. Reference it everywhere it needs to appear. Change it once, watch every reference update. Add the AMS integration so registration logic, member identity, and pricing rules sit underneath the program, and the conference site stops being a one-time custom build and becomes an asset the association reuses every year.
The same shift means a new event, a regional summit, a workshop series, an awards night, can be built on the same template. The investment in the first congress site amortises across the next several events.
The proof: associations running this outcome with 3DN
Royal College of Pathologists of Australasia, integrated conference registrations
Pathology Update is RCPA’s biggest annual conference. Many optional items, dependencies between them, member and non-member pricing, multiple streams. RCPA needed the registration to enforce the rules without staff babysitting it, and they needed to be able to configure new conference options themselves in future years rather than relying on an external vendor.
3DN delivered deep integration between iMIS and Kentico, so staff could build registration options and dependencies directly. The result is a conference registration that the college now runs without external development support, and a member-facing flow where the right items appear together at the right price.
Australian Dental Association, 2017 and 2019 ADA Congress
The ADA Congress involved over 200 sessions, six audience groups, and four streams running over five days. ADA needed visibility and cross-functionality across managing each session, location, and speaker, and they needed the team to be able to do it themselves.
The microsite was built on Kentico structured content, with content types representing each day, stream, time, speaker, and location. The implementation was on budget and took five weeks. The 2017 conference saw a 20% increase in attendees compared to 2015. By 2019, ADA had a ready-made template they could self-manage with no technical intervention from 3DN, the second year ran on the first year’s investment.
AIM WA, the rolling-event version of the same outcome
AIM WA’s calendar isn’t a single annual conference but a continuous schedule of training, qualification programs, and member events. The same principle applies: real-time integration between the website and the AMS means the calendar, prices, and availability are always current, and registrations boomed once the friction came out.
CEDA, the email and communications layer
CEDA’s automated communications drive event-related messaging across their member base. The right invitation reaches the right member at the right point in the cycle, with personalised links that take them straight into a registration flow that already knows them.
Where this outcome applies
Any association running a flagship annual conference, a continuous program of events, or both. Medical colleges with annual updates that carry CPD weight. Industry associations with summits, awards nights, and chapter events. Professional bodies with continuing education programs delivered through conferences. Trade associations with member-and-supplier event calendars.
The outcome scales: a 200-session, multi-day, multi-stream congress and a quarterly chapter dinner can run on the same underlying patterns, with the same template, the same registration logic, and the same self-management capability for the team.
Related work and tools
The Royal College of Pathologists of Australasia and the Australian Dental Association are the two flagship proof points for this outcome at the high end, with RCPA’s Pathology Update and ADA’s Congress both showing that complex multi-stream, multi-audience, dependency-driven conferences can be self-managed by the association’s own team in future years. AIM WA represents the rolling-calendar version of the same outcome, with continuous training and qualification events running on the same patterns. CEDA contributes the communications layer that drives the right member to the right session through personalised, automated email.
The tools that supported this outcome were Kentico for structured content, microsites, and drag-and-drop program management, iMIS for member identity, pricing, and the registration logic that enforces dependencies between items, the Kentico/iMIS Synchronisation Bridge that lets sessions defined in the AMS appear automatically as Kentico content, the 1-Click pattern for the registration shortcut from the personalised invitation, and Howler for the email channel that drives the right member to the right session. A successful annual conference is the result of the program, the registration, and the communications all working from the same view of the member. The tools support the design.
