Technology, fintech and B2B software
Separating roadmap briefings from public sessions
A software company or vendor forum wants to tell some people what is coming next, but the conference programme is also open to others.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
Classify every session before the programme is published: public, registered delegates only, or invited and confidential. Then give each class its own room or time slot, access rule, recording rule and named approver.
Whether a briefing is truly confidential is for the product owner and its legal adviser to decide. The organiser's job is to make the access rules clear and to run them.
Start with three session classes
Public sessions can be promoted, recorded and shared. Delegate sessions are for registered attendees only. Invited briefings are for named people, often under a confidentiality agreement that the company manages.
Write the class beside every session in the draft programme. A session with no class has not been decided yet.
Decide who sits in which tier
| Audience tier | Typical examples | Question to settle |
|---|---|---|
| Customers | Current users of the product. | Do they need a signed agreement before the room, and who holds it? |
| Partners and resellers | Integrators and channel companies. | May they bring colleagues who are not named? |
| Press and analysts | Journalists, research firms. | Are they allowed in delegate sessions only, or in briefings too? |
| Competitors and prospects | Staff of rival vendors, potential buyers. | Who decides, and how is a registrant checked against the invite list? |
Make the separation physical and visible
- Use a separate room or a clearly timed slot, not a curtain or a corner of the exhibition hall.
- Agree how names are checked at the door and who holds the invited list.
- Mark the programme and the app with the class of each session, in plain words.
- Decide where closed-briefing speakers wait, so they are not mixed into public areas.
Recordings, slides and live posting
A public session may be recorded and its slides shared. An invited briefing normally needs the opposite default: no recording, no slide upload, and a stated rule on phones and social media.
Ask the product owner what happens to slides after the event, and tell speakers before they build the deck.
Sequence for the organiser
- Collect the list of planned sessions and ask the product owner to mark each class.
- Agree audience tiers and the person who approves exceptions.
- Place invited briefings in rooms that can be closed, away from open traffic.
- Brief registration staff and ushers on checks and who to call for a doubtful case.
- Record each decision in a decision log and send the final rules to speakers and the AV team.
Worked example · Fictional example
A fictional user summit with one closed briefing
Fictional organisation and figures, for illustration only.
A fictional business software company, Platform Fiktif, runs a two-day user summit with 12 sessions. Three are marked invited briefings on future product plans, and nine are for registered delegates.
Registration shows two attendees from a rival vendor. The product owner decides they may attend delegate sessions but not the briefings, and the registration lead updates the door list the day before. The AV team is told that briefing rooms have no recording and the programme shows a lock label on those three sessions.
Use this yourself
Session classification table
Copy this table, one row per session, and have the product owner and organiser sign off before publication.
| Session | Audience tier | Access rule | Recording and slides | Approver |
|---|---|---|---|---|
Handle it in-house, or bring in help?
Your team can usually handle this when
- Few sessions are closed, the audience is small and known, and the company handles its own agreements.
- The venue has a room that can be closed off easily.
- One person has authority to decide who attends.
Outside planning help earns its fee when
- Several closed briefings run beside public sessions and attendee lists change daily.
- Confidentiality questions involve customers, partners and press at once.
- Registration, AV and programme decisions must be matched across suppliers.
Need the access rules coordinated?
A conference project lead can turn your session classes into a programme, a door procedure and instructions for registration and AV, and keep the decision log current. Legal terms and confidentiality agreements stay with the company and its advisers. Send your session list and the audiences you need to separate.
Questions organisers ask
Who decides what is confidential?
The product owner, usually with legal advice. The organiser records the decision and applies the access rule.
Can a closed briefing be in the same room as a public session?
Only at different times, and the room should be cleared and re-checked between them. A separate room is simpler if one is available.
Should invited briefings appear in the public programme?
That is a choice for the company. Some list them with a lock label, others leave them off the public version.
What if someone forwards the invite?
Ask how names are checked at the door and whether invitations are personal. Agree the answer before invitations go out.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.