[E13] Tenant Reports & Insights

Summary

Cross-event aggregates, rollups and exports at tenant scope — the INSIGHTS group’s Reports row in the C01 sidebar.

ID allocated 2026-08-14; not yet designed. This page exists so the use-case ID is reserved and the Claude Design directory, this page and any ADO item share one key.

The design directory was previously E11-portfolio-reports, which collided with E11 Export Timing; its README carried an older E07 code internally. Renamed to E13 during the 2026-08-14 navigation-module refactor. "Portfolio" was dropped because rev 6 of C01 superseded that scope name.

Open scoping question — does this screen survive as its own use case?

Two readings, both defensible, unresolved:

  • It is the tenant anchor of the dual-use reports screen. Under C01 rev 6 dual-use, reports is declared once with levels: ['tenant', 'event', 'membership'] and rendered at each anchor. On that reading there is no separate screen here — the tenant-level view is reports at its tenant anchor, and this page should be folded into C01’s registry rather than specced alone. It also dissolves the "Reports collides with E01’s per-event Reports tab" worry the design placeholder agonised over: they are deliberately the same declaration.

  • It is genuinely distinct. The placeholder describes content that a wider filter on the per-event report does not produce: affiliating-body season rollups, cross-event unique-participant exports with deduplication, year-end financial rollups, a custom report builder, and a compliance dashboard tracking filed vs outstanding per regulator.

Decide before designing. If the second reading wins, the naming question returns — "Insights" was the placeholder’s own preferred label.

Actor & Context

Actor: tenant admin, finance, results officer.

Frequency: periodic — season end, quarter end, affiliating-body filing deadlines.

Entry point: Reports row in the tenant sidebar (C01 INSIGHTS group).

Intent (from the design placeholder)

  • Annual / quarterly summaries — total events, participants, revenue, with YoY and QoQ deltas.

  • Affiliating-body rollups — one filing per season covering every event, instead of one per event.

  • Financial rollups across events — organisation accounting and VAT, especially at year end.

  • Cross-event participant exports — unique-participant CSV, deduplicated across events the same person entered.

  • Custom report builder (further out) — metric, dimension, range, filter; saved templates.

  • Compliance dashboard — per affiliating body, what is filed vs outstanding across all events.

Distinct From

  • E01's per-event Reports tab — single event, deep.

  • E05 — curated "right now", no historical rollups or exports.

  • E12 — finds and slices; does not aggregate beyond per-row metrics.

Open Questions

  1. The scoping question in the IMPORTANT block above — separate screen, or the tenant anchor of reports?

  2. Where do scheduled / emailed reports configure — here, or T01?

  3. Cross-organisation rollups for super admins — here, or S01 only?

Design Anchors

  • C01 — INSIGHTS group, dual-use screens, capability gating

  • ADR-0008

Change History

Date Change

2026-08-14

ID allocated. Placeholder created so the shared use-case key holds. Content carried over from the design directory’s README; renamed from the colliding E11-portfolio-reports, dropping the superseded "portfolio" scope name. Recorded the unresolved question of whether this is a distinct screen or the tenant anchor of the dual-use reports declaration.