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 |
About this data: This table uses columns: Page, Purpose, Main visuals. This table uses columns: Wrong result, Reason, Correction. Values shown are the lesson examples already on this page (not a new dataset).
Read this table as Monday jobs, not as a menu of charts you must all build before lunch. Page 1 answers "are the cities inside the promise, or is volume trying to look like success?". It does not answer "which store". If it tries, it becomes the cluttered page from Module 23. Page 2 is where Ravindra and Shraddha earn their morning: Kothrud at 50% (3 of 6) and Gangapur at 66.7% (4 of 6), against stores that have fewer orders and a cleaner week. Page 3 changes a repeat offer or a product, not a rider. Page 4 changes which platform is late in which city, which is a different meeting from the Monday store call. The hidden pages are how you keep order lists off the front. None of that appears because you renamed a report to "dashboard".
Ravindra Bagale's Tip
Friends, many students cram eight to ten visuals onto the overview page. Keep the overview to KPIs plus two or three key visuals, and move the detail to other pages or drill through. A page that loads fast and reads in ten seconds is worth more than a crowded one. Keep this in mind!
Ravindra Bagale's Tip – मराठी
मित्रांनो, बरेच students overview page वर आठ-दहा visuals कोंबतात. Overview मध्ये KPIs आणि दोन-तीन मुख्य visuals एवढंच ठेवा, आणि तपशील इतर pages वर किंवा drill through मध्ये न्या. पटकन load होणारं आणि दहा सेकंदात वाचता येणारं page गर्दीच्या page पेक्षा जास्त मोलाचं आहे. लक्षात ठेवा!
Ravindra Bagale's Tip – हिंदी
दोस्तों, बहुत से students overview page पर आठ-दस visuals ठूँस देते हैं. Overview में KPIs और दो-तीन मुख्य visuals ही रखो, और details को दूसरे pages या drill through में ले जाओ. जल्दी load होने वाला और दस सेकंड में पढ़ा जाने वाला page भीड़ वाले page से ज़्यादा कीमती है. ध्यान रखना!
Fix common mistakes
| Wrong result | Reason | Correction |
|---|---|---|
| 10 visuals on overview | Crowded | KPIs + 2–3 visuals; detail on other pages |
| Navigation inconsistent | Buttons placed differently | Copy a template page |
Practise independently
Practice task
Plan 3 pages for the sample data: Overview, Delivery, Stores.
Practice file (fictional): visuals_orders_apr_may_2026.csv
Hints
- One question per page.
Solution
Overview: Sales ₹2,100, Orders 8, AOV ₹300; Delivery: avg 11.0 min, 42.9% under 10; Stores: Kothrud ₹650 top.
Revision card