Delegated authority matrix

Register

Who may decide what, by role, with the limits and conditions you set.

Authority attaches to a role, not to a person

People change jobs. An authority recorded against a name would follow that person out of the building, and the row left behind would be a live delegation to somebody who no longer works there. So the primitive here is a role or title, and the only person named on a row is whoever wrote it down. It is a design decision, not a labeling preference.

It confers nothing and enforces nothing

No other tool in this product reads a limit recorded here. No approval anywhere is checked against it. And nothing in this register gives anybody legal power to bind any entity — who may commit an organization is set by its own constitution and by law, not by a list somebody typed. This is an internal note of how you have decided to run things.

Related governance tools: Resolution register · Policy register · Budget request

An internal note of who may decide what, by role, with limits you set. It confers nothing, enforces nothing, is read by no other tool, and gives nobody legal power to bind any entity. Everything runs on your device.

Questions people ask

Can I name the person who holds the authority?
Not as the authority itself — the row is a role. Record the role and the limit, and let your own records say who currently holds the role.
Does anything check approvals against these limits?
No. No other tool reads this register and no approval anywhere in the product is validated against a limit recorded here.
Does this give somebody authority to sign a contract?
No. Nothing in this register gives anybody legal power to bind any entity. That comes from your constitution and from law.
What limits should I set?
CompliMaint suggests no threshold. The figures are entirely yours.