Translate an ESG request into a bounded work order and evidence inventory

An ESG specialist receives a message: “We need this year's ESG report.” It sounds like one task but hides several decisions. Why is the report being made, who will read it, which entities and sites does it cover, what is the reporting period, which framework has the authorized owner selected, and which data can the team actually substantiate? Collecting everything labelled environmental or social before answering those questions creates an impressive folder with incompatible boundaries. The first professional task is to turn the request into a bounded, testable work order and route decisions outside the specialist's authority to their owners.

A work order does not itself authorize publication or a claim of compliance with a standard. It names the purpose, audience, entity and time boundaries, deliverables, acceptance tests, decision owner, data owners, and permitted use of information. “Prepare an internal 2025 data draft for operating companies A and B, with source and exception logs” is different from “approve a public GRI-compliant report.” The specialist can assemble evidence and draft the former. The latter needs an authorized choice of reporting basis, a defined meaning of compliance, review requirements, and approval before the claim appears in public copy.

Fix the period first: calendar or fiscal year, with exact start and end dates. Next draw the entity boundary, listing subsidiaries, sites and excluded activities. The overall reporting boundary does not automatically describe every metric. Headcount might cover two companies while water data exist for one site. Give each metric its own coverage field instead of using a broad heading to conceal the difference. Do not silently choose a greenhouse-gas consolidation approach; an inventory will later require a documented organizational and operational boundary decision. At this stage the specialist exposes that decision and identifies who must make it.

Translate the deliverable into inspectable files. A useful internal draft needs a metric dictionary defining each quantity, unit and period; a source register connecting numbers to systems or files and owners; an exception sheet identifying missing, estimated or conflicting observations; and narrative copy that separates supported fact from interpretation. When a requester says “show our progress,” ask for the baseline, stable definition and comparison data. A desire to show progress is not evidence that progress occurred. A suitable acceptance rule is: “Every draft number can be recalculated from a retained source, with its coverage and exception visible, and every qualitative claim has a document and context.” That rule does not pretend that the data are complete. It makes incompleteness reviewable.

Use a three-column decision sheet: known, decision needed, evidence needed. For example, the management audience is known; the reporting framework and eventual public audience need decisions; electricity invoices and a site register are evidence needed for an energy total. This separates an obtainable missing input from a governance choice that the specialist cannot make. Set a date for resolving critical questions before broad collection. If the framework remains undecided, a neutral data register may proceed; a final compliance mapping built on an unapproved assumption should not.

Frameworks answer different questions. GRI 3 determines material topics through an organization's most significant impacts on the economy, environment and people, including human rights. IFRS S1 focuses on material information about sustainability-related risks and opportunities that could reasonably affect the entity's prospects and influence users of general purpose financial reports. The word “ESG” does not authorize the specialist to select one lens or merge them without a method. Record in the work order whether the requested product is impact assessment, sustainability-related financial disclosure, or another internal product, and who approved that choice. Neither framework becomes a universal legal mandate merely because it is mentioned here; the organization's elected basis and actual applicable requirements govern its use.