Skip to content

Delegation Letter or Authority Envelope

Authority-granting instrument — instantiates Role Expectation Architecture

Transfers a bounded, revocable slice of decision authority to a named holder — stating exactly what they may decide, up to what limit, and what to do at the edge of that envelope.

A Delegation Letter or Authority Envelope hands a specific person a concrete quantum of decision authority, drawn with an explicit boundary. Its defining move is to make the limit as clear as the grant: the letter names not only what the holder may now decide but the ceiling beyond which they may not, and the path a decision takes when it exceeds the envelope. This is what sets it apart from a role charter, which fixes an office's authority in the abstract and for whoever holds the seat; the delegation letter is person-addressed, bounded, and revocable — it says you, specifically, may decide up to here, until further notice, and here is where your discretion stops.

Example

A company promotes a regional manager, and the CFO issues a delegation of authority to her. The envelope: she may approve operating expenditures up to ≈$50k per commitment and sign vendor contracts under twelve months without head-office sign-off. The edge rule: anything above that ceiling, or any multi-year contract, escalates to the VP Finance. The bounds: the delegation is personal to her, expires at fiscal year-end, and may be revoked in writing at any time.

The effect is speed with a fence around it. Inside the envelope she moves without waiting on head office; the moment a decision pushes past the ceiling she knows exactly whose desk it goes to. The organization, in turn, always knows where her discretion ends — a delegation letter and its schedule of authorities are precisely the record an auditor asks for when checking who could commit the firm to what.

How it works

  • Name the holder and the grant. The letter is addressed to a specific person and states the particular authority being transferred to them.
  • Draw the envelope. Set the ceiling and scope — the amount, the categories, the duration — that bound what may be decided under this grant.
  • Write the edge rule. State what happens when a decision exceeds the envelope: to whom it escalates, and any conditions or exceptions attached to the grant.
  • Fix expiry and revocation. Bound the grant in time and make clear it can be withdrawn, so authority does not outlive its purpose.

Tuning parameters

  • Envelope size — how much discretion is granted. A wider envelope removes bottlenecks and speeds decisions; a narrower one is safer but pushes more up the chain.
  • Edge-rule sharpness — a bright-line ceiling versus a judgment-based boundary. Bright lines are unambiguous but gameable at the margin; judgment covers novel cases but invites dispute over what counts.
  • Revocability and expiry — standing versus time-boxed or at-will. Time-boxing is safer and creates more administrative churn.
  • Sub-delegation — whether the holder may re-delegate downward. Allowing it lets authority scale; it also dilutes control and lengthens the chain back to the source.
  • Personal vs. positional — tied to the individual or to the seat. Positional grants survive turnover; personal ones are tighter and must be re-issued.

When it helps, and when it misleads

Its strength is that it lets authority flow to where the work actually happens without losing the boundary — it makes "am I allowed to decide this?" a question with a written answer, and it gives the organization a checkable record of who could commit it to what.

Its failure modes cluster around the boundary. A grant of authority made without a matching line of accountability opens an authority–responsibility gap: the holder can act but no one is clearly answerable for how they act — the classic principal–agent problem.[1] Envelopes also proliferate until no one holds the map of live delegations, and escalation "review" becomes a rubber stamp that only nominally checks what crosses the ceiling. The signature misuse is a letter written after the fact to launder a decision the holder was never authorized to make. The discipline that keeps it honest is to pair every grant with a report-back to the delegator, maintain a register of active delegations, and actually exercise the edge rule rather than treating escalation as a formality.

How it implements the components

This instrument fills the person-specific authority slice of the archetype — the bounded grant and its edges — and leans on other mechanisms for the standing frame:

  • authority_and_permission_scope — grants a specific, bounded quantum of decision authority to a named holder. (The office-level, standing remit is the Role Charter's; this is the individual grant made within it.)
  • interpretation_and_exception_rule — defines the envelope's edge: what to do when a decision exceeds the granted scope, and the conditions and exceptions attached to the grant.

It grants authority but does not constitute the office or its legitimacy (that is the Role Charter), define the duties the authority serves (Position Description or Office Mandate), or set the accountability review the holder answers to (Role Charter).

Notes

Both this letter and the Role Charter touch decision authority, but at different grain: the charter fixes what the office may do; this grants a person a bounded slice of it, revocably. The distinction matters most for the register — a live "authority envelope" that no one tracks is exactly how organizations discover, after an incident, that someone had discretion nobody remembered granting. A delegation without a report-back path is authority without accountability; keep the two together.

References

[1] The principal–agent problem — the difficulty a principal faces in ensuring an agent, acting with delegated authority, acts in the principal's interest rather than the agent's own. Delegation inherently creates it, which is why a report-back to the delegator and a live register of grants belong with every authority envelope. ↩