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

# Analytics

> Measure terminal workflow reliability, content quality, template performance, throughput, and production backlog.

Analytics is WriterzRoom's dedicated measurement view. Where the Dashboard's Production health panel gives a 30-day snapshot, Analytics gives the full breakdown across a selectable range, with reliability, quality, throughput, and a prioritized recommendations feed in one place.

<div style={{ display: 'grid', gridTemplateColumns: 'repeat(3, 1fr)', gap: '12px', margin: '1.5rem 0' }}>
  <div style={{ border: '1px solid rgba(128,128,128,0.20)', borderRadius: '14px', padding: '18px' }}>
    <div style={{ fontSize: '12px', color: '#4f6ef7', fontWeight: 800, textTransform: 'uppercase', marginBottom: '8px' }}>Range</div>
    <div style={{ fontSize: '18px', fontWeight: 800, marginBottom: '8px' }}>7, 30, or 90 days</div>
    <div style={{ fontSize: '13px', color: 'var(--colors-content-secondary)', lineHeight: 1.55 }}>Every metric, chart, and recommendation recalculates for the selected window.</div>
  </div>

  <div style={{ border: '1px solid rgba(128,128,128,0.20)', borderRadius: '14px', padding: '18px' }}>
    <div style={{ fontSize: '12px', color: '#22c5d4', fontWeight: 800, textTransform: 'uppercase', marginBottom: '8px' }}>Headline metrics</div>
    <div style={{ fontSize: '18px', fontWeight: 800, marginBottom: '8px' }}>6 tracked figures</div>
    <div style={{ fontSize: '13px', color: 'var(--colors-content-secondary)', lineHeight: 1.55 }}>Reliability, quality, throughput, and publishing, at a glance.</div>
  </div>

  <div style={{ border: '1px solid rgba(128,128,128,0.20)', borderRadius: '14px', padding: '18px' }}>
    <div style={{ fontSize: '12px', color: '#f59e0b', fontWeight: 800, textTransform: 'uppercase', marginBottom: '8px' }}>Recommendations</div>
    <div style={{ fontSize: '18px', fontWeight: 800, marginBottom: '8px' }}>Prioritized, not static</div>
    <div style={{ fontSize: '13px', color: 'var(--colors-content-secondary)', lineHeight: 1.55 }}>Derived from this period's actual numbers, with a direct action for each.</div>
  </div>
</div>

## Headline Metrics

| Metric               | What it measures                                                                     | Healthy signal      |
| -------------------- | ------------------------------------------------------------------------------------ | ------------------- |
| Terminal reliability | Share of finished workflows (successful plus failed) that succeeded                  | 95% or higher       |
| Average quality      | Blended SEO and readability composite across scored outputs, on a 0-100 scale        | 70 or higher        |
| Generations          | Total generations in range, with change versus the prior period                      | Stable or growing   |
| Failed outputs       | Count of failed workflows in range, alongside the current draft or in-progress count | Zero                |
| Average output       | Average words produced per generation                                                | 300 words or more   |
| Published            | Count of published assets, and the share of finished output that actually shipped    | Rising publish rate |

A quieter secondary row sits below the headline strip with supporting context: average duration, total words generated, scoring coverage, and draft backlog.

<Info>
  An em dash in place of a number means the metric is unavailable for the selected range, not zero. Terminal reliability with no finished workflows yet, or a quality score with no scored outputs, are both shown as unavailable rather than defaulting to a misleading value.
</Info>

## Range and Refresh

The 7d / 30d / 90d selector re-queries every chart, table, and recommendation for the new window. Refresh re-runs the same queries without changing the selected range, useful when checking on a generation or publishing run that just completed.

<Note>
  Reliability is read from your saved content records for the selected window when any exist. If no content record falls inside that window, reliability falls back to the backend-reported success rate for the same period instead of showing as unavailable.
</Note>

## Recommended Actions

Analytics surfaces a prioritized recommendations feed above the detailed views, generated from the current period's metrics rather than a static checklist. Severity determines ordering: critical and warning items surface issues that need a decision, info items are situational, and a single positive card appears only when nothing else fired.

