Reporting Cycles wireframes · 03 Wizard Basics

New reporting cycle

Follow the steps below to create a reporting cycle for Bluefin Foods Group. Creation produces a draft; activation is a separate action on the final step.

Basics

Framework and period

Scope

Organizations in scope

Methodology lock

GWP, approach, conventions

Review and activate

Verify and activate

Framework*

GRI-NG-2026

Validated against the framework registry and the tenant entitlement set. Legacy GRI generation codes are not offered for new cycles.

Annotation · not proposed UIGRI-NG-2026 is a stand-in. The real GRI new-generation registry code is spec ii's deliverable; until it exists, native cycles are created only in non-production environments against a test-registry entry (spec 6.3).

Annotation · not proposed UIPM ruling 2026-08-23: the engine is an internal attribute fixed by framework, never user-facing. GRI cycles run on the native engine only; existing frameworks stay on their current path; there is no user choice.

Start month*

January

Start year*

2029

Range 1980 to current year plus 10 (2036)

End month*

December

End year*

2029

12 months is the interface default and stays editable; any duration is legal subject to the start-year invariant (interface default, not a server rule). Month precision only; all month math is UTC.

Label preview · built from persisted fields only (spec 6.1)

2029 (Jan 2029 - Dec 2029) · GRI-NG-2026 [draft]

Framework code appended after a middle dot. The [draft] suffix drops on activation; [archived], [superseded], and [backfilled] append in that order when they apply.

Annotation · not proposed UIStep order drawn per spec: Basics, Scope, Methodology lock, Review and activate. The shipped Reporting Boundary wizard orders Year first (Year, Framework, Organizations, Review). The spec order stands as drawn per the PM's review completion, 2026-08-23.

Back disabled on the first step

Cancel Save as draft Continue to Scope

State gallery · Basics step · annotation · not proposed UI

The step repeated in its refusal and historical states. White cards are the proposed rendering; the amber frames are scaffolding.

409 CYCLE_OVERLAP

Framework*

BFG-Group

Start month*

April

Start year*

2025

End month*

March

End year*

2026

409 CYCLE_OVERLAP · these months overlap an existing draft or active cycle of the same framework: 2025 (Apr 2025 - Mar 2026) · BFG-Group [backfilled]

Overlap is checked per company and framework against draft and active cycles. Historical years get the same check, no relaxation.

409 CYCLE_STARTYEAR_TAKEN

Framework*

GRI-NG-2026

Start month*

January

Start year*

2026

End month*

June

End year*

2026

409 CYCLE_STARTYEAR_TAKEN · another draft or active GRI-NG-2026 cycle already starts in 2026: 2026 (Jan 2026 - Dec 2026) · GRI-NG-2026

Sub-year cycles sharing a start year are unsupported in I1, so a fiscal H1 plus H2 attempt is refused.

422 PERIOD_INVALID · the 1980 floor negative

Start month*

January

Start year*

1979

End month*

December

End year*

1979

422 PERIOD_INVALID · start year below the 1980 floor. 1980 is accepted; 1979 is rejected.

The same code fires for an incomplete period, a month outside 1 to 12, an end before the start, or a start year above current year plus 10.

Historical path · creating a 1998 cycle

Framework*

GRI-NG-2026

Start month*

January

End month*

December

End year*

1998

Past cycles are supported down to 1980 for historical onboarding. Historical cycles obey the same overlap, start-year, and org-scope checks as current years, and historical data entry and import run through the same mechanisms.

Label preview

1998 (Jan 1998 - Dec 1998) · GRI-NG-2026 [draft]

Annotation only, not UI: publication-date selection inheritance is spec ii; historical activity import is spec iv. No separate historical import screen exists here.

422 FRAMEWORK_UNKNOWN and 422 FRAMEWORK_NOT_ENTITLED

Framework*

QSR-2020

422 FRAMEWORK_UNKNOWN · code not in the framework registry

Framework*

TCFD-2021

422 FRAMEWORK_NOT_ENTITLED · code exists in the registry but is not entitled for this tenant

422 NATIVE_FRAMEWORK_INVALID

Framework*

BFG-Group

422 NATIVE_FRAMEWORK_INVALID · the native engine is legal only with the GRI new-generation framework code

The engine is fixed by framework server-side (PM ruling 2026-08-23), so no screen offers this combination; the refusal guards direct API writes. 409 CYCLE_BUSY can also fire on create when another create, activate, or identity-changing PATCH holds the per-company-per-framework critical section. It is retryable and never blocking; its retry affordance is drawn on the Review step page.