Insights

Cash Runway Reporting: Burn Rate, Forecast Risk, and BigQuery Model

Cash runway reporting guide for growing companies: burn rate, cash forecast, working capital risk, board reporting, and BigQuery model.

Cash runway reporting is the finance reporting process that estimates how long a company can operate under its current cash plan.

It should help leadership answer one of the most practical finance questions in the business.

How long can the company keep operating under the current cash plan?

For a growing company, that answer is rarely as simple as dividing cash by last month's spend. Cash may be tied up in receivables. Vendor obligations may be coming due. Payroll may step up after hiring. Inventory purchases may pull cash forward. A large customer payment may be delayed. A forecast may include aggressive collections assumptions that have not been tested against actual behavior.

Cash runway reporting turns those moving parts into a management view. It connects current cash, burn rate, expected receipts, expected outflows, working capital timing, forecast scenarios, and reconciliation status so founders, CFOs, finance leaders, boards, and operators can make better decisions before cash pressure becomes urgent.

The goal is not to create a dramatic crisis dashboard.

The goal is to make runway explainable.

What cash runway reporting should do

Cash runway reporting estimates how many months of operating capacity the business has based on cash available, burn rate, and expected future cash movement.

A useful runway report should answer questions like:

• How much usable cash does the business have right now?
• What is the current gross burn and net burn?
• How many months of runway remain under the base forecast?
• How does runway change under downside and upside scenarios?
• Which assumptions drive the runway calculation?
• Which customer collections, vendor payments, payroll changes, or inventory purchases matter most?
• Which numbers are bank-reported, accounting-approved, modeled, or forecast?
• What changed since the last leadership or board review?
• Which actions could extend runway without damaging the business?

This is why runway reporting belongs near cash flow reporting, working capital reporting, and board reporting. Each view answers a different question, but the underlying cash logic should not be rebuilt separately for every meeting.

Cash runway versus cash flow

Cash flow reporting shows actual and expected cash movement.

Cash runway reporting uses that cash movement to estimate how long the business can operate before it needs a material change: more cash, lower spend, faster collections, better margin, delayed investment, or a revised operating plan.

The two views should connect, but they are not the same.

Cash flow reporting answers:

• What cash came in?
• What cash went out?
• What is expected to happen next?
• Which receipts and disbursements explain the movement?

Cash runway reporting answers:

• How long does the current cash plan last?
• Which assumptions shorten or extend that timeline?
• Which actions matter most?
• How confident should leadership be in the forecast?

If the company already struggles to reconcile cash movement, fix the cash flow foundation first. A runway calculation built on weak cash data will only make the problem look more precise than it is.

The core runway metrics to define

Runway reporting loses trust when leadership uses familiar terms without agreed definitions.

Before building a dashboard or board view, define the small set of metrics that drive the calculation.

Cash available

Cash available should not be treated casually.

Define:

• which bank accounts are included
• whether restricted cash is separated
• whether credit facilities are included or excluded
• whether foreign currency balances are converted
• whether uncleared payments are deducted
• whether payment processor balances are included
• whether the number is bank-reported, accounting-reported, or finance-approved

The report should make usable cash visible. Cash that is legally restricted, operationally reserved, or tied to customer deposits may need a separate label.

If cash available is used in a CFO dashboard, the same definition should feed runway reporting. Two cash definitions will create avoidable leadership friction.

Gross burn

Gross burn is the cash leaving the business over a period before incoming cash is considered.

It is useful because it shows the scale of the company's cash consumption.

Define whether gross burn includes:

• payroll and contractor payments
• vendor payments
• rent, insurance, taxes, and debt service
• software and subscriptions
• inventory purchases
• customer refunds and credits
• capital expenditures
• owner distributions
• one-time restructuring or legal costs

Some businesses should show operating burn separately from unusual or financing-related items. The point is not to hide spend. The point is to prevent one-time cash movement from distorting the operating picture.

Net burn

Net burn is the cash leaving the business after cash receipts are considered.

For many growing companies, this is the metric leadership watches most closely.

But net burn can be misleading if collections are unusual. A large customer payment can make one month look healthy. A delayed invoice can make the next month look worse. Seasonal purchasing, tax payments, annual software renewals, or financing activity can also distort the view.

Runway reporting should usually show both recent actual net burn and forecast net burn. The report should also explain whether the number is based on a trailing average, current month actuals, or forward-looking forecast assumptions.

Runway months

Runway months are usually calculated as cash available divided by expected net burn.

That formula is simple. The hard part is choosing the right burn number.

Common approaches include:

