From Policy to Procedure: How Governance Documents Cascade

Structural Analysis · No. 04

Institutions govern on paper before they govern in practice: a constitution or founding instrument states purpose and power; policies translate power into standing rules; procedures translate rules into executable steps. The cascade is healthy when each layer derives visibly from the one above, and unhealthy when practice quietly rewrites procedure without the change ever travelling back up.

This document is reference material for institutional and analytical understanding. It is not legal, financial, tax, or regulatory advice.

Scope and method

This analysis describes the document hierarchy at a framework level. Layers are compared on three dimensions: derivation (does the layer cite its source of authority), ownership (who maintains it), and cadence (how often it is reviewed).

The three layers of the cascade

The constitutional layer (charters, founding instruments) changes rarely and defines what the institution is and may do. The policy layer states standing positions: risk appetite, delegation thresholds, conduct standards. The procedural layer specifies who does what, in which order, with which records. Authority flows down; evidence of compliance flows up.

Where cascades break

Three break patterns recur. Orphan procedures exist with no parent policy: practice invented locally and never authorised. Dead policies exist with no implementing procedure: positions announced but not executable. Version drift occurs when a policy is amended and its dependent procedures are not, leaving the institution formally compliant with a rule that no longer exists.

Testing a cascade

The test is mechanical and revealing: sample a procedure and ask for its parent policy; sample a policy and ask for its constitutional basis; sample a real transaction and ask which procedure governed it. Every unanswered question is a finding, and the pattern of findings maps the institution's real, as opposed to nominal, governance.

How this connects to the wider framework

The cascade is the documentary expression of mandate architecture; its review cadence is set by the oversight stack; and testing it is step two of the entity mapping method.

Frequently Asked Questions

What is a governance document cascade?

The hierarchy in which founding instruments authorise policies and policies authorise procedures, so every operational step traces back to constitutional authority.

What is an orphan procedure?

An operating practice with no parent policy: locally invented, formally unauthorised, and invisible to oversight until something fails.

How often should the cascade be tested?

On a fixed cadence set by the oversight layer: commonly annual for policies and after every material change for dependent procedures.