Skavio Meeting: keeping the internal summary separate from the public statement

A recorded meeting often ends up producing two documents: a working record for the people who were in the room, and — potentially — a message for people who were not. The first can be detailed, messy and full of names. The second has to be short, approved and defensible. Skavio Meeting generates a speaker-aware transcript and an actionable report from a recording; it does not decide which parts may leave the company. That decision stays with a person. This guide sets out a simple operating split: build the internal record first, verify it against the transcript, then open a separate release gate before anything is written for an outside audience.

One recording, two documents with different rules

A single recording carries material that belongs to two very different audiences. Internally, colleagues need the whole picture: who raised what, which numbers were challenged, where the discussion stopped. Externally, most of that does not belong in a statement — and some of it must never appear at all. The practical failure here is not technical. It is a copy-paste failure: someone takes the generated summary, trims a paragraph and sends it out as the company position. That summary was prepared to summarise a discussion for the people who attended it, not to serve as a public position. So make the split explicit before the first upload. Decide the audience of each file, name an owner for each, and mark the internal one as internal in the title and the first line — not in a comment at the bottom of the page.

Build the internal record before anything else

Start from the recording and let the pipeline produce the material you will review. Skavio Meeting runs AssemblyAI transcription with speaker diarization, followed by OpenAI meeting analysis and report generation. The verified outputs are a speaker transcript, summary, key points, decisions, action items, open questions and a follow-up draft, exportable as TXT, DOCX or PDF. The report is a structured draft, not a record of fact. Its value comes from being checkable: a claim in the summary should be traceable to a line in the speaker transcript. Keep the two together. A summary that travels without its transcript is an assertion, not evidence. Two fields deserve particular caution. The decisions list holds candidates until a human confirms them, and the follow-up draft is text to edit rather than text to send.

The verification pass: decisions, proposals and questions

Meeting analysis reads language; it does not attend the meeting. A firm-sounding sentence can be a proposal, a hypothetical, or a restatement of something already rejected. The review pass exists to separate those cases. Work through the claimed decisions one by one against the transcript. Ask who said it, whether the room agreed, and whether the speaker had authority to settle the point. Check names, dates, amounts and product terms against the spoken words rather than against the summary's phrasing. Where several people spoke at once, speaker attribution can land on the wrong participant, so listen again before quoting anyone. On speed: the product knowledge includes internal fixture measurements, such as a 3,763-second fixture that completed in 40 seconds and identified three speakers across 113 utterances. That describes processing time on one fixture. It does not establish accuracy across accents, audio quality or meeting types, and it should not be presented as a quality claim.

The release gate: redaction, approval and one reviewed export

Skavio Meeting generates documents. The supplied product description documents no automatic sending of the follow-up draft, no automatic publication control and no automatic redaction step. Those remain human steps — and they are the steps that matter most. Treat external release as a gate with a checklist rather than a judgement call. Redact client names, personal data, commercial figures and anything said under an expectation of confidence. Write down who approved the public version and when. Keep the internal original unmodified so the approved text can always be compared against it. Export format is a handoff choice, not a control. A PDF is not more approved than a DOCX; both are only as final as the person who signed off on the text.

What this workflow does not settle

This is operational guidance, not legal advice. Confidentiality, professional privilege and data-protection obligations depend on jurisdiction, contract and the nature of the material, and they need review by someone qualified to give it. A tool that produces a tidy report neither creates those obligations nor discharges them. Nor does the workflow replace judgement about what a company should say publicly. The most useful thing the split achieves is simpler: the people drafting the public statement can see exactly what was said, in whose voice, with which caveats — while the people who were in the room keep their working record intact.

Open Skavio Meeting and turn a recording into a reviewable draft →