Pro Forma Modeling: What You Need to Know

Introduction

You're sizing future choices and need a way to turn guesses into numbers; pro forma modeling is simply building forward-looking financial statements from explicit assumptions so you can see future profit and loss (P&L), balance sheet, and cash flow under different paths. Use it for fundraising, M&A, budgeting, and strategic planning-typically run as three scenarios across a 12-month operational plan and a 5-year strategic view. The payoff: it helps you test outcomes and make decisions with numbers; for example, a 10% revenue shortfall on a $1,000,000 run-rate cuts top-line by $100,000, which increases near-term cash need and can change your funding ask. Here's the quick math, and what this hides: assumptions drive results, so state growth rates, margin assumptions, and timing clearly-defintely document sources.

Key Takeaways

• Pro forma modeling = turning explicit assumptions into forward-looking P&L, balance sheet, and cash flow to test outcomes and inform decisions.
• Use it for fundraising, M&A, budgeting, and strategic planning-typically run as a 12‑month operational plan plus a 5‑year view across base, downside, and upside scenarios.
• Core components: income statement, balance sheet, cash flow, and supporting schedules (capex, depreciation, debt, working capital).
• Document clear drivers (revenue, margins, CAC, working capital, financing), run sensitivity and stress tests, and ensure the three‑way tie reconciles.
• Immediate actions: build a drivers tab, run three scenarios, validate reconciliation; CFO/finance lead owns the model and an analyst performs sensitivities.

Pro Forma Modeling: Core components of a pro forma

You're building a forward-looking financial picture to decide capital needs, runway, or deal price - here's what to include and how to link it so the numbers actually tell the right story. Takeaway: get the income, balance sheet, cash flow, and supporting schedules correct and linked; they drive decisions, not dashboards.

Income statement: revenue, gross profit, operating expenses, EBITDA

If you want to test outcomes, start with the income statement - it's the primary engine for margins and operating cash. Build revenue from explicit drivers (units, price, churn, new customers) and express each component as a separate, auditable line on a drivers tab.

Steps and best practices:

• Break revenue into product lines or customer cohorts.
• For each line, model units × price, with conversion and churn rates tied to marketing spend.
• Calculate gross profit as revenue minus cost of goods sold (COGS); show COGS drivers (materials, labor, freight).
• Separate operating expenses into fixed (rent, salaried SG&A) and variable (commissions, usage-based costs).
• Derive EBITDA as gross profit minus operating expenses; show D&A and interest below EBITDA, not hidden inside it.

Example FY2025 quick math: assume revenue $120,000,000, COGS 48% -> gross profit $62,400,000; SG&A $30,000,000 -> EBITDA $32,400,000. Here's the quick math: revenue × (1 - COGS%) - SG&A = EBITDA.

What this estimate hides: one-offs, customer concentration, and deferred revenue timing. Flag unusual items on a separate line so EBITDA reflects ongoing ops, not timing quirks. A small typo in an input can swing EBITDA materially - double-check assumptions.

One-liner: Build revenue from drivers, then prove your EBITDA with clear cost logic.

Balance sheet and supporting schedules: assets, liabilities, equity and capital needs

The balance sheet shows the funding consequences of your income forecast - working capital moves, capex, and financing needs live here. Link every balance-line item to a supporting schedule so changes are traceable back to drivers.

Steps and best practices:

• Create supporting schedules for capex, depreciation, long-term debt, and working capital.
• Compute working capital from days metrics: AR days, AP days, inventory days. Convert days to balances with revenue and COGS flows.
• Model capex by project with timing and expected useful lives; map to depreciation method (straight-line or accelerated) on schedule.
• Build a debt schedule that separates principal amortization, interest expense, and covenant measurements (leverage, interest coverage).
• Show equity movements: new raises, share-based comp, and dividends; reconcile opening and closing equity each period.

