Delegation of authority explained for not-for-profits

Delegation of Authority for NFPs is one of the most practical governance tools a not-for-profit can have. 

It explains who has permission to make decisions on behalf of the organisation, what limits apply, and which decisions must go back to the board.

For many not-for-profits, delegation starts informally. A Chair approves one thing, the Treasurer reviews another, the CEO signs contracts, a program manager orders supplies, and the board approves major spending when someone remembers to bring it to a meeting.

That may work for a small organisation with limited activity. But as a not-for-profit grows, informal authority can create confusion and risk.

People may not know who can approve spending, sign funding agreements, hire staff, accept grants, enter contracts or use reserves. Decisions may be delayed because everyone is unsure who can say yes. Or worse, decisions may be made by someone who does not have the authority to make them.

A clear delegation of authority framework helps the board, management and staff make decisions at the right level. It supports accountability, protects governance controls and helps the organisation operate without every decision needing to return to the board.

This article explains delegation of authority in plain English for not-for-profit boards and management teams, including what can be delegated, what should stay with the board, how approval limits work and how delegations connect to financial delegations policies.

What is “Delegation of Authority” for NFPs?

Delegation of authority means giving a person or role permission to make certain decisions or take certain actions on behalf of the organisation.

In a not-for-profit, the board is usually responsible for overall governance. But the board cannot and should not make every operational decision.

Delegation allows the board to set boundaries so management and authorised people can act within those boundaries.

In plain English:

• the board keeps responsibility for governance
• the board decides what can be delegated
• management or authorised people make decisions within agreed limits
• the board receives reporting so it can monitor what is happening
• major decisions still return to the board

Delegation is not the same as giving away responsibility. The board remains accountable for ensuring the organisation is governed properly. Delegation simply makes it clear who can do what.

Why delegation of authority matters

Delegation of authority matters because not-for-profit organisations need both control and efficiency.

If every decision needs board approval, the organisation can become slow and difficult to run. Staff and managers may wait weeks for routine decisions. Opportunities may be missed. Board meetings may become overloaded with operational detail.

If too many decisions are made without clear limits, the organisation may be exposed to financial, legal or governance risk.

A delegation framework helps balance these two needs.

It supports:

• clear decision-making
• better financial oversight
• faster operational decisions
• stronger governance controls
• reduced confusion about authority
• better accountability between board and management
• clearer approval limits
• more consistent financial delegations
• stronger not-for-profit governance

Delegations also help protect people. If authority is clear, staff, managers, Treasurers, CEOs and board members are less likely to be placed in uncomfortable situations where they are expected to approve something outside their role.

Delegation does not remove board accountability

One of the most important points is that delegation does not remove board accountability.

The board may delegate authority to management, a committee, the CEO, the Treasurer or another authorised person, but the board still has an oversight role.

For example, the board may delegate authority to the CEO to approve budgeted operational spending up to a certain amount. But the board should still receive financial reports that show how the organisation is tracking against budget.

The board may delegate responsibility to an Audit and Risk Committee to review internal controls. But the full board should still understand major control issues and approve significant policy changes.

Delegation should create clarity, not distance.

This connects closely with board financial responsibilities. Board members do not need to approve every invoice, but they still need enough information to oversee the organisation’s financial position, risks and major decisions.

What can be delegated?

The board can usually delegate operational and administrative decisions, provided the organisation’s governing rules and relevant laws allow it.

Delegated authority may cover areas such as:

• routine spending within approved budgets
• supplier payments below set limits
• staff recruitment within approved positions
• day-to-day program management
• grant administration
• minor contract approvals
• operational policies and procedures
• purchasing and procurement
• expense reimbursements
• credit card use
• payroll processing
• banking administration
• routine compliance tasks

The board may delegate authority to:

• the CEO or Executive Officer
• the Treasurer
• the Chair
• committees or subcommittees
• senior managers
• program managers
• finance staff
• authorised volunteers
• external providers, within clearly defined limits

Delegation should usually attach to a role rather than a person’s name. This makes it easier to manage changes when people leave or roles change.

What should stay with the board?

Some decisions should usually stay with the board because they affect governance, strategy, financial sustainability, legal obligations or organisational purpose.

The exact list will depend on the organisation’s structure and rules, but board-reserved decisions often include:

• approving the strategic plan
• approving the annual budget
• approving annual financial statements
• appointing or removing the CEO
• approving major policies
• approving major unbudgeted expenditure
• approving use of reserves above a set threshold
• entering significant contracts or leases
• accepting major funding agreements with material obligations
• approving major changes to programs or services
• approving mergers, wind-ups or structural changes
• approving borrowing or finance arrangements
• changing financial delegations
• responding to serious financial or governance risks

The board should be clear about which decisions cannot be delegated.

This is sometimes called a reserved powers schedule or matters reserved for the board.

