Skip to content

Authority Matrix

Authority map — instantiates Speech-Act Clarification

Maps who may validly perform each consequential act — approve, bind, consent, publish, declare — for a group, and under what conditions and within what limits, so an utterance is not treated as binding when the speaker lacked standing.

An Authority Matrix is a standing reference table that pairs each consequential act a group can perform — approve, sign, bind, consent, publish, declare — with the roles authorized to perform it, plus the conditions and ceilings on that authorization. Its distinguishing move among its siblings is that it answers who may, in advance and reusably: it is a validity look-up consulted before or after an utterance to test whether the speaker actually had the standing the act required. It does not classify a live statement's force, record a decision, or repair a broken act; it is the authority reference the other mechanisms consult so that clarifying an utterance's action force never accidentally validates unauthorized speech.

Example

A company maintains a spend-approval matrix as part of its delegation of authority. The rows are act-plus-resource pairs — approve a vendor contract, sign an NDA, grant a customer refund — and the columns are roles. Each cell states a ceiling and a condition: a team lead may approve purchases up to $5k for budgeted line items; a director up to $50k; a VP up to $500k; anything above needs the CFO plus board notice, and only while the person is the named budget owner. A manager emails a vendor "approved — go ahead" on a $120k contract. Read on its own, the words look like a binding approval. Checked against the matrix, the approval is invalid: the manager's standing tops out at $50k. The vendor's reliance on that "approved" is misplaced, and the matrix is what catches it before the purchase order is cut — turning a would-be dispute over "but you said approved" into a plain question of who was entitled to say it.

How it works

The matrix is built by enumerating the consequential act types (crossed with the resources or amounts they touch), assigning the roles with valid standing to each, and then attaching two qualifiers to every authorization. The standing condition is what must currently hold for the authority to be live — the role actually occupied, not recused, within term, quorum present. The scope or limit bounds the authority — a dollar ceiling, a category, a jurisdiction — so no cell grants open-ended power. It is consulted as a validity check rather than fired in the moment of speaking; its whole function is to separate said the words from was entitled to say them.

Tuning parameters

  • Granularity — a few broad authority tiers, or a fine per-act row for every distinct decision. Fine granularity prevents over-broad grants but produces a matrix so large that people stop consulting it.
  • Condition strictness — how many gating conditions each authorization carries. Strict conditions (in role, not recused, quorum met) prevent invalid acts but slow legitimate ones and can strand a decision when a condition lapses.
  • Centralization — one global matrix, or delegated sub-matrices owned by each unit. Central is consistent but rigid; delegated adapts locally but risks drift and contradiction.
  • Refresh cadence — how often the matrix is re-verified against who actually holds which role. Authority drifts as people join, leave, and change titles; a stale matrix certifies standing that has already moved.

When it helps, and when it misleads

Its strength is that it stops invalid acts from being relied on and makes the "you lacked authority" objection checkable in advance rather than litigated after the fact. It is what keeps action-force clarification honest: an utterance can be perfectly clear in its force and still be void because the speaker could not perform it.

Its failure modes are equally real. A matrix so detailed that nobody consults it protects nothing, and a stale one is worse than none — it certifies authority that has since moved to someone else.[n1] The characteristic misuse is treating presence in the matrix as sufficient while skipping the standing condition — reading the row that says a director may approve $50k without checking that this director is still in role and not recused. And over-checking can throttle a group, turning every ordinary act into an authority hunt. The discipline that keeps it useful is to keep it current, to check the live condition and not just the row, and to scale the number of gated acts to those whose invalidity would actually matter.

How it implements the components

Authority Matrix fills the standing side of the archetype's machinery — the components that decide whether an act is validly performable:

  • authority_or_standing — its home: it states, per act, which roles hold valid standing to perform it, so a binding utterance can be checked against a real grant.
  • standing_condition — each authorization carries the condition that must currently hold — in role, not recused, quorum met — for the standing to be live rather than nominal.
  • scope_or_limit — each cell bounds the authority with a ceiling, category, or jurisdiction, so standing is never open-ended and an act beyond the limit reads as invalid.

It does not classify a live utterance's force (speech_act_type) — that is Request / Order Clarification Prompt; it does not record what a valid act changed (consequence_record, record_channel) — that is Formal Declaration Record; and it does not confirm a counterparty accepted a repair (uptake_confirmation) — that is Apology / Repair Protocol. It settles who may act; siblings label, record, and repair the acts.

Editorial Notes

Form Classification

Form family: Representation, Specification & Plan

Rationale: Maps who may validly perform each consequential act — approve, bind, consent, publish, declare — for a group, and under what conditions and within what limits, so an utterance is not treated as binding when the speaker lacked standing, making its operative form a non-executable information artifact that externalizes static or prospective structure.

Independent corroboration: The frozen evidence defines Authority Matrix as 'Maps who may validly perform each consequential act — approve, bind, consent, publish, declare — for a group, and under what conditions and within what limits, so an utterance is not treated as binding when the speaker lacked standing', so its operative form is Representation, Specification & Plan.

Review outcome: Independent reviewer agreement; high confidence.

Origin Attribution

Primary origin: Organizational & Management Science

Origin pattern: Cross-disciplinary synthesis

Present-day reach: Multi-domain

Rationale: Delegation-of-authority and decision-rights matrices are organizational governance artifacts that map acts to roles, conditions, and approval limits.

Related originating lineages:

  • Law & Governance — Agency, delegation, capacity, and scope determine whether an act can legally bind the represented body.
  • Philosophy — Speech-act theory supplies the distinction between uttering authoritative words and validly performing the act.

Review resolution: The UK Charity Commission governance framework maintains explicit levels of delegated authority, and the U.S. Appraisal Subcommittee publishes a compilation of delegated acts and financial limits. These are direct organizational precedents for the page's role-by-act matrix; law and speech-act philosophy explain validity, while the exact generalized matrix is synthesized.

Attribution caveat: Legal standing determines validity, but the reusable matrix form and its maintenance are organization-design and management controls.

Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.

Review outcome: Researched adjudication after independent review; high confidence.

Sources consulted:

Notes

The matrix is a reference, not an enforcer: it says who may validly perform an act, but it neither performs nor blocks the act itself. Its value depends on being consulted at the right moments — at formation of a binding commitment and at the point of recording a declaration — which is why the mechanisms that do create and record acts, such as Formal Declaration Record, should treat a matrix check as a precondition rather than an afterthought.

[n1] Separation of duties and delegation of authority are the governance disciplines an authority matrix operationalizes: consequential powers are divided across roles and bounded by limits precisely so that no single actor can validly perform an act end-to-end without a check. The matrix is worthless if it is not maintained against actual role occupancy — the moment it lags reality, it launders unauthorized acts as authorized ones.