Example FY2025 items to include: planned capex $8,000,000 with $5,000,000 annual depreciation; debt outstanding $40,000,000 with principal amortization $4,000,000. Use AR days 45, AP days 30, inventory days 60 to compute working capital balances.

How forecasts drive capital needs: if working capital increases by $2,000,000 in FY2025 and capex is $8,000,000, your funding gap is the sum of those outflows minus operating cash generation - that shortfall defines the raise or drawdown requirement. What this estimate hides: seasonality and timing of receipts; model monthly or weekly for startups to avoid false comfort.

One-liner: Link every balance item to a schedule so funding needs are transparent and auditable.

Cash flow statement: operating, investing, financing and free cash flow

The cash flow ties income and balance sheet to actual liquidity. Build a true three-statement model so cash reconciles every period and you can test runway, covenant risk, or refinance triggers.

Practical steps and controls:

• Start cash flow from net income, add back non-cash items (depreciation, stock comp), then adjust for changes in working capital to get operating cash.
• List investing cash flows separately (capex, asset purchases, acquisitions) and financing flows (debt draws/repayments, equity raises, dividends).
• Calculate unlevered free cash flow (UFCF) as EBIT × (1 - tax rate) + D&A - capex - Δworking capital; use this for valuation or covenant stress tests.
• Reconcile: closing cash = opening cash + operating + investing + financing. Add a reconciliation table that ties to the balance sheet.
• Model interest paid on the debt schedule and tax cash paid (use current tax payable schedule, not just tax expense).

Example FY2025 cash calculation: EBIT $27,400,000, tax rate 21% -> NOPAT $21,646,000; add D&A $5,000,000 -> operating cash before WC $26,646,000; less capex $8,000,000 and ΔWC $2,000,000 -> unlevered FCF $16,646,000.

What this estimate hides: timing differences between tax expense and cash taxes, and one-off financing receipts. Always stress-test runway: if revenue falls 20% and ΔWC reverses, recompute monthly cash to see when covenants bite.

One-liner: Reconcile all cash flows and run monthly scenarios so liquidity risk is visible early.

Pro Forma Modeling: Key assumptions and inputs

Direct takeaway: pick a small set of measurable drivers, convert them into cash and P&L flows, and clearly document timing and sources so your pro forma is testable. This chapter shows exactly which numbers to set, how to convert them into model lines, and what to check first.

Revenue drivers and margins

Start with a drivers tab that separates volume, price, retention, and acquisition cost. For a subscription or product business, model cohorts (monthly or quarterly) and use three selectable growth paths: base, upside, downside. One clean one-liner: model cohorts, not averages.

Practical steps

• List customer types and unit definitions (accounts, subscriptions, SKUs).
• Build monthly cohorts: starting customers, new adds, churn, reactivation.
• Set prices and upsell rules per cohort; link to AR (billing) schedule.
• Compute CAC (customer acquisition cost) by channel and amortize acquisition spend over expected customer life.

Concrete example (FY2025 illustrative assumptions): assume annualized revenue $48,500,000, average revenue per account (ARPA) $500/month, monthly churn 3.0%, blended CAC $1,200. Here's the quick math: average customer life = 1 / churn = ~33.3 months; simple LTV = ARPA life gross margin (use gross margin below). With a 70% gross margin, LTV ≈ $11,667, so LTV:CAC ≈ 9.7x. What this estimate hides: cohort decay, price changes, and channel mix shifts.

Best practices and checks

• Validate ARPA against billing system for FY2025 months.
• Reconcile new bookings to recognized revenue by month.
• Run sensitivity on churn ±1ppt and CAC ±20% (what moves revenue most?).
• Tag uncertain drivers (product launch, seasonality) and stress-test timings.

Capex, depreciation, and working capital

Capex and working capital drive cash; get timing right. One clean one-liner: cash timing matters more than matching P&L.

Capex and D&A steps

