Session summaries in Sociana are drafted by AI and published only after a named organiser approves them. Open AI Session Admin on your Profile, read each draft against the session, then tap Approve, Reject or Edit Summary. Approved summaries record who approved them and when; members see nothing until then.
Who this guide is for
You are the secretariat, programme chair or content lead for a conference or association event. Members ask for proceedings, speakers rarely send slides and nobody has two weeks to write notes. You are open to AI drafting a first pass, as long as a human decides what goes out under the association’s name.
Why approval is the whole point
AI-drafted text is quick and sometimes wrong. A summary can drop a caveat, mis-attribute a view or compress a panel into a slogan. For an association, the speaker’s name is on the line and so is the host’s. The risk is not the draft; it is a draft that reaches members unreviewed.
The approach that works is the one editors have always used: the machine proposes, a named person disposes. Sociana’s summaries follow that. A draft stays hidden from members until an organiser approves or edits it, and the app states that summaries appear only after they are approved. Sociana does not generate your polls or quizzes with AI; summaries, avatars and activations are the AI features on offer.
The review workflow at a glance
| Stage | Who | What happens | Status shown |
|---|---|---|---|
| Draft created | System | An AI-drafted summary appears per session | Draft |
| First read | Content editor | Reads the draft against the session recording, notes or slides | Draft |
| Edit | Content editor | Adjusts title, priority and summary points; adds or removes points | Draft |
| Speaker check | Optional | Speaker confirms their own section by email | Draft |
| Approve or reject | Owner, Manager or named panel admin | Taps Approve, or Reject to hide | Approved or Rejected |
| Publish | Automatic on approval | Members can read the summary under the Ai Session tile | Approved |
Step by step
Step 1: Agree who may approve
Approval sits with Owners and Managers, or with panel admins named for the occasion. Name two people, a primary and a backup. Write down who has final say if the content editor and the speaker disagree.
Step 2: Agree the house rules for tone and content
Decide, before the first draft, what a summary must and must not contain. Typical rules: key points only, no verbatim quotes without the speaker’s consent, no commercial claims by sponsors, no personal data. Keep the list to five items so reviewers actually use it.
Step 3: Open AI Session Admin
On the organiser’s Profile, AI Session Admin lists each AI-drafted summary per category with a status badge. Work category by category, starting with the sessions members asked about most.
Do it in Sociana: AI session summaries with the AI Session Admin switch on for the roles that review.
Step 4: Check each draft against the source
Read the draft with the session open beside it. Check names, numbers, dates and every sentence that starts “the panel agreed”. If a point is not supported, delete it. If something important is missing, add a point.
Step 5: Edit, then save
Edit Summary lets you change the title, priority, status and the summary points, and add a point where needed. Tap Save changes. Treat the edit as the real work; the AI saved you the blank page, not the review.
Step 6: Approve or reject
Tap Approve to publish or Reject to hide. Rejected summaries stay hidden; you can come back to them. The app records who approved a summary and when, which gives you an audit trail when a speaker asks “who signed this off?”.
Step 7: Tell members, and tell speakers
Announce that summaries are live and link to the Ai Session tile. Send each speaker the link to their own summary so a correction arrives early.
A short reviewer’s checklist
Keep this beside the draft while you read it. Does every name and title match the programme? Does every number appear in the speaker’s slides or the recording? Is every sentence that starts “the panel agreed” supported, or did the panel only discuss it? Does the summary stay inside what was said in the room, or has it added background that the AI supplied? Would the speaker be comfortable seeing it quoted under the association’s name? Is there anything a sponsor could read as an endorsement?
If any answer is no, edit or delete that point. If more than two answers are no, reject the draft and write the summary by hand. Rejecting is not a failure of the workflow; it is the workflow doing its job.
Pitfalls
- Approving in bulk. Ten summaries approved in a minute were not reviewed. Cap the daily batch.
- One approver for a three-day programme. Fatigue lowers quality; use a backup.
- Publishing before speakers have seen it. Not required by the system, but it avoids the awkward email.
- Leaving the house rules unwritten. The reviewer on day three will not have the same judgment as on day one.
- Claiming the summaries are verbatim. They are summaries; label them so.
India and SAARC notes
Indian associations run on volunteer secretariats and part-time conference chairs, and proceedings often take months to appear, if they appear at all. A 24-hour approved summary is useful to members who could not attend a parallel track, and to sponsors who want to see their session recorded. India’s national convention body, ICPB, runs the annual Conventions India Conclave, in its 15th edition in 2026 (ICPB, 2026); events of that kind generate dozens of sessions in a few days, which is exactly the volume where drafting help and a human check pay off. For events with speakers in several languages, review the English summary only if you can verify the source; do not approve what you cannot check.
Avoid personal data in summaries. Speaker and audience names should appear only where already public, and the association’s own data-handling statement should cover AI use. Sociana’s trust centre is where data handling is described.
How Sociana handles this
Members browse categories, open a session and read a Session Summary under the Ai Session tile. Behind it, AI Session Admin lists each draft with a status badge and gives the organiser Approve, Reject and Edit Summary. Approved summaries store the approver and the time. Where the draft input comes from is part of per-occasion setup, so confirm that at kickoff rather than assuming it.
The worked example is EEMA Connect, the multi-occasion app for the Event & Entertainment Management Association, where members read summaries only after the organisers approved them. Because EEMA Connect is a multi-occasion app, approved summaries sit beside the next occasion in the same app; see multi-event and agency apps. You can walk through the session summary approval demo.
FAQ
Does Sociana publish AI summaries automatically?
No. A draft stays hidden from members until an organiser approves or edits it. The app also states that summaries appear only after approval.
Who can approve a summary?
Owners and Managers, or panel admins named for the occasion. Agree the names before the event.
Can we change the summary after publishing?
Yes. Use Edit Summary to change the title, priority, status and points, and save. If the correction is material, tell the speaker and note it in the update.
Do we need AI summaries for every session?
No. Pick the sessions members ask about, and skip sensitive sessions, closed-door discussions and anything under Chatham House rules.
Related reading
Glossary: AI session summary, keynote, breakout session. Occasion hubs: conferences, association events, recurring communities.