Revenue is ahead of plan. The dashboard is green. The meeting moves on.
Yet a capacity commitment still needs approval, and nobody has named the date by which waiting becomes a choice. That is the gap a finance leader should expose. Good board reporting decision requests make the unresolved choice visible alongside business performance: what must be decided, which alternatives exist, what management recommends and when authority must act.
A favorable financial result cannot answer a question the board has never been asked.
Arron's post on decision-connected reporting supports connecting visibility to accountable action. The short decision note below is an editorial application of that principle, not a published Bennett board policy.
Board reporting decision requests belong before the charts
An executive summary should distinguish an update from a request. “Revenue is ahead” is an update. “Approve the proposed capacity commitment by Friday, within these conditions” is a request.
For each material issue, provide six core components:
Choice: the exact commitment or direction requiring approval.
Alternatives: workable options, including delay and its consequences.
Recommendation: management's preferred option and why.
Basis: decisive financial data, operating assumptions and major risks.
Authority: who is entitled to approve, and who will execute.
Deadline: when the decision is needed and what happens if it is deferred.
The authority depends on the company's actual governance arrangements. Do not assume that every budget item belongs to the full board, or that inclusion in a board book itself authorizes spending.
The dashboard is not a decision explains the wider problem. This board note handles the specific choice that a green status can conceal.
Board pack examples: a hypothetical $100,000 capacity choice
Consider a fictional company whose monthly revenue plan is $500,000. Actual revenue is $540,000. The $40,000 difference divided by $500,000 is 8%.
That comparison describes financial performance. It does not establish whether a proposed $100,000 capacity purchase is affordable, whether customers have committed to future demand or whether delivery can use it effectively.
Assume management has three options: commit the full $100,000 now, buy a separately cancellable $40,000 initial stage, or defer while verifying demand. These figures are illustrative; they do not represent a client result or an investment return.
A short board note could read:
Decision requested: authorize the $40,000 initial stage within the stated cash and demand conditions.
Reason: it addresses the immediate delivery constraint without approving the remaining $60,000.
Uncertainty: two prospective customer commitments remain unconfirmed.
Alternative: defer the entire purchase until those commitments are verified.
Deadline: Friday, before the quoted availability expires.
Execution owner: the operations lead, after finance verifies the conditions and approval is recorded.
The $40,000 stage is not automatically the correct choice. The example shows how to expose the choice. If the “stage” contract actually binds the company to all $100,000, the recommendation must change.
Board reports need evidence close to the request
Attach the financial information that could alter the decision. The income statement describes recent performance. The balance sheet and cash flow statement provide different context. Financial statements should be identified by period and preparation status, rather than presented as interchangeable proof.
Show the cash flow assumption behind the proposed commitment, the contractual exposure and the operational update that explains the constraint. State which customer commitments are signed and which remain prospective.
Bennett's financial reporting examples cover the wider reporting craft. Here, the aim is to help board members review materials with sufficient time to challenge the recommendation.
If the request reveals recurring gaps between the financial reports and actual commitments, use the Profit & Tax Leak Check to frame that wider review.
A consistent format helps board members find critical information. It should not squeeze a significant risk into a green label. Put key metrics and variance analysis beside the operational updates that explain them. Forward looking insights should name their assumptions and future risks, rather than sound like forecasts already achieved.
The decision note also identifies who will route the outcome. Where the company uses a company secretary, general counsel or an audit committee, follow its established responsibilities for the request and record. That routing should give finance leaders a clear owner, not another unresolved handoff. Board effectiveness here means the operating team can tell what was decided.
Board engagement needs time for meaningful discussion
Send the request and supporting board materials before the upcoming meeting. Give readers enough time to ask where a number came from and whether an alternative was considered. The finance leader should surface open questions rather than hiding them in multiple email attachments.
Version control matters when the recommendation changes. Mark the current note, explain the changed assumption and withdraw the superseded request. Board management software can distribute documents; management still owns the reasoning and the accuracy of the pack.
A long pack can create information overload without improving the board's ability to act. Check whether the reader can find the request, evidence and deadline without reconstructing them from the last meeting. Keep the detail accessible, and put the choice where it will receive board input.
At the meeting, ask the authorized decision makers to approve, reject, request further evidence or defer explicitly. If they defer, record what evidence is missing, who will provide it and the next decision date. “We discussed capacity” is not enough to guide an operating team.
Board minutes: best practices for an executable outcome
Judge board pack creation by whether it delivers timely information for decision making. Board members rely on an identifiable version, adequate time to review it and a clear explanation of what the financial information says about the company's financial health. Keep an audit trail from the documents distributed to the recorded outcome. Use the company's access controls for sensitive materials, and name the person who can supply the missing evidence. This is a practical check on the request's usability, rather than a demand for a longer pack.
The official record should identify the outcome and conditions according to the company's established process. The execution owner needs a practical instruction: which amount, which scope, which conditions and which deadline.
Do not silently treat a recommendation as approved because no one challenged it. Do not ask an operations lead to infer permission from a favorable discussion of financial results.
Arron's financial execution post emphasizes action beyond passive advice. Closing the execution gap adds the broader leadership context.
For the next board meeting, pick one unresolved commitment and write its six-part decision note. Where financial visibility repeatedly fails to produce a clear action, start a Bennett Leak Check conversation.
Frequently asked questions
What belongs in a board reporting decision request?
State the choice, alternatives, recommendation, decisive evidence, approval authority and deadline. Include conditions that would change the recommendation.
Why is a green board pack insufficient?
Green usually describes performance against a selected measure. It does not establish that a pending purchase, hiring choice or contract commitment has been decided.
Does 8% revenue growth justify the hypothetical purchase?
No. The example is 8% above a fictional revenue plan, not a verified growth rate or proof of investment value. Cash timing, demand and contractual exposure still matter.
Must the full board approve every request?
No. Follow the company's actual approval arrangements. Name the authorized decision maker instead of assuming a meeting or document grants authority.
What should happen when board members defer?
Record the reason, missing evidence, evidence owner and next decision date. Explain any consequence of waiting so deferral is a visible choice.
Can board management software solve the gap?
It can support document distribution and version control. It cannot decide which commitment requires approval or supply management's judgment.
What should the execution owner receive?
The approved scope, amount, conditions and next action, supported by the established record. A discussion summary alone can leave permission ambiguous.
How should a changed assumption be handled?
Issue a clearly identified replacement note, explain the change and reassess the recommendation. Withdraw the older version so readers do not act on conflicting requests.