Keep event details consistent across a campaign
An update table for the artwork, booking page and email after an event detail changes.
Detailkite field notes · Reviewed 28 October 2026
A handoff sheet for a venue change
Example: the venue changes from Cedar Room to Cedar Hall. Assign a person and a checked version to every output.
| Output | Who updates it | Evidence to keep |
|---|---|---|
| Poster and flyer | Designer | New PDF filenames and approval |
| Social post and story | Designer or publisher | Final crops with venue visible |
| Booking page | Event organiser | Reviewed page URL |
| Email and partner materials | Assigned sender | Checked copy or delivery file |
- Update the approved brief and note the change.
- List every affected output and its owner.
- Export fresh artwork and compare it with the new brief.
- Review the booking page and email separately.
- Attach approval to the exact files being handed over.
Record what changed
Keep one current brief with an approval date and a short change note. Mark the older version as superseded. If different files intentionally advertise different offers, write those exceptions down so a reviewer knows what to compare.
Assign the outputs
Use the table above to give each output an owner. Artwork is only part of an event campaign: a correct poster does not fix the booking page or email. Detailkite compares the artwork you add; those other surfaces need a separate review.
Name the files in the approval
Put the final exports in a clearly named delivery folder. Record who checked the facts and which files were approved. If the venue changes again, update the brief, export fresh files and repeat the review. A saved report is a record of its inputs, not approval of a later version.
Compare a sample export
The fictional workshop PDFs contain a date, price and QR example you can inspect in the checker.
Open the sample