Start from the original brief, then log each change with the date, the request, its likely effect and who has authority to decide. The log keeps requested, accepted and unresolved changes in separate lists. A change counts as accepted only when you record that the right person agreed to it.
What this log does
It gives you one chronological record of how the brief has moved since booking. Each entry shows what was asked, when, by whom, what it would affect and what has been decided. Entries sit in one of three states: requested, accepted or unresolved.
The log does not amend a contract or approve anything on its own. It makes sure that the message you send to the team is complete and that nobody has to rebuild the history later.
How to use it
- Enter the date and version of the original brief.
- Log each change as it arises, with the date and time.
- Describe the request in a sentence and note what it affects: date, hours, venue, crew, deliverables or deadline.
- Name the person who can decide it.
- Mark it requested until that person agrees, then mark it accepted and record the date.
- Leave anything still open in the unresolved list.
Reading the result
The accepted list is what you share with the team. The unresolved list is your agenda for the next conversation. Anything requested but not accepted should be treated as not agreed.
Changes made on the day need particular care, since decisions are quick. Our guide to approving extra work during an event explains how to do it cleanly. If the venue itself has changed, read changing the venue after booking. Once the changes settle, recording the final brief before event day shows how to wrap up.
What to do next
If several people are involved, see our guide on agreeing priorities with several decision-makers. For handing the brief between colleagues, use the brief handover tracker. If venue access changes, track it with the venue-access recheck tracker.
Assumptions and limits
The log records what you enter. It does not send anything to anyone, and it does not mark a change as approved unless you do. It cannot tell you whether a change is allowed under your booking terms. Your written quotation and our confirmations govern. Your answers stay in your browser unless you choose to save them on this device.
Send us the accepted changes and the contact responsible for the booking. We will confirm in writing how each one affects date, crew, venue or deliverables.
Share our accepted scope changesCommon questions
Does the log change my agreement?
No. It is a worksheet. A change takes effect only when it is agreed in writing with the team under your booking terms. Use the log to prepare that message, not to replace it.
Why separate requested from accepted?
A request is an idea. An acceptance is a decision. Mixing them is how people end up believing something was agreed when it was only suggested.
Who should decide a change?
The person who has authority over the booking, which may differ from the person who raised it. Record the name of the decision owner for every entry.
What if a change affects the price?
Note it as an effect to be confirmed. The team states any change to the quotation in writing, so do not assume a change is free.
Share our accepted scope changes
Send us the accepted changes and the contact responsible for the booking. We will confirm in writing how each one affects date, crew, venue or deliverables.
What happens next: You send your event details on WhatsApp. Our team reads the brief, asks what is missing, then confirms in writing whether the date, venue and coverage can be booked, with a quotation. Opening WhatsApp does not send anything, and a message is not a booking until both sides confirm.
Last reviewed: