Commission and appoint the project lead
What happens if the event project expands
Registrations are ahead of forecast, the committee wants a second track, and the agreed scope no longer matches the event.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
Treat every addition as a change request: describe it, estimate its effect on cost, time, people and risk, then have the named approver accept, adjust or decline it before any work starts. Record the outcome.
Expansion is normal. Unmanaged expansion is what turns a planned event into a cost and workload surprise.
Common ways a project expands
- A second track, workshop or side event is added.
- Attendance forecast rises beyond the original room or catering plan.
- A new supplier, such as translation or live streaming, is requested.
- A sponsor or senior member asks for a specific feature or session.
- Reporting, meetings or approvals become more frequent than the appointment assumed.
What changes when scope grows
| Area | Questions to ask |
|---|---|
| Cost | What is the extra cost for suppliers, the venue and project lead time, and which budget line pays? |
| Time | Does it move any milestone or supplier deadline? |
| People | Who carries the work: the project lead, the secretariat or a supplier? |
| Risk | Does it add new venue, supplier or contract issues that need an adviser's review? |
| Existing commitments | Does it breach a cap, a venue limit or a deposit already paid? |
| Value | Does it serve the original purpose, or has the purpose shifted? |
A six-step change routine
- Anyone may raise a request, but it goes to one named person, usually the project lead, who writes it on the change form.
- The project lead estimates the effect on cost, time, people and risk, with assumptions stated.
- Where the effect is above a threshold agreed in advance, the budget owner or committee decides; below it, a named delegate can.
- The decision is accept, accept with changes, defer or decline, with a reason.
- Accepted changes update the plan, budget and fee, and are recorded in a decision log.
- Declined or deferred requests are kept so they can be revisited.
Agree thresholds before the first request
In the appointment, set amounts or categories of change that the project lead may handle within the existing fee, and those needing approval. The proposal should show how additional work is priced.
Without thresholds, either every small request interrupts the committee, or large ones slip through unnoticed.
When expansion means a new engagement
Sometimes added work is not a change but a different job: another event, a regular programme or a longer period. Agree a new scope and fee rather than stretching the old one.
If scope expansion is a pattern, step back and ask whether the purpose or the capacity needs to be reset. A timing review of when to appoint can help.
Worked example · Fictional example
A second track is requested six weeks out
Fictional organisation and figures, for illustration only. Amounts are in RM and not market rates.
A fictional engineers' association has a one-day conference with one track. The committee proposes a second track for 80 delegates. The project lead's change form estimates an extra room, extra AV, more moderators, a programme rework and about 25 hours of added coordination.
The extra cost is RM 14,000 against a contingency of RM 9,000. The budget owner accepts the second track with a shorter afternoon programme and drops one planned printed item, so the total stays within the approved budget. The decision and its reasons are logged.
Use this yourself
Event change request form
Use one form per request. Keep the original request wording, and do not start work until Decision is filled.
- Request number and date:
- Raised by, and what they are asking for:
- Reason or benefit, and link to the event purpose:
- Effect on cost (by line) and which budget line pays:
- Effect on dates, milestones and supplier deadlines:
- Effect on people: who does the extra work and the hours estimated:
- Effect on risk, contracts and existing commitments:
- Options (do it, do it smaller, swap for something else, defer):
- Recommendation from project lead:
- Decision (accept, accept with changes, defer, decline), approver and date:
- Updates made to plan, budget and fee:
Handle it in-house, or bring in help?
Your team can usually handle this when
- Few changes are expected and one person controls the plan.
- The scope is small and a simple note records each change.
- The committee already has a clear approval threshold.
Outside planning help earns its fee when
- Many people can ask for additions and nobody prices them.
- The project fee and the budget both move with every change.
- Past projects grew without anyone able to say when scope was agreed.
Want a change process running before scope starts to move?
A conference project lead can set up the change form and thresholds with your committee, price each request against the agreed fee basis, and keep the log of decisions. Your committee decides what is accepted, and the agreed scope stays visible.
Questions organisers ask
Will every change cost extra?
Not necessarily. Small adjustments within the agreed scope and fee are normal. Your appointment should state what counts as a change and how it is priced.
Who should approve changes?
The budget owner or the person named in your decision list, with a threshold above which the committee decides. Write the thresholds into the appointment.
What if a sponsor asks for a change?
Treat it as any other request. Estimate effect, then the named approver decides. Sponsorship terms stay with your organisation.
Can we freeze scope?
Yes. Many organisers set a date after which changes need committee approval. Choose it with your milestones in mind.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.