A delegation of authority matrix defines who can make which decisions in your company, up to what limit, and who reviews or is informed. Together with the organisational structure, job descriptions, processes and performance indicators, it forms the operating model that lets a company grow without everything stalling when one person is away.
This guide covers the main types of organisational structure and how to choose between them, explains the delegation of authority matrix with an example and a step-by-step build, and connects it to job descriptions, governance and performance indicators, with signs that show whether your company runs on people or on a system.
What is an organisational structure, and why isn't it enough?
An organisational structure sets out how units and roles are arranged in the organisation, the reporting lines between them and the levels of management. It usually appears as an organisation chart showing where each role sits and whom it reports to.
Designing it together with roles and a delegation of authority matrix is core to SELA's organisational structure and operations design services.
Its value is that it makes the organisation visible: every employee knows their place and their manager, and leadership can see where effort is concentrated and where gaps exist. Yet many companies find that redrawing the chart changed nothing about how work actually gets done.
The reason is that the chart answers one question: who reports to whom. It does not answer other questions that matter just as much. Who makes this decision? What exactly is expected of this role? How does work move between departments? How do we know performance is good?
The answers to those questions together are what we call the operating model. It is a set of layers that build on each other; the organisational structure sits at the base, but it is not the whole thing:
The components of a structure
Every organisational structure is built from a few elements; understanding them helps you read and assess your current one:
- Organisational units: departments, sections and teams, and how roles are grouped within them.
- Management levels: the number of layers between top leadership and front-line staff.
- Span of control: how many people report directly to each manager; too narrow adds layers, too wide weakens oversight.
- Degree of centralisation: whether decisions are made at the top or delegated to units close to the work.
- Reporting lines: whom each role reports to, and whether reporting is single or dual.
Watch the gap between the formal structure and the real one, too. The formal structure is what the chart shows; the real one is the path work actually takes. When the two drift far apart, the formal structure no longer reflects how your company works and needs a review.
When one of these layers is missing, people fill the gap with improvisation. That works at first, but as the company grows it turns into slow decisions, overlapping responsibilities and heavy reliance on particular individuals.
Types of organisational structure: which fits your company?
There is no ideal structure for every company. Each type has strengths and risks, and the right choice is the one that serves your current strategy and the nature of your work. These are the most common types:
Functional
People grouped by specialism. Suits a single line of business.
Divisional
Units by product, market or region, each with its own functions.
Matrix
People report to their function and to a project lead at once.
| Type | Main strengths | Main risks | Best suited to |
|---|---|---|---|
| Functional | Deep expertise and efficiency within each function | Slow coordination between departments | One main product or line of business |
| Divisional | Focus on each market or product; faster decisions within it | Duplicated functions and higher cost | Several products, markets or regions |
| Matrix | Flexible teams formed around projects | Dual reporting if authority is unclear | Project-based, multi-disciplinary work |
Other forms exist too, such as the flat structure, which suits small start-ups, and the process-based structure built around the customer journey.
How does structure evolve as a company grows?
Most companies pass through similar stages, each with a structure that fits it:
- Founding: the founder leads almost everything, and the structure is flat and unwritten. That works while the team is small and in one place.
- Specialisation: the team grows and specialist departments appear, such as finance, sales and operations; a functional structure becomes necessary.
- Diversification: the company expands into new products, regions or markets and needs semi-autonomous units with delegated authority.
The problem is that the structure often lags behind the stage: a company that has diversified is still run as if it were at founding stage, so every decision goes through the founder. Knowing your current stage is the first step in choosing the right structure for it.
Common structure design mistakes
- Designing around people: creating a department because someone needs a title, not because the work needs it.
- Copying another company's chart: what suits a company of a different size and market may not suit you.
- Too many levels: every extra layer slows decisions and distances leadership from the work.
- Redrawing the chart without changing authority: work carries on as before under new names.
How to choose a structure
Start from strategy, not the drawing. Ask where the company will grow in the coming years: through new products, new markets or deeper specialisation in one line of business. The answer points to the right shape.
Then test the proposed structure against five decisions that come up often: who proposes each, who approves it, and how many levels it crosses. If a simple decision passes through four levels, the problem is the design, not the people.
A matrix structure in particular will not work without a clear delegation of authority matrix, because people report in two directions and any ambiguity about who decides becomes a daily conflict.
What is a delegation of authority matrix?
A delegation of authority matrix is a document that sets out, for each significant decision in the organisation, who proposes it, who approves it, who reviews it and who must be informed, and up to what financial or operational limit each level holds that authority. It is also called a schedule of authorities.
Its value is that it moves decisions from people to rules. Instead of an employee waiting for the managing director to approve everything because nobody knows who owns the decision, they check the matrix and know the route at once. The result is faster decisions, less pressure on leadership and clearer accountability.
A matrix usually contains:
- Decisions: grouped by area, such as finance, procurement, people, contracts and operations.
- Levels: the roles that hold authority, from section head to the board.
- Limits: the financial or operational ceiling for each level, such as approval amounts.
- Type of involvement: whether the role proposes, approves, reviews or is only informed.
Types of authority
Authority is usually divided into areas, each with its own limits:
- Financial: approving expenses and payments, and moving amounts between budget lines.
- People: hiring, promotion, leave and disciplinary decisions.
- Contractual: signing and renewing contracts with customers and suppliers.
- Operational: day-to-day decisions, such as production scheduling or accepting special orders.
Do not forget temporary delegation during absences. State who exercises each role's authority when its holder is away, and up to what limit, so work does not stop during leave or travel.
Here is a simplified, illustrative extract from a matrix. The limits are symbolic (A, B, C), because every company sets them according to its size and budget:
| Decision | Section head | Finance director | Managing director | Board |
|---|---|---|---|---|
| Operating expense within budget, up to limit A | Approves | Informed | — | — |
| Operating expense above A, up to limit B | Proposes | Reviews | Approves | — |
| Expense outside the approved budget | Proposes | Reviews | Recommends | Approves |
| Hiring into an approved position | Proposes | Reviews cost | Approves | — |
| Supplier contract above limit C | Proposes | Reviews | Recommends | Approves |
Notice that every row has exactly one party that approves. That is the heart of the matrix: every decision has one clear owner, with defined supporting roles around it.
How to build a delegation of authority matrix, step by step
Building the matrix is operational work, not just a legal exercise, and it needs the people who make decisions every day:
- 1List the recurring decisionsGather the important decisions in each area, starting with those that recur or cause delays.
- 2Set levels and limitsLink each decision to the right level, with financial and operational limits that fit the company's size.
- 3Assign roles around each decisionWho proposes, reviews, approves and is informed, with one approver per decision.
- 4Test it on real casesRun recent months' decisions through it and fix what slows things down or duplicates.
- 5Approve it and build it into systemsApprove it formally, reflect it in approval workflows and forms, and review it yearly.
The last step is what makes the delegation of authority matrix part of daily work: once it is reflected in approval systems, it becomes a ready foundation for automating approval workflows.
When setting limits, avoid two common mistakes: limits so low that every decision climbs to the top, and high limits with no oversight, so large decisions are made without the full picture.
How to set the financial limits
There are no universal numbers, but there is a method. Start with last year's actual decisions: how many fell in each amount band, and how long each took to approve. Most will be small and recurring, the best candidates for delegation.
Then set each limit at the point where most recurring decisions are settled close to the work, while rare, large decisions stay with leadership. Linking limits to each unit's approved budget means they grow with the company instead of needing constant revision.
Delegation does not mean giving up responsibility: whoever delegates stays responsible for how the authority is used, so add regular reporting to the matrix, letting leadership see delegated decisions without stepping into them.
Expect a transition period in which some people slip back into old habits. In the first weeks, name one reference point who interprets the matrix and answers questions quickly.
The matrix in family businesses
In family businesses the matrix matters twice over, because it separates a person's role as an owner from their role as a manager. A family member may be a shareholder and an executive at the same time, and without written rules, family decisions and operational decisions blur together.
Here the matrix clarifies which decisions belong to the partners or the family council, which to executive management and which are delegated further. That clarity protects family relationships from daily friction, eases succession between generations and reassures any new investor or partner.
The matrix, governance and the law
The delegation of authority matrix is a core part of corporate governance, because it sets how decisions are made and who answers for them. It must also be consistent with company law and with the company's own constitutional documents, which set the powers of the board and managers according to its legal form.
In Saudi Arabia, the Capital Market Authority's Corporate Governance Regulations set the rules for how listed companies are run and what their boards are responsible for. Internationally, the G20/OECD Principles of Corporate Governance are the widely used reference. Unlisted companies benefit from both when designing their authority framework, especially as they grow or prepare for new investment.
Job descriptions: how do roles connect to the structure?
If the structure sets where a role sits and the delegation of authority matrix sets its decisions, the job description sets what is expected of it day to day. Without it, the structure stays a tidy chart that changes nothing about how work gets done.
A good job description is short and specific, and includes:
- Purpose of the role: one or two sentences on why the role exists.
- Key responsibilities: five to eight, written as outcomes rather than tasks.
- Authority: a reference to what the role holds in the delegation of authority matrix.
- Performance indicators: how success in the role is measured.
- Relationships: whom the role reports to, who reports to it and whom it works with.
- Requirements: the qualifications, experience and skills needed.
The most common mistake is writing a long list of tasks that ends with "and any other duties as assigned". That phrase invites overlapping responsibilities and weakens accountability. Write responsibilities as clear outcomes instead, such as "orders delivered on the agreed date" rather than "follow up on orders".
| Written as a task | Written as an outcome |
|---|---|
| Follow up on orders | Orders delivered on the date agreed with the customer |
| Prepare reports | A performance report reaches management before the review meeting |
| Liaise with suppliers | Materials arrive on time and to the approved specification |
| Any other duties as assigned | Dropped; any new responsibility is added in writing when it arises |
Job descriptions versus RACI
You may also come across the RACI matrix, which defines for each activity or project who is Responsible, who is Accountable, who is Consulted and who is Informed. The difference is that a job description covers the whole role over time, while RACI covers how work is shared within a specific activity. The two complement each other.
How to write a practical job description
Start by interviewing the role holder and their manager together, and ask which outcomes the role is really held to. Write a draft, then share it with people in other departments who work with the role; they are the fastest to spot overlaps. Finally, approve it and revisit it whenever the role changes materially.
Connecting job descriptions to hiring and reviews
A job description is not written once and forgotten. Use it in hiring to define what you are looking for, in onboarding to show a new employee what is expected, and in performance reviews to link results to the written responsibilities. Used this way it becomes a daily management tool, not a file in HR.
Make sure responsibilities line up across job descriptions: one written into two descriptions creates duplication, and one written into none creates a gap the customer pays for.
How to build an operating model that scales
A company that runs on particular people grows until it reaches the limits of those people, then stops. A company that runs on a clear operating system can add teams, markets and products without multiplying the pressure on leadership.
Signs your company runs on people, not on a system
- Most decisions, even small ones, go through the founder or managing director.
- One absent employee halts a whole piece of work because nobody else knows how it is done.
- Each department works its own way, with no shared written processes.
- People do not know how their performance is measured, so it is judged by impression.
- Arguments about who owns shared tasks between departments keep coming back.
Making the transition in stages
Do not try to build the whole operating model at once. Start by diagnosing the current state, then design the target organisational structure and the delegation of authority matrix together, write job descriptions for the most influential roles, document the core processes, and finally link everything to performance indicators and a steady review rhythm.
This mirrors an organisational consulting engagement for a plastics manufacturer that began with a full diagnosis: the interventions were not built on assumptions but on a clear picture of the organisation, which then became three focused development interventions.
To bring in outside help for this work, see our guide on how to choose a management consulting firm to lead the diagnosis and design with you.
The role of leadership
The new operating model succeeds or fails with leadership. If the managing director bypasses the matrix and takes decisions that belong to others, everyone will conclude the rules are for show. Leading by example matters more than any document.
Performance indicators and review rhythm
The last layer of the operating model is what keeps it alive. Give each unit a small number of indicators linked to company goals, and give every indicator a clear owner in the structure.
Then set a steady review rhythm: a monthly meeting per unit that reviews its indicators and settles pending decisions, a quarterly review at leadership level, and an annual review of the organisational structure and the matrix themselves. That way the model evolves with the company instead of freezing.
To check whether the new model is working, look a few months after launch: are decisions faster, are fewer requests escalated to leadership, and does work continue when a key person is away?
Frequently asked questions
What is the difference between an organisational structure and a delegation of authority matrix?
The organisational structure shows the units, roles and reporting lines: the shape of the company. The delegation of authority matrix shows who decides what, up to which limit, and who reviews or is informed. The structure answers where a role sits; the matrix answers who owns a decision.
When does a company need to restructure?
Usually when strategy changes, when the business expands into new markets or products, or when slow decisions and overlapping responsibilities become a recurring complaint. A clear signal is that most small decisions pass through one person, or that operations depend on particular individuals rather than on processes.
Do small companies need a delegation of authority matrix?
Yes, sized to their stage. A small company does not need a long document; a table of its main financial and operational decisions and the limits for each level is enough. It takes pressure off the founder and makes growth easier, because decision rules exist before the first disagreement.
How often should the matrix be reviewed?
At least once a year, and with any significant change in structure, strategy, business size or systems. Between reviews, watch for decisions that are often escalated higher than expected. They point to limits that need adjusting, or to roles that need support and training before they can be given wider authority.
Who approves the structure and the matrix?
Normally the highest decision-making level in the company, such as the board, the partners or the managing director, depending on the legal form and the company's constitutional documents. What matters most is announcing the approval clearly and updating systems and forms so the new authorities apply in practice, not only on paper.
Next step: start with decisions, not the chart
A good organisational structure starts with one question: which decisions does your company need in order to grow, and who should own them?
List those decisions first, design the structure and the delegation of authority matrix around them, then connect both to roles, processes and performance indicators. A few months in, review how fast decisions move and how many still climb to leadership, and adjust.
If you want to start from a clear picture, talk to us about diagnosing your operating model before any restructuring.
