A delegations of authority document is the piece of paper that actually determines whether a chief executive can sign a contract, approve an expense, or commit the organisation to a decision without ringing the chair first. Most associations have one. Fewer have one that would genuinely hold up the day a signature is challenged, a payment is disputed, or a board wants to know exactly who approved what.
The legal machinery underneath the document
Section 127 of the Corporations Act 2001 (Cth) sets out how a company formally executes a document, generally by two directors signing, or a director and company secretary. That provision alone would make a chief executive's signature on a contract worthless without something else operating alongside it. Section 126 is that something else: an individual acting with the company's express or implied authority can validly execute documents on the organisation's behalf. A delegation of authority document is, in practical terms, the instrument that actually creates that express authority for your chief executive and other senior staff. Without it, or with one too vague to rely on, every contract your executive signs rests on shakier ground than most boards realise.
The principle the aicd states most clearly
The AICD's guidance on this point is worth quoting closely, because it resolves a tension several earlier articles in this series have circled: the board may delegate some of its authority, but it cannot delegate its responsibility. This is precisely the section 190 point from the inner board article earlier in this quarter, restated as a design principle rather than a liability warning. Certain matters are considered good practice to reserve for the board regardless of how much operational authority is otherwise delegated: appointing, overseeing and evaluating the chief executive's performance, and reviewing and approving financial reports, among others. A delegations document that hands these away, even informally, even because a capable executive makes it tempting to do so, is delegating exactly the responsibility the board cannot legally shed.
A delegation that is not recorded and regularly reviewed is not really a delegation. It is an informal habit wearing a governance document's clothes.
Building a delegation that actually holds under pressure
A genuinely useful delegations of authority document does several things that a vague one-page summary does not. It sets specific financial thresholds by role, what the chief executive can approve alone, what requires a second signatory, what requires the finance committee, and what requires full board approval, rather than a single blanket figure that either constrains routine operations pointlessly or leaves genuinely significant decisions under-scrutinised. It separates financial delegation from other categories of authority entirely, contracts, employment decisions, property matters, and strategic commitments each carry different risk profiles and deserve their own thresholds rather than being folded into a single figure. And it names specific roles rather than specific individuals, so the document survives a staff change without needing to be rewritten.
- Set tiered financial thresholds by role and transaction type, not a single figure covering every kind of decision.
- Explicitly exclude the matters the AICD's own guidance identifies as properly reserved for the board, chief executive appointment and evaluation, and financial report approval chief among them.
- Require any delegate approving expenditure to be someone other than the person who initiated it, a basic segregation of duties that closes off the most common avenue for undetected error or misuse.
- Record delegated authority in a single current register, not scattered across historical board minutes, so anyone can quickly confirm who is actually authorised to do what today.
- Set a fixed review cycle, connecting directly to the constitutional review discipline from the Foundations quarter of this series, so delegated authority does not quietly become outdated as the organisation's scale and risk profile change.
Reporting back is what makes delegation governance rather than abdication
None of the drafting discipline above means anything without genuine reporting back to the board on how delegated authority is actually being used, precisely the guardrail against the inner board problem discussed earlier in this quarter. A delegations document that specifies thresholds but never requires the board to see what has actually been approved under them is solving only half the problem. The board retains full legal responsibility under section 190 for how delegated power is exercised. Genuine oversight, not just a well-drafted document sitting in a policy folder, is what actually discharges that responsibility.
A well-built delegations of authority document does something more valuable than protecting the organisation from a worst-case dispute. It frees the board to genuinely trust the operational decisions made within it, precisely because everyone knows exactly where the boundary sits and what happens when it is approached.
Explore the Board Director course
Want the fully branded, board-ready PDF of this article? Download the whole 52-part series — free.
Until next week,
Annie