Event content production schedule: from draft to final
Speakers send material in different formats at different times, and the programme cannot be printed until the last one arrives.
The short answer
Content runs on its own chain: request, draft, review, approval, formatting, proof and release. Schedule it backward from the date each item is needed, and give every item an owner, a format and a lock date after which changes need approval.
The most common slip is not writing but waiting: for speakers, for reviewers and for the one person who can approve.
List the content before you schedule it
- Session titles and abstracts, speaker bios and photos.
- Slides and any videos or demonstrations to be played.
- The programme as it will appear online, in print and on screens.
- Moderator or host scripts and run-sheet wording.
- Signage, name badge text and any printed delegate pack.
- Post-event material such as summaries or recordings, if promised.
The stages each item passes through
- Request: tell the owner exactly what is needed, in what format and by what date.
- Draft received: log the date it arrived, not the date it was promised.
- Review: one named reviewer and a fixed return time.
- Approval: a named person who can say yes, so approval is not repeated.
- Formatting and proof: designer or printer receives content only after approval.
- Lock: after this date a change is a decision, not an edit. Record it in the decision log.
Work backward from the dependent dates
Start from when each output is needed: the print deadline, the day the programme goes online, the date the AV team needs slides and the date the run sheet is issued. Use the milestone back-planner for these dates.
Content that feeds several outputs, such as speaker bios, should have its lock date before the earliest of them.
What changes the sequence
- A late speaker confirmation delays titles, which delays the programme, which delays print.
- A new reviewer or approver adds a round.
- A new language version adds translation and its own review.
- Moving a speaker or session after lock reopens every output that includes it.
Pitfalls
- Collecting content by email with no single tracker.
- Setting a due date for speakers equal to your own deadline, with no time for review.
- Letting speakers send revised slides after the AV lock date without anyone deciding to accept them.
- Not saying who owns the final version of each item.
Worked example · Fictional example
Content for a one-day professional seminar
Fictional organisation and figures. Durations are hypothetical working days to show the structure.
A fictional accountants' association plans a seminar with 12 speakers and publishes a programme online and in a printed delegate pack. The secretariat works back from the print deadline.
It sets the speaker content lock at 10 working days before print, so there is time for one review round and a proof. The programme lock is earlier than the slides lock, because the programme appears in more places and the slides are only used on the day.
| Item | Owner | Request sent | Draft due | Review and approval | Lock | Used in |
|---|---|---|---|---|---|---|
| Session titles and abstracts | Programme chair | T-35 | T-25 | T-20 | T-15 | Web, print, run sheet |
| Speaker bios and photos | Secretariat | T-35 | T-22 | T-17 | T-12 | Web, print |
| Slides | Each speaker | T-30 | T-8 | T-5 | T-3 | AV only |
| Delegate pack text | Secretariat | T-25 | T-15 | T-10 | T-7 |
Use this yourself
Content tracker
Use one row per content item. Update the status column every time something arrives.
- Content item and format required
- Owner who supplies it and owner who approves it
- Dates: request sent, draft due, review due, lock
- Where it is used (web, print, screens, run sheet)
- Status and date received
- What happens if it is late (default text, placeholder, delay)
| Item | Supplier | Approver | Draft due | Lock | Used in | Status |
|---|---|---|---|---|---|---|
Handle it in-house, or bring in help?
Your team can usually handle this when
- Few speakers and one person who reviews everything.
- A familiar programme format with existing templates.
- Content is produced internally.
Outside planning help earns its fee when
- Many speakers, languages or reviewers, and nobody holds the master version.
- The programme goes to print or to members before speakers are confirmed.
- Content approvals need sign-off from a committee or a regulator-facing group.
Need the content chase run for you?
An Event Blueprint sets out the content stages, owners and lock dates in the schedule. A project lead would keep the content tracker, chase speakers and reviewers and bring any late items to your decision owner before they hold up print or AV.
Questions organisers ask
When should speakers be asked for slides?
Ask early and say what you will use them for. Set the due date well before the AV lock date to leave time for review, and tell speakers that later changes need approval.
Who should approve content?
One named person per item. If several people must see it, give them a shared review window rather than passing it down a chain.
What if a speaker misses the lock date?
Decide in advance what happens: publish default text, use a placeholder or accept the late version with an approver's yes. Log the choice.
How does this relate to the milestone plan?
The event milestone plan holds a few content milestones. This schedule lists each content item behind them.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.