What it measures
A figure that cannot be computed, such as reliability before any workflow has finished, is reported as unavailable rather than as zero.
Issues and next steps
Analytics evaluates these conditions for the range and reports each one that applies, most severe first.
When none of these applies, the period is reported as on track. The reliability measure and the issue list use the same thresholds, so they never disagree.
Detailed views
Using Analytics
1
Start with the issues
Work the critical and warning issues first. Each names the condition that fired and where to act on it.
2
Confirm a trend before acting on it
A dip in a 7-day range can be a single bad day. Widen to 30 or 90 days before you change templates or tiers.
3
Isolate the cause by template
Use the Reliability view to turn “reliability is down” into “this template is failing”, then inspect that template’s failed runs.
4
Read quality by tier
Quick runs skip the editing stage by design and lower the average. Judge a low score against Standard and Premium output.
Limits
- Analytics reports aggregates. It does not show why an individual run failed; the run’s status and dossier do.
- Reliability counts only finished work. A backlog of stalled runs does not lower it; check drafts and in-progress runs separately.
- Thresholds are fixed product targets, not configurable service levels.
Dashboard
Assurance posture: verification coverage, reviews, and publication validity.
Generation Tiers
How Quick, Standard, and Premium affect the figures reported here.