skills/financial-modeling/references/modules/M043-revenue-forecasting-by-driver.md

<!-- Generated loss-aware reference mirror from God_Level_Public_Company_Financial_Analyst_Job_Guide_V6_99_ALL_SUB70_FIXED.docx. Canonical source remains the bundled DOCX. -->

<!-- Module: 043 | Title: Revenue Forecasting by Driver -->

## PART IX - MODEL BUILDING | MODULE 043

# Revenue Forecasting by Driver

> Mission. Forecast units, customers, capacity, utilization, price, mix, or other business-specific drivers.

## Decision output

Objective: Forecast units, customers, capacity, utilization, price, mix, or other business-specific drivers. The completed work product must be reproducible from evidence, show the downstream financial or decision effect when material, state the strongest contrary case, and define a dated update rule.

## Explicit operating procedure

1. Choose the shortest causal revenue equation available: units x price, customers x ARPU, capacity x utilization x price, stores x sales/store, users x monetization, MW x realization, or another native model.

1. Rebuild historical revenue from the selected drivers and explain residuals through mix, FX, acquisitions, geography, accounting scope, or measurement error.

1. Forecast demand and the practical ability to serve it separately. Constrain revenue by salesforce, manufacturing, qualified supply, installed capacity, power, permits, channel, customer implementation, or capital where applicable.

1. Model price, volume, mix, churn, and new business as separate assumptions when they respond differently to competition and macro conditions.

1. Use backlog/RPO/orders only after modeling cancellation, timing, conversion, renewal, and capacity.

1. Tie each forecast driver to a dated evidence source and create a high/low range based on historical error and scenario conditions.

## Required evidence and model bridge

- Primary-source set: normalized historicals, KPI bridges, driver assumptions, debt/share schedules, source notes. Preserve exact document/version, date, period, and source location for every material factual input used in revenue forecasting by driver.

- For each key concept - units/customers, price, mix, usage, retention, capacity - state whether it is a reported fact, analyst calculation, management claim, external estimate, or judgment. Quantitative concepts must retain raw components and units; qualitative concepts must retain the specific evidence and counterevidence.

- Map only economically relevant findings into the model or decision record. Process-control modules such as revenue forecasting by driver may have no direct valuation line; in that case document the downstream error or governance risk the control prevents.

## Metrics and calculation controls

| Metric / concept | Construction | Required validation |
| --- | --- | --- |
| driver identity | % of forecast revenue/cost lines linked to explicit economic drivers rather than simple growth-rate extrapolation or plugs. | driver identity: Recalculate independently from cited source data; verify definition, period, units, scope, signs, and any reconciliation to reported financial or operating totals. |
| capacity headroom | Effective available capacity less forecast demand, expressed in units and as a % of effective capacity after utilization/yield constraints. | capacity headroom: Tie cash, debt, facilities, maturities, and fixed charges to balance-sheet/footnote data; stress availability restrictions, refinancing assumptions, and downside cash generation. |
| implied share | Forecast company units or revenue divided by forecast market units or revenue for the same definition, geography, and period. | implied share: Recalculate from same-scope numerator and denominator; confirm period, units, cohort/geography, and issuer definition; reconcile material differences to filings or operating data. |



## Driver-based revenue laboratory

- Use the most causal available architecture: units x price, customers x ARPU, capacity x utilization x price, stores x sales/store, users x engagement x monetization, or project MW x realization. Avoid consolidated percentage guesses when drivers exist.

- Reconcile the driver model back to reported revenue for every historical period. The residual should be explained as mix, FX, M&A, scope, or measurement error.

- Forecast bottlenecks before demand. A demand forecast is not executable if sales capacity, manufacturing, power, permits, supply, or financing cannot support it.

## Worked application

> Case: semiconductor revenue is units x ASP constrained by fab, yield, packaging, and demand.

- Reconstruct the relevant reported fact from primary evidence before interpreting the case. For revenue forecasting by driver, show the raw components rather than only the resulting ratio or narrative.

- Build the causal chain through units/customers, price, mix, usage, then identify which link is directly observed and which link remains an assumption.

- Calculate driver identity, capacity headroom, implied share from sourced components under the reported/base interpretation and at least one skeptical alternative interpretation.

- Translate the difference between cases into the variable that matters for revenue forecasting by driver: evidence quality, revenue, operating profit/NOPAT, free cash flow, invested capital, financing/dilution, risk, or valuation. Mark non-applicable links instead of inventing them.

- Expert consistency test: build bull/base/bear by changing drivers, not arbitrary CAGR percentages.

- Precommit the specific future filing, KPI, customer/supplier observation, regulator action, or market input that would materially invalidate the revenue forecasting by driver conclusion.

## Failure tests

- FAIL if units/customers cannot be defined and reproduced from the source pack.

- FAIL if revenue is forecast from a top-line percentage when units, customers, capacity, price, mix, retention, or another observable economic driver is available and material.

- FAIL if the revenue forecasting by driver conclusion depends on an unstated assumption, unreconciled definition, or evidence that cannot be traced to its source/version.

- FAIL if evidence materially inconsistent with the revenue forecasting by driver conclusion is omitted, reclassified, or dismissed without a documented definition, materiality, causal, timing, and source-quality analysis.

## Completion test

A senior reviewer must be able to reproduce the revenue forecasting by driver conclusion, vary the most sensitive assumption independently, trace the change through the model, understand the strongest opposing case, and identify the next evidence that would force an update. If any link is missing, the module remains open.