| Condition                                                        | Severity | Surfaces as                             | Default action            |
| ---------------------------------------------------------------- | -------- | --------------------------------------- | ------------------------- |
| No generations in range                                          | Info     | No production data in this period       | Open Studio               |
| Terminal reliability below 80%                                   | Critical | Terminal reliability is critical        | Review failed outputs     |
| Terminal reliability between 80% and 95%                         | Warning  | Reliability is below the 95% target     | Review failed outputs     |
| Average quality below 70                                         | Warning  | Average content quality is below target | Open Content Quality view |
| Quality scoring coverage below 60% (with quality data available) | Warning  | Quality scoring is incomplete           | Open Content Quality view |
| No quality telemetry at all, despite generations existing        | Info     | No quality telemetry captured           | Open Studio               |
| Draft backlog of 10 or more, or over half of all content         | Info     | N drafts awaiting review                | Open Content Library      |
| Average output under 300 words                                   | Warning  | Outputs are unusually short             | Open Studio               |
| None of the above                                                | Positive | Production posture is healthy           | None                      |

## Views

<AccordionGroup>
  <Accordion title="Executive">
    Daily generation volume plotted as a line chart over the selected range.

    Paired with an executive summary panel:

    * **Reliability target** — status badge reading target met, below target, or awaiting terminal runs when no finished workflow exists yet
    * **Most used template** — the highest-volume template for the range
    * **Terminal workflows** — total finished (successful plus failed) workflow count
    * **Scoring coverage** — scored outputs out of total outputs
  </Accordion>

  <Accordion title="Reliability">
    Daily terminal success-rate trend, plotted 0 to 100%.

    Paired with a per-template reliability table: Template, Runs, Success rate, Average duration, and Words. A template with no finished run yet shows an em dash for success rate and duration rather than a zero.
  </Accordion>

  <Accordion title="Content Quality">
    A coverage panel showing average SEO score, average readability score, total scored outputs, and overall scoring coverage as a percentage.

    Paired with the platform's quality operating rule: no output is presented as validated without a persisted score. Missing telemetry is shown as unavailable, never folded into an average as a zero.
  </Accordion>

  <Accordion title="Usage">
    Hourly distribution of when generations are initiated, plotted as a bar chart, so you can see which hours or days concentrate your team's activity.

    Paired with a usage summary: total generations, total words generated, and average output length for the range.
  </Accordion>
</AccordionGroup>

## How to Use It Well

<Steps>
  <Step title="Start with Recommended Actions">
    Treat the feed as triage, not the views. A critical or warning card tells you exactly what to look at before you go browsing charts manually.
  </Step>

  <Step title="Widen the range before concluding a trend">
    A single bad day reads very differently at 7d than at 90d. Confirm a reliability or quality dip holds up at a longer window before treating it as a pattern.
  </Step>

  <Step title="Use Reliability to isolate the template, not just the number">
    The per-template table turns "reliability is down" into "this specific template is failing," which is the difference between a real fix and a guess.
  </Step>

  <Step title="Cross-reference Content Quality with generation tier">
    Quick-tier runs skip editing by design and will pull the average down. A low composite score is only a problem if it's showing up in Standard or Premium output.
  </Step>
</Steps>

## When to Return to Analytics

* After the Dashboard's operational attention banner flags a reliability or publishing issue, to find the specific cause
* Before increasing generation volume, to confirm current reliability and quality can absorb it
* When deciding whether a workflow needs a higher generation tier
* When comparing templates before standardizing your team on one
* At the end of a billing cycle, to review the full period rather than the Dashboard's rolling 30-day summary

<CardGroup cols={2}>
  <Card title="Dashboard" icon="layout-dashboard" href="/product/dashboard">
    Return to the operational command center.
  </Card>

  <Card title="Generation Tiers" icon="layers" href="/getting-started/generation-tiers">
    See how Quick, Standard, and Premium affect the quality and reliability figures shown here.
  </Card>
</CardGroup>