• Define capex types: maintenance vs growth; set capitalization threshold.
• Assign useful lives (IT servers 3-5 yrs, leasehold/improvements 7-10 yrs, equipment 5 yrs) and choose method (straight-line typical).
• Schedule purchases monthly/quarterly and link depreciation (D&A) to P&L and accumulated capex to balance sheet.

Concrete example (FY2025 illustrative numbers): plan total capex $6,000,000 in FY2025 split $4.0M growth, $2.0M maintenance; useful lives average 5 years → annual depreciation ≈ $1,200,000. Quick math: straight-line depreciation = capex / life.

Working capital assumptions and calculation

• Set days metrics: receivables (DSO), payables (DPO), inventory (DIO) per product line.
• Link days to revenue and COGS: AR balance = revenue/365 DSO; Inventory = COGS/365 DIO; Payables = COGS/365 DPO.
• Model changes in NWC (net working capital) month-to-month to feed cash flow.

Concrete working-capital math (FY2025 illustrative): with revenue $48,500,000, daily revenue ≈ $133,000. If DSO = 45 days, AR ≈ $6,000,000; DIO = 20 days, inventory ≈ $2,660,000; DPO = 30 days, payables ≈ $4,000,000. Net working capital ≈ $4,660,000. What this estimate hides: seasonality and billing lags; update monthly if collections slip.

Controls and best practices

• Reconcile model AR, inventory, payables to sub-ledgers monthly.
• Use rolling 13-week cash to capture near-term swings from capex and NWC.
• Flag capex commitments and vendor terms (prepayments, retainers).

Financing terms and capital timing

Model debt, equity, and covenants as first-class drivers. One clean one-liner: assume financing takes time-model the cash cliff before it arrives.

Key items to model

• Debt balances, interest rate (fixed or spread over SOFR), amortization, fees, and call/step-up dates.
• Covenants: EBITDA-based leverage, interest coverage, minimum liquidity-model breach triggers and cure mechanics.
• Equity raises: amount, timing, pre-money valuation, issuance costs, and dilution (shares outstanding).

Concrete FY2025 illustrative terms and math: assume outstanding term debt $50,000,000 at all-in rate 8.0% → interest expense ≈ $4,000,000 in FY2025. Covenant example: net leverage ≤ 3.5x (Net Debt / EBITDA). If modeled EBITDA falls to $4,000,000, leverage = 12.5x → immediate breach risk. Equity bridge: plan an equity raise of $20,000,000 in Q2 FY2025 to support growth capex and extend runway; model issuance costs at 5% (cost ≈ $1,000,000). Quick math: runway impact = cash + equity raise - projected burn; always show pre- and post-financing cash balances.

Stress tests and governance

• Run a covenant breach scenario: drop EBITDA by 25% and simulate waiver cost or accelerated amortization.
• Model refinancing: assume market rate +500bps if refinancing in stressed markets.
• Document financing assumptions and owner: debt lead (Treasury) updates rates weekly.

Next step: Finance - build the drivers tab, add debt and equity timing, and run three scenarios (base/down/up) by Friday; analyst to run covenant-breach stress tests and report required cures.

Modeling structure and techniques

Takeaway: Use top-down for rapid market sizing and bottom-up for operational detail, build a drivers-based model with clear input/logic/output separation, and manage circulars with controlled iteration or algebraic fixes. You're building a model to answer a specific decision-fundraising, pricing, or runway-so structure it to match that question and validate the math.

Top-down versus bottom-up forecasting - when to use each and exact steps

If you need a quick check on market opportunity or a board slide, use top-down; if you need cash flow accuracy, unit economics, or investor diligence, use bottom-up. Top-down starts with market size and penetration rates; bottom-up aggregates granular drivers (customers, units, prices).

Practical steps for top-down

• Estimate TAM (total addressable market) for 2025: e.g., $2.5 billion.
• Set realistic penetration: 0.1% → implied 2025 revenue $2.5 million.
• Run sensitivity: test 0.05% and 0.2% penetration.

