Timelines, Scope & Boundary Decisions

If the "why" is the compass of an ESG reporting engagement, the boundary is the map. Get the boundary wrong, and you will spend the entire project fighting data inconsistencies, redoing sections, and explaining to stakeholders why the numbers do not match their other reports. This lesson covers the practical decisions around timelines, scope, and reporting boundaries: the structural choices that everything else builds on.

The Timeline: Ideal vs. Real

The ideal timeline for an ESG report is 2.5 to 3 months from kickoff to final delivery. That assumes the client has reasonable data readiness, a responsive team, and a clear sense of what they want.

In reality, it takes as long as it takes. The timeline stretches based on how quickly (or slowly) teams provide data, how many review rounds leadership demands, and whether the board approves the report without major changes.

The Ideal Reporting Timeline

Here is a realistic breakdown of where time actually goes:

Weeks 1-2: Kickoff and setup

Align on scope, boundary, standards, and timeline
Begin peer benchmarking
Share the data requirement template

Weeks 3-8: Data collection (the long middle)

This is where most of the calendar time is consumed
Templates go to departments, and then you wait
Parallel activities: writing the table of contents, preparing the blueprint, starting sections where you have enough information

Weeks 6-10: Writing

Writing overlaps with data collection: you start as soon as data begins arriving
You do not wait for all data before writing. If you do, you will never start.

Weeks 9-12: Reviews and revisions

The review cycle often takes as long as the writing itself
Multiple stakeholders review, provide feedback (sometimes conflicting), and the document goes through several iterations

Weeks 12-14: Design and final QA

Design work, final data verification, proofreading
GRI content index creation (always last)
Final sign-off

The delay is almost always on the client side. Data comes late, reviews take longer than planned, and approvals stall. If you have done your work competently and on schedule, and the report is still delayed, it is because the client's internal processes are slow. This is normal. The key is to have set a timeline from the start that accounts for this reality.

Deadlines Are Event-Driven

The deadline for an ESG report is almost never arbitrary. It is anchored to a specific corporate event, and understanding which event drives the timeline changes how you plan the engagement.

The annual report anchor. The sustainability report is published after the annual report, not before it. This is because the sustainability report often references financial data, governance structures, and strategic direction from the annual report. The annual report comes first, and the sustainability report follows, sometimes weeks later, sometimes a quarter later.

The BRSR exception. If the company is filing a BRSR (mandatory for top-listed Indian companies), the timeline is completely different. The BRSR is part of the annual report itself, which means it must be ready before the Annual General Meeting (AGM) where the annual report is presented to shareholders. This is a hard deadline with no flexibility. BRSR timelines are therefore tighter and more rigid than standalone sustainability report timelines.

The rating cycle anchor. For companies that participate in ESG ratings and indices (CDP, DJSI, MSCI, Sustainalytics), the sustainability report needs to be in the public domain before the rating cycle begins. Rating agencies score based on publicly available information. If your report is published after the rating submission window closes, it will not be considered until the next cycle, which means an entire year of improved performance goes unrecognized.

In practice, this creates a sequence: annual report first, then sustainability report, then rating submissions. The sustainability report sits in a window between the annual report publication and the start of the rating cycle. Miss that window, and you lose a year of ratings value.

The typical Indian timeline: A company with a March 31 financial year-end holds its AGM in August or September. The BRSR must be ready before the AGM. The standalone sustainability report is usually targeted for publication by September or October, ahead of the CDP questionnaire deadline (typically October-November) and the DJSI assessment cycle. Working backwards from these dates gives you the real deadline, not the aspirational one the client mentions in the kickoff call.

The Boundary Decision

The reporting boundary is the most consequential structural decision in an ESG report, and it needs to be made before you collect a single data point.

The boundary defines what entities are included in the report. At its simplest, the question is: does this report cover only the parent company (standalone), or does it include subsidiaries and joint ventures (consolidated)?

This sounds like a simple administrative choice. It is not. Whatever boundary you set in the "About the Report" section is the boundary you must follow for all data across the entire report. Every energy number, every diversity metric, every emissions figure, every financial disclosure must correspond to the same set of entities.

Think of the boundary like the frame of a photograph. Once you decide what is in the frame, everything (the composition, the focus, the lighting) must work within that frame. You cannot include a subsidiary's community programs in the Social section but exclude their emissions from the Environmental section. Either the subsidiary is in the photo or it is not.

Standalone vs. Consolidated: How to Decide

Choose standalone when:

Subsidiaries do not have organized sustainability data
The company is reporting for the first time and wants to keep scope manageable
Subsidiaries operate in very different industries or geographies and including them would complicate the narrative
The company's other reports (annual report, regulatory filings) also use a standalone boundary

Choose consolidated when:

Investors or rating agencies expect a group-level view
Regulatory requirements mandate consolidated reporting
The company has data collection processes across all entities
The annual report uses a consolidated boundary and you need consistency

The decision often comes down to data availability. If a subsidiary cannot provide reliable environmental or social data, including them in the boundary creates a problem: you either report incomplete data (which looks bad) or you make up numbers (which is worse). It is far better to exclude them upfront and note it transparently.