Having this list helps prevent confusion. Management knows what it can decide. The board knows what must come back for approval.

How approval limits work

Approval limits are the dollar limits attached to delegated authority.

They show who can approve financial decisions and up to what amount.

For example, an organisation might set approval limits like this:

• Program Manager: up to $1,000 for budgeted program expenses
• CEO: up to $10,000 for budgeted operational expenses
• CEO and Treasurer jointly: up to $25,000 for budgeted expenses or urgent operational matters
• Board: above $25,000, or any major unbudgeted commitment

These numbers are examples only. The right approval limits depend on the organisation’s size, budget, staffing, risk and financial complexity.

Approval limits should consider:

• whether spending is budgeted or unbudgeted
• total contract value, not just monthly cost
• whether funding is restricted or unrestricted
• whether the decision creates an ongoing commitment
• whether there is a conflict of interest
• whether the decision affects cash flow or reserves
• whether the decision carries legal, reputational or service delivery risk

This is why approval limits should not be treated as simple spending permissions. They are governance controls.

Budgeted versus unbudgeted authority

A delegation of authority framework should distinguish between budgeted and unbudgeted decisions.

Budgeted spending has already been considered as part of the board-approved budget. This means management may have more authority to approve it within agreed limits.

Unbudgeted spending has not been approved in the budget. It may need stricter limits or board approval.

For example:

• A manager may approve $2,000 of budgeted program supplies.
• The CEO may approve $8,000 of budgeted software costs.
• The board may need to approve a $12,000 unbudgeted equipment purchase.

The distinction matters because a cost may be reasonable but still create pressure if it was not planned.

For not-for-profits managing tight funding or grant obligations, budgeted versus unbudgeted authority should also be linked to budgeting and funding support.

Total contract value matters

Approval limits should consider the full value of a commitment, not only the first invoice or monthly payment.

For example, a software subscription costing $900 per month may look small. But if the contract runs for three years, the total commitment is $32,400.

Similarly, a lease, service agreement or employment commitment can create future obligations beyond the current month.

A delegation of authority policy should make clear whether approval limits apply to:

• single transactions
• total contract value
• annual commitment
• whole-of-life project cost
• cumulative spending with one supplier

Without this clarity, people may unintentionally approve commitments that are larger than they appear.

Delegation and restricted funds

Delegation of authority should also consider restricted funds.

A person may have authority to approve spending up to a certain dollar amount, but that does not mean they can approve spending from restricted funding for any purpose.

Restricted funds must be used in line with the funding agreement, grant condition, donor restriction or approved purpose.

For example, a program manager may have authority to approve expenses within a funded project. But they still need to make sure the expense is eligible under the grant agreement.

The delegation framework should make clear that restricted funding conditions override general approval authority.

For more detail, see restricted funds explained for charities and not-for-profits.

Delegation and conflicts of interest

Delegated authority should never be used to bypass conflict of interest rules.

If a person has a conflict, they should not approve the decision just because it falls within their normal authority.

For example:

• A manager should not approve payment to a supplier owned by a family member without declaring the conflict.
• A Treasurer should not approve reimbursement for their own expenses without independent review.
• A board member should not influence a contract decision involving their employer.

The delegation framework should clearly state that conflicts must be declared and managed before approval.

This connects directly with conflict of interest policies explained for not-for-profits.

Delegation and committees

Boards may delegate certain responsibilities to committees.

For example:

• An Audit and Risk Committee may review audit findings and risk controls.
• A Finance Committee may review budgets and forecasts.
• A Governance Committee may review board policies and nominations.
• A Fundraising Committee may oversee campaign plans within approved limits.

Committee delegation should be documented in terms of reference.

The terms of reference should explain:

• the committee’s purpose
• what authority it has
• whether it can make decisions or only recommendations
• what decisions must go back to the board
• membership and quorum
• meeting frequency
• reporting requirements

If your organisation is considering a committee structure, see Audit and Risk Committees: Do you need one?.

Delegation and quorum

Delegation does not remove the need for valid meetings and proper decision-making.

If a decision must be made by the board or a committee, the meeting must follow the organisation’s rules, including quorum requirements.

For example, if the board needs to approve a major contract, that approval should be made at a valid meeting or through a permitted written resolution process.

If the meeting does not have quorum, the board may not be able to make the decision.

For a practical explanation, see quorum explained for not-for-profit boards.

Delegation and financial controls

Delegation of authority is one part of a wider control environment.

It should work alongside:

• financial delegations
• approval limits
• segregation of duties
• banking controls
• payment approvals
• credit card controls
• budget monitoring
• grant tracking
• conflict of interest processes
• board reporting

For example, a CEO may have authority to approve an invoice, but a separate person may still need to process the payment, and two authorised signatories may need to release it through online banking.

This separation supports better governance controls.

