Skip to main content
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.
Range
7, 30, or 90 days
Every metric, chart, and recommendation recalculates for the selected window.
Headline metrics
6 tracked figures
Reliability, quality, throughput, and publishing, at a glance.
Recommendations
Prioritized, not static
Derived from this period’s actual numbers, with a direct action for each.

​
Headline Metrics

A quieter secondary row sits below the headline strip with supporting context: average duration, total words generated, scoring coverage, and draft backlog.
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.

​
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.
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.
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.

​
Views

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
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.
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.
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.

​
How to Use It Well

1

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.
2

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.
3

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.
4

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.

​
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

Dashboard

Return to the operational command center.

Generation Tiers

See how Quick, Standard, and Premium affect the quality and reliability figures shown here.
Last modified on August 8, 2026