Proofing an event programme booklet
The booklet goes to print on Friday, and three people have each sent a different version.
The short answer
Proof a programme booklet in numbered rounds with fixed owners: a content freeze, a read against sources, a language check, and a final sign-off on the printer's proof. Each round has a deadline and a log of changes.
Nobody edits a file after sign-off. A late change becomes a new version that goes through the checks again.
Set the freeze before proofing starts
Agree a content freeze date with the programme owner, after which only corrections of errors, not new content, are accepted. Late speaker changes and sponsor pages are the usual causes of reprints.
What each reader checks
| Round | Reader | Checks |
|---|---|---|
| 1. Content against sources | Programme coordinator | Session titles, times and rooms against the approved programme; speaker names, titles and organisations against confirmations. |
| 2. Names and logos | Secretariat | Organiser, partner and sponsor names and logos against approved files and the co-branding hierarchy. |
| 3. Language versions | Language owners | Each language reads the same facts; no untranslated or mismatched sections. |
| 4. Layout and numbering | Designer and a second reader | Page order, contents page, session numbers, cut-off text and image quality. |
| 5. Printer's proof | Named approver | Final sign-off on the numbered proof. |
Keep a change log
Record every change: page, what changed, who asked, who approved and which version it appears in. This lets you answer 'who changed that?' within a minute and shows what the printer needs to re-proof.
Sequence
- Freeze content on the agreed date and name the version.
- Run rounds 1 to 3 in parallel on the same file, with each reader marking comments in one place.
- The designer applies the consolidated corrections in one pass.
- Run round 4 on the new version.
- The approver signs off the printer's proof and quotes the version number to the printer.
Common errors to read for
- A session that moved rooms or times after the draft.
- Speaker name spelled differently in the programme and the biography.
- A sponsor listed in the wrong tier or with an old logo.
- Contents page numbers that do not match after edits.
- Different dates or venue names between languages.
Link to the version record
Log each language version and approval in the materials and translation-version checker. If a change is only a typo after print is locked, use the typo correction workflow to decide between a correction slip and a reprint.
Worked example · Fictional example
A bilingual programme booklet
Fictional organisation and figures, for illustration only.
Persatuan Fiktif Perakaunan Pengurusan prepares a 24-page English and Malay booklet for a one-day conference. After the freeze, a keynote speaker's title changes in the English file only.
Round 3 catches that the Malay page still shows the old title. The designer corrects both, the log records the request and approver, and the approver signs the printer's proof v3. Version 2 is marked superseded.
Use this yourself
Programme booklet proofing checklist
Use for each round and attach the change log.
- Content freeze date and version name agreed with the programme owner.
- Session titles, times, rooms and session numbers checked against the approved programme.
- Speaker names, titles and organisations checked against their confirmations.
- Organiser, partner and sponsor names and logos checked against approved files.
- Each language version reads the same facts, dates and venue names.
- Contents page and page numbers match the final layout.
- Images and logos are the approved files, at the quality the printer asked for.
- Change log updated for every correction with requester and approver.
- Printer's numbered proof checked and signed by the named approver, with date.
- Printer instructed to print only the signed version.
Handle it in-house, or bring in help?
Your team can usually handle this when
- A short booklet, one language and a settled programme.
- Two readers can check it against the programme within the schedule.
- One person can apply corrections in a single pass.
Outside planning help earns its fee when
- Multiple languages, many sponsors and a programme that changes up to the freeze.
- Several people send edits to different copies.
- A tight schedule between final content and print with no spare reading time.
Want someone to run the proofing rounds?
A conference project lead can set the freeze date, assign the reading rounds, consolidate the corrections, keep the change log and make sure the printer works only from the signed proof. Design and printing stay with your designer and printer.
Questions organisers ask
How many proofing rounds are enough?
Enough that every reader has a defined job and the final proof is checked by someone who did not edit it. Five short rounds beat one long one.
Who should approve the final proof?
One named approver, usually the programme owner or event owner, after the second reader has checked names and numbers.
What if a speaker changes after the freeze?
Treat it as a new version, apply it to every language and log it, or decide with the approver whether a correction slip is enough.
Can the printer check our language versions?
Printers check layout and files. The language owners confirm the wording.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.