The boundary trap: A company decides to include three overseas subsidiaries in their consolidated boundary. When data collection begins, two of those subsidiaries have no system for tracking energy consumption or waste. The company now faces a choice: delay the report by months while subsidiaries set up data collection, report with massive data gaps, or quietly change the boundary mid-engagement and redo the sections that already referenced consolidated figures.

All three options are painful. The right move was to assess data readiness at each entity before setting the boundary. If the data does not exist, exclude the entity and state it clearly: "This report covers XYZ Ltd. on a standalone basis. Subsidiary data will be included in future reporting cycles as data systems are established."

The BRSR Alignment Trap

This is specific to Indian companies but critically important: if the company also files a BRSR (Business Responsibility and Sustainability Reporting) as part of its annual report, the boundary of the sustainability report and the BRSR must be reconciled.

If both documents use the same boundary, the data must match. You cannot report Scope 1 emissions as 50,000 tCO2e in the sustainability report and 48,000 tCO2e in the BRSR. Rating agencies, investors, and auditors will catch this, and it destroys credibility.

A lot of companies make this mistake. It happens because the sustainability report and the BRSR are often prepared by different teams, sometimes with different consultants, on different timelines. Nobody checks whether the numbers align until it is too late.

The fix is simple: decide on the boundary early, communicate it to everyone involved in both documents, and cross-check data between the two before publication. It sounds obvious, but it is one of the most common and serious errors in practice.

The Scope Conversation

Beyond the entity boundary, you also need to align on:

Reporting period. Most ESG reports cover a financial year (April to March in India, January to December in many global contexts). The period must be consistent across all data. You cannot mix calendar-year emissions with financial-year water data.

Geographic scope. If the company operates in multiple countries, are all geographies included? Or only domestic operations? This affects everything from diversity definitions to regulatory applicability.

Topic scope. Not every company needs to report on every ESG topic. A software company may have minimal environmental impact but significant governance and social topics. A manufacturing company is the opposite. The material topics (ideally informed by a materiality assessment) determine which sections get detailed treatment and which get a lighter touch.

Putting It All Together: The Scope Document

After the first conversation and the boundary decision, you should produce a short scope document (one or two pages) that captures:

Reporting boundary: which entities are included, which are excluded, and why
Reporting period: the exact dates
Standards referenced: GRI (always), plus any others (SASB, TCFD/ISSB, BRSR, etc.)
Material topics: the ESG topics that will receive detailed treatment
Timeline: key milestones with dates and responsible parties
Deliverables: what the client will receive (PDF report, designed version, microsite, executive summary, GRI content index, etc.)

Get this signed off by the project sponsor before proceeding. It becomes your reference document for the entire engagement. When scope creep happens (and it will), you point back to this document and say "this is what we agreed to."

The boundary, scope, and timeline decisions feel like administrative setup. They are not. They are the structural foundation of the entire report. Every data point you collect, every section you write, every number you publish must be consistent with these decisions. Getting them right at the start prevents the most painful and time-consuming problems later.

A Note on Scope Creep

Scope creep in ESG reporting is sneaky. It does not come as a single big change: it comes as a series of small additions. "Can we also include our CSR foundation?" "Can we add a section on our new green building?" "Our CEO wants a separate section on innovation."

Each request sounds reasonable in isolation. Together, they expand the report beyond what was planned, stretch the timeline, and create data collection requirements that nobody budgeted for.

The scope document is your defense. When a new request comes in, evaluate it against the agreed scope: does this require new data? Does it change the boundary? Does it affect the timeline? If yes, it is a scope change, and it needs to be discussed and agreed to formally, not absorbed quietly.

Sometimes a client will insist on a consolidated boundary that includes entities with no data readiness. They may want it for optics: a group-level report sounds more impressive than a standalone one.

In this situation, be direct about the tradeoffs. A consolidated report with data gaps looks worse than a clean standalone report. Suggest a phased approach: "Let us do a standalone report this year with excellent data quality. Next year, we expand the boundary to include subsidiaries that have had a year to build their data collection systems."

Most clients will accept this when you frame it as a quality decision rather than a scope limitation. Nobody wants to publish a report full of "data not available" entries.

The Takeaway

Before you write a word of the actual report, three things must be locked down: the boundary (who is in and who is out), the timeline (with realistic buffers), and the scope (what topics, what standards, what deliverables). These are not exciting decisions. They are the decisions that determine whether the next three to five months are manageable or chaotic.

Invest the time upfront. Your future self (buried in data collection and review cycles) will thank you.

Key Takeaways

1Lock down three things before writing begins: boundary (which entities are in or out), timeline (with realistic buffers), and scope (topics, standards, deliverables)
2The reporting boundary must be consistent across the entire report - you cannot include a subsidiary in one section and exclude it in another
3If both a BRSR and sustainability report use the same boundary, every data point must match across both documents - cross-check before publication
4Deadlines are event-driven: anchor your timeline to the annual report, AGM, or rating cycle submission windows, not the client's aspirational date
5Produce a signed-off scope document (boundary, period, standards, material topics, timeline, deliverables) and use it as your defense against scope creep
6Choose standalone over consolidated reporting when subsidiaries lack data readiness - a clean standalone report is far better than a consolidated report full of gaps

Timelines, Scope & Boundary Decisions