Your board reserves the decisions that must stay with it: strategy, mergers and acquisitions, capital structure, changes to the company's listing, director appointments, and the group's own delegated-authority levels. Everything else cascades down through committee terms of reference and the management delegation of authority. But when the schedule of matters reserved for the board and the authority beneath it live in separate static PDFs, reviewed once a year, the board cannot readily see that what it reserved was respected and what it delegated was exercised within limits. Aptly makes the reserved matters and the cascade one live system, so the board can prove both, on demand.

Most boards can produce a schedule of matters reserved for their decision and a management delegation of authority beneath it. Far fewer can show, on demand, that the two still agree, that nothing reserved was decided below the board, and that delegated authority was exercised within the limits the board set. The schedule says what should happen; the cascade beneath it is where it either holds or quietly fails.
The reserved-matters schedule and the cascade drift apart. The board's schedule and the management delegation of authority (DOA) are written and approved separately, then maintained separately. A reorganization, a new subsidiary, or a leadership change moves the real authority without anyone updating the schedule, and the two diverge until something forces the question.
The thresholds and escalation triggers are imprecise. A static schedule often reserves "major capital expenditure" or "significant acquisitions" without a precise financial threshold or a qualitative escalation trigger, so it is unclear at the front line which decisions must come back to the board and which may proceed below it.
It is reviewed once a year, at best. The schedule is approved, filed, and revisited at the annual governance review, if then. Between reviews, the board has no living view of whether reserved matters were respected and delegated authority stayed within limits, only the document it signed months ago.
~90%
In the EY US and Society for Corporate Governance study The Delegation Edge (2025; survey of more than 200 corporate-governance professionals, fielded fall 2024), nearly 90% of organizations had implemented a delegation of authority policy. The challenge was rarely having one. It was training people on the policy, enforcing it, and keeping it updated, and the study recommends the board maintain sufficient oversight of the delegation process itself. That is the exact gap that opens between a schedule that exists and a cascade the board can actually see operating.
Aptly sits between your identity systems (Okta, Microsoft Entra ID, SailPoint) and your execution systems (SAP, Oracle, NetSuite, Workday, ServiceNow) as the system of record for who can approve, sign, and commit on behalf of the enterprise. The board reserves the decisions that must stay with it and sets the limits beneath which authority may be delegated; Aptly holds those reserved matters as structured records, cascades the delegated authority down through committee and management levels, and records who held and exercised what, at every level.
Because the reserved matters, the thresholds that route a decision back to the board, the committee delegations, and the management DOA all live in Aptly as structured, versioned records, the board's two questions have a live answer rather than an annual one: was anything reserved decided below us, and did delegated authority stay within the limits we set? When a decision exceeds a delegated limit, the threshold routes it upward to the level that holds the authority, with the escalation recorded. The schedule and the cascade stay in agreement because they are the same system, not two documents maintained by different people.
A formal schedule of matters reserved for the board, and a scheme of delegation beneath it, sit at the foundation of corporate governance. Aptly maps the board's reserved authority and its cascade to the codes that expect them:
Meridian Industries' board reserves capital commitments above the CEO's authority for its own decision. When the CEO proposed a $48M new manufacturing line, the commitment exceeded the CEO's $25M authority, so the reserved-matter threshold routed it to the Board rather than letting it proceed below. Under the old way of working, whether that routing happened at all depended on someone remembering what a static schedule said.
Answered from the system, not reconstructed. The threshold that reserved the matter, the resolution, the co-signs, and the cascade below it that stayed within limits were all captured against the live delegation of authority. No minutes to reconcile. No schedule to take on faith.
Bring your schedule of matters reserved for the board and the delegation of authority beneath it. We'll show you the cascade Aptly makes live, using your authority data.