Short answer
The answer, before the reasoning
A credible first GRI output can be prepared in 90 days when scope is stable, source evidence is accessible, data owners respond and governance decisions are scheduled. The project can establish an impact inventory, approve material topics, prepare disclosures and a Content Index, and document gaps.
It cannot responsibly manufacture stakeholder evidence, close structural data problems, rush governance approval or promise assurance. The final reporting claim must match the requirements actually met.
LRA Knowledge Hub visual — branded for editorial and learning use.
Source-grounded educational draft. Final LRA technical sign-off is required before publication.
PUBLIC ARTICLE
In practice
FORMAT
| FORMAT | LANGUAGE | VERSION |
|---|---|---|
| Planning Guide | British English | 1.0 • 1 August 2026 |
Ninety days is a project constraint, not a reporting shortcut
A 90-day timetable can concentrate decisions and create a credible first reporting output. It cannot change the evidence needed to support those decisions. The accelerated project succeeds when the organisation already has accessible corporate records, knowledgeable data owners and a sponsor able to resolve scope and governance issues quickly. It fails when the deadline is used to replace impact evidence with a generic ESG topic list or to make an in-accordance claim before the applicable requirements have been met.
The right objective is therefore not ‘publish something labelled GRI in three months’. It is ‘produce the strongest technically defensible output possible within thirteen weeks, state its reporting route accurately, and leave a controlled remediation plan for the next cycle’.
Figure 1. The 13-week roadmap accelerates sequencing but preserves five release gates and separates a minimum credible output from work that must not be invented or compressed.
Quick orientation
- APPLIES TO First-time reporters, organisations restarting a stalled project, and
- PRIMARY DECISION What reporting route and output can be supported in 90 days, and which gaps require deferral, transparent limitation or a later cycle.
- KEY SOURCES GRI 1 for reporting route and requirements; GRI 2 and GRI 3 for the
- COMMON CONFUSION Assuming that a short report or a Content Index automatically means that the organisation has completed the GRI process.
Rule
NON-NEGOTIABLE CLAIM CONTROL
The publication claim follows the evidence—not the project ambition. Use an in-accordance statement only when every applicable requirement is met. Otherwise use a technically correct with-reference route or postpone the claim and publication.
In practice
When a 90-day project is realistic
| Enabling condition | Why it matters | Early evidence |
|---|---|---|
| Executive sponsor and empowered reporting owner | Scope, resources and disagreements can be resolved within days rather than weeks. | Named sponsor, project charter and decision calendar. |
| Stable reporting organisation and period | The team can define entities and reporting boundary without reopening the project repeatedly. | Legal entity list, financial reporting perimeter and approved sustainability boundary principles. |
| Existing policies, data and operational records | GRI disclosures can be supported from real source evidence rather than created retrospectively. | Prior report, HR/operations/environmental datasets, governance minutes, policies and complaint records. |
| Responsive cross-functional working group | Data owners can answer technical questions and approve wording quickly. | Confirmed roles, weekly meeting and escalation route. |
| Focused but credible impact assessment | The organisation can build from due diligence, incidents, stakeholder evidence and previous work while addressing known gaps. | Impact universe, existing risk/impact studies, complaints, audits, media/NGO evidence and stakeholder channels. |
| Disciplined publication scope | The team is willing to publish a proportionate first output and state gaps instead of filling every desired chapter. | Approved page architecture, material-topic scope and deferred-content list. |
| No dependency on immediate external assurance | The timetable is not contingent on procuring, scoping and completing assurance without readiness. | Separate assurance-readiness plan and accurate wording. |
Warning signs that the deadline is not credible
• The organisation cannot agree which legal entities and operations are covered.
• There is no senior sponsor or no one can approve material topics and the final claim.
• The project begins with graphic design or report structure rather than impact identification.
• The only materiality evidence is a generic stakeholder survey or a management preference matrix.
• Key data owners do not know the definitions, period or evidence expected.
• Large acquisitions, disposals, incidents or controversies have not been assessed.
• Human-rights and community impacts require specialist or confidential review that has not started.
• The project plan assumes that external assurance can be commissioned after drafting and completed immediately.
• Management insists on an in-accordance claim regardless of unresolved requirements.
In practice
Minimum credible output versus work that must wait
| Can be achieved in a controlled 90-day cycle | Must not be shortened into a false conclusion |
|---|---|
| Approved project scope, reporting organisation, reporting period and working governance. | Resolution of a disputed legal boundary or complex joint-venture control question without evidence and approval. |
| A documented impact inventory drawing on existing operational, due-diligence, stakeholder and external evidence. | A complete understanding of affected people and severe human-rights impacts where meaningful engagement or specialist review has not occurred. |
| A focused significance assessment, calibrated criteria and an approved list of material topics. | Mechanical scoring or management override designed to exclude difficult impacts. |
| GRI 2, GRI 3 and selected/applicable topic disclosures supported by available evidence. | Invented data, unsupported narrative, retrospective policies or ‘not applicable’ labels for processes that do not exist. |
| A requirement-level Content Index with precise references and transparent omissions or limitations under the applicable route. | A Content Index that implies complete disclosure when references are broad, inaccessible or partial. |
| Internal technical review, consistency checks, management sign-off and a next-cycle remediation plan. | External assurance, legal opinion or board approval without sufficient review time and evidence. |
| A clear decision between in accordance, with reference and deferred claim. | An in-accordance statement based on effort, intention or the presence of a GRI logo. |
In practice
The 13-week accelerated roadmap
| Week | Primary work | Key output — Decision owner |
|---|---|---|
| 1 | Mobilise: confirm sponsor, reporting owner, working group, timetable, version control and reporting-route decision criteria. | Project charter, RACI, source request and decision calendar. — Executive sponsor / reporting owner. |
| 2 | Lock initial scope: reporting organisation, period, entity/site population, acquisitions/disposals, applicable Sector Standards and known constraints. | Boundary memo, entity/site register and applicability log. — Reporting owner with finance/legal input. |
| 3 | Build impact universe from operations, value chain, due diligence, incidents, grievances, stakeholder evidence, external sources and prior assessments. | Impact inventory and evidence register. — Materiality lead and functional owners. |
| 4 | Assess actual/potential, positive/negative impacts; apply severity, likelihood and human-rights logic; record uncertainty. | Scored or tiered impact assessment with rationale and exceptions. — Materiality working group. |
| 5 | Calibrate criteria and threshold; challenge omissions; test Sector Standard likely material topics; identify evidence gaps. | Calibration record, decision log and provisional topics. — Technical lead / management sponsor. |
| 6 | Validate and approve material topics; define topic boundaries, owners, applicable Topic Standards and disclosure plan. | Approved GRI 3-2 list and disclosure applicability matrix. — Authorised management or governance body. |
| 7 | Prepare GRI 2 and GRI 3-1/3-2 disclosures; launch topic-specific data requests and GRI 3-3 drafting. | Universal Standards draft and controlled data-request tracker. — Reporting owner and data owners. |
| 8 | Prepare topic metrics, methodologies, limitations and evidence; identify required reasons for omission where permitted. | First topic disclosure pack and estimate/gap log. — Data owners and technical reviewers. |
| 9 | Complete GRI 3-3 for each material topic; reconcile policies, actions, effectiveness and stakeholder engagement with metrics. | Integrated topic packs and evidence map. — Topic owners / reporting team. |
| 10 | Assemble draft report and requirement-level Content Index; test references, accessibility and reporting claim. | Controlled draft and Content Index version 0.9. — Editor / reporting owner. |
| 11 | Technical red-team and consistency review across annual report, website, policies and public claims; resolve critical findings. | Findings log, corrected draft and go/no-go recommendation. — Independent technical reviewer. |
| 12 | Management and governance approval; finalise limitations, statement of use, publication note and remediation plan. | Approved final content and signed control pack. — Executive sponsor / governance body. |
| 13 | Lock version, publish or defer, notify relevant stakeholders, archive evidence and open next-cycle actions. | Published package or documented no-go decision; next-cycle roadmap. — Final approver / publisher. |
In practice
Five go/no-go gates
| Gate | Timing | Pass criteria — No-go action |
|---|---|---|
| G1 — Scope and route | End of Week 2 | Reporting organisation, period, applicable standards, preliminary route and approvers are defined. — Escalate unresolved scope; do not launch broad drafting or promise a claim. |
| G2 — Impact evidence | End of Week 5 | Impact universe covers operations and relevant business relationships; significance logic and major gaps are documented. — Extend evidence work, narrow publication ambition or defer materiality conclusion. |
| G3 — Material topics and owners | End of Week 6 | Final topics, rationale, approval, topic owners and disclosure applicability are recorded. — Do not present a provisional management list as approved material topics. |
| G4 — Disclosure traceability | End of Week 11 | Critical disclosures, calculations, limitations and Content Index references can be traced to evidence; no unresolved blocker. — Revise route, remove unsupported claim, disclose permitted omission or delay publication. |
| G5 — Governance and release | End of Week 12 | Approvals, statement of use, final version, legal/confidentiality review and publication controls are complete. — Do not publish until accountable approval and version control are complete. |
In practice
How to choose the reporting route at the end of the project
| Route | Use when | Minimum publication discipline — Red flag |
|---|---|---|
| Report in accordance with the GRI Standards | All applicable GRI 1 requirements are met, including required Universal, Sector and relevant Topic Standard treatment, Content Index and statement of use. | Requirement-level completion test, permitted omissions only where conditions are met, accurate statement of use and final approval. — Management equates substantial completion with full in-accordance eligibility. |
| Report with reference to the GRI Standards | The organisation uses selected Standards or disclosures for a clearly defined purpose but cannot or does not seek to meet all in-accordance requirements. | State precisely which GRI Standards/disclosures are used, prepare the applicable Content Index information and avoid broader compliance language. — The report is marketed as a full GRI report despite a limited selection. |
| Defer the public GRI claim | Materiality, boundary, evidence or governance gaps are so significant that either route would mislead readers. | Publish a non-GRI sustainability update if appropriate, or delay; retain the internal gap and remediation plan. — Deadline pressure is treated as a reason to invent evidence or obscure uncertainty. |
Rule
DECISION RULE
An accelerated project is successful even when the correct output is ‘not ready to claim in accordance’. The value lies in making the gaps visible, controlled and funded rather than hiding them in an overstated report.
Meaningful stakeholder and affected-person evidence
Existing engagement records can be reused when relevant and reliable. A rushed online survey cannot substitute for understanding affected workers, communities, vulnerable groups or rights-holders where severe impacts are plausible. Where direct engagement is not possible within the timetable, record the limitation, use available evidence carefully and create a specific next-step plan.
Human-rights severity and remedy decisions
Potential human-rights impacts require severity-led judgement and may involve confidentiality, ongoing investigations and affected-person safety. These decisions should not be delegated to a scoring spreadsheet or compressed to meet a publication date. Specialist and legal input may be needed.
Structural data remediation
A calculation can be estimated transparently; a broken system cannot be repaired by rewriting the narrative. Missing site meters, inconsistent HR populations, unavailable supplier locations or unapproved methodologies need remediation plans with owners and dates. The report should distinguish measured, estimated and unavailable information.
Governance approval
Management and the highest governance body need sufficient information and time to understand the material topics, significant judgements, gaps and reporting claim. Approval is not a signature collected after the file is designed.
External assurance
Assurance requires criteria, scope, provider procurement, evidence readiness, walkthroughs, testing, findings and management response. A 90-day reporting project can include assurance-readiness review, but assurance itself should only be promised when the provider and timetable are realistic. GRI does not automatically require independent assurance.
Hypothetical example — a service group with partial data
The group can plausibly complete a focused impact assessment, approve material topics, prepare GRI 2 and GRI 3 disclosures and report selected topic information within 90 days. It should not claim a complete supply-chain assessment if only high-level procurement screening is available. If all in-accordance requirements are not met, the publication can accurately use selected disclosures with reference to GRI and include a 12-month plan for supplier evidence, topic metrics and assurance readiness.
Hypothetical scenario
ILLUSTRATIVE SCENARIO
A professional-services group has a prior sustainability update, reliable HR and office-energy data, established grievance channels and a stable legal perimeter. It has limited supply-chain impact evidence and no formal GRI materiality methodology. The Board has a scheduled meeting in Week 12.
Illustrative only. It shows how the decision is made, not wording that can be copied or relied on.
In practice
| Weak project conclusion | Stronger project conclusion |
|---|---|
| “We completed a comprehensive GRI-compliant report in twelve weeks.” | “During the 13-week first cycle, we established the reporting boundary, assessed impacts using operational, workforce, grievance, stakeholder and external evidence, and approved five material topics. The publication uses specified GRI 2, GRI 3 and Topic Standard disclosures with reference to the GRI Standards. Supply-chain impact evidence is currently limited to priority procurement categories and country-level screening; supplier-level assessment and additional metrics are scheduled for the next cycle. The report has not been independently assured.” |
Common mistakes
• Designing the report before the reporting route, impact process and material topics are agreed.
• Using a previous ESG topic list without testing current impacts and significant changes.
• Running one management workshop and labelling the outcome a stakeholder-informed materiality assessment.
• Requesting every possible metric before selecting material topics and applicable disclosures.
• Leaving GRI 3-3 until the end and producing generic policy narratives unrelated to each impact.
• Building the Content Index after publication and discovering that references are incomplete.
• Treating missing evidence as ‘not applicable’ or using one generic reason for omission.
• Seeking Board approval on a near-final design without a technical findings and gap summary.
• Promising external assurance in the report when only internal management validation occurred.
Rule
MYTH VERSUS REALITY
Myth: A first GRI report must either be perfect or should not be published. Reality: a proportionate first output can be useful when the reporting route is accurate, material judgements are documented, disclosures are traceable and limitations are specific. What is unacceptable is using the learning curve as a reason for a misleading claim.
Readiness
Final 90-day readiness checklist
- • ☐ Executive sponsor, reporting owner, working group and final approver are named.
- • ☐ Reporting organisation, period, entities, sites and major boundary differences are approved.
- • ☐ Applicable Sector Standards and current Topic Standard editions have been checked.
- • ☐ Impact inventory covers actual/potential and positive/negative impacts across activities and relevant business relationships.
- • ☐ Stakeholder, due-diligence, incident, grievance and external evidence are retained and limitations are explicit.
- • ☐ Significance criteria, threshold or prioritisation logic and human-rights treatment are documented.
- • ☐ Material topics and changes from the prior period are formally approved.
- • ☐ GRI 3-3 and relevant Topic Standard information are traceable to evidence and owners.
- • ☐ GRI 2 disclosures and Content Index references are reviewed at requirement level.
- • ☐ Estimates, reasons for omission, confidentiality and unavailable information have approved wording.
- • ☐ Technical findings and cross-publication contradictions are resolved.
- • ☐ The statement of use matches the requirements actually met.
- • ☐ Governance approval, version lock, publication files and evidence archive are complete.
- • ☐ Next-cycle actions have owner, budget or resource path and deadline.
Bottom line
The fastest credible GRI project is not the one that writes most quickly. It is the one that makes scope decisions early, uses existing evidence intelligently, brings the right owners into the room, refuses unsupported claims and passes explicit release gates. Ninety days can establish a strong first cycle and a sustainable reporting system—provided the deadline remains subordinate to evidence and governance.
Official source anchors
The source set below should be rechecked as part of the pre-publication update control. Normative conclusions in this article are based on the current official editions listed here.
1. GRI 1: Foundation 2021. Official requirements for reporting in accordance or with reference, reporting principles, Content Index and statement of use. Open official source
2. GRI 2: General Disclosures 2021. Official disclosures about the reporting organisation, reporting practices, workers, governance, policies and stakeholder engagement. Open official source
3. GRI 3: Material Topics 2021. Official process and disclosures for determining, listing and managing material topics. Open official source
4. GRI Standards — English language. Official access point for current Universal, Sector and Topic Standards, effective dates and editions. Open official source
Take it with you
The checklists as a working spreadsheet
Every checklist and table on this page, with empty status, owner and evidence columns for your team to fill in and keep.
✓ Knowledge Hub AI Assistant · Human-in-the-loop
Ask about this guide
It answers from this page, and reaches into the linked disclosure cards when your question is about the standard itself. Your first two answers are free without signing in.
Go deeper · GRI
Certified GRI Standards Training
This page settles one disclosure. The GRI Standards Certified Training — two live days, taken as a bundle with an ESRS course — walks the whole cycle: material topics, datapoints, evidence, the Content Index and assurance readiness, with exercises on your own data.
Available as two live training days online or on-site in London, bundled with an ESRS course.
