2026-10-29 · AI-drafted · Finance · Modeling · Accounting · 5 min read
Build the Inputs Sheet That Makes Every Model Honest
Every broken model shares one flaw: assumptions scattered across dozens of cells, some hardcoded into formulas, others buried in tabs nobody opens. When a reviewer changes one number and the model contradicts itself three sheets later, trust collapses. The inputs sheet — a single, named, auditable home for every assumption — is the structural fix. Build it correctly once and every formula downstream becomes a reference, not a guess. I'll show you how, with worked numbers drawn from a European manufacturer and an Indian IT services firm.
Why Scattered Assumptions Break Models
A financial model is a system of linked claims. Each claim depends on an assumption — a revenue growth rate, a tax rate, a days-payable figure. When those assumptions live inside formulas rather than in a dedicated cell, two things happen. First, the model becomes impossible to audit: a reviewer must open every formula to find every driver. Second, scenario analysis becomes manual surgery, changing cells one by one and hoping nothing is missed.
Consider a German manufacturer with EUR 120m of revenue. If the analyst hardcodes a 3.2% revenue growth rate into the income statement formula, a 2.8% rate into the working capital schedule, and forgets to update the DCF terminal growth assumption entirely, the model tells three different stories about the same business. No single number is wrong in isolation. The model as a whole is incoherent.
The inputs sheet solves this by enforcing a rule: every assumption lives in exactly one cell, that cell has a name, and every formula in the workbook references that name. Change the cell once; the entire model updates consistently. This is not a stylistic preference — it is the structural condition for a model that survives review.
Architecture of a Rigorous Inputs Sheet
The inputs sheet is the first sheet in the workbook, before the income statement, balance sheet, and cash flow statement. It contains no formulas that calculate outputs — only raw assumptions entered by the analyst. Organize it into labeled blocks: Revenue Drivers, Cost Structure, Working Capital, Capital Expenditure, Financing, Tax, and Valuation. Each block sits in its own row group with a bold header and a shaded background so the eye finds it instantly.
Every cell in the inputs sheet carries three attributes: a descriptive label in the adjacent column, a unit annotation (%, EUR m, days, x) in the next column, and a Named Range — Excel's mechanism for giving a cell a text identifier. A cell named Rev_Growth_Y1 is unambiguous in any formula. A cell at row 14, column C is not. Named Ranges also survive row insertions, which hardcoded references do not.
Add a Source column as the final column in each row. Populate it with a brief note: 'Management guidance Q4 2024', 'IFRS 16 schedule', 'Industry median, Damodaran 2024'. This column does not affect calculations. It tells the next analyst — or your future self — why the assumption is what it is. Models without source notes are archaeology projects waiting to happen.
A Worked Example: Two Firms, Two Regimes
Take a retailer with EUR 40m of revenue reporting under IFRS, and an Indian IT services firm with INR 3.2bn of revenue reporting under Ind AS (India's IFRS-converged standard). Both models need a revenue growth assumption, a tax rate, and a working capital policy. The inputs sheet for each firm looks structurally identical even though the numbers differ. EUR 40m firm: Rev_Growth_Y1 = 4.5%, Tax_Rate = 29.9% (German statutory combined rate), DSO (days sales outstanding, the average number of days to collect a receivable) = 42 days. INR 3.2bn firm: Rev_Growth_Y1 = 11.0%, Tax_Rate = 25.17% (Indian base corporate rate), DSO = 55 days.
Because both models use Named Ranges, the analyst can run a scenario — say, a recession case where growth drops to 1.5% for the EUR firm and 6.0% for the INR firm — by changing two cells. Every downstream schedule, every tie-out, every DCF output updates in one recalculation. Without the inputs sheet, the same scenario requires hunting through every formula in both workbooks. The time cost is real; the error risk is higher.
The discipline also enforces intellectual honesty. When every assumption is visible on one sheet, it is obvious when the model contains 47 assumptions and the analyst has a defensible source for only 12 of them. That visibility is uncomfortable. It is also the point. A model that hides its weaknesses in scattered cells is not a model — it is a spreadsheet that looks like one.
Naming Conventions That Scale
Named Ranges fail in practice when analysts name them inconsistently. A workbook where one analyst uses Rev_Gr, another uses RevenueGrowth, and a third uses rg_1 is a workbook nobody can maintain. Establish a convention before the first cell is named and enforce it across every model in the department. A workable standard: Category_Descriptor_Period. Examples: Rev_Growth_Y1, Rev_Growth_Y2, COGS_Pct_Y1, WC_DSO, CapEx_Maint_Annual, Debt_Rate_Senior, Tax_Rate_Statutory.
Excel's Name Manager (Formulas tab → Name Manager) is the audit tool. Open it after building the inputs sheet and confirm that every Named Range points to the inputs sheet, not to a formula cell or an output. Any name pointing elsewhere is a structural error. Fix it before the model leaves your desk.
For multi-scenario models, consider a second sheet called Scenarios that holds three or four columns of assumption sets — Base, Upside, Downside, Stress — and a single toggle cell on the inputs sheet that selects which column feeds the Named Ranges. This pattern, sometimes called a scenario selector, keeps the inputs sheet clean while making scenario switching a one-click operation rather than a manual override process.
The Inputs Sheet as a Communication Tool
A well-built inputs sheet does something the rest of the model cannot: it makes the argument visible. When a CFO or a credit committee reviews a model, they do not read every formula. They read the inputs sheet. If the assumptions are labeled clearly, sourced honestly, and organized logically, the reviewer can assess the model's credibility in minutes. If the inputs sheet is a mess, the model's credibility is already damaged before a single output is examined.
This matters across jurisdictions. A Brazilian retailer presenting a model to a São Paulo lender and the same retailer presenting to a London private equity firm face different audiences with different conventions — BRL versus USD translation, CVM versus FCA disclosure norms — but both audiences will look at the inputs sheet first. A clean, sourced, consistently named inputs sheet communicates competence before the numbers do.
Course 2 builds the inputs sheet in module 3 and references it in every module that follows. The income statement, working capital schedule, capital expenditure schedule, debt schedule, and DCF all draw from the same named cells. That architecture is not incidental — it is the reason the model ties out. Start with the inputs sheet. Everything else follows from it.
A Note on What This Course Is — and Isn’t
We don’t pursue CE accreditation. The courses are pure education, not credentialing.
Nothing in this course constitutes personalized financial, legal, or investment advice. You’ll learn frameworks and analytical tools — what you do with them is your decision.
We use AI heavily and we’re transparent about it.
Drafted with AI from the outline of Dr. Kareem Tannous’s Course 2. Published automatically under his editorial standards.
$189 per course. $504 for the bundle of three.
100% refund within 3 days of enrollment AND zero module access. Accessing any module — even briefly — waives the right to a refund permanently. Decisions are final; no appeals.
Course 2: Excel Modeling for Financial Decisions →
New to financial statements? Start with Course 1 →
Instructor: Kareem — DBA International Business · MS Applied Economics & Predictive Analytics · MBA Finance & Accounting · Series 65 · university-level instructor since 2014.
— Dr. Kareem Tannous