How a small secretariat can run a year-round event programme
The secretariat is three people, the events calendar keeps filling, and every event is run as if it were the only one.
The short answer
A small secretariat copes with a year-round programme by treating it as one system: a single calendar, a standard set of event stages, and a monthly check of who is overloaded. The aim is to stop each event restarting from zero.
Start by plotting every event on one calendar with its busiest weeks, then decide which tasks become repeatable and which need extra capacity at peak.
Plot the real load, not the event dates
An event date hides the work around it. A one-day forum usually has a long build-up (programme, speakers, registration) and a tail (payments, feedback, reports), so three events a quarter can overlap for most of the year.
Draw each event as a band from first decision to final close-out, then look at where bands stack on the same people. Those weeks are where mistakes appear.
Make the repeatable parts repeatable
- One stage list used by every event: brief, date and venue, programme, registration, communications, final week, close-out.
- One shared folder structure and file naming rule, so any staff member can find a speaker list or a supplier quotation.
- Standard documents kept as templates: speaker invitation, run sheet, supplier brief, post-event report.
- A supplier list with notes on what worked, so choices are not reopened every time.
- A decision log per event, so a handover does not depend on one person's memory.
Decide who owns what across the year
With three staff, each event needs one named lead and one named backup, and no person should lead two events in their final month. A responsibility matrix across the year shows quickly where one name appears too often.
Committee volunteers should own content decisions, such as the theme or speakers, rather than logistics that staff then have to chase.
Plan for the peaks, not the average
Average capacity looks fine on paper. The trouble comes in the two or three weeks when registration, speaker materials and supplier confirmations all fall together.
| Pressure point | Early sign | Typical response |
|---|---|---|
| Two events in the final month together | Both leads attend each other's meetings | Move one lead, or add temporary coordination for those weeks |
| Registration and finance queries at once | Inbox is the only tracking tool | Assign one person to registration queries with a short reply guide |
| Committee asks for new items late | Programme changes after supplier briefs | Set a change-freeze date per event and record it in the log |
| Staff leave during a busy month | No backup named | Name backups at the start of the year and check leave against the calendar |
When the programme outgrows the team
Some secretariats keep adding events until the member services work suffers. That is a capacity decision for the committee, not a staff performance problem.
The options are fewer events, a different mix of formats, temporary help for peaks, or recurring programme management. See what the committee can decide if nobody owns the programme day to day.
Worked example · Fictional example
A three-person secretariat maps nine events
Fictional organisation and figures, for illustration only.
Persatuan Fiktif Pengamal Logistik has three staff and plans nine events in a year: one annual conference, four half-day seminars, two roundtables and two member briefings. Plotting each as a band, the secretary sees that the conference build-up overlaps two seminars between August and October.
The team gives the conference to the most experienced officer, moves one seminar to November, assigns backups for every event and agrees that two extra weeks of temporary coordination will be sought for September. The committee approves the calendar and the change-freeze date for each event.
Use this yourself
Year-round programme load worksheet
Copy this table into a spreadsheet. One row per event. Review it monthly.
| Event | First decision date | Event date | Close-out date | Lead | Backup | Overlaps with | Peak weeks | Action |
|---|---|---|---|---|---|---|---|---|
| Event name | dd/mm | dd/mm | dd/mm | Name | Name | Other events | Week numbers | Move, add help, or keep |
| Event name | dd/mm | dd/mm | dd/mm | Name | Name | Other events | Week numbers | Move, add help, or keep |
Handle it in-house, or bring in help?
Your team can usually handle this when
- No more than one event is in its final month at any time.
- Every event has a lead, a backup and a written stage list.
- Committee volunteers handle content and staff handle logistics.
Outside planning help earns its fee when
- Two or more events regularly collide and the same people lead them.
- Staff time for member services keeps being absorbed by event coordination.
- The committee wants a steady programme but cannot add headcount.
Want the programme run as one system?
Recurring programme management means an outside lead holds the annual calendar, stage lists, supplier handovers and monthly status for your secretariat, while the committee keeps programme content and budget. If that service is not the right fit, a conference project lead can cover the peak events only.
Questions organisers ask
How many events can a three-person secretariat run?
There is no fixed number, because it depends on event size, how repeatable the formats are and how much member service work sits alongside. Test the calendar against the load worksheet and look at overlapping final months.
Should we outsource every event or only some?
Usually only the ones that coincide with peaks or are new to your team. Familiar formats with strong templates can stay in house.
What is the first thing to fix?
Name a backup for every event and agree a change-freeze date. Both are quick and reduce last-minute rework.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.