New reporting cycle
Bluefin Foods Group · last step. Check the cycle, check the edition set it will be built from, then activate. Saving the draft and activating are separate actions.
1
Basics
Framework and period
2
Scope
Organizations in scope
3
Methodology lock
GWP, approach, conventions
4
Review and activate
Verify and activate
CycleFY2026 GRI reportlabel: FY2026 (Jul 2025 - Jun 2026) · GRI (native) [draft]
FrameworkGRI (native)
Reporting periodJul 2025 to Jun 2026
Intended publication date30 Nov 2026the date you will publish this report; it decides the edition set below
Organizations in scopeAll organizations14 sites across Singapore, Thailand, and Malaysia
Methodology lockRecorded, provisionalAR6 · operational control · GCV
Statusdraft
Prepared byMei TanSustainability Admin
Edition set
The standard editions this report will be built from, worked out from 30 Nov 2026
resolved
5editions
53disclosures
214clauses to answer
0disclosures excluded
| Edition | Covers | In force for publications | Disclosures | Clauses | Excluded here |
|---|---|---|---|---|---|
| GRI 2 2021 edition | Organization and reporting practices | From 1 Jan 2023 onward. No newer edition is scheduled. | 30 | 118 | None |
| GRI 3 2021 edition | Selecting and managing the topics that matter | From 1 Jan 2023 onward. No newer edition is scheduled. | 3 | 9 | None |
| GRI 302 2016 edition | Energy use and energy intensity | From 1 Jul 2018 onward. A newer edition is required for reports published on or after 1 Jan 2027. | 5 | 21 | None |
| GRI 305 2016 edition | Greenhouse gas emissions and other air releases | From 1 Jul 2018 onward. A newer edition replaces most of this one for reports published on or after 1 Jan 2027; two of its disclosures carry on after that date. | 7 | 34 | Nonefrom 1 Jan 2027: 305-1 to 305-5 |
| GRI 101 2024 editionadded by this date | Biodiversity impacts and dependencies | From 1 Jan 2026 onward. Included because 30 Nov 2026 falls on or after that date. | 8 | 32 | None |
This edition set is fixed by your intended publication date, and it locks when the cycle is activated. After activation it does not change.
Locking is what keeps the report consistent. Every answer your team enters is written against the same editions from the first entry to the final export, the way a published report names the editions it was prepared under. Editions published after you activate cannot move the ground under a report that is already in progress.
While the cycle is still a draft nothing is committed. Change the intended publication date and the edition set is simply worked out again from the new date.
If the date turns out to be wrong after the cycle is active, you archive that cycle and create a new one for the date you will really publish on. Nothing your team has entered is silently rewritten.
Why does the edition set lock?
guidance layer (placeholder)
Want to use a newer edition before the date it becomes required? That is a separate, recorded decision: Adopt a newer edition early. Draft cycles only.
Annotation · not proposed UISpec ii 6.1, binding at activation. While the cycle is a draft this edition set is computed on demand for the preview and is NOT stored. At activation, inside the cycle critical section, the edition set is resolved once more, the content hash of every member edition is verified, and the resolved edition set plus the entitlement state at that moment persist onto the cycle atomically with the status change. From then on every native surface reads the frozen edition set. Internal names for the reviewer: the resolved edition set is an
assembly, the cycle field is catalogAssemblyId, and the identity string is assemblyKey. None of those words appear on a screen.The lock wording, rewritten · the PM's part 1 review, ruling R2-2What changed and why. The earlier lockline ended on "never changes afterwards", which the PM read as a commitment an admin may not be ready to take and which would send them to support before they activate anything. The wording now carries the same behavior with the reason attached: the edition set is fixed by the intended publication date, it locks at activation, and locking is what lets every answer be written against one set of editions from first entry to export. Nothing was softened. The draft-stage escape ("change the date and the edition set is worked out again") and the post-activation recourse ("archive the cycle and create a new one; nothing entered is rewritten") were both already true in spec ii 6.1 and are now on the screen instead of only in the spec. The "Why does the edition set lock?" link is a PLACEHOLDER, not a drawn feature. It marks the point where the guidance layer lands: the PM decided on 2026-08-24 that runtime AI plus deterministic guidance ships in I1, so this is the first anchor for it in this wireframe set. What the link opens, how the guidance is composed, and how AI-written text is labeled are the guidance workstream's to settle, not this drawing's.
Back
Cancel
Save as draft
Activate cycle
State gallery · the same edition set card after activation · not proposed UI
The white card inside the amber frame is the proposed rendering on the cycle detail Overview tab once a cycle is active. Same card, no longer a preview. The cycle shown is the workspace's other cycle, FY2025 GRI report, which is already active; the draft above has not been activated.
Active cycle FY2025 GRI report · edition set locked and read-only
Edition set
FY2025 GRI report · Jan 2025 to Dec 2025 · fixed when this cycle was activated. It cannot change.
locked
5editions
53disclosures
214clauses to answer
0disclosures excluded
Editions in this reportGRI 2 2021 editionGRI 3 2021 edition · GRI 302 2016 edition · GRI 305 2016 edition · GRI 101 2024 edition
Disclosures excludedNone
Fixed byPublication date 30 Jun 2026no early adoption was chosen for this cycle
Locked on12 May 2026, 09:18 UTCwhen the cycle was activated, by Mei Tan
Methodology lockProvisionalthe only lock state I1 can reach; an active cycle with a provisional lock is fully bound to this edition set
This report is built from the editions in this edition set and nothing else, which is what keeps it consistent from the first entry to the final export. Newer editions of these standards can be published tomorrow without changing any answer already entered against this cycle. To report under a different edition set you would archive this cycle and create a new one, and nothing entered here is rewritten.
Read-only: no publication-date field, no early-adoption link, no action of any kind on this edition set card. The counts stay so an admin can see the size of the cycle without leaving the tab. Spec ii 6.1: activation persisted this edition set onto the cycle, and lock completion later freezes what activation bound rather than resolving it again.
Annotations for this page · not proposed UI
Each block names the spec section behind a drawn behavior. Counts, sites, and dates on the screen above are invented.
Why GRI 101 is in the edition set · spec ii 3.2 and 7.1The framework registry holds the authored set as data: standards 2, 3, 302, and 305 always take part, and 101 takes part only when the publication date falls on or after 1 Jan 2026. That is a data rule on the registry row, not prose in a document. This cycle publishes on 30 Nov 2026, so 101 joins. A cycle publishing on 20 Dec 2025 would not show 101 at all, and that is not an error state: the edition set would simply have four editions. Ruling D-ii-6 of 2026-08-24 settled the content side:
gri-101-2024 is authored in I1 and I1 supports truthful publication dates from 1 Jan 2026 onward, so the conditional rule fires in practice rather than in theory. If 101 were required by the date but not published in the catalog, this screen would refuse instead, which is state 1 on the next page of this wireframe set.The Excluded column · spec ii 3.6 and 3.3A newer edition sometimes replaces only part of an older one. When that happens the older edition stays in the edition set for the disclosures the newer one does not cover, and its replaced disclosure codes are excluded per edition. The Excluded column is where that is shown, listing the excluded codes on the row of the edition they belong to. For 30 Nov 2026 no newer edition takes part, so nothing is excluded and every row reads None. The known case in the schedule is GRI 305: from 1 Jan 2027 its successor replaces 305-1 to 305-5 while 305-6 and 305-7 carry on, so a 2027 set holds both editions with those five codes excluded. The hint under the 305 row states that forward fact; say the word if you would rather that hint were not on the screen.
Counts, and what they are for · spec ii 3.6Editions, disclosures, and clauses to answer are the three numbers that tell an admin how much work the cycle is about to create, and they are the numbers that change when the publication date or an early-adoption choice changes. The fourth count, disclosures excluded, is drawn deliberately at zero: it earns its place because when it is not zero the admin needs to see it without opening a row. Alternative if you find four counts noisy: drop the excluded count from the count strip and rely on the Excluded column. The clause count is what the entry screens are built from, so it is the one a data collector feels.
Vocabulary and framework naming · proposal, PM can veto"Edition set" and "edition" are proposed user-facing words for what the spec calls an assembly and a standard version; the reasoning and the veto are on the wireframe set index. The Framework row reads "GRI (native)", the framework's display name, which is the only place any framework wording appears on a screen. The internal registry code stays out of the interface entirely, including out of error messages: a workspace with no GRI access is told the framework is unknown, byte-identical to naming a code that does not exist (spec ii 3.7 masking). The readable cycle names in this wireframe set ("FY2026 GRI report" for the draft above, "FY2025 GRI report" for the active cycle in the gallery) are a drawing convention; the real label built from persisted fields sits under it.
The two cycles used across this wireframe set · invented dataThe workspace holds one ACTIVE cycle and one DRAFT, and every page of this wireframe set uses one of them. Active: FY2025 GRI report, period Jan 2025 to Dec 2025, intended publication date 30 Jun 2026, activated 12 May 2026 by Mei Tan, methodology lock provisional. Pages 5 to 12 of this wireframe set all show that cycle. Draft: FY2026 GRI report, period Jul 2025 to Jun 2026, intended publication date 30 Nov 2026. Pages 2, 3, and 4 show that draft, because preview, refusal, and early adoption are draft-only states. The access grant that lets either exist is dated 12 Mar 2026 on the access card, before both activations, which is the order spec ii 6.1 requires: a cycle cannot bind before the grant it is checked against.