Stephen Green & Associates · ACS 6

Automated Reports preview

Four of the report templates from ACS 6, rendered against illustrative mock data. The HTML and calculations are exactly what the production app produces from real SwiftTrack data.

Phase 3.1

Workflow report

One row per (appointment × RPA) pair, joined to client and appointment type. The view Dayna gets each Monday morning.

View →

Phase 3.2

KPI — Weekly RPA Time & Motion

Per-RPA appointment counts bucketed into Office, Visit, Training, Holiday, Sick, Hotel and Other for the current ISO week.

View →

Phase 3.3

Ops flash report

Operational health snapshot for the current ISO week: weekly totals, per-day rollup, and data-quality flags (unassigned RPA, missing postcode).

View →

Phase 3.4

Raw CSV export

Flat dump of appointments matching Dayna's existing workflow-raw.csv shape. HTML preview + downloadable CSV.

View →

What is and isn’t real on these pages

Real: the Jinja2 templates (app/templates/reports/*.html), the column headings, the rendering pipeline, the styling.
Real: the aggregation logic on KPI — bucket boundaries follow the production rule that appointment_types.visit_schedule = 0 fences off-time (Holiday / Sick / Hotel) from on-time (Office / Visit / Training).
Real: the multi-RPA fan-out on the Workflow report — some appointments are attributed to 2 or 3 RPAs, exactly as appointment_rel emits in production.
Mock: client names, RPA names, towns, account numbers, dates, notes. All deterministic from a fixed seed; no resemblance to real SGA contacts is intended or implied.