Practical steps for bottom-up

• Model units, price, conversion, churn by channel.
• Example: 50,000 units × $120 ASP (average selling price) = $6,000,000 revenue for 2025.
• Roll up variable costs to compute gross margin by cohort.

When to pick which: use top-down for early hypothesis; switch to bottom-up once you have real channel metrics or need cash-driven answers. Here's the quick math: bottom-up ties directly to cash; top-down is a reality check. What this estimate hides: channel mix, seasonality, and conversion lag.

Drivers-based model and linking historicals to forecasts with consistent accounting policies

Build three zones: Inputs (drivers), Logic (calculations), and Outputs (financials and KPIs). Keep inputs on one tab, logic on separate tabs, outputs on a presentation tab. That enforces one-way flows and makes audits easier.

Exact setup steps

• Create an Inputs tab with named ranges for key drivers (units, ASP, CAC, churn, COGS %).
• Put calculations (revenue build, gross margin, working capital) on Logic tabs; reference Inputs only-never hard-code values in Logic.
• Produce Outputs that read only from Logic; protect the sheet.

Linking historicals to forecasts - stepwise

• Reconcile chart of accounts across 2022-2024 historicals so line items match forecast categories.
• Strip non-recurring items (one-time gains, M&A adjustments) from historical EBITDA before deriving margins.
• Set the 2025 forecast baseline to the adjusted 2024 closing balances; document any policy changes (revenue recognition, capitalization).

Example: historical revenue 2022 $8,000,000, 2023 $9,000,000, 2024 $10,000,000. If you apply a 20% growth driver, 2025 forecast = $12,000,000. Here's the quick math: 2024 × (1 + growth driver). What this estimate hides: accounting policy shifts (e.g., moving a line from Opex to Capex) that change margins but not cash.

Managing circular references and iterative calculations - control, document, and test

Circular references arise when two items depend on each other (interest depends on debt balance; debt balance depends on cash; cash depends on interest). You must either remove the circle with algebraic rearrangement or allow controlled iteration. Don't leave circulars hidden.

Step-by-step tactics

• Identify circles with Excel's Formula Auditing or a model checker.
• Isolate the loop: move the dependent calculation to a single schedule (e.g., Debt & Interest schedule).
• Prefer algebraic fixes: compute interest from opening balance and use separate cash sweep logic for principal payments to avoid recursion.
• If iteration is unavoidable, add an Iteration Switch input (TRUE/FALSE) and set Excel to max 100 iterations and 0.001 precision; document it.

Concrete example and quick math

• Debt opening balance = $5,000,000; coupon = 6% → first-pass interest = $300,000.
• If interest is paid from cash, cash reduces, possibly triggering a $1,000,000 drawdown in the model; that draw increases interest next period. Iteration converges if the draw schedule is stable.
• Use a Control Flag: Iterative = TRUE runs iterative solution; Iterative = FALSE runs algebraic approximation for audits.

Testing and governance

• Run a circular-check: break the loop (set interest to zero) and compare results; differences show sensitivity.
• Document the loop, the resolution method, and add a model test that fails if circulars appear outside the authorized schedule.

One-liner: control iterations, document them, and always provide a non-iterative fallback. Next step: Finance lead to add an Iteration Switch and Debt schedule by Friday; analyst to test convergence and document assumptions.

Validation, scenarios, and sensitivity

You're about to ask investors or the board to act on a model, so you need it tight: reconcile the three statements, measure which inputs move the dial, and stress the plan until weak links surface. Quick takeaway: lock the three-way tie first, then run focused sensitivities and three clear scenarios with stress tests.

Three-way tie: ensure income, balance sheet, cash flow reconcile

Start by treating reconciliation as a non-optional control: if Income Statement, Balance Sheet, and Cash Flow Statement don't tie, the model is unreliable. Here's the practical checklist you'll use every build.

