Managing product-release timing and speaker confidentiality
The product team wants to announce something at the conference, the release date keeps moving, and speakers need to know what they may and may not say.
The short answer
Product timing is the vendor's decision. The event team's job is to make that decision visible in the programme: who confirms the announcement is going ahead, until when it can still change, and what each speaker is told in the meantime.
Agree one release owner, a confirmation deadline and a fallback version of every affected session. Ask the vendor's legal and communications advisers what confidentiality, disclosure and embargo terms apply. Those answers are theirs, not the event team's.
Who decides what
| Decision | Owner | What the event team needs from them |
|---|---|---|
| Whether and when the product is announced | Product leadership | A named release owner and a confirmation deadline |
| What may be shown, said or published | Release owner with communications | A written list of approved messages and materials |
| Confidentiality terms for speakers and staff | Vendor's legal adviser | The wording to use and who sends it |
| Press and social media timing | Communications | Embargo times and who may post |
| Programme changes if the date moves | Event owner | Fallback sessions agreed before the deadline |
Build the programme around a confirmation deadline
Pick a date after which the announcement is either in or out, and tell the product team the programme will be locked to it. Before that date, keep two versions of each affected slot.
Sessions that depend on a release should have a version that still works if it is delayed, for example a roadmap discussion in place of a demonstration.
- List every session, demo, slide and handout that mentions unreleased features.
- Mark each as depends on release or independent of release.
- For dependent items, write the fallback and who decides to switch.
- Set the confirmation date and the date after which printed or published materials are final.
- Record changes in the decision log so everyone sees the current position.
Speaker confidentiality: coordination, not conclusions
Speakers include employees, customers, partners and outside experts, and each group has different obligations. Do not assume one rule fits all.
Use the confidential information schedule to list what is confidential, to whom it may be shown and until when. Send speakers the wording your legal adviser provides, and keep a record of who has received it.
- Ask the legal adviser whether speakers need a written confidentiality agreement and who signs for the vendor.
- Ask which unreleased information customers and partners may be shown, and in what setting.
- Ask whether any disclosure rules apply because of the vendor's own status or its customers' status, such as for a listed company.
- Ask who approves speakers' slides on unreleased material and by when.
- Ask what happens to slides, recordings and notes after the session.
Materials, recording and publication
- Slides with unreleased content go through a single approver, with a version number and a final deadline.
- Check speaker recording permissions before any session with embargoed content is recorded or streamed.
- Decide what delegates may photograph or post. Say it on arrival, in the programme and on signs where relevant.
- Agree press timing with communications and use the embargo communication guide to see what to give and when.
- Store embargoed materials in an access-controlled place and name who can open them.
Common failure points
- The release date moves after the programme is printed and nobody owns the correction.
- A customer speaker is given more detail than the vendor intended, because no one wrote down what to share.
- Slides circulate in several versions and an old one is projected.
- Social media posts go out before the embargo time because the audience was never told.
- Rehearsal is held without the final slides, so the first full run is on stage.
Worked example · Fictional example
A fictional fintech platform's announcement day
Fictional organisation and figures, for illustration only.
Bayar Teras, a fictional payments platform, plans to launch a new reporting module on day one of its customer conference. Release depends on a final internal sign-off nine days before the event.
The event owner sets a confirmation date at ten days before, with two versions of the day-one keynote and two customer demos. The product director is release owner, and the vendor's legal adviser supplies confidentiality wording for the three partner speakers. On the confirmation date the release holds, and the fallback slides are archived rather than deleted in case the date moves again.
Use this yourself
Release and confidentiality question pack
Copy this list, send the questions to the named owner and record each answer with a date.
- Release owner and backup (name and role):
- Confirmation date and last date for printed or published changes:
- Which sessions, demos and slides depend on the release, and what is the fallback for each:
- For the legal adviser: what confidentiality terms are needed for employee, customer, partner and external speakers, and who sends them:
- For the legal adviser: do any disclosure or timing rules apply to this announcement, and who manages them:
- For communications: embargo times for press, social media and the website, and who may post:
- Who approves slides on unreleased material and what is the final slide deadline:
- May sessions on unreleased material be recorded or streamed, and who decides:
- What may delegates photograph or post, and how will they be told:
- Where embargoed materials are stored and who has access:
Handle it in-house, or bring in help?
Your team can usually handle this when
- The announcement is small and affects one keynote.
- The product team has a clear release owner and speakers are all employees.
- Your legal and communications advisers already have standard wording.
Outside planning help earns its fee when
- Several sessions, partners and customers depend on a date that can still move.
- Speakers come from different organisations with different expectations.
- Printing, publishing and rehearsal deadlines must be held against a moving confirmation date.
Need the release date and the programme kept in step?
A conference project lead can keep the dependency list, fallback sessions and confirmation deadline on one calendar, send your questions to the right adviser and track the answers. Legal terms and release decisions stay with your own advisers and leadership.
Questions organisers ask
Can the event team draft a confidentiality agreement?
No. Ask the vendor's legal adviser for the wording. The event team can send it, track who has received it and record the answers.
What if the release date moves after the programme is published?
Use the fallback versions agreed before the confirmation date and update delegates through the channels you listed. The decision log shows who approved the change.
Should unreleased content be recorded?
Only if the release owner and the speaker agree, and the question is answered before the session is advertised as recorded.
Do customers speaking at the event need the same terms as employees?
That is a question for the legal adviser. Do not assume the same terms apply.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.