For practical examples of finance checks, see internal controls for charities.

What is a delegation of authority policy?

A delegation of authority policy is a document that sets out who can make decisions and within what limits.

It may also be called:

• delegations policy
• delegated authority policy
• authority matrix
• approval authority framework
• financial delegations policy
• delegation of authority schedule

The policy should be practical and easy to use.

It should help people answer questions like:

• Can I approve this expense?
• Does this need CEO approval?
• Does this need board approval?
• Can this contract be signed?
• Is this spending within budget?
• Does the funding agreement allow this cost?
• Who approves reimbursements?
• What happens if there is a conflict of interest?

The policy should be supported by a clear table or matrix where possible.

What should be included in a delegation of authority policy?

A strong policy should include:

• purpose of the policy
• scope and who it applies to
• definitions of key terms
• roles and responsibilities
• matters reserved for the board
• approval limits for different roles
• rules for budgeted and unbudgeted spending
• rules for contracts and total commitment value
• rules for restricted funding
• expense reimbursement approvals
• credit card approvals
• banking and payment approval rules
• conflict of interest requirements
• emergency approval process
• reporting and monitoring requirements
• review date

For a deeper article on finance-specific authority, see financial delegations policies.

How delegations support not-for-profit governance

Delegation of authority supports governance because it makes decision-making clearer and more accountable.

It helps the board avoid two common problems:

• becoming too involved in operational detail
• being too distant from important financial and governance decisions

With good delegations, the board can focus on strategy, oversight, risk and sustainability. Management can make day-to-day decisions within clear boundaries. Finance teams can check whether approvals are valid. Auditors or reviewers can see the approval trail.

Delegations also help improve board reporting. If the board knows what has been delegated, it can ask for reporting on exceptions, major commitments, unbudgeted spending and policy breaches.

This supports stronger financial governance because authority, oversight and reporting work together.

Common delegation mistakes

Delegation problems often happen when authority is assumed rather than documented.

A practical delegation of authority checklist

Use this checklist to review whether your delegation framework is clear and useful.

Board authority:

• Are matters reserved for the board clearly documented?
• Does the board approve the annual budget?
• Does the board approve major unbudgeted expenditure?
• Does the board approve major contracts, leases or funding agreements?
• Does the board approve changes to delegations?

Management authority:

• Does the CEO or Executive Officer have clear approval limits?
• Do managers know what they can approve?
• Are delegations attached to roles rather than individuals?
• Are budgeted and unbudgeted decisions treated differently?
• Are urgent decisions covered by a clear process?

Financial controls:

• Are payment approvals separate from payment processing, where possible?
• Are bank approvals clearly documented?
• Are reimbursements independently approved?
• Are credit card limits and review processes clear?
• Are supplier bank detail changes independently checked?

Restricted funds and grants:

• Do delegations explain how restricted funds can be approved?
• Are grant conditions checked before spending?
• Are acquittal obligations considered?
• Are major funding agreements approved at the right level?

Governance and reporting:

• Are conflicts of interest managed before approval?
• Are committee delegations documented in terms of reference?
• Are significant delegated decisions reported to the board?
• Are policy breaches or exceptions reported?
• Are delegations reviewed annually?

When should delegations be reviewed?

Delegations should be reviewed regularly and whenever the organisation changes.

A review may be needed when:

• the organisation grows
• new staff roles are created
• funding increases or changes
• larger grants are received
• the organisation signs new contracts or leases
• financial reporting becomes more complex
• there are audit or review findings
• there is a control failure or near miss
• board or management roles change
• the organisation introduces new finance systems

At a minimum, the board should review delegations annually. This review can sit alongside budget approval, policy review, internal controls review or audit planning.

How Hopscotch can support delegation of authority

Delegation of authority works best when it is connected to finance systems, board reporting and practical workflows.

It is not enough to approve a policy if payment processes, accounting records, and board packs do not reflect it.

Hopscotch helps not-for-profits strengthen financial reporting, approval processes, internal controls, and governance rhythms so boards can oversee decisions without being pulled into every operational detail.

For organisations that need clearer authority levels, approval limits, or board reporting, our not-for-profit accounting and NFP compliance and reporting support can help turn delegation into a practical system.

Final thoughts

Delegation of authority helps not-for-profit boards and management teams make decisions clearly, responsibly, and efficiently.

It explains who can approve what, what limits apply, and which decisions must stay with the board. It supports governance controls, financial oversight, and accountability.

Good delegations do not remove board responsibility. They help the board focus on the right decisions while giving management the authority to operate within clear boundaries.

For growing organisations, delegation of authority should connect directly to financial delegations, approval limits, internal controls, restricted funds, conflict of interest processes, and board reporting.

If your organisation is relying on informal approval habits or unclear authority levels, Hopscotch can help you build a practical delegation framework that supports confident decisions and stronger financial governance.