Guide · Evidence Q&A

Ask in plain language, get an answer you can check.

Every answer in Citesvue is composed from retrieved evidence and cites what it retrieved. This guide covers where to ask, how to ask well, how to read a citation, and why a declined answer is a feature.

Updated26 August 2026Read6 minForEveryone; works on every plan
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.

Pushed to Jira · CV-1284Frame14:23.4
Where to ask

Four scopes, from one recording to the whole workspace.

Pick the smallest scope that could contain the answer; tighter scope, sharper retrieval.

One recording

Ask from the recording page. Best for "what happened in this session" questions: what failed, what was agreed, what did the customer object to.

One document

Ask from the document page. Answers cite the page and section they were read from.

A project

Ask across everything filed in a project - recordings and documents together. One question about a client returns spoken evidence by timestamp and written evidence by page.

The workspace

Ask across sources you select from the whole workspace, when the answer could be anywhere.

Anatomy of an answer

What a citation carries.

This is what makes an answer verifiable instead of plausible.

Quote

The verbatim words the answer rests on, not a paraphrase of them.

Speaker

Who said it, by name when the speaker is known.

Timestamp

The second it was said. One click seeks the player there.

Frame

When the evidence was visible rather than spoken, the citation carries the video frame - an error toast, a form state, a dashboard value.

Page and section

Document citations name the page and heading they were read from, scanned pages included.

Confidence

Each answer shows how well supported it is, so a thin answer looks thin.

Worked example

One question, one checkable answer.

"What did the customer say about SSO?"

They committed to it conditionally: SSO is required for the security review, but only for the enterprise rollout, not the pilot.

Citation: Priya N. at 22:41 - "we can pilot without SSO, but procurement will block the wider rollout until it is there" - with the frame showing the requirements slide on screen.

Click the citation, hear the sentence, see the slide. If someone later remembers the commitment differently, the dispute takes thirty seconds to settle.

Technique

Four habits that get better answers.

  • Ask about facts, not opinions

    "What did the tester say when checkout failed?" retrieves evidence. "Was the meeting productive?" asks for a judgement the record cannot support.

  • Name the thing

    Use the words people actually said where you can - feature names, error text, clause numbers. Retrieval searches meaning and exact wording together, and exact wording is precise.

  • One question at a time

    Compound questions dilute retrieval. Ask the follow-up as a follow-up; the conversation keeps its context.

  • Then open the citation

    The answer is a claim; the citation is the proof. For anything that matters, click through and read or watch the source. That is the workflow the product is built around.

If an answer comes back with no supporting evidence, the page says so and suggests rephrasing or waiting for indexing to finish - see troubleshooting for the full list of states.

Common questions

Evidence Q&A, answered.

  • It means retrieval found nothing that supports an answer, and the system declines rather than guessing. That is information: the record is silent on the point. If you believe the evidence exists, rephrase using the words that were actually used, or check that processing has finished.
  • Yes. Questions run as conversations: each follow-up keeps the context of the ones before it, and past conversations are saved so you can return to them.
  • Each plan includes Evidence Q&A questions per seat per month - 50 on the free plan, more on paid tiers - pooled across the team and shared between recording and document questions. Reading transcripts and recaps never costs questions.
  • Yes. Speech, on-screen activity, and document pages are indexed together, so one answer can cite a spoken sentence and the frame where the error was visible at that moment.
  • Send it, citations included, to Slack or Notion, or to your own systems through a webhook. The answer arrives with its quotes and timestamped links, not as a bare paragraph.
  • Yes - the search page runs keyword and meaning search across transcripts, findings, on-screen text, and documents, and is often faster when you know roughly what you are looking for and just need the moment.
Closing argument

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.