The Institutional Charter Template 2.3C.1-1

The institutional charter is scaffolding for encoding your organization's structure into binding form. This template guides the work; your institution fills it.

The charter is not written once and filed. It is the decision framework your institution uses to answer: what are we, what can we do, what can we not do, and who decides?

This sidebar provides the structure. You provide the content.

Institutional Charter Template

Institution Name: ___________________

Charter Version: ___ | Last Revised: ___________ | Next Review Date: ___________

Mandate and Scope

1.1 Primary Mandate

This institution is authorized to: [Write a single clear statement of what the institution exists to do.]

Example frame: "The Finance Controls team is authorized to design, implement, and maintain financial decision approval frameworks for operational units with annual budgets exceeding $2M."

Guidance: Be specific enough to exclude action. If you cannot say what you are not authorized to do, the mandate is too broad.

1.2 Scope Boundaries

This institution does NOT have authority to:

• [Decision/action type 1]
• [Decision/action type 2]
• [Decision/action type 3]

Guidance: Name at least three things you are explicitly not empowered to decide. These are circuit breakers.

1.3 Duration and Renewal

This charter is valid from [start date] to [sunset/review date]. Renewal requires [decision process]. If not renewed by [date], this institution's authorities expire and must be explicitly re-chartered.

Guidance: Do not create permanent institutions. Build sunset clauses. Force yourself to justify existence periodically.

Authorities and Decisions

2.1 Core Decisions

Guidance: Map your critical decisions. If a decision is not in this table, the authority to make it is not formally held by anyone — which means it will be made informally, and unevenly.

2.2 Escalation Triggers

When a decision matches the conditions below, it escalates automatically to the next authority level:

• [Condition 1]: Escalates from [Role A] to [Role B]
• [Condition 2]: Escalates from [Role B] to [Role C]
• [Condition 3]: Escalates to [Committee]

Guidance: Escalation prevents any single point of failure on high-stakes decisions.

2.3 Sub-delegation Permissions

Role [Title] may delegate [specific decision types] to [role], provided:

• Written record is maintained of the delegation
• The delegated decision is reviewed by [frequency/trigger]
• [Additional guardrails]

Guidance: Some authorities can be delegated; some cannot. Be explicit about which.

Limits and Non-Delegation

3.1 Authorities That Cannot Be Delegated

The following authorities cannot be delegated below the stated level:

• Charter revision: Requires [Committee/Board] approval. Delegation forbidden.
• Emergency declaration: Requires [Executive], confirmed by [Committee] within [timeframe]. Delegation forbidden.
• Due process override: Requires [Executive] + [Committee] review, documented in writing with stated justification. Delegation forbidden.
• [Institution-specific limit]: Requires [Authority]. Delegation forbidden.

Guidance: These are your circuit breakers. Write them down. The moment they are not written down, they will be delegated during the first crisis.

3.2 Temporal Limits on Authority

Decisions made under this charter expire or require renewal on the following schedule:

• [Decision type A]: Valid for [time period], then requires renewal
• [Decision type B]: Valid until [trigger], then requires review
• [Oversight mechanism]: Reviews all decisions in category [X] annually

Guidance: Permanent authority breeds stagnation. Force renewal. Force review.

3.3 Suspension and Revocation

Authority under this charter may be suspended or revoked if:

• [Trigger 1: charter violation, due process breach, capture evidence]
• [Trigger 2]
• [Trigger 3]

Suspension/revocation requires [Committee/Process] and [notice period] notice to the authority holder. Appeals go to [higher authority].

Guidance: The institution must be able to remove authority from someone who misuses it. If you do not have this mechanism, you have given away power permanently.

Accountability Ladders

4.1 Reporting and Responsibility Structure

[Role A: Decision-maker]
     ↓ reports to
[Role B: First-level reviewer]
     ↓ reports to
[Role C: Escalation authority]
     ↓ reports to
[Committee/Executive: Final appeal]

Guidance: Draw your ladder. Make it visible. Use it.

4.2 Breach Determination and Correction

When a decision violates the charter or its operating rules, the process is:

Guidance: Write this down. Who notices? Who investigates? Who corrects? Who follows up? If you cannot answer these, your accountability is decorative.

4.3 Escalation for Correction Refusal

If the person responsible for a breach refuses to correct it:

• [Role B] documents refusal in writing and escalates to [Role C]
• [Role C] may [action 1: remove authority, reassign responsibilities, impose consequences]
• [Final appeal available to: Role/Committee]

Guidance: The institution must be able to enforce its own rules. If it cannot, the rules are theater.

4.4 Public Record of Corrections

All breaches detected, investigated, and corrected are recorded in [repository/ledger] and reviewed [quarterly/annually] in [public/senior-team] setting.

Guidance: Hidden corrections teach people that rules do not matter. Public corrections teach people that the institution takes itself seriously.

Appeals and Exits

5.1 Appeal Rights

Anyone affected by a decision made under this charter has the right to appeal to [Authority] within [timeframe]. The appeal must state:

• Which decision is being appealed
• Why the decision violates the charter
• What decision should have been made instead

Appeal timeline: [Authority] responds within [timeframe] with decision and written justification.

Guidance: Appeal rights without timeline are not rights. Appeal rights that take longer than the original decision mean the original decision was not really appealable.

5.2 Process Exits

If this institution requires participation in a process, participation must be voluntary or there must be a defined exit. The exit process is:

• [Process X]: Participation required; exit available by [method], with [notice period], with [consequence, if any]
• [Process Y]: Participation voluntary; no exit required
• [Process Z]: Participation required; exit by [method]; no penalty beyond [consequence]

Guidance: If you cannot describe how someone exits your process without destroying their career, you do not have a process. You have a trap.

Revision and Sunset

6.1 How This Charter Changes

Amendment to this charter requires:

• Proposal in writing stating [what is changing, why, what problem it solves]
• Review by [Committee/Process] for [consistency with institutional values, impact assessment]
• Approval by [Authority] with supermajority/consensus [choose governance model]
• [Waiting period] before amendment takes effect, during which [appeals/exceptions process]

Guidance: Make charter change deliberate. Do not let convenience rewrites erode the document.

6.2 Sunset Clause

This charter expires on [date] unless formally renewed. Renewal requires:

• Review of [what metrics/outcomes have been achieved]
• Assessment of [what assumptions need re-examination]
• Reaffirmation or amendment by [Authority]

If this charter is not renewed by [date], all authorities granted herein expire and must be re-chartered explicitly.

Guidance: Sunsets force you to decide whether the institution still deserves to exist.

How to Use This Template

For a new institution: Fill in each section. Leave nothing blank. If you cannot complete a section, that is information — it means you have not yet decided that part of the structure.

For an existing institution without a charter: Interview the people who hold power. Ask them what they think their authorities are. You will likely get different answers. Those gaps are where accidents happen.

For an existing institution with an informal charter: Write down what actually happens, not what the handbook says. Where there is a gap between policy and practice, that gap is a weakness.

For revision: Use this template to force a deliberate conversation about whether your current structure still serves your current reality. The charter is not set in stone — it is a living decision document. But make revision deliberate, not drift.

Integration Points

This charter is the backbone of three other structural tools built in Sub-Arc 3C:

• Rights boundary enforcement (2.3C.1): The charter's stated commitments — non-coercion, consent validity, least privilege — become auditable through the rights boundary test from Arc 1 (2.1.6), now enforced in policy and code.
• Accountability ladder enforcement (2.3C.1): The accountability ladder identified here becomes the enforcement mechanism for encoded objective law rollout (2.3C.3).
• Organization evidence pack (2.3C.4-3): Your charter is the first document in the evidence pack — the public record of what your institution claims to be.