How to Present Runway to Your Board
Build a board runway discussion around the current position, material changes, assumptions, scenarios, and the decisions that need attention.
Updated
A runway number becomes useful in a board discussion when the people reviewing it can see where it came from, what has changed, and which decision could move it next. A number without assumptions can look more certain than it is. A detailed report without a decision can hide the point.
Direct answer: A useful board runway discussion should show the current cash/runway estimate, the assumptions behind it, what changed since the prior review, material obligations or collection timing, and the decisions or scenarios that matter next.
Start with the current position
Open with the financial position at the review date. Depending on the business, that may include recorded cash, recent cash movement or burn, the headline runway estimate, and one operating measure that explains the trajectory.
Keep the labels precise. Recorded cash is not expected revenue. Runway is an estimate based on defined inputs and assumptions, not a guarantee. If a number comes from a scenario rather than the current recorded position, label it as hypothetical.
Add the operating context that explains movement
The exact metrics depend on the business model and the board. A recurring-revenue company may need retention or recurring-revenue context. A services business may need collections, utilization, or project timing. A multi-location operator may need location-level pressure beside the group view.
Useful context often includes realized-cash or revenue movement, major payroll changes, material tools or vendor costs, and collections that arrived earlier or later than expected. Revenue and cash should remain separate whenever timing creates a meaningful difference.
Show forward commitments without calling them paid cash
Known payroll, tools, contracts, tax obligations, hiring decisions, and funding assumptions can change the runway conversation before every amount has been paid. Show material forward commitments with their timing and status, but do not subtract them from recorded cash as if payment has already occurred.
The review should make clear what is recorded, what is committed, what is expected, and what remains a planning assumption. That boundary lets the board discuss pressure without collapsing several financial states into one number.
Explain what changed since the prior review
A comparison is more useful than a fresh snapshot. Identify the few changes that materially affected the position: a receipt landed, a planned hire started, payroll changed, a commitment moved, or an assumption was revised. Then explain whether the current plan still reflects the business.
The financial dashboard framework can help organize current position, material movement, forward context, and the decision that follows.
Use scenarios for decision questions
Board discussions often introduce questions that are not recorded facts: what if hiring moves, a receipt arrives later, a cost changes, or funding closes on another date? Keep those questions in explicit scenarios so the current position remains intact.
There is no mandatory best, base, and worst set. Use a small number of alternatives that illuminate the decision in front of the board. Scenario Planning documentation explains how hypothetical assumptions stay separate from recorded values.
A flexible one-page runway structure
- Current position: Cash, burn, runway, key operating measure
- What changed: Collections, payroll, commitments, revenue
- Assumptions: What the runway estimate assumes
- Scenarios: A small number of decision-relevant alternatives
- Decisions or asks: What needs discussion or approval
Prepare the output, then review it
The Board Reports documentation explains the supported reporting workflow. Financial Statements provides recorded Income Statement and Statement of Cash Flows output, while Investor Reporting explains how reviewed context can become a communication artifact.
Generation does not remove the need for review. Check the reporting period, source values, assumptions, scenario labels, commentary, and access settings before anything is shared. This article is a financial-communication framework, not governance, fiduciary, securities, or investor-relations advice.
Put the runway estimate in decision context.
Prepare the current position, assumptions, material changes, and decision-relevant scenarios before the board discussion.
Explore Investor Reporting