Planning a professional association's annual event portfolio
The secretariat runs a conference, four seminars, a members' dinner and a regional forum, all with the same small team.
The short answer
An annual event portfolio is one year-view of every event the association runs, showing purpose, audience, date window, owner and the workload each places on the same people.
Plan it before planning any single event, so that overlaps in people, suppliers, members' time and budget are seen early.
List every event and its job
Start with a single list: flagship conference, seminars, workshops, annual general meeting, members' networking, regional or chapter events, awards and any recurring online sessions.
Write one line on what each event is for and who it serves. If two events serve the same audience for the same reason, the portfolio should say so, because members notice.
Show the year, not the events one by one
Place every event on a twelve-month grid, including its build-up and wrap-up, not only the event date. A two-day conference may need eight weeks of heavy work before and four weeks of reconciliation after.
The picture to look for is where heavy periods stack on the same people. Use the recurring calendar capacity planner to see role availability against workload.
Check the four pressure points
- People: the same secretariat staff, committee chairs and volunteers across events.
- Members' time: events that draw the same members in the same fortnight, including school and public holidays and other professional calendars. Check dates with the right sources.
- Suppliers: the same venue, AV or registration supplier asked for several dates, and the shared supplier calendar approach to coordinate them.
- Money: commitments that fall due in the same quarter.
Decide the order of priority
When two events collide, decide by purpose, not by habit. The method is described in event calendar prioritisation; here, note which events are fixed, which can move and who decides.
Record each decision in a decision log so the next committee can see why.
Review the portfolio on a rhythm
- Agree the portfolio at the start of the planning year.
- Review every quarter against actual workload and committee changes.
- After each event, add what it really took in people and time.
- At year end, use the record to set the next year's calendar.
Worked example · Fictional example
One secretariat, seven events
Fictional organisation and figures, for illustration only.
A fictional association of chartered engineers runs a two-day annual conference for about 400 members, three half-day seminars, a members' dinner, and a regional forum. The secretariat has two full-time staff and a volunteer committee of nine.
Laid on one grid, the conference build-up overlaps with two seminars and the dinner invitations, and both staff are fully loaded in the same six weeks. The committee moves one seminar by a month, hands the dinner invitations to a named volunteer, and records that the regional forum is the event that can slip if workload rises.
Use this yourself
Annual event portfolio year-view
Copy this table into a spreadsheet. Add one row per event, with build-up and wrap-up shown as separate months.
- Event name and one-line purpose
- Audience and approximate size range
- Fixed, movable or optional
- Build-up months, event month, wrap-up months
- Owner role and deputy
- Staff, committee and volunteer roles needed
- Shared suppliers and venue dependencies
- Budget commitments by quarter
- Decision logged on collisions (reference)
| Event | Purpose | Status | Build-up | Event | Wrap-up | Owner | Shared pressure |
|---|---|---|---|---|---|---|---|
| Annual conference | Flagship learning and networking | Fixed | Jan to Mar | Apr | May | Secretary | Staff, venue, committee |
| Seminar 2 | Technical update | Movable | Apr to May | Jun | Jul | Programme lead | Staff, AV supplier |
| Members' dinner | Community and recognition | Fixed | Aug to Sep | Oct | Nov | Treasurer | Volunteers, venue |
| Regional forum | Chapter engagement | Optional | Sep to Oct | Nov | Dec | Chapter chair | Staff, travel |
Handle it in-house, or bring in help?
Your team can usually handle this when
- Up to a handful of events with one clear owner and a committee that meets regularly.
- The same team can review actual workload each quarter.
Outside planning help earns its fee when
- Several events compete for the same few people and nobody holds the whole-year view.
- Committees rotate and each new group re-plans the year from scratch.
Need the year held together?
Recurring programme management can build the portfolio year-view with your committee, keep it current, and bring clashes in people, suppliers and dates to the right decision owner before they become last-minute fixes. If recurring management is not available, a conference project lead can cover the planning and coordination workstream.
Questions organisers ask
How early should the portfolio be set?
Before any single event is booked, ideally at the start of the planning year. Dates and venues are easier to place when the whole year is visible.
Who should own the portfolio?
Usually the secretariat head, with the committee confirming priorities. One person must hold the whole view.
What if a member event is not fully planned yet?
List it with an estimated date window and mark it Optional or To be decided. A placeholder shows its load on the same people.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.