Reports (for hosts)
A report is dembrane’s automatic synthesis of a project - the quickest way to capture the atmosphere and the main questions and hand them back in a form a busy stakeholder will actually read. Best for a council that wants a written summary after a town hall, a findings document for the team, or a funder’s end-of-engagement write-up. It’s the natural home for everything you found in chat and the library: themes, quotes, answers - gathered, ordered, presented.
The full mechanics live in the canonical Reports reference.
Build a report#
Open your project and go to Reports. dembrane analyses all the conversations (a few minutes) and drafts the report from sections - each a focused piece: an overview, a theme, a question, a recommendation. A practical order:
- Decide the shape. What does the reader need - an executive summary, a theme-by-theme breakdown, the standout quotes? Sketch the sections first.
- Add sections. dembrane drafts each from the conversations, in participants’ own words.
- Review against the sources. Use the library and chat to sanity-check nothing’s missing.
- Order it so the report reads top to bottom for your audience.
Tip
Generate the library first. It gives you the map of themes and the best quotes, so you know which sections are worth having before you draft.
Reports also include a timeline view - useful for a programme across several events or weeks, to see how the conversation evolved, not just its final shape. And a report isn’t frozen: as more conversations come in, or after you improve the project’s context, regenerate the sections to refresh it.
Share and send#
Two ways to get a report out:
- Publish - make it available to share (owners, admins and members can publish; external collaborators cannot).
- Export - download it, usually as a PDF for circulation.
You can also put a report on a schedule so dembrane regenerates and emails it on a cadence - handy for a weekly digest to a steering group.
Best of all: participants who left an email at the end of their session can be notified automatically when the report is ready or updated. Turn on participant updates in the portal editor and you’ve got built-in post-event follow-up, including for people who couldn’t attend.
Important
A published report shares findings, not raw recordings. If a stakeholder needs the source transcripts, use export instead - and mind the data-ownership implications of who sees what.
What your plan gives you#
Reports use built-in analysis to draft their sections, so generation needs Changemaker or above.
| You’re on | Reports |
|---|---|
| Free | Generation gated under free-tier limits. |
| Innovator | Generation gated (no built-in analysis). |
| Changemaker | Full report generation, on EU-hosted Gemini. |
| Guardian | As Changemaker, on an EU-sovereign stack (coming soon). |
Publishing is also role-gated: external collaborators can generate but not publish. See the capability matrix.
Related#
- Reports - feature reference - the canonical how-it-works page.
- Export & data portability - transcripts, CSV/Excel, and transcript zips when you need the raw inputs.
- Library & analysis - find the themes and quotes before you draft.
- Chat & Ask - pull together what people said about one topic, with sources.
- Tiers, billing & usage - what each plan unlocks.
Comments