Academy / Guides / Chapter 4

After the session

For a one-off event, follow-up is a courtesy. For a cohort, it's the connective tissue that decides whether week five has the same energy as week one.

Debrief while it's warm

Within 48 hours, three questions with the core team. What worked? What would we change? What surprised us? The small observations fade fastest and matter most: where the energy spiked, which transition dragged.

Close the loop with participants

Two or three highlights, links to what was produced, one specific next step. Conversational, not transactional. You're continuing a relationship, not confirming a booking.

NewAI summaries and visual recaps. After a session, Kolab can produce a summary with key points, decisions and action items, plus a visual recap of the board. Edit it, then send it. The first draft of your follow-up email is already written.

Report impact in a form a funder will read

This is the part of the job nobody writes playbooks about, and for grant-funded programs it's the part that decides whether the program runs again.

Attendance is the weakest number you have. It tells a funder that people opened a link. Reach for evidence of what changed.

WeakStrongerWhere it comes from
142 registered89 attended, 71 came to three or more sessionsSession history across the cohort
Lively discussionContributions per participant, and how evenly talk time was sharedPer-speaker session analytics
Good feedbackThe share who say they'll do something differently, and whatOne-question survey, sent within 24 hours
Participants networkedWho worked with whom, across which countriesThe persistent space at the end of the program

Figures in the table are an illustrative example, not results from a real program.

NewSession history and analytics for every team. Kolab records who participated and how, including per-speaker talk time. That's observed engagement data, not a survey answer, and it's the strongest evidence most programs never collect.

In Kolab: recordings, searchable transcripts and board exports come out as Markdown or Word files, so the raw material for a report is a by-product of running the session. Recording requires the consent of the person being recorded and is included on Pro, Event Pass and program plans. Kolab doesn't train AI models on participant speech.

Ask better questions

Swap "did you like this session" for "what will you do differently because of it". Swap "how satisfied were you" for "what was the most useful or surprising moment". Five questions at most, sent within 24 hours.

Turn sessions into a system

Review, reflect, record, repeat. Two or three takeaways per session, written into the same doc every time, and folded back into your agenda template before the next run. After a year you have an institutional playbook instead of a folder of recordings nobody opens.

Get new guides and tutorials as they land

One short email when something new is published. Nothing here is gated, so skip this if you just want to read.

Keep me posted