Conference recovery: readiness, scope and accountability
Last-minute additions exceed the agreed scope
Four new requests have arrived in ten days, each reasonable alone, and together they go beyond what was approved.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
Log every request as a change, compare its effect on cost, time and people with the baseline, and let the person with approval authority say yes, no or later. Requests that are not decided are not approved.
The change impact comparator shows differences side by side without recommending an answer, and the change request builder records who approved what.
What is known and what is not
| Known | Not yet known |
|---|---|
| The approved scope lists two keynotes, six breakouts and a lunch for 250 people. | Whether the requests are separate or whether some depend on each other. |
| The new requests are a third keynote, a networking dinner, a live-streamed session and a printed delegate book. | What each costs, who asked and who supports it. |
| The budget was approved by council in two lines: venue and catering, and speakers. | Whether any line has spare room and who can approve extra spend. |
| Suppliers have already been briefed on the original scope. | Which suppliers can absorb each request and by which date. |
Who has authority to decide
The council or its chair owns the scope. The treasurer owns the budget effect. The requester can propose but not approve. Supplier contract changes are for the person who signs contracts, and any legal question is for the competent party.
Record each request, its requester, effect and decision in a decision log. Undecided means not yet approved.
The realistic options
| Option | What it involves | Consequence to weigh |
|---|---|---|
| Approve with a budget change | Approve the request, increase the budget and revise contracts and timeline. | Meets the request. Needs treasurer approval and supplier agreement. |
| Approve as a swap | Add the request and remove something of similar effort, for example a breakout. | Keeps cost close to the baseline. Needs speaker and chair agreement. |
| Defer to a later event | Record the request for the next conference or a separate activity. | Protects the current plan. The requester may be disappointed. |
| Decline | Say no, with the reason, and who decided. | Clear and fast. Needs a respectful message. |
Communications: who says what to whom
Reply to each requester within the same message format: what was asked, the effect, the decision and who made it. For decisions still open, give a date. Tell suppliers only about approved changes.
Send the committee one combined summary so that nobody is surprised by the total effect.
- Short message template: Thank you for the request for [item]. We compared it with the approved scope: estimated effect on cost [x], on time [y], on people [z]. The decision owner is [name] and will decide by [date]. We will confirm in writing.
Follow-up and preventing a repeat
- Set a scope freeze date after which changes need chair approval in writing.
- Keep the log of requests and decisions open to the committee.
- Brief suppliers on how to treat requests received outside the log.
- After the event, list which requests came late and ask whether they belonged in the original brief.
Worked example · Fictional example
Persatuan Fiktif Akauntan: four late requests
Fictional organisation and figures, written to show the level of detail that is useful.
A fictional accountants' association has approved a one-day conference. In ten days it receives four requests: a third keynote, a networking dinner, a live-streamed session and a printed delegate book. Each has a different sponsor in the council.
The secretariat records each as a change request and fills the comparator with baseline and revised figures. The chair sees that the dinner and the keynote together exceed the budget line. Council approves the stream and the book, defers the dinner, and declines the third keynote. Every requester receives the same short message.
Use this yourself
Late request comparison table
Copy the table below, one row per request. Do not fill the Decision column until the approval owner has chosen.
- Request and who asked:
- Baseline scope item it changes:
- Estimated cost effect (a range is acceptable):
- Time effect and the date it must be decided:
- People effect (speakers, volunteers, suppliers):
- Approval owner:
- Decision: approve, swap, defer or decline, and the date:
| Request | Requester | Effect on cost | Effect on time | Effect on people | Approval owner | Decision and date |
|---|---|---|---|---|---|---|
Handle it in-house, or bring in help?
Your team can usually handle this when
- One or two small requests and one person owns the scope and budget.
- The effect is clear and the supplier can absorb it.
- The decision is already recorded.
Outside planning help earns its fee when
- Many requests arrive from different sponsors with no single approver.
- Cost or supplier terms are unclear and nobody has compared them.
- The programme, budget and speakers all move at the same time.
Want the late requests sorted into decisions?
A planning diagnostic can compare the baseline with the requested changes and list the decisions, owners and dates needed. A conference project lead can then run the agreed change process with the committee for a set period. Contract questions stay with your own adviser.
Questions organisers ask
Should we say yes to small additions?
Record them anyway. Small items add up, and a log lets the approver see the total effect before saying yes.
Who decides when the chair is also the requester?
Ask the council or the treasurer to approve, so the requester is not the only approver.
Can we change the scope after suppliers are briefed?
Sometimes. Check the contract with the competent party and tell suppliers only about changes that are approved.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.