• Make a single reconciliation row: Assets - (Liabilities + Equity) should equal $0 each period.
• Link Net Income to Retained Earnings: Retained Earnings(t) = Retained Earnings(t-1) + Net Income(t) - Dividends(t).
• Verify Cash Flow: Change in Cash from the Cash Flow Statement must equal Ending Cash on the Balance Sheet.
• Build a dedicated Checks tab: one-line pass/fail flags, color-coded errors, and a timestamped check formula (use CELL and NOW sparingly).
• Set a tolerance: for operational models use $1 absolute or ±0.01% relative error as acceptable; anything larger needs immediate fix.

Example quick math (FY2025 illustrative): Start Cash $5,000,000. Net Income $9,600,000, Depreciation $3,600,000, ΔWorking Capital $1,200,000, CapEx $8,000,000, Debt raise $10,000,000.

Here's the flow: CFO = 9,600,000 + 3,600,000 - 1,200,000 = $12,000,000. CFI = -$8,000,000. CFF = +$10,000,000. Net change in cash = $14,000,000. Ending Cash = 5,000,000 + 14,000,000 = $19,000,000. Retained earnings increase by Net Income less dividends, and the Balance Sheet balances.

Best practices: separate inputs, logic, outputs; keep hard links to historics only on the Historic tab; avoid circulars unless documented; turn iterative calculations off during audits; lock key cells and add a named-range map for reviewers. If you must use circulars (e.g., interest-capitalized or management fee tied to ending cash), isolate them to one small module and document the iteration logic.

One clean line: get the three-way tie to zero before you show numbers to anyone.

Sensitivity analysis: one-variable tests, tornado charts for impact

Sensitivity tests show which assumptions matter most. Use one-variable (one-way) analysis first, then a ranked tornado chart to focus conversations and resource allocation.

• Pick outputs: EBITDA, free cash flow, EPS, runway months, or NPV.
• Choose 6-8 candidate drivers: price, volume, churn, CAC, gross margin, fixed opex, capex, and tax rate.
• Run one-way shocks: typical steps are ±10%, ±20%, and scenario-specific steps (e.g., price -30% in downturn).
• Produce a tornado chart: compute absolute dollar impact on the chosen KPI, sort drivers by impact, and show bars for down/up.
• Capture both % and $ impact: present change in KPI and percent change to prevent misreading (small % on a big base may be large $ impact).

Example sensitivity math (FY2025 illustrative): base EBITDA $18,000,000. Price -10% → EBITDA = 18,000,000 × 0.9 = $16,200,000 (impact -$1,800,000). Volume -10% → EBITDA impact might be -$1,200,000 if some costs are fixed. A tornado chart will show Price on top if it moves EBITDA more than volume.

Operational tips: build a Sensitivity tab with named inputs and Data Table (Excel) or parameter sweep (Python), store snapshots of each run, and automate charts. Use scenario probability weights only if you can justify them; otherwise present ranges and let stakeholders apply probabilities.

One clean line: find the top three drivers by $ impact and treat them as the model's control levers.

Scenario planning and stress tests: base, downside, upside with covenant and liquidity checks

Scenarios give decision-makers a map of plausible futures; stress tests probe breaking points. Define scenarios with explicit, grouped assumptions and then test covenant and refinancing resilience.

• Define three scenarios: Base (management plan), Downside (plausible adverse case), Upside (realistic best case). Tie each to a concise assumption set.
• Document every assumption: growth rates, margin paths, capex schedules, working capital behavior, financing events, and timing.
• Run scenario outputs: revenue, EBITDA, free cash flow, net debt, covenant ratios, and runway in months.
• Stress-tests to run: covenant breach triggers, liquidity runway under downside, and refinancing need at debt maturity points.
• Set triggers and playbook: when coverage < 3.0x or runway < 6 months, activate the contingency plan (draw, cost cuts, asset sale, covenant waiver).

Example scenario numbers (illustrative FY2025): if FY2024 revenue was $100,000,000, then Base FY2025 = $110,000,000 (+10%), Downside = $95,000,000 (-5%), Upside = $120,000,000 (+20%). Apply margins: Base EBITDA margin 16% → $17,600,000; Downside margin 10% → $9,500,000; Upside margin 18% → $21,600,000.

Run covenant examples: if interest expense = $4,000,000 and the covenant requires interest coverage ≥ 3.0x, then minimum EBITDA = 3.0 × 4,000,000 = $12,000,000. The Downside EBITDA of $9,500,000 breaches the covenant - that's a formal red flag requiring immediate action.

Compute runway: Ending Cash $19,000,000 divided by downside monthly cash burn (for example $2,000,000) = 9.5 months runway. If a major debt of $50,000,000 matures in 12 months, you defintely need a refinancing plan even with 9.5 months runway.

Stress-test tactics: model covenant waiver scenarios, incremental equity raises, delayed capex, and bridge financing alternatives. Use a waterfall of mitigations (cost cuts, asset sale, equity, debt) and show timing - lenders care about the first 90-180 days.

One clean line: if a scenario causes a covenant breach or < 12 months runway against a material maturity, treat that scenario as a planning priority and mobilize contingency funding now.

Immediate next step: Finance - build a three-scenario workbook, add a Sensitivity tab with tornado chart, and validate the three-way tie; Analyst - produce the first run and deliver charts by Friday.

Presentation, governance, and tools

You're preparing a board pack or investor deck and need the model to be defensible, readable, and auditable - lead with the numbers, document the assumptions, and automate checks so you don't get surprised. Quick takeaway: present a tight set of executive outputs, keep a strict assumptions log and version control, and use disciplined tooling to reduce manual errors.

Executive outputs: what to show, how to calculate, and how to present

One-liner: give executives a one-page scorecard with clear drivers and ranges.

What to include: show top-line revenue, adjusted EBITDA (earnings before interest, taxes, depreciation, amortization and unusual items), free cash flow (operating cash after capex and working capital), diluted EPS, and runway (months of cash remaining). Keep the time frame to 12 months rolling plus a 3-year strategic view.

How to calculate quick: revenue = units × price; EBITDA = revenue - COGS - SG&A; free cash flow = cash from operations - capex; runway = cash balance / monthly cash burn. Here's the quick math example: if cash = $6,000,000 and monthly burn = $500,000, runway = 12 months. What this hides: seasonality and optional financing can change runway by several months.

• Show central case and two ranges: downside and upside.
• Present variance to prior forecast and to actuals, in $ and %.
• Flag one or two lead indicators (eg, new bookings, MRR growth, churn) with trend arrows.
• Use one chart: waterfall from revenue to free cash flow, and one table: 12-month cash bridge.

Documentation and controls: make models auditable and sign-off ready

One-liner: every number in the model must trace to an owner, a source, and a date.

Assumptions log: keep a single tab listing each major assumption, owner, source link, effective date, and expected sensitivity. Add a short rationale and a confidence score. Example fields: assumption name, baseline value, low/high, owner, source URL, last updated. If you update an assumption, update the date and note why.

• Version history: use semantic versioning like v1.2.3 with a change summary row for each release.
• Change notes: require sign-off comments for material changes (eg, changes > 5% of revenue or > $1,000,000 in cash impact).
• Peer review: assign a reviewer independent of the builder; checklist items: three-way tie (P&L, balance sheet, cash flow), no hard-coded outputs, consistent accounting policy, plausible growth and margin paths.
• Audit checklist: formula consistency, named ranges, protected inputs, test cases for idempotence, and reconciliations to actuals.
• Sign-offs: require CFO sign-off for model release and board materials; require head of FP&A sign-off for weekly cash forecasts.

Tools and best practices: reduce manual work, increase repeatability

One-liner: start with disciplined Excel, add automation and version control when the model becomes business-critical.

Excel discipline: separate inputs, logic, outputs; color-code inputs; avoid merged cells; use named ranges sparingly; keep one drivers tab. Protect logic sheets and lock cells that are not inputs. Build a simple unit test tab that checks totals, margin ranges, and the three-way tie each run. If you see circular references, document why and limit iteration settings.

• Templates: use a standardized template for P&L, balance sheet, cash flow and supporting schedules to shorten reviews.
• Automation: export core feeds (GL, AR, payroll) into CSV pulls and load into the model via Power Query or Python for reproducible updates.
• Python/R use: use pandas for ETL (extract-transform-load), numpy for calculations, and Jupyter notebooks for reproducible scenario runs and charts. Store notebooks and scripts in Git for version control.
• Ops: schedule automated sanity checks each night and email exceptions to owners.
• Access control: keep a single source file in a secure repo, restrict edit rights, and require branch+PR (pull request) workflow for material changes.

Next step: Finance: draft the drivers tab and automated 12-month cash bridge, and analyst: run three sensitivity cases and peer review by Friday - owner: head of FP&A. (Yes, defintely keep the reviews tight.)

Conclusion

Immediate actions - build a drivers tab

You need a single drivers page so changing assumptions updates every schedule automatically.

Start with a compact, validated inputs sheet that maps to every output:

• List core drivers: 12-20 items (revenue units, price, churn, CAC, conversion, COGS%, SG&A%, capex plan).
• Name each cell clearly and use consistent units (months, $ thousands, %).
• Link each driver to exactly one downstream calculation; avoid scattered hard-coding.
• Add source notes for each driver (contract, pipeline, benchmark) and a last-updated date.
• Build simple validation checks: totals, ranges, and a data-quality flag (green/amber/red).

One clean line: keep drivers visible and editable, not buried in tabs.

Here's the quick math for one common check: if monthly ARPU is $120 and active customers are 8,500, monthly revenue = $1,020,000. What this estimate hides: seasonality and cohort decay - model those as separate drivers.

Immediate actions - run three scenarios and validate three-way tie

You should exercise three clear scenario sets and then confirm the income statement, balance sheet, and cash flow reconcile exactly.

• Define scenarios: Base = management plan, Downside = revenue -25%, Upside = revenue +30%. Keep margins and capex assumptions explicit.
• Run sensitivity sweeps on key drivers (revenue ±10-30%, gross margin ±200-500 bps), produce a tornado chart for top 6 drivers.
• Validate the three-way tie: check Net Income → Retained Earnings change → Equity; check ending cash on cashflow statement equals balance sheet cash; set tolerance to $1 for rounding.
• Use reconciliation rows: Opening cash, +Operating CF, +Investing CF, +Financing CF, = Ending cash; instrument an error flag if mismatch ≠ $1.
• Stress-test one path: simulate covenant breach (EBITDA < covenant by 15%) and produce an action plan (capex pause, extra equity, bridge loan).

One clean line: if the three-way tie fails, stop and fix links before sharing.

Quick checklist to run now: copy the drivers, apply scenario multipliers, update debt schedule, refresh working capital, then confirm cash equals balance sheet cash.

Owners, timeline, and immediate deliverables

You want clear ownership and firm dates so the model is ready to act on.

• CFO or finance lead: draft the first full pro forma model and drivers tab by Friday, December 5, 2025.
• Financial analyst: populate supporting schedules and run the three scenarios and sensitivities; deliver outputs and tornado charts by Friday, December 5, 2025.
• Treasury/FP&A: produce a 13-week cash view derived from the model and flag any runway <6 months.
• Governance: peer review and sign-off on material changes; document assumptions in an assumptions log with version history.

One clean line: owners + due dates make decisions executable.

Next step and owner: Finance (CFO): draft the drivers tab and full pro forma by Friday, December 5, 2025; Analyst: run sensitivities and validate the three-way tie by the same date.