• trailing 3-month average net burn
• trailing 6-month average net burn
• current month net burn
• forecast monthly net burn
• scenario-based net burn
• board-approved plan burn

Each approach can be valid. Each one answers a different question.

A practical report should label the method instead of presenting runway as a single absolute truth.

Minimum cash threshold

Many companies should not calculate runway down to zero cash.

The business may need a minimum cash threshold for payroll, inventory purchases, taxes, vendor commitments, debt covenants, or operating reserves. If so, the runway calculation should use cash above the minimum threshold, not total cash.

This is especially important in board reporting. A company with eight months of mathematical runway may have fewer months of practical decision runway if a minimum reserve must be protected.

The assumptions that drive runway

Runway reporting is only as good as the assumptions underneath it.

The most important assumptions usually sit in a few areas.

Collections timing

Expected customer collections can materially change runway.

Useful inputs include:

• open accounts receivable
• AR aging
• customer payment terms
• dispute status
• expected collection date
• customer concentration
• renewal or invoice timing
• collection owner
• historical payment behavior

If a customer payment is large enough to change runway, it should be visible as an assumption, not buried inside a forecast total.

For the invoice-level foundation, use the accounts receivable reporting guide before feeding collections into the runway model.

Payables and commitments

Vendor obligations can shorten runway quickly when they are not modeled with enough detail.

Useful inputs include:

• open accounts payable
• AP aging
• scheduled payments
• payroll timing
• tax payments
• rent and debt obligations
• software renewals
• inventory purchase commitments
• contractor commitments
• payment holds or deferrals

If leadership is considering delaying spend, the report should show which payments are discretionary, which are contractually required, and which create operational risk if deferred.

The accounts payable reporting guide is the right starting point when vendor bills and payment timing drive the cash forecast.

Revenue and margin assumptions

Runway is not only a spending problem.

Revenue quality and margin structure affect how quickly cash recovers.

Important assumptions may include:

• new bookings
• invoice timing
• recognized revenue
• collected revenue
• gross margin
• contribution margin
• customer profitability
• discounting
• churn or renewal risk
• delivery cost required to earn the revenue

If leadership assumes growth will extend runway, finance should be able to show whether that growth turns into cash quickly enough and whether the margin profile supports the forecast.

That connects runway reporting to revenue reporting, gross margin reporting, and contribution margin reporting.

Hiring and operating expense plans

Hiring plans can change runway faster than many forecast models show.

Runway reporting should make payroll and operating expense assumptions visible:

• planned hires
• start dates
• compensation and benefits
• contractor conversions
• department budget changes
• vendor renewals
• marketing spend
• travel, events, and discretionary spend
• software commitments

If the company uses runway to make hiring or spend decisions, the report should connect to operating expense reporting rather than treating spend as one flat forecast line.

Working capital and inventory

Working capital can make runway feel confusing.

A company can be profitable on paper and still lose cash if receivables stretch, inventory builds, deposits reverse, or payables come due before customer cash arrives.

Runway reporting should show the operating cash drivers, including:

• receivables
• payables
• inventory
• customer deposits
• deferred revenue
• prepaids
• accrued expenses
• work in progress or unbilled delivery cost

If these items are material, use a working capital reporting model so runway is not calculated from a simplified cash forecast that ignores the operating cycle.

Scenario views leadership actually needs

Runway reporting should rarely show only one number.

Most leadership teams need a small set of scenarios:

• base case based on the current operating forecast
• downside case with slower collections, weaker sales, or higher spend
• upside case where growth or collections improve
• expense-control case showing the impact of specific spend actions
• financing case where new debt, equity, or owner funding is added

The scenarios should be specific enough to support decisions.

"Downside case" is not useful by itself. A better downside case names the assumptions: collections slip by 30 days, two hires move forward, gross margin falls by three points, and a large vendor payment cannot be deferred.

Runway scenarios should also preserve versions. If leadership reviews a scenario in June, the business should be able to compare July actuals against the June assumptions. That same versioning discipline is important in forecast variance reporting.

What the BigQuery model should include

BigQuery can be useful for cash runway reporting when the business needs to connect bank activity, accounting, billing, collections, payables, payroll, forecast assumptions, and leadership reporting without rebuilding the model in spreadsheets every cycle.

A practical first model usually includes:

• raw source tables for bank, accounting, billing, AP, payroll, CRM, and forecast files
• cleaned tables with consistent dates, identifiers, statuses, and amounts
• cash account, customer, vendor, department, product, and date dimensions
• cash movement fact tables
• invoice, payment, refund, bill, payroll, and expense fact tables
• AR and AP snapshot tables
• burn rate tables by week and month
• forecast assumption tables
• scenario version tables
• runway calculation tables
• reconciliation tables comparing bank, accounting, and modeled cash
• exception tables for missing mappings, stale source data, duplicate transactions, unmatched payments, and forecast assumptions needing review

The goal is not to overbuild the finance stack.

The goal is to make the runway calculation repeatable, traceable, and easy enough to explain in a leadership or board setting.

For many companies, this is a natural extension of BigQuery reporting automation. If the source tables and model layers do not exist yet, BigQuery implementation is usually the right starting point.

Reconciliation should be visible before the board sees the number

Cash runway is sensitive because it affects hiring, spending, financing, and board conversations.

The report should include basic checks before it becomes part of a leadership pack.

Useful checks include:

• bank cash compared with accounting cash
• restricted cash identified separately
• payment processor balances reconciled to deposits
• open AR compared with accounting AR
• open AP compared with accounting AP
• payroll forecast compared with active headcount and planned hires
• large vendor commitments included or explicitly excluded
• forecast collections compared with current invoice status
• scenario assumptions approved by finance
• manual adjustments documented with owner and reason

These checks do not need to clutter the main report. But finance should be able to show whether the runway number is reconciled, provisional, or dependent on known exceptions.

That visibility is one of the main ways to prevent dashboard trust issues.

Common mistakes to avoid

Mistake 1: using one burn rate without context

Trailing burn, current burn, and forecast burn can all produce different runway results.

The report should label the method and show why leadership is using it.

Mistake 2: ignoring working capital timing

Runway can change materially because customers pay late, vendors are due sooner than expected, inventory is purchased ahead of demand, or deposits create future obligations.

Ignoring working capital makes the runway number look cleaner than the business reality.

Mistake 3: treating the forecast as a fixed truth

A cash forecast is an informed view, not a guarantee.

Runway reporting should version assumptions and compare them with actuals so finance can improve the model over time.

Mistake 4: leaving scenario logic in a private spreadsheet

Scenario planning is useful, but the assumptions should not live only in one person's workbook.

If a runway scenario influences hiring, vendor negotiations, financing, or board communication, the assumptions should be documented and traceable.

Mistake 5: separating runway from board reporting

If the board pack includes cash position, runway, forecast confidence, or financing need, it should use the same cash logic finance uses internally.

Otherwise, finance ends up reconciling the board story separately from the operating story.

A practical first phase

A first runway reporting phase should stay focused.

For many growing companies, the useful starting point is:

1. define cash available and minimum cash threshold
2. define gross burn, net burn, and runway months
3. choose the burn method used for leadership reporting
4. map bank, accounting, billing, AR, AP, payroll, and forecast sources
5. centralize the core source data in BigQuery
6. build actual cash movement and burn tables
7. add AR, AP, payroll, and working capital assumptions
8. create base, downside, and expense-control scenarios
9. add reconciliation checks and exception flags
10. publish a concise finance-owned runway view for leadership and board reporting

That scope is enough to move runway out of fragile spreadsheets without pretending every future finance decision has been automated.

FAQ

What should cash runway reporting include?

Cash runway reporting should include current cash, restricted cash where relevant, gross burn, net burn, expected collections, expected outflows, working capital timing, forecast scenarios, runway months, and reconciliation status. It should also show which assumptions are actual, finance-approved, forecast, or scenario-based.

How is cash runway different from cash flow reporting?

Cash flow reporting explains actual and expected cash movement. Cash runway reporting uses that cash movement, burn rate, and forecast assumptions to estimate how long the business can operate before it needs more cash, lower spend, or stronger collections. The views should share source data and timing logic.

Why does runway reporting lose trust?

Runway reporting loses trust when burn rate definitions change, actual cash is not reconciled, forecast assumptions are not versioned, AR and AP timing are ignored, or finance and leadership use different cash views. The issue is usually weak reporting discipline underneath the runway metric.

Can BigQuery support cash runway reporting?

BigQuery can support cash runway reporting by centralizing bank, accounting, billing, AP, payroll, forecast, and working capital data, then modeling burn rate, scenario assumptions, reconciliation checks, and board-ready reporting tables. It is most valuable when runway depends on several disconnected systems.

Final thought

Cash runway reporting should not be a single fragile number copied into a board deck.

It should be a repeatable finance view that shows how current cash, burn rate, collections, payables, working capital, and forecast scenarios affect the company's decision window.

When the runway model is tied to reconciled cash data and clear assumptions, leadership can spend less time questioning the calculation and more time deciding what to do with it.