BUGhigh
00:14:23“The export button is broken - when I click it, nothing happens and there’s no error.”
Maya - Product Lead
Reproduces on Chrome 121 + Safari 17. Same step in dashboard. Audio confirms.
Guide · Meeting records
A meeting record you can check line by line.
Summaries are excellent for catching up and useless for settling arguments. This guide separates the two jobs: why summarisation loses the detail that matters, and what a citable record contains instead.
Updated4 August 2026Read6 minForPMs, agencies, delivery and revenue leads
Three failure modes
What summarisation costs you.
None of these are model quality problems. They are consequences of the format.
- 01
Compression removes the decisive detail
A summary optimises for readability, so it drops the version number, the literal error string, the conditional that made the approval conditional. Those are precisely the details a dispute turns on.
- 02
Attribution collapses
Six people speak, one paragraph is produced. "The team agreed" hides who agreed, who objected, and who was silent. Consensus gets manufactured in the summarising step.
- 03
Confidence is uniform
A summary reads with the same certainty whether a point was stated plainly or inferred from a half sentence. Nothing in the output distinguishes the two, so the reader cannot calibrate.
The shape
Six fields per claim.
This is the whole idea: the record is a list of claims, and every claim carries its own proof.
Claim
One sentence, one assertion, so it can be individually accepted or challenged.
Speaker
Who said it, by name, not by role or by team.
Quote
Their words, verbatim, long enough to carry the qualifier.
Timestamp
The second the quote begins, so playback is one click away.
Frame
The screen state at that moment when the claim is about something visible.
Confidence
Whether the claim was stated, implied, or contested, surfaced rather than smoothed.
Practice
Five habits that keep a record defensible.
- Record the sessions that produce commitments
Not every call. The ones where scope, money, dates, or acceptance are decided.
- Keep the source, not just the derivative
A note is a pointer. If the recording is gone, the pointer dangles and the note becomes an assertion again.
- Separate the record from the readout
Publish the readable summary if you like, but generate it from the cited record so the two cannot diverge.
- Make disagreement visible
A record that flattens dissent will be contradicted by the first person who remembers dissenting.
- Decide retention deliberately
Long enough to defend the decision, short enough to honour privacy commitments. Then make deletion actually remove derived copies.
Worth saying plainly
Summaries are not the enemy.
Nobody wants to read citations to find out whether a call was useful. Keep the summary. The argument here is about which artifact is authoritative: derive the readable version from the cited record, so improving the prose can never quietly change what the meeting decided.
That ordering is also what makes an answer safe to automate. When retrieval comes first and composition is constrained to what was retrieved, an unsupported question produces a refusal instead of a confident invention.
Common questions
Citable meeting records, answered.
- Because a summary asserts without showing its source. When someone remembers a conversation differently, there is nothing to check: no speaker attribution on the specific line, no quote, no timestamp. The disagreement becomes a matter of authority rather than evidence.
- A record where each claim carries the speaker, the verbatim quote, and the moment it was said, so a reader can verify any line against the source. In Citesvue a claim can also carry the video frame when the point was about something on screen.
- A transcript is the raw material, not the record. Nobody reads 12,000 words to settle a question, and a transcript does not distinguish a decision from an aside. The useful artifact is a short set of claims, each bound to the transcript moment that supports it.
- Yes. Upload the recording you already have from any source. Citesvue does not require a meeting assistant to join the call in order to index it.
- Recording obligations depend on your jurisdiction and participants, so treat consent as a process decision. On the platform side, deleting a recording removes the media and everything derived from it, and customer content is never used to train models.
Closing argumentYour next recording could be
Your next recording could be
your most valuable asset.
Or it could sit in a Drive folder nobody opens again. The difference is whether it has citations attached.
- SetupOne drag-and-drop upload, or send the notetaker. No plugins.
- First insightCited Q&A on a 60-min recording in under 6 minutes.
- Cancel anytimeFull data export, full right to erasure.