An event catering change log is a dated history of decisions. Give each request a reference, record the answer and cost position, and show which agreed document it changes. Keep that history beside a separate current event plan so a pending request cannot quietly replace a confirmed arrangement.
This becomes useful when several conversations are happening at once: the venue changes a room layout, the organiser asks about extra portions, and a quotation arrives for additional clearing. The log lets you see what happened to each proposal without rebuilding the booking from a long email chain.
Keep the current plan and the decision history separate
Use two pages or spreadsheet tabs. The current plan contains only the arrangements supported by the accepted booking and agreed written changes. The change log records the path to those decisions, including requests that were declined, withdrawn or replaced.
At the top of both, put the booking reference, event date and current document version. Keep the supporting quotation and correspondence with the record. The log is an organising aid: it does not itself amend the booking or replace the agreed documents. For the information to include when asking for a change, use the catering booking amendment checklist.
Give each request a permanent reference
Use a short sequence such as C01, C02 and C03. Keep the same reference through the request, quotation and decision rather than issuing a new number every time someone replies. If one email contains two independent decisions, give them separate rows.
Record the actual dates when the request was sent and the decision arrived. A date mentioned inside an old attachment may be the event date, a proposed deadline or a previous revision; label those fields instead of relying on a single unexplained date.
| Field | What to record |
|---|---|
| Change reference and request date | A stable ID and the actual date the request was sent. |
| Current arrangement and proposal | The agreed item or document version, followed by the precise requested replacement. |
| Decision state | Requested, quoted, agreed, declined, withdrawn or superseded. |
| Cost position | Whether a price is awaited, quoted, agreed or being corrected; retain the amount in the supporting quote. |
| Decision evidence | The dated written response and quotation or revision reference that supports this state. |
| Affected plans and next action | Which food plan, room layout or schedule needs attention, who owns the next step and its agreed deadline. |
Use states that describe what actually happened
Requested means the proposal has been sent. Quoted means a price or option has been supplied for consideration. Agreed means you have the relevant written agreement for that change. Declined, withdrawn and superseded close a proposal without making it part of the current plan.
Do not use an empty cell or a tick to stand for all these outcomes. Where an answer is incomplete, keep the decision open and write the missing point explicitly, such as “price received; revised finish time awaiting confirmation”. A quote for an extra does not establish that it has been booked.
The current Fables terms require written agreement for special arrangements and date changes. A date-change request alone does not change or cancel the original booking. Record the written outcome rather than treating an updated personal spreadsheet as acceptance.
Follow one illustrative change through the log
The following is a fictional planning example. It shows record handling only, without implying a Fables price, availability or accepted arrangement.
| Entry | What happened | State and cost position | Effect on the current plan |
|---|---|---|---|
| C01 — first request | The organiser asks for extra clearing after the meal. | Requested; price awaited. | Keep the previously agreed clearing responsibilities. |
| C01 — quotation received | A written option describes the work and proposed hours. | Quoted; proposed cost only. | Keep the option outside the accepted booking total. |
| C01 — request revised | The organiser asks for a shorter period instead. | Earlier option superseded; revised quote requested. | Retain the old quote as history and identify the replacement request. |
| C01 — written decision | The required parties agree the revised scope and price in writing. | Agreed; reference the accepted revision. | Update the relevant responsibilities and cost record, then issue the new plan version. |
Record the cost change once
Keep quoted options separate from agreed changes. For an agreed change, record whether the confirmed adjustment adds to, replaces or reduces an existing line. A replacement price is easy to double-count if it is entered as an extra while the old line remains.
Reconcile the revised scope and total against the actual issued documents. Record payments already made separately from the booking total, then check any revised balance and deadline. Ask Fables to clarify a mismatch before changing your working figure. Do not infer a refund, reduction or revised payment date from your own calculation.
The optional extras record helps compare open choices before deciding. The change log has a different job: retaining the dated evidence for the decision and showing where its agreed effect was applied.
Close the row only after the affected plans are checked
An agreed change may need more than one document updated. Record the new current-plan version and check the affected venue schedule, food plan and responsibilities against it. Tell only the relevant suppliers what changed, using the agreed information they need.
Keep previous versions clearly marked as superseded rather than deleting the history. Remove obsolete printed copies from the working pack. If a later email changes part of the decision, add the new evidence and explain which part it replaces; do not overwrite the earlier entry so completely that the sequence disappears.
Use role labels and quantities in a shared planning log. Keep personal contact details and any sensitive guest information in the appropriate private booking records. Existing customers should send questions in their current Fables booking email chain, with their booking reference and event date. Read the Fables booking journey alongside your own accepted agreement.
Use a short version note when sharing the plan
A useful cover note is: “Current event plan: version [reference], issued [date]. Agreed changes included: [change IDs]. Open requests excluded: [change IDs]. Replaces version [reference]. Please raise any discrepancy before using this version.” Fill the placeholders from the evidence you hold.
For new enquiries, start with the date, venue, guest numbers and services you would like Fables Catering & Events to quote. You can also find the business on its official Facebook Page. Keep later booking decisions in the agreed correspondence and documents.
Request a catering quote from Fables with your date, venue, approximate guest numbers and requested services.
Tell Fables about your event
Share your date, venue or postcode, guest numbers and the food you have in mind.
Read the Fables booking journey.
Request a catering quote