Delegation Rulebook¶
Document — instantiates Decision Load Management
A document specifying which decisions are delegated to which roles under which constraints.
A Delegation Rulebook is a standing document that grants decision authority to roles: for each class of decision, it names the role that may decide it, the limits within which they may decide, and the point at which the decision must instead escalate. Its defining move is the durable grant of authority by domain — it moves the right to decide down to the role best placed to hold it, permanently and in writing, so that a whole category of choices stops flowing back to a central decider. It is not a per-magnitude schedule of who must sign, and it is not a live intake router; it is the codified answer to "who owns this class of decision, and how far does their power run?" Crucially, the archetype insists that delegation only relieves load when the delegated role has the authority, information, and support to actually decide — otherwise the rulebook merely displaces burden without power.
Example¶
A retail chain's regional managers escalated nearly everything to head office — a markdown on slow-moving stock, a $300 goodwill refund to an angry customer, a local supplier swap — because no one had ever written down what a store manager was actually allowed to decide alone. Head office was a bottleneck; stores felt powerless. The operations director writes a Delegation Rulebook. Store managers may authorize markdowns up to a set depth on their own inventory, issue goodwill refunds within a per-incident limit, and adjust staff schedules without approval. They may not sign new supplier contracts, alter pricing on core lines, or change store hours — those remain head-office decisions. Anything unusual — a supplier dispute, a legal threat, a safety incident — escalates immediately regardless of size.
The rulebook is a shared document each manager can point to. Its effect is that a category of decisions now dies at the store level instead of round-tripping to head office, but only because the grant came with the spending latitude and information to make those calls stick. This is the principle of subsidiarity[n1] — decisions handled at the lowest capable level — written into operating policy.
How it works¶
A rulebook is assembled decision-class by decision-class. For each class it fixes three things: the owning role (who holds the authority), the constraints (the limits, budgets, or conditions inside which that role may decide freely), and the escalation trigger (the conditions — novelty, risk, dispute, threshold breach — that pull the decision out of the delegated lane and up to a higher authority). The load relief comes from durability: unlike a routing queue that re-decides each item's destination, the rulebook settles ownership once, so a whole class of recurring decisions simply stops arriving at the center. The discipline that makes it real rather than nominal is pairing every grant with the resources to exercise it — spending latitude, data access, and backing — so delegated authority is genuine, not a title without power.
Tuning parameters¶
- Delegation distance — how far authority moves from the original decider. Greater distance relieves the center more but demands more trust, clearer constraints, and better information at the edge.
- Constraint tightness — how narrow the limits on delegated authority are. Tight limits reduce risk but funnel more decisions back up as exceptions; loose limits relieve more load but widen the blast radius of a bad call.
- Escalation-trigger breadth — how many conditions force a decision back up. Broad triggers keep risky calls central; narrow triggers maximize local autonomy but can let an unusual case be handled routinely.
- Role granularity — whether authority is granted to broad roles or specific positions, trading simplicity against precision of accountability.
- Support provisioning — how much information, budget, and backing accompanies the grant, which determines whether delegation transfers real power or just work.
When it helps, and when it misleads¶
A rulebook helps when a central decider is a chronic bottleneck for a stable set of decision classes and there are competent roles ready to own them. Writing the grant down ends decision ping-pong, clarifies accountability, and lets recurring choices resolve where the knowledge is.
Its signature failure is the one the archetype names: delegation without authority — decisions pushed to roles that lack the power, information, or support to make them, so the work moves but the burden and risk land on someone unequipped, and the decisions quietly bounce back or go badly. A rulebook can also drift into over-delegation, handing out authority for decisions that genuinely need central judgment, or go stale as roles and risks change while the document does not. The guarding discipline is to grant authority and resources together, keep escalation triggers honest so genuinely hard cases still route up, and review the rulebook as the organization changes rather than treating it as settled forever.
How it implements the components¶
default_or_delegation_rule— the document is a set of standing delegation rules: for each decision class, the delegated owner and the conditions of the grant.choice_owner_map— it maps decision classes to the roles accountable for them, ending ambiguity about who decides.exception_and_escalation_path— each grant carries explicit triggers that route unusual, high-risk, or out-of-limit cases back up to higher authority.
It does not classify decisions by monetary stakes into review-depth tiers (decision_stakes_classification) — that graded signature schedule is the Approval Threshold Matrix — and it does not preselect a default answer within a single decision (choice_reduction), which is Default Option Design.
Related¶
- Instantiates: Decision Load Management — the rulebook realizes the "delegate decisions to accountable owners under constraints" load treatment.
- Sibling mechanisms: Approval Threshold Matrix · Decision Triage Queue · Default Option Design
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: Delegation Rulebook operates as a standing rule, threshold, contractual commitment, or policy constraint governing future conduct because it a document specifying which decisions are delegated to which roles under which constraints.
Independent corroboration: The frozen evidence defines Delegation Rulebook as 'A document specifying which decisions are delegated to which roles under which constraints', so its operative form is Rule, Policy & Commitment.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Organization design cohered durable role-by-domain rules specifying who decides, within what limits, and where escalation begins.
Related originating lineages:
- Public Administration & Policy — Subsidiarity and administrative delegation supplied a parallel lineage for codified local authority.
Review resolution: Organization design cohered durable role-by-domain rules specifying who decides, within what limits, and where escalation begins. The retained alternate lineages materially shaped the mechanism's form.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The rulebook and the Approval Threshold Matrix answer different questions and are strongest together: the rulebook says which role owns a class of decision by domain; the matrix says how much review a decision needs by magnitude. A grant of authority in the rulebook typically still lives inside the matrix's thresholds — a store manager decides markdowns, but a large enough one still trips the review tier.
[n1] Subsidiarity — the principle that a decision should be handled by the smallest or lowest competent authority able to make it, with higher levels stepping in only for what the lower cannot. A delegation rulebook operationalizes it, pushing authority down to capable roles while reserving escalation for what exceeds them. ↩