Contract administration and commercial boundaries
Event change request form: fields and approval route
A speaker slot moves, a room is swapped, and three people have agreed to it in three different messages.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
A change request form turns a casual "can we also..." into a record: what is asked, why, who asked, what it does to scope, cost and time, and who may approve it.
The approval line stays blank until the named approver signs or confirms. The form describes the effect; it does not decide it.
When a change needs a form
- It alters something in the agreed scope, programme or schedule.
- It changes cost, even by a small amount, or moves a supplier deadline.
- It affects another supplier, a speaker or the venue.
- It reverses something already approved.
The fields, and why each is there
| Field | What to write | Why it matters |
|---|---|---|
| Reference and date | A running number such as CR-007 and the date raised. | Lets everyone point to the same item. |
| Requested by | Name and role, including whether they hold authority over this area. | Separates a request from an instruction. |
| Change requested | One sentence describing the change. | Prevents several changes hiding in one request. |
| Reason | Why now, and what happens if it is not made. | Helps the approver weigh it. |
| Baseline | What the agreement, programme or plan says today. | A change needs something to be compared with. |
| Effect on scope, cost, time | Added, removed or moved items, with figures and dates, marked quoted or estimated. | Shows the real size of the change. |
| Dependencies | Other suppliers, rooms, speakers or deliverables touched. | Changes rarely stay in one place. |
| Approver and route | Named person and the limit of their authority; who else must be consulted. | Stops approval by the wrong person. |
| Decision | Approved, declined or deferred, with date and approver. Left blank until completed. | The record that counts. |
Working a request through
- Log the request the day it arrives, even if it is only a message.
- Ask the supplier or team member for the effect on scope, cost and time in writing. Where a supplier quotes extra cost, follow the variation quotation process.
- Compare baseline and revised figures side by side in the change impact comparator. Note where figures are missing instead of treating them as zero.
- Send the form to the named approver with a decision date.
- Record the decision, update the schedule and tell every affected party.
Things to avoid
- Starting work on a change before it is approved, unless an agreed emergency rule allows it.
- Letting a supplier's quote count as approval.
- Recording the cost effect as a single number with no basis.
- Using the form to settle what a contract clause means. That question goes to your legal adviser.
Worked example · Fictional example
Swapping a breakout room on the day before
Fictional organisation and figures, for illustration only.
A fictional logistics association asks to move its afternoon breakout from a room seating 60 to a larger room, because registrations have grown. The venue coordinator replies by message that a larger room is available.
The project coordinator raises CR-004. The venue quotes RM1,800 extra; the AV supplier says re-cabling needs two extra technician hours at the quoted overtime rate. The comparator shows both effects and the change in setup time. The honorary treasurer, who holds authority up to RM3,000, approves in writing, and the signage printer is told the same day.
Use this yourself
Change request form (copy and complete)
Leave the Decision block empty until the approver completes it.
- Reference and date raised:
- Requested by (name, role, authority over this area?):
- Change requested (one sentence):
- Reason, and consequence if not made:
- Baseline today (agreement clause, programme or plan reference):
- Effect on scope (added / removed / moved):
- Effect on cost (amount, quoted or estimated, tax stated or not):
- Effect on time (dates, deadlines moved):
- Dependencies and other parties affected:
- Named approver and their limit:
- Consulted before decision:
- DECISION (approved / declined / deferred), approver, date: left blank until completed
Handle it in-house, or bring in help?
Your team can usually handle this when
- One person holds authority and few suppliers are affected.
- Changes are rare and mostly internal.
- The schedule is short and everyone sits in one room.
Outside planning help earns its fee when
- Changes arrive from committee members, sponsors and speakers at once.
- Several suppliers must reprice or reschedule for each change.
- Nobody is sure who may approve what.
Need change control run for you?
A conference project lead can log each request, collect the cost and time effect from suppliers, show the effect side by side and route it to the named approver. Approval stays with the people who hold authority.
Questions organisers ask
Does every small change need a form?
Not every wording tweak. Use one whenever scope, cost, time or another party is affected. When unsure, log it; a short form takes minutes.
Who should be the approver?
The person who holds authority over that budget or decision in your organisation. Write the limit of their authority on the form and name a second approver above that limit.
Can the form replace an agreement variation?
The form records the request and decision. Whether a written amendment to the agreement is also needed is a question for your legal adviser.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.