Annual Report Design Agency

What has changed in Indian annual reports

Since 2023, India's top 1,000 listed companies have been required to file a Business Responsibility and Sustainability Report. It is not a narrative exercise: 140 questions — 98 mandatory, 42 voluntary — across nine principles covering emissions, water, human rights, wages, anti-corruption, employee wellbeing, inclusive growth, consumer redress and policy engagement.

A thousand Indian companies now publish, annually, a document that is at once a legal disclosure and a piece of communication.

Very few are designed as one thing. The common structure is two documents stapled together — a designed front half with a chairman's portrait and adjectives, and a compliance back half in a different typeface, a different grid, and visibly a different budget.

Readers notice. Not consciously, but the shift from designed pages to undesigned ones reads as a shift from *what we want to tell you* to *what we are obliged to tell you.* On a sustainability disclosure, that is the wrong signal to send.

Sustainability and ESG report design

BRSR made ESG reporting mandatory, and for many companies the disclosure is now the most scrutinised part of the document — read by analysts, index providers, lenders and increasingly by customers.

Designing it well is mostly information design rather than graphic design. Nine principles, 140 data points, and a reader who needs to find one figure without reading the surrounding page. That requires a navigational structure, a consistent chart language and typography that holds at table sizes — not illustration.

For companies whose environmental performance is genuinely good, the disclosure is the strongest asset in the report. Burying it behind the financials is a design decision with a commercial cost.

Data visualisation and financial typography

The technical core of the work, and where most reports are lost.

One chart language across the whole document. One bar style, one line style, one axis treatment, one label position. Reports typically use whatever the finance team's spreadsheet produced for the tables and something bespoke for the narrative pages, and the inconsistency is the first thing a careful reader registers.

Typography that works at 6pt and 60pt. The same system has to hold inside a financial table and on a section divider. This is the single hardest constraint in report design, and it is solved by choosing one superfamily rather than by good layout.

Tabular figures, always. Financial columns set in proportional numerals do not align. A reader looking at wobbling decimals is being told something about the company's attention to detail.

One grid for editorial and financials. Two grids is why the halves of most reports do not agree.

Print and digital

The report is printed, and it is filed digitally on the exchanges.

Analysts open the PDF. They rarely receive the book. So we design the PDF as the primary artefact and the print run as the derivative — which is the reverse of standard practice and matches how the document is actually read.

In practice: tagged headings and real bookmarks, tables as selectable text rather than images, charts with alt descriptions, and a page format that reads on a laptop without zooming. Fold-out spreads look magnificent in the boardroom and are unusable on screen.

Timeline

Annual reports run against a fixed deadline — the AGM, and the filing date behind it. Everything works backward from there, and the constraint that bites is rarely design. It is the financial data arriving late and the auditor's sign-off arriving later.

A workable schedule locks structure and design system early, while the numbers are still moving, so that the final weeks are production rather than decisions. Reports that leave the design system unresolved until the data is final are the ones that end up as two documents stapled together.

Tell us your AGM date and we can tell you whether the schedule is realistic.

What determines the cost

Page count, which for a listed company is largely set by disclosure requirements rather than by choice.

Whether the BRSR section is designed or dropped in. The single largest variable, and the one most often decided by accident.

How much of the data visualisation is bespoke versus applying an established chart language.

Whether we manage print production or hand over files.

Whether the design system is being built this year or applied from last year's. Year one costs more than year two, and a system built properly makes every subsequent year cheaper — which is the argument for treating it as a system rather than a project.