24.3 Designing a Report Layout
Module 23 covers design principles. A proven structure for our report:
| Page | Purpose | Main visuals |
|---|---|---|
| 1. Executive Overview | How are we doing? | KPI cards, Orders & Sales trend (festival spikes), Orders by City, Platform share |
| 2. Delivery Operations | Are we fast? | Avg Delivery Time by City/Store (red > 15 min), % Under 10 Mins, orders by hour, rider table |
| 3. Customers & Products | Who buys what? | Repeat Customer %, top products (dynamic Top N), category treemap, customer table |
| 4. Blinkit vs Amazon Now | How do platforms compare? | Clustered bars by city, AOV and delivery comparisons, field-parameter explorer |
| Hidden: Dark Store Details | Drill-through target | Store KPIs and order list |
| Hidden: TT City Snapshot | Report page tooltip | Mini cards and chart |
Ravindra Bagale's Tip
Mitrano, khup students cram eight to ten visuals onto the overview page. Keep the overview to KPIs plus two or three key visuals and move detail to other pages or drill through. A page that loads fast and reads in ten seconds is worth more than a crowded one. Dhyan rakho!