Financial Modelling - Best Practice Guide

Quick View

A good financial model is one a stranger can pick up, understand and trust: they can find where any number came from, follow the logic through to the outputs, and change an assumption without breaking something they cannot see. Four disciplines get you there: plan the model's purpose and life before building it, let the logic flow one way from inputs to outputs, key your colour conventions on the cover page, and keep every input in one place and every formula simple. Published models from the Civil Aviation Authority, Ofgem, Ofwat, the Australian Energy Regulator and the Utility Regulator show each of these in practice.

About

A good financial model is easy to understand, use and modify. This guide sets out how to get there, illustrated throughout with regulators' published models. It is not an exhaustive list of modelling methods; complementary guidance is set out in the FAST Standard, the Corporate Finance Institute's financial modelling resources and the National Audit Office's Financial modelling in government, published January 2022.

Key Takeaways

  • Plan before building: purpose, lifespan and reusability determine layout, structure and level of detail.
  • Structure the workbook so logic flows one way, with cover pages and a model map so any user can orient themselves.
  • Keep every input in one place, hyperlinked to its source, and never hard-code numbers inside formulas.
  • Apply consistent colour rules for text, cells and tabs, keyed on the cover page.
  • Build for the person who did not build it: checks, simple formulas and short section notes make a model auditable by strangers.

Why plan a financial model before building it?

Because purpose, lifespan and reusability determine the model's layout, structure and level of detail, and settling them first prevents logical problems surfacing late. Three questions need answering first.

What is the model for? Define the purpose clearly and early, and identify the stakeholders who will use the model, so the design is not redirected later. Different purposes require different designs: a budget needs monthly granularity, whereas a price control model needs scenario capability.

How long is the model expected to remain in use? Longer-lived models need more operating detail, greater flexibility and sensitivity capability, because they must accommodate changes that cannot yet be anticipated.

Will the model be reused? Decide whether the model will support a single transaction or be used repeatedly, and set the level of detail accordingly: greater detail often reduces reusability, while a more streamlined model is typically easier to reuse.

How should a financial model be structured?

In segregated sections, so the logic flows one way, from inputs through calculations to outputs, with cover pages before them and scenario analysis where required. Segregation keeps the model easy to audit and amend. The flow rule is standard practice; the CAA states it on its own guidance sheet:

In accordance with the FAST modelling standard the model logic flows from left to right in the general form of Inputs > Calculations > Outputs.

Further detail regarding the model design and logic flow is presented within the graphic provided in the 'Map' sheet. Hyperlinks to specific sheets are included within the Map to aid navigation.

Source: Civil Aviation Authority, H7 Price Control Model, Guidance worksheet. The model itself follows the FAST Standard. Contains public sector information licensed under the Open Government Licence v3.0.

What belongs on the cover pages?

Enough for any user to understand the model's purpose and intent without opening another document: the project name, a short statement of purpose, author details, disclaimers, a version log, sign-offs, a navigation guide and a model map. The CAA's H7 Price Control Model carries seven such sheets before its first input.

Figure 1: Cover-page tabs in the CAA's H7 Price Control Model

The cover-page tabs of the CAA's H7 Price Control Model: guidance, an introduction, a version log, a key, a sign-off sheet, a user guide and a model map, all sitting to the left of any input.

Select a tab to see what that sheet holds.

Source: Civil Aviation Authority, H7 Price Control Model (Excel workbook, approximately 20MB), cover worksheets, redrawn from the model's tab strip. The workbook is published on the CAA's H7 proposals and determination page. Contains public sector information licensed under the Open Government Licence v3.0.

That is seven sheets before the first input. A reviewer can establish what the model is for, who built it, which version they have and whether it has been signed off, without asking anyone. Without those sheets, a reviewer may have to rely on the original modeller, who may no longer be with the organisation. Among the seven, the intro sheet is the most important because it defines the model's purpose and its intended use.  

Figure 2: Intro worksheet from the CAA's H7 PCM

The intro worksheet, carrying the model's purpose, its intended uses and its limitations.

The intro worksheet of the CAA's H7 Price Control Model: the model's purpose, its intended uses and, in the closing paragraphs, its limitations. Reproduced as text rather than a screenshot; wording is the CAA's, including the unresolved placeholder text in the final paragraph.

Development of Financial Model

The Civil Aviation Authority (CAA) provides this Price Control Model (PCM). It is prepared in relation to setting price controls over Heathrow Airport for the H7 period.

The purposes of the PCM are to:

  • assess the affordability and financeability of the proposed price controls applied by the CAA;
  • allow assessment of policy options in respect of incentives;
  • calculate the maximum allowable yield; and
  • incorporate high-level cost modelling on a base plus marginal basis.

The inputs, calculations and outputs in the PCM are solely for the purposes stated above. There may be discrepancies with other related data sources (e.g. HAL's accounts) due to different assumptions used, different time periods, etc.

The inputs are for illustrative purposes and do not reflect CAA policy OR This model is published alongside the CAA's [initial proposals] (CAPxxxx published in mmm yyyy) and the inputs in the model reflects CAA's assumptions in the [initial proposals].

Source: Civil Aviation Authority, H7 Price Control Model (Excel workbook, approximately 20MB), Intro worksheet. Published on the CAA's H7 proposals and determination page. Contains public sector information licensed under the Open Government Licence v3.0.

The most useful line on the intro sheet is often the one saying what the model is not for. A stated boundary stops the model being used for decisions it was never built to support, especially once it has passed between teams or been inherited years later. Few models state their own limits; those that do are much harder to misuse.

Declaring the boundary is what stops a model being quoted in contexts it cannot support. Few models state their own limitations; those that do are far harder to misuse.

A workbook should explain itself before the user reaches the calculations. Guidance and control sheets set out the conventions, explain how the checks work and show where inputs go. Consistent ordering and colours make the model easier to read and cut the risk of error.

Figure 3: Guidance worksheet from the CAA's H7 PCM

The guidance worksheet of the CAA's H7 Price Control Model: the model explains its own purpose, its logic flow and the colour convention for each sheet type before a user reaches any of them. Reproduced as text rather than a screenshot; wording is the CAA's.

MODEL OVERVIEW

Summary: This is a Price Control Model with the primary aim of calculating the appropriate pricing per passenger by Heathrow Airport to its customers (the airlines), considering the planned expansion programme associated with the proposed new runway (the "Project").

The model is also be used to:

  • assess the affordability and financial viability of the proposed expansion program under the pricing controls applied by the CAA;
  • allow assessment of policy options in respect of incentives;
  • calculate the maximum allowable yield;
  • incorporate high-level cost modelling on a base plus marginal basis; and
  • incorporate and support Monte Carlo analysis as necessary.

In accordance with the FAST modelling standard, the model logic flows from left to right in the general form of Inputs > Calculations > Outputs.

Further detail regarding the model design and logic flow is presented within the graphic provided in the 'Map' sheet. Hyperlinks to specific sheets are included within the Map to aid navigation.

Map

1.1 Sheet Overview:

Guidance & Control Sheets
Guidance sheets provide qualitative information about the model and assist users in their understanding and navigation. Control sheets include a summary of model integrity checks and a list of macros, including descriptions of their purposes. These sheets are shaded purple. Following standard model convention, they appear first (from left to right).
Input Sheets
Input sheets are where users are required to enter information which is then used to drive the rest of the model. These sheets are shaded yellow. Following standard model convention, they appear after model guidance and control sheets and before calculations. I_Global holds static inputs which are not expected to be updated by users. I_Scenarios holds static inputs which can be edited by users and allows users to select from multiple scenarios.

Source: Civil Aviation Authority, H7 Price Control Model (Excel workbook, approximately 20MB), Guidance worksheet. Published on the CAA's H7 proposals and determination page. Contains public sector information licensed under the Open Government Licence v3.0.

The conventions sit inside the model itself, so a user learns its structure and intended use before touching a calculation.

How should inputs be organised?

On a dedicated Inputs tab immediately after the cover pages, clear enough for any potential user, and separated into dynamic inputs, which vary period to period, and static inputs, which do not. Every row should name its units and its price basis.

Figure 4: Input sheet from the Utility Regulator's PC21 financial model

An inputs sheet with rows labelled, price basis and units stated in their own columns, and years running across.

Years Prices Units 2015-16 2016-17 2017-18 2018-19 2019-20 2020-21 2021-22 2022-23
Inflation
RPI nr 259.4 265.0 274.9 283.3 290.6 294.5 302.0 308.4
% Inflation % 1.1% 2.1% 3.7% 3.1% 2.6% 1.3% 2.6% 2.1%
RCV – PC15
Closing RCV (previous year) Nominal £m 2,054.8 2,192.2 2,335.4 2,484.5 2,640.4 2,802.4
Indexation Nominal £m 69.9 74.5 79.4 84.5 89.8 95.3
Opening RCV Nominal £m 2,124.6 2,266.7 2,414.8 2,569.0 2,730.2 2,897.7
Total Capital Expenditure Nominal £m 156.8 160.7 164.5 168.9 172.7 179.2
Grants and Contributions Nominal £m -6.3 -6.5 -6.7 -6.7 -7.0 -7.2
Depreciation (net of PPP depr'n) Nominal £m -60.4 -62.1 -63.8 -65.6 -67.4 -69.3
Depreciation of Capital Grants Nominal £m 4.0 3.9 3.8 3.6 3.5 3.3
Infrastructure Renewals Charge Nominal £m -25.3 -26.0 -26.7 -27.5 -28.2 -29.0
Disposal of Assets Nominal £m -1.3 -1.3 -1.3 -1.4 -1.4 -1.5
Closing RCV Nominal £m 2,192.2 2,335.4 2,484.5 2,640.4 2,802.4 2,973.3
RPI – PC15 Assumption nr 266.8 275.9 285.3 294.9 305.0 315.3

Source: Utility Regulator of Northern Ireland, PC21 financial model, Annex N (Excel workbook) , inputs sheet. Published with the PC21 price control determination . Contains public sector information licensed under the Open Government Licence v3.0.

Every row names its price basis, nominal, and its unit, £m, in dedicated columns. Stating the price basis and units on every row prevents the commonest expensive mistake in modelling: mixing real and nominal values.

What do the calculation sheets do?

They turn the inputs and assumptions into projections and feed the key results to the output sheets. They are the heart of the analysis, and should read as a single argument: one operation per row, one period per column.

Figure 5: Calculation sheet from the AER's gas distribution roll forward model

An asset base rolled forward year by year: opening base, additions, depreciation, closing base.

A calculation sheet from the Australian Energy Regulator's gas distribution roll forward model: the capital base is carried forward year by year, capital expenditure is added and regulatory depreciation deducted, and the asset classes beneath sum to the base above them. Depreciation exceeds capex in every year after 2014–15, so the base rises once and then falls, ending at $3,920m against $4,873m at the start. Reproduced as a table rather than a screenshot.

Aus Gas – Asset Roll Forward – DNSP RFM v1.1 2014–15 2015–16 2016–17 2017–18 2018–19 2019–20 2020–21
Asset values ($m nominal)
Nominal opening capital base 4,873.00 4,936.50 4,817.57 4,584.06 4,396.36 4,117.54 3,919.92
Pipelines 1,000.00 1,020.00 1,051.17 1,031.92 1,012.28 987.10 970.29
Service pipes 800.00 810.00 828.17 827.86 872.62 864.40 857.19
Supply regulator and valve stations 700.00 705.00 713.13 713.99 717.98 713.72 708.38
SCADA 600.00 602.00 568.22 525.69 483.03 431.69 377.59
Meters 500.00 502.00 472.27 435.32 398.32 354.22 307.93
Computer equipment 400.00 402.00 339.20 267.76 193.22 111.17 24.98
Vehicles 300.00 302.00 235.42 162.26 86.62 5.78 6.34
Land and easements 500.00 508.00 527.92 543.68 562.75 576.54 590.40
Spare straight-line tax asset class
Buildings, capital works 40.00 48.00 52.00 55.48 59.19 62.22 65.13
In-house software 30.00 34.00 26.57 16.62 6.88 7.28 8.35
Equity raising costs 3.00 3.50 3.51 3.48 3.46 3.41 3.36
Nominal actual net capex 114.50 118.27 67.14 105.64 68.01 81.39
Nominal forecast regulatory depreciation (51.00) (237.19) (300.65) (293.34) (346.83) (279.01)

Source: Australian Energy Regulator, gas distribution roll forward model, asset roll forward sheet. Figures are the illustrative values published with the model template, not those of an operating business.

One operation per row and one year per column lets a reviewer read the sheet top to bottom and follow each assumption through to the output.

What makes a good output sheet?

It relays results efficiently, because the output tab is the part of the model most users actually read. For complex models the outputs may split into an executive summary tab, mixing graphs, charts and tables for strategic decision-making, and a financial output tab summarising the projections in more detail.

Figure 6: Outputs sheet from Ofgem's GT2 Price Control Financial Model

The executive summary carries the headline lines for strategic reading; the financial output gives the projections in full, with numbered rows, units and the licence term symbol each line feeds. Reproduced as a table rather than a screenshot.

Executive summary. The headline lines from the Live results sheet: the totex allowance after the incentive mechanism, the closing asset value, and the four components of calculated revenue.

PCFM year ending Licence term 31 Mar 2022 31 Mar 2023 31 Mar 2024
3 Post-TIM totex allowance 319.4 437.3 443.7
9 Closing asset value 5,861.2 5,845.1 5,827.6
Final Proposals allowances (calculated revenue) Rt
10 Fast money FMt 105.7 146.0 149.5
11 Pass-through expenditure PTt 146.8 146.8 147.1
12 Depreciation DPNt 298.5 300.3 305.3
13 Return RTNt 171.1 164.3 160.6

→ Scroll sideways to see the remaining years

All figures are £m at 2018-19 prices. Source: Ofgem, GT2 Price Control Financial Model , Live results sheet. The two-tab split is illustrative: Ofgem presents these rows on a single sheet. Contains public sector information licensed under the Open Government Licence v3.0.

Outputs get lifted into board papers, presentations and consultations, where nobody can see the model behind them. A standing note keeps the assumptions, scope and caveats attached to the figures wherever they go.

When is scenario analysis worth adding?

When users need to examine a set of pre-programmed scenarios with a degree of customisability. Build intuitive scenarios and varied sensitivities, and keep the switch that selects a scenario separate from the table that defines what each scenario contains.

Figure 7: Scenario analysis from the CAA's H7 PCM

A scenario selector, with named scenarios, the input set each uses, and a base case for comparison.

A scenario selector from the CAA's H7 Price Control Model: one cell chooses which scenario the model runs, and a separate table defines what each scenario contains. Select a scenario below to see what the model would run.

1. Live scenario
Live combination Scenario 1
Input set for prices Input set 1 — Base case
Input set for outturn statements and ratios Input set 1 — Base case
Base vs stress Base
ID Scenario Description Input set for prices Input set for outturn Base vs stress

Source: Civil Aviation Authority, H7 Price Control Model (Excel workbook, approximately 20MB), Scenario Selector sheet. Published on the CAA's H7 proposals and determination page. Contains public sector information licensed under the Open Government Licence v3.0.

The purpose of scenario analysis is not simply to create more outputs, but to make uncertainty easier to explore. The difference between a robust scenario model and a fragile one is often this separation: users can explore different outcomes without accidentally changing the assumptions that drive them. 

How should a financial model be formatted?

With consistent colour rules applied at three levels, each keyed on the cover page: text colour for how a number arrived in the cell, cell colour for what a user may change, and tab colour for what each sheet does. Formatting matters as much as structure, because it shows a user at a glance where a number came from and where to go next.

Text colour

Text colour shows how a number arrived in the cell: typed in, calculated on the sheet, brought in from another sheet, or linked from another workbook. Ofgem's RIIO-2 Electricity Transmission model keys three of these on its cover page.

Table 1: Text colour key

The text colour key from a published model, shown here as an example: colour tells a reader how a number arrived in the cell.

Text colour Meaning
Sample Black Calculated value
Sample Blue Import: a reference to another sheet or workbook
Sample Red Export: a value read by another sheet or workbook

Source: Ofgem, RIIO-2 Electricity Transmission Price Control Financial Model, Cover sheet, Model key. Contains public sector information licensed under the Open Government Licence v3.0.

Figure 8: Text colour in use, Ofgem's RIIO-2 Electricity Transmission PCFM

The convention applied through the model: black for values calculated on the sheet, colour for values brought in or read out.

The text colour convention applied through Ofgem's RIIO-2 Electricity Transmission model: black marks a value calculated on the sheet, blue a value imported from elsewhere. Reproduced as a table with the model's own colours, rather than as a screenshot.

14,446.6 Black — calculated on this sheet 1,261.3 Blue — imported from another sheet
Parameter Units 31 Mar 2022 31 Mar 2023 Why this colour
RAV — running total
Opening RAV (before transfers) £m 18/19 14,055.8 14,446.6 Carried from the prior year's closing RAV within this sheet
Transfers £m 18/19 Nil in both years
Opening RAV (after transfers) £m 18/19 14,055.8 14,446.6 Opening RAV plus transfers
Net additions (after disposals) £m 18/19 1,261.3 1,278.0 Imported: comes from the totex sheets, not calculated here
Depreciation £m 18/19 (870.5) (871.8) Imported: comes from the depreciation sheet
Closing RAV £m 18/19 14,446.6 14,852.8 Opening plus additions less depreciation, calculated here
Post-vesting balance — cost
Opening balance brought forward (before transfers) £m 18/19 24,969.8 26,231.1 Carried from the prior year's closing value
Transfers £m 18/19 Nil in both years
Opening balance brought forward (after transfers) £m 18/19 24,969.8 26,231.1 Opening balance plus transfers
Net additions (after disposals) £m 18/19 1,261.3 1,278.0 The same imported figure as in the RAV block above
Removals £m 18/19 Nil in both years
Closing value carried forward £m 18/19 26,231.1 27,509.1 Opening plus additions less removals, calculated here

Source: Ofgem, RIIO-2 Electricity Transmission Price Control Financial Model, Return and RAV sheet. Colours follow the model's own key; the explanations are MCC's. Contains public sector information licensed under the Open Government Licence v3.0.

In a model updated annually by different people, marking which cells a user may change is the difference between a controlled update and an uncontrolled modification. Clear cell conventions ensure that users know where to enter information, where not to make changes, and how the model should evolve from one update cycle to the next.

Cell colour

Cell colour differentiates input types and is a common feature of best practice models. Ofgem's RIIO-ED1 model keys five categories on its cover page.

Table 2: Cell colour key. Cell colour marks what a user may change: fixed inputs, values updated each year, values linked from the annual update, and cells that are guidance rather than data.

The cell colour key from a published model, shown here as an example: cell colour marks what a user may change, separating fixed inputs, values updated each year, values linked from the annual update, interface elements, and cells that carry notes rather than data.

Cell colour Meaning
Orange Information and interface
Yellow Fixed input value
Green Annual update input
Blue Input linked from annual update
Grey Notes and instructions

Source: Ofgem, Electricity Transmission Price Control Financial Model: RIIO-2.

Tab colour

Tab colour differentiates the function each part of the model performs, and is the convention that makes a workbook's architecture visible before anything is opened. Ofwat's PR19 Revenue Forecasting Incentive model keys six categories, two of which mark sheets that should not survive to publication.

Table 3: Tab colour key.

The tab colour key from a published model, shown here as an example: tab colour makes the workbook's architecture legible from the tab strip alone, and reserves the last two colours for sheets that are unfinished or must be removed before publication.

Tab colour Meaning
Light yellow Input sheets
No colour (default Excel tab colour) Calculation and documentation sheets
Pale blue Key output sheets
Turquoise Quality control sheets
Yellow To be completed, temporary, restructured, or deleted
Orange Internal purposes only, removed prior to publication

Source: Ofwat, PR19 Revenue Forecasting Incentive model, Model formatting sheet. Contains public sector information licensed under the Open Government Licence v3.0.

Figure 9: Tab colour in use, Ofwat's PR19 model.

The tab strip of Ofwat's PR19 Revenue Forecasting Incentive model: the colours defined in Table 3 applied across a real workbook, so its architecture is legible before any sheet is opened. Note that no tab is yellow or orange, the two colours the key reserves for sheets that are unfinished or must be removed before publication.

Select a tab to see which category its colour denotes.

Source: Ofwat, PR19 Revenue Forecasting Incentive model, tab strip and Model formatting sheet. Redrawn from the model. Contains public sector information licensed under the Open Government Licence v3.0.

With a consistent tab colour convention a user can tell inputs, calculations, outputs and checks apart from the tab strip alone. The guidance is built into the workbook, so it does not depend on whoever built it being available.

What are the structure and layout rules?

The rules below govern how the workbook is arranged and how its sheets feed one another. (The rest repeats the sentence under the Table 4 title.)

Table 4: Structure and layout rules 

The full set of structure and layout rules, covering how a workbook is arranged, how sheets flow into one another, and what should be visible to a reader.

Rule Description
Limitation to one row Limit inputs and formulas to one row so users understand the model vertically as they scroll down the model.
Do not hide rows or columns in use Rows and columns containing data should never be hidden, as visibility improves transparency. The same applies to worksheets.
Limit the number of tabs
  • Fewer tabs with more content is preferable to many tabs with less content.
  • It is easier to follow and audit a continuous array of data across a large tab than across multiple smaller tabs.
No merged cells
  • Do not merge cells for presentation purposes.
  • Merging often leads to problems later when moving, copying or deleting cells.
  • A better solution is normally to change the colour of the cell border and relocate or change text alignment.
Hide gridlines Use the View tab to hide gridlines and make the sheets more presentable.
Identical spacing for columns and rows Columns and rows should be identically spaced for each sheet in the workbook, with the same font and font size used throughout.
Simple workbook and sheet names Ensure that workbook and sheet names are short and simple.
Hide unused rows and columns Unused rows at the bottom of each sheet and unused columns to the right of each sheet should be hidden.
Ensure the flow of sheets is logical
  • A sheet should start at the top and flow to the bottom before feeding another sheet, which in turn runs top to bottom.
  • Sheets on the left should feed sheets on the right: inputs on the left-hand side, outputs on the right.
Spacing calculations
  • Each worksheet should have one or two spare rows between sections of calculations, so each distinguishable section feeds the one below it.
  • For example, finish one set of calculations and produce a total, then leave a spare row before starting the next set that uses that total.
Spare columns Keep several spare columns to the left, using one to state the units for each row and one to state any constants for that section of the sheet.
Hide the filter button
  • When making tables, particularly those destined for presentations or screenshots, hide the filter button on the header row.
  • The filter icon hides the cell text and can create other problems, particularly when sorting with columns excluded.
No empty cells in data tables Data tables, and any other tables, should have no empty cells and should be complete both vertically and horizontally.
Create a model map Include a model map regardless of the size or complexity of the model, as shown in Appendix A.
Add a contents page For ease of reference, particularly in larger models, add a contents sheet with hyperlinks.

Source: MCC Economics & Finance.

What are the content rules?

The rules below govern where inputs live, how they are sourced and labelled, and what should be kept out of a sheet.

Table 5: Content rules 

The full set of content rules, covering where inputs live, how they are sourced and labelled, and what should be kept out of a sheet.

Rule Description
Reference sources for inputs Evidence every input with a hyperlink to its source document, so any reference can be tracked down. This is documentation rather than a formula link.
Differentiate cell contents Clearly highlight and separate the inputs from the formulas, so a user can see at a glance which cells are theirs to change.
Sign convention Follow a consistent sign convention throughout the model, for example displaying deductions as negative rather than positive numbers.
Organisation of inputs Consolidate all inputs on an Inputs tab, so users reference them from a single point of origin.
Avoidance of cross-linking Avoid linking to other files. Include inputs from other files as hard-coded values, updated manually.
No external formula links
  • Under Data, then Edit Links, there should be no files shown, no external Excel files and no links to SharePoint.
  • Any input taken from another spreadsheet should be hard-coded, with backup to the source file retained.
Short text notes for each sheet Each section of each worksheet should carry a short note, under 20 words, briefly explaining what that section is designed to do.
Consistent styling
  • When making graphs and charts, keep the styling consistent with what is sent to clients in presentations and briefs.
  • The same font should be used for graphs and charts as elsewhere in the model.
Do not copy formatting across infinitely
  • Avoid copying formatting across a whole row or column, such as colouring cells beyond the range actually used.
  • Excel records a used range for every sheet, and blank formatted space counts towards it.
  • Copying cell colours from column A to column XFD, for instance, makes Excel treat the whole width as used and significantly increases file size.
Excess information in sheets Avoid unnecessary or irrelevant rows and columns, so a user can trace an output easily. Trace Dependents will show what is actually used.

Source: MCC Economics & Finance.

What are the formula rules?

A formula has two jobs: give the right answer, and let someone who did not build the model see why. The rules below serve the second.

Table 6: Formula rules

The full set of formula rules, covering how a calculation should be written so that someone who did not build the model can follow it and check it.

Rule Description
No hardcoding Never embed hard-coded numbers inside formulas. They are very difficult to spot for a user less familiar with the model.
Simplicity Avoid complicated formulas. Break a calculation into digestible steps, so others can follow it without untangling it.
Creating checks using formulas
  • Build checks throughout the model so its integrity can be reviewed quickly.
  • It is usually better to put checks at the foot of each sheet and consolidate them on a separate Checks tab.
  • This makes it easier to trace errors introduced while the model was being built.
Consistency in formulas Formulas should be consistent from left to right. If cell C5 is C3+C4, then D5 should be D3+D4, not D1+D2+D3+D4.
Avoid auto-updating cells
  • Avoid cells that recalculate whenever anything in the workbook changes, such as =NOW() or =TODAY(), as these slow the sheet down.
  • Where one is necessary, set calculation options to manual.
No daisy-chaining formulas
  • Daisy-chaining is where a cell feeds another, which feeds another, across sheets or far apart on a sheet, so no single cell can be understood without following the chain.
  • Keep the steps of a calculation stacked together in one visible block, so a reader sees the whole sequence at once.
  • This is the boundary of the simplicity rule above: breaking a calculation into steps is good practice, scattering those steps is not.
Avoid specific text in lookups Lookups should match on a reference number rather than on specific text where one is available. Keep reference lists on a single separate tab if needed.

Source: MCC Economics & Finance.

What do these rules add up to?

Models built this way are cheaper to audit, safer to update and more persuasive to the regulators, investors and boards who rely on them. The test behind every rule is the same: can someone who was not there when the model was built find where a number came from, follow it to the outputs and change an assumption safely? If not, the model depends on the memory of one person, and that person will leave.

Appendix A: what does a model map look like?

A model map shows every sheet in the workbook and how information moves between them, so a reader can see the architecture before opening a single sheet.

Figure 10: Model map from the CAA's H7 Price Control Model

The workbook's sheets grouped into guidance and control, inputs, calculations and outputs, with checks spanning all of them.

The model map from the CAA's H7 Price Control Model: every sheet in the workbook, grouped into guidance and control, inputs, calculations and outputs, reading left to right, with checks spanning all five columns. The outputs run across two columns.

Select a group heading or a sheet to see what it does.

CHECKS — span every stage

Source: Civil Aviation Authority, H7 Price Control Model (Excel workbook, approximately 20MB), Map sheet, redrawn from the model. Published on the CAA's H7 proposals and determination page. Contains public sector information licensed under the Open Government Licence v3.0.

References & Author

Author

 What’s next

Featured

This paper has been published on following other platforms

No items found.

I was delighted that MCC's work was completed on time, and within budget, helping us deliver important changes and improvements, to the benefit of our stakeholders. ​ MCC's report is published on the CCC website.

- Bea Natzler
Team Leader at Climate Change Committee, UK

I am delighted to recommend MCC Economics. Specifically, I worked closely with PJ, who helped us with our Nuclear and CCUS projects. PJ helped us develop new policies and answer questions from our stakeholders. ​​His support helped us deliver important changes and improvements, to the benefit of our stakeholders.

- Gordon Hutcheson
Head of Nuclear Policy at Ofgem, UK

MCC Economics has helped us better understand the most important issues for our stakeholders, including: charges, shareholder returns, debt payments and inflation impacts.

- Leila N. Nasr
Section Head at Department of Energy, Abu Dhabi

I am delighted to recommend PJ and his team at MCC Economics. We've been working together on National Policy Statements to help meet net zero targets for 2030 and 2050. We initially appointed MCC Economics to support us on offshore wind consultation analysis and have recently reappointed MCC Economics to undertake a larger consultation analysis role across all sectors, including hydrogen, CCUS and networks. I can confirm that PJ and his team have shown excellent spreadsheet skills, alongside very good project management, planning and analysis skills, helping us deliver important changes, and continuous improvements, to the benefit of our stakeholders.

- Amy McHugh
Head of Environment in the Energy Infrastructure Planning Policy, UK

I am delighted to recommend PJ and his team from MCC Economics. They helped us with our price controls for Heathrow airport and for NATS (En Route) plc (the air traffic services provider). Specifically, the MCC team helped us deliver important changes and improvements to our financial models and supporting policy documents, to the benefit of our stakeholders.

- Dan Rock
Head of Corporate Finance at CAA, UK

I am delighted to confirm that I worked with PJ on a retail project in 2015. The project helped stakeholders understand electricity costs and charges. Specifically, the project helped us explain to stakeholders, internally and externally, why electricity charges differed across the regions (GB, NI & Ireland). PJ was a key member on the project team, which helped deliver changes and improvements in the understanding of energy retail.

- Kevin Shiels
Director at Utility Regulator, Northern Ireland