Objective
- Surface average fee as a first-class metric on the Client Care dashboard (Attik Admin) so users do not derive it manually from revenue and job counts.
Background
- Dashboard review: revenue and confirmed jobs exist, but average fee is still missing despite being a core KPI.
- The codebase already models
averageFeein shared dashboard types (attik-frontend/src/components/dashboard/dashboardTypes.ts) and displays it in components likeInspectionVolumeFee.tsx; the gap is exposing it in the client-care dashboard grid (KPIStatsGrid/ related view wiring).
Scope
Frontend
attik-frontend/src/app/admin/client-care-dashboard/includingCCDashboardClient.tsxand_components/KPIStatsGrid.tsx, plus any data-fetch layer that populatesKpiMetricsin_types.- Reuse patterns from
src/components/dashboard/InspectionVolumeFee/InspectionVolumeFee.tsxwhereaverageFeeis already formatted.
Backend
- Ensure aggregations feeding the client-care dashboard API include average fee consistently with other metrics (Decision needed on exact endpoint—trace from admin client-care server actions or routes).
References
attik-frontend/src/app/admin/client-care-dashboard/_components/KPIStatsGrid.tsxattik-frontend/src/components/dashboard/InspectionVolumeFee/InspectionVolumeFee.tsxattik-frontend/src/components/dashboard/dashboardTypes.ts
Original description
Average fee should be available as a first-class dashboard metric instead of requiring users to derive it manually.
Transcript Context
During dashboard review, the team called out that average fee is missing even though it is considered one of the more important metrics. They noted that revenue and confirmed jobs are visible, but calculating average fee manually is not enough for everyday use. The request was to surface average fee directly in the dashboard, potentially in a prominent position near other core scheduler metrics.
