Product demonstrations without unapproved claims
A product demonstration is the part of an insurance programme where unapproved wording is most likely to slip in, because it is live and often improvised.
The short answer
Treat every demonstration as content with an owner: the company showing the product. Agree who approves the script, slides, handouts and on-screen figures, set a close date, and brief the presenter on what is covered and what is not.
Whether particular wording about benefits, returns or protection is acceptable is a question for the company's own compliance, legal or Shariah-related contact. The organiser asks the question and keeps the answer on file.
Where unapproved claims creep in
Claims rarely enter through the main script. They arrive in a slide added the night before, a handout printed by a sponsor, a comment during Q&A or a live example with real-looking numbers.
The organiser cannot judge the wording, but can make sure each channel has an approved version and an owner.
Every channel, one owner
| Channel | Typical risk | Owner to name | What to ask for |
|---|---|---|---|
| Stage demo script | Improvised wording. | Presenting company's product or compliance lead. | Approved script and the approval date. |
| Slides and on-screen figures | Late changes, illustrative numbers. | Same owner. | Final file, version number, and a label for illustrative figures if the company requires one. |
| Handouts and leaflets | Printed before approval. | Company marketing contact. | Approved artwork before print order. |
| Booth or live demo | Staff speaking off script. | Company event lead. | A briefing note for booth staff. |
| Q&A and chat | Questions about specific products. | Moderator, agreed with company. | A rule for how product questions are answered or redirected. |
| Recording and social posts | Clips taken out of context. | Organiser and company jointly. | Whether recording and sharing are allowed for this session. |
Setting the approval route
- Ask each presenting company who approves demonstration content and how many working days review takes.
- Fix a content close date and a last-change date, and tell presenters both.
- Collect script, slides and handouts in one folder with version names, and record what was approved and when in a decision log.
- Send presenters a short briefing: what they may show, where their time ends and how Q&A is handled.
- Agree who may stop or redirect a session if wording departs from the approved script, and tell the presenter beforehand.
Questions for the company's compliance contact
- Which parts of the demonstration need review before the event?
- Are figures, examples and screenshots to be labelled in any particular way?
- May the presenter answer questions about specific terms, benefits or eligibility on stage?
- May the session be recorded, shared or clipped for social media?
- Who may approve a late change, and how fast?
Keeping the programme honest
Label sessions clearly as a product demonstration so delegates know what they are attending. Keep demonstrations separate from independent learning sessions in the programme and the room schedule.
Neutral wording on the programme page is the organiser's responsibility; product wording belongs to the company.
Worked example · Fictional example
A fictional claims app demonstration
Fictional organisation and figures, for illustration only.
A fictional takaful operator plans a 20-minute demonstration of a claims app at a seminar for about 150 practitioners organised by the fictional Persatuan Perlindungan Contoh.
The operator says its compliance contact needs 12 working days. The secretary sets the script and slide close date at week 4, the last-change date at week 7 and the event at week 10. A printed leaflet is dropped, because artwork could not be approved before the print order.
The moderator is briefed to redirect questions on specific terms to the operator's booth. The operator confirms in writing that the session may not be recorded.
Use this yourself
Demonstration approval checklist
Copy this checklist per presenting company and complete it before the content close date.
- Presenting company and session slot confirmed.
- Approver named for script, slides, handouts and booth briefing.
- Review time confirmed in writing, in working days.
- Content close date and last-change date sent to presenter.
- Final script, slides and handouts filed with version names.
- Illustrative figures labelled as the company requires.
- Q&A rule agreed with moderator.
- Recording and social sharing decision recorded.
- Late-change route and approver confirmed.
- Booth staff briefed.
Handle it in-house, or bring in help?
Your team can usually handle this when
- One company, one short demonstration, and a compliance contact who replies promptly.
- No printed material and no recording.
- A committee member can review the file before the event.
Outside planning help earns its fee when
- Several companies demonstrate in the same programme, each with its own approval route.
- Last-minute slide changes and printed materials keep arriving.
- Nobody on the committee can coordinate approvals and the final file set.
Need someone to hold the demonstration approvals?
A conference project lead can ask each presenting company for its approval route, set the content close dates, collect and version the final files, brief moderators and presenters, and keep the record. Product wording and its approval stay with each company. Send your demonstration list and event date to scope the work.
Questions organisers ask
Who is responsible for the wording in a demonstration?
The presenting company. The organiser makes sure there is an approved version and a named approver.
Should handouts be approved too?
Yes. Treat every printed or on-screen item as content with an owner and ask for approval before the print order.
How do we handle Q&A about specific products?
Agree a rule with the company: for example, the moderator redirects product-specific questions to the booth or to a follow-up contact.
Can we record demonstration sessions?
Ask the company in writing before the event and record the decision.
Related resources
- Planning an insurance professional conference versus an agency rally
- Coordinating insurer and takaful partner event approvals
- Managing broker and intermediary conference audience categories
- Planning claims and risk practitioner knowledge-sharing events
- Event brief builder
- Outsourced conference project management
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.