Define the changed exhibitor fact
Record the exact proposed difference, such as contact information, product wording, stand identifier or approved participant name. Identify the source owner and effective time. Check which artwork variants and organiser records carry the information. A change reported in a conversation is a request until the authorised content owner confirms it. Keep the event edition and current accepted proof reference visible so the team does not update the wrong year’s material.
Trace operational consequences
Identify whether the change affects submitted graphics, production, packing labels, site instructions or another accepted record. Ask the selected provider what stage the work has reached and what actual timing or scope consequences apply. Ask the organiser about its submission route where the relevant rules require it. Do not infer that a late new file replaces the organiser’s or supplier’s existing accepted version automatically.
Use a controlled revision
Create a new artwork or information version with a readable description of the difference. Reopen the affected content, visual and technical decisions as required by the actual policy. Keep unaffected records separate. A changed stand identifier can affect location instructions even if the graphic geometry is unchanged. Obtain the responsible buyer’s decision on any external variation and preserve the accepted baseline rather than erasing it under a final-final filename.
Worked example — fictional
A fictional exhibitor changes one product statement after proof version 4 has been accepted. The coordinator confirms the new wording, identifies two affected graphic files and asks the printer about production status. The organiser has a separate submission requirement, so its owner checks the actual edition rules. Revised proof version 5 is accepted through the relevant scopes and a new manifest is issued. Other approved graphics remain unchanged. The event plan records the actual revised delivery response instead of shortening the supplier’s earlier promise by assumption.
Common pitfalls
A rushed correction can introduce a different contact error or omit a qualifier. A positive response from one reviewer does not cover technical production or organiser acceptance. An old official deadline may belong to another edition. Do not mark a digital upload as installed or assume that every supplier queue automatically notices a newly uploaded artifact. Confirm the actual recipient’s replacement reference.
Release a readable late-change pack
Use the proof and change register to record exact versions, decisions, recipients and remaining conditions. Export a manifest that states what is superseded and which variants remain current. Ask responsible recipients to confirm the revised reference. After the event, record any resulting discrepancy or lesson so the next programme can establish earlier content checks without promising that all future late changes will be harmless.
Decision checkpoint
Ask whether the latest information change is factual correction or a new campaign message. Both require responsible review, but their affected scope may differ. Do not label a new promotional claim as a minor typo simply to bypass its actual approval or evidence requirement.
Take this to the next job
- Confirm source owner and edition
- Identify all affected records
- Ask actual production and organiser status
- Review exact revised versions
- Confirm superseded references with recipients
