> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bigspin.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Understand and Act on AI-Generated Project Reports

> Bigspin generates AI-powered reports from your transcripts, surfacing quality issues, patterns, and trends. Learn how to view reports and improve your AI.

Reports are the analytical core of Bigspin. Once your project has transcripts, Bigspin generates a briefing — an AI-produced summary that analyzes your conversations in aggregate and identifies what your AI is doing well, where it struggles, and what recurring issues you should address. Reports give you a structured, evidence-backed view of your AI's behavior that would take hours to compile manually.

## What reports surface

A Bigspin report analyzes your project's full transcript set and surfaces:

<CardGroup cols={2}>
  <Card title="Quality issues" icon="triangle-exclamation">
    Specific failure modes and errors in your AI's responses, with examples drawn directly from your transcripts.
  </Card>

  <Card title="Behavioral patterns" icon="chart-line">
    Recurring patterns in how your AI responds to certain types of inputs or contexts.
  </Card>

  <Card title="Trends over time" icon="arrow-trend-up">
    How your AI's behavior is changing as you make updates, so you can track whether improvements are taking hold.
  </Card>

  <Card title="Strengths" icon="circle-check">
    Areas where your AI is performing well, so you know what to protect when making changes.
  </Card>
</CardGroup>

## How to view reports

<Steps>
  <Step title="Open a project">
    From the Projects dashboard, click the project card you want to analyze.
  </Step>

  <Step title="Navigate to the reports section">
    Inside the project, navigate to the reports or briefing section. Bigspin displays the most recent completed report.
  </Step>

  <Step title="Read the briefing">
    The briefing organizes findings into sections covering issues, patterns, and highlights from across your transcripts. Each finding links back to specific conversations so you can investigate further.
  </Step>
</Steps>

## Briefing Freshness

The **Briefing Freshness** indicator appears next to the report and tells you when the current briefing was last generated — for example, "Updated just now" or "Updated 2h ago." It briefly highlights when a new report has just completed, so you know when you're looking at fresh analysis.

<Tip>
  If your briefing is stale — for example, after uploading a new batch of transcripts or making changes to your AI — use the **Refresh** button next to the freshness indicator to generate a new report against the latest data.
</Tip>

## The iterative improvement cycle

Reports are most valuable when you use them as part of a continuous feedback loop:

<Steps>
  <Step title="Analyze">
    Generate a report for your current transcript set. Read the briefing to understand where your AI is falling short and what's working.
  </Step>

  <Step title="Identify issues">
    Use the findings to pinpoint specific behavior problems — broken flows, unhelpful responses, edge cases your AI mishandles. Drill into individual transcripts to see the issues in context.
  </Step>

  <Step title="Make changes">
    Update your AI's prompts, instructions, or underlying logic based on what you found. Deploy the updated version.
  </Step>

  <Step title="Re-analyze">
    Upload new transcripts from your updated AI (or let your connected data source sync them automatically), then refresh the report. Compare the new briefing to the previous one to confirm your changes had the intended effect.
  </Step>
</Steps>

This cycle — analyze, fix, re-analyze — is how you systematically improve your AI's behavior over time. Each report gives you a clear signal of whether you're making progress.

<Note>
  Generating a new report requires at least some transcripts in the project. If your project is empty, upload transcripts or connect a data source first. See [Upload Transcripts](/projects/upload-transcripts) and [Connect Data Sources](/projects/connect-data-sources).
</Note>