Promotional offer50% off every paid plan, billed monthly.See pricing
Citesvue
Projects and findings

Findings and evidence

Citesvue extracts typed findings from a session instead of a wall of notes. Each one carries the quote, speaker, and moment that produced it, and visual evidence can add the frame and on-screen text. In the app they live under Artifacts.

Updated
8 October 2026
Read
4 min
For
Everyone; approving needs member
The types

Seven kinds of finding.

Typed because they route differently: a bug belongs in a tracker, a decision belongs in a record.

Bug
A defect, unexpected behaviour, or regression somebody hit. Carries a severity.
Requirement
Something the product or the work must do, including new capabilities somebody asked for.
Decision
A choice the group agreed to.
Action item
A concrete task, with an owner and a date where they were named.
Risk
Something flagged as able to go wrong, including concerns a customer raised. Carries a severity.
Question
A question that was left open.
Insight
A durable learning worth keeping.
Artifacts: every recording with its findings, how many still need review, and the mix of types.
On the recording
The Artifacts tab on a recording lists its findings with type filters. Open one for its evidence.
By recording
Artifacts in the sidebar lists every recording with how many findings it produced and how many still need review. Open one to review its whole list: Approve all, then Push everything approved.
One recording's findings, grouped by type, with Approve all and Push.
Search all
Switch to Search all to search every finding and its quote across the workspace, filtered by type and project.
Search all: every finding and its quote, filtered by type.
Export
Export on the Artifacts page downloads the current list as CSV.
Evidence and review

What each finding carries, and what to do with it.

  • The evidence

    A verbatim quote, the speaker, and the second it was said. When visual evidence corroborates a finding, it also carries the frame and the text read from the screen. The quote is checked against the transcript rather than paraphrased.

  • Severity

    Critical, high, medium, or low, on bugs and risks. It maps to priority when a finding is pushed to a tracker.

  • Review

    Findings arrive as Needs review. Approve the ones you stand behind and dismiss the rest; this is the step that keeps a tracker trustworthy. Reopen review undoes a decision.

  • Approval gates pushing

    A finding cannot be pushed until it is approved. Viewers cannot push at all; members and above can.

Open a finding and its evidence comes with it: the words, who said them, and when. That is what makes it checkable by someone who was not there.

Approved findings go to a tracker, a page, or a channel. See how integrations work.

Common questions

Findings, answered.

  • Extraction reads intent from a conversation, and conversations are ambiguous. Dismiss a finding that is wrong; types cannot be reassigned today.

  • Extraction only keeps findings it is reasonably confident in and that it can tie to a verbatim quote, so a short or exploratory session may genuinely produce none. The transcript and recap are still there.

  • A generated overview of the whole session that forms the body of the recap. It is produced separately from the finding types above.

  • Yes. Export on the Artifacts page downloads CSV, and a recording's own export includes its findings in PDF, Word, CSV, or JSON.

  • No. Approval only marks it as one you stand behind. Pushing is a separate, deliberate action.

Next steps

Next steps.