Delegated Authority Charter¶
Governance charter — instantiates Conditional Authority Envelope Design
Records the source, scope, and accountability of a delegation in a standing document — who holds the authority, over what domain, and to whom they answer.
A conditional authority envelope only holds together if someone can point to why the local actor is allowed to act at all. Delegated Authority Charter is the standing document that answers that question: it names the source of the authority, the domain it covers, the actor who holds it, the forum that reviews its use, and the parties whose interests it touches. It is the constitutional layer of the envelope, not the operating layer — it does not spell out the moment-to-moment "if this condition, do that action" rules; it establishes who may act, where, under whose oversight, and at whose risk, so that everything the other mechanisms do inherits a traceable legitimacy. Where a rulebook tells an actor what to do, the charter tells the institution why that actor was ever trusted to decide.
Example¶
A city's building department is drowning in minor variance requests — a fence six inches over a setback, a porch step out of code by an inch — that all currently wait for the full planning board. The department writes a Delegated Authority Charter. It names the source: a council ordinance authorizing administrative variances. It fixes the domain: dimensional variances under a stated threshold, within the city limits, for residential parcels only. It defines the actor: senior plan reviewers with three years' tenure and a current certification. It designates the review forum: a monthly audit by the planning board, which can reverse any grant. And it maps the affected parties: adjoining neighbors, who keep their notice-and-objection rights, and the applicant. The charter is signed, versioned, and published on the department's site. From then on, a plan reviewer granting a small variance is not improvising — they are exercising a written, bounded, revocable authority, and any citizen can read exactly where it came from.
How it works¶
The charter is assembled as a small set of binding clauses, each answering one question the envelope cannot leave implicit:
- Authority source — the ordinance, board resolution, or executive order the delegation flows from, so the chain back to legitimate power is unbroken.
- Scope clause — the domain, jurisdiction, and operational state within which the delegation is valid, and nowhere else.
- Holder profile — the role, seniority, and credential an actor must have to exercise the authority.
- Accountability forum — the standing body that reviews the delegate's use of the authority and can correct or revoke it.
- Impact register — the parties affected and the protections they retain despite the delegation.
The document is versioned and published, because an unfindable charter cannot legitimize anything.
Tuning parameters¶
- Scope breadth — how wide a domain the charter covers. Broader saves more charters but drifts toward a blank check; narrow scopes stay legible but multiply the paperwork.
- Holder bar — how demanding the eligibility profile is. A high bar concentrates the authority in trusted hands but shrinks the pool who can act.
- Forum independence — whether the review body sits inside or outside the delegate's own chain. More independence hardens accountability but slows correction.
- Publication reach — from internal-only to fully public. Wider publication strengthens legitimacy and invites scrutiny in equal measure.
When it helps, and when it misleads¶
Its strength is traceability: when an action is later contested, the charter lets a reviewer separate a bad actor from a bad grant — was the person outside their authority, or was the authority itself drawn too widely? It is the instrument that keeps delegation from decaying into unaccountable agency, the classic hazard whenever a principal hands discretion to an agent whose incentives may diverge.[1]
Its failure mode is the dead charter: a document written once, filed, and never consulted, whose scope quietly no longer matches what delegates actually do. A charter written too broadly is worse than none, because it launders overreach as authorized. The discipline that guards against both is to keep the scope narrow enough to be legible and the review forum real enough to bite — a charter whose accountability clause is never exercised is decoration.
How it implements the components¶
Delegated Authority Charter fills the legitimacy-and-accountability side of the envelope — the components that say who and under whose watch, not what and when:
operating_context_boundary— the scope clause fixes the domain, jurisdiction, and state within which the delegation is valid.authorized_actor_profile— the holder clause names the role, seniority, and credential required to exercise it.independent_review_body— the accountability forum is designated as a standing reviewer that can correct or revoke.stakeholder_impact_map— the impact register enumerates affected parties and the protections they retain.
It does not set the moment-of-action rules — condition_trigger_set, permitted_action_catalog, and prohibited_action_boundary are Rules-of-Engagement Matrix's — and it does not expire itself. A self-sunsetting, time-boxed grant is revision_and_sunset_rule, which belongs to Temporary Authority Window: the charter is standing, the window ends.
Related¶
- Instantiates: Conditional Authority Envelope Design — the charter is the envelope's source-of-authority record that the operating mechanisms hang off.
- Sibling mechanisms: Rules-of-Engagement Matrix · Engagement Threshold Table · Field Decision Card · Readback Authority Confirmation · Scenario Rehearsal Protocol · Exception Escalation Form · Temporary Authority Window
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: Delegated Authority Charter operates as a standing rule, threshold, contractual commitment, or policy constraint governing future conduct because it records the source, scope, and accountability of a delegation in a standing document — who holds the authority, over what domain, and to whom they answer.
Independent corroboration: The frozen evidence defines Delegated Authority Charter as 'Records the source, scope, and accountability of a delegation in a standing document — who holds the authority, over what domain, and to whom they answer', 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 governance cohered charters that state the source, holder, scope, oversight forum, and accountability of delegated authority.
Related originating lineages:
- Law & Governance — Agency and corporate law supplied traceable grants and limits of authority.
- Public Administration & Policy — Administrative charters supplied standing mandates and review relationships.
Review resolution: Organization governance cohered charters that state the source, holder, scope, oversight forum, and accountability of delegated authority. The retained alternate lineages materially shaped the mechanism's form.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The charter is the parent document the operating mechanisms presuppose: the matrix, table, and card all encode what to do inside a domain the charter has already declared legitimate. Keeping the two layers separate is what lets an institution rewrite its rulebook without re-litigating the delegation, and revoke a delegation without touching the rulebook.
References¶
[1] Jensen, Michael C., and William H. Meckling. "Theory of the Firm: Managerial Behavior, Agency Costs and Ownership Structure". Journal of Financial Economics 3(4): 305-360, 1976. Defines agency as delegated decision-making authority and identifies the resulting possibility that the agent will not act in the principal's best interests. registry ↩