Advanced analytics
Advanced analytics answers the question the dashboard can't: is the project getting better or worse? The dashboard is a snapshot; this is the trend.
Advanced analytics depends on your plan. Where it isn't included you'll see the Advanced analytics notice instead of the charts. See Features gated by plan.
Choosing a period
Pick This week, This month, Quarter, Year, or Custom with a From and To date, then Apply. Figures are shown compared to the previous equivalent period, and the granularity adjusts between day, week and month to suit the range.
Evolution over time
Three tiles carry the headline:
| Tile | What it means |
|---|---|
| Issues created | Raised over the period |
| Issues resolved | Closed + validated over the period |
| Net flow | Created − resolved |
Net flow is the number to watch. It reads either backlog growing or backlog shrinking.
- Positive net flow — you're raising issues faster than the site is closing them. Early in a project this is normal. Close to reception it is not.
- Negative net flow — the backlog is coming down.
Pace & backlog evolution
The chart plots created and resolved against the Cumulative backlog. The vertical axis is the number of issues.
The shape tells you more than the totals. A cumulative line that flattens means the site has reached equilibrium; one that turns downward means it's catching up.
Resolution figures
- Resolution rate — the share being closed, annotated when it's only a partial catch-up.
- Average resolution time — measured detection → closure, in days.
Average resolution time is the figure to quote to a contractor. It's not how many defects they have, it's how long they take.
Breakdown by period
The Breakdown by period table gives the numbers behind the chart:
| Column | Meaning |
|---|---|
| Period | The day, week or month |
| Net | Created − resolved |
| Cumul. | Running backlog total |
As the table footnote puts it: Net = created − resolved. A decreasing cumulative = backlog catch-up.
Reading it before reception
Two months out from reception, the pattern you want is: created flattening, resolved holding steady, cumulative falling, average resolution time stable or improving.
If created is still climbing at that point, the OPR is finding more than the site is fixing — which is a scheduling problem, not a quality one.