IBQMI

Reasons on Record

graph

Every material determination is docketed with a reason bundle and provenance references; minority positions are preserved where applicable; high-impact determinations enter fixed review windows such as 30 and 90 days; appeal is procedural and time-bounded.

Node reasons_on_record · type record_duty · cluster Doctrine · updated 2026-09-02 · JSON-LD · Markdown

Canonical definition

Reasons on record is the duty that every material determination is docketed with a reason bundle and provenance references, that minority positions are preserved where applicable, that high-impact determinations enter fixed review windows, and that appeal exists as a procedural path.

Why this node exists

"Procedure, not assertion, creates legitimacy" is only true if the procedure leaves a trail. This node names the trail.

Operational meaning

Review windows for high-impact matters default to fixed cadences such as 30 and 90 days and must be docketed; accelerated schedules are docketed too. Appeal challenges compliance with the Statute — thresholds, record duties, review triggers, independence safeguards, publication boundaries — with defined standing, time-bounded windows and remedy pathways. Reviews are triggered by threshold class, allegations of procedural defect, material new evidence or scheduled cadence.

What this does not mean

Substantive disagreement alone is not a ground of appeal absent a procedural defect. Reasons on record do not require publication of sensitive plaintext; the publication boundary applies.

Canonical facts

Reason bundle for every determination; dissent preserved with proportional weight (Statute §5.4)
Fixed review windows for high-impact matters (Statute §5.5); e.g. 30/90 days (Board Statute page)
Procedural appeal
defined standing, timelines, remedy pathways (Statute §5.6, §7.2)
Review triggers
threshold class, alleged defect, new evidence, cadence (Statute §7.1)

Structural relationships

Outgoing

Incoming

Sources

Knowledge